Salesforce

How to run two sets of databases on different Windows cluster nodes using conmgr.properties files

« Go Back

Information

 
TitleHow to run two sets of databases on different Windows cluster nodes using conmgr.properties files
URL Name000039110
Article Number000163470
EnvironmentProduct: OpenEdge
Version: 10.2B05 or later, 11.x
OS: Windows 2008 R2
Question/Problem Description
How to run one database (or set of databases) on one Windows cluster node and another database (or set of databases) on another Windows 2008 R2 cluster node at the same time while using database startup parameters defined from 2 different %DLC%\properties\conmgr.properties files? (one on each cluster node)
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
First ensure that OpenEdge is installed locally on each cluster node in the same directory structure and have the same service pack level installed. 
 
Then the files %DLC%\properties\conmgr.properties need to be configured so that they contain all the databases that need to be able to run on both clusters (this can be done using OpenEdge explorer on http:\\localhost:9090)
 
To be able to run one database (or set of databases) on one Windows cluster node and another database (or set of databases) on another Windows cluster node at the same time it is necessary to create 2 'Services and applications' entries in the Windows 2008 R2 cluster manager. To do so first create a new 'OpenEdgeDatabase' Services and applications entry containing the first databases resources 
 
The command to use to register a database as a cluster resource in 'OpenEdgeDatabase' is:
set PSC_CLUSTER_PATH=%DLC% 
procluster <dbname> enable -pf <dbname>.pf 
(executed as local Windows Administrator in a PROENV command prompt window)
 
with the file <dbname>.pf containing for example:
 
-cluster protected 
-properties %DLC%\properties\conmgr.properties 
-servergroup <db configuration name>.defaultconfiguration.defaultservergroup 
-adminport <port> 
-m5 
 
Concerning <db>.defaultconfiguration.defaultservergroup, the <db> is not the physical name of the database, but the "Logical name" of the database object specified in the file conmgr.properties
 
In this way, the adminserver is not cluster aware and only serves to configure the databases, and the databases can be used on both nodes of the cluster. 
 
After having configured all the databases for the first set of databases change the 'OpenEdgeDatabase' name to another name for example databasesForNode1
 
Then create a new 'OpenEdgeDatabase' Services and applications containing the second set of databases ressources 
 
The command to use to register a database as a cluster resource in 'OpenEdgeDatabase' is then still:
 
set PSC_CLUSTER_PATH=%DLC%    
(if nor already set)
procluster <dbname> enable -pf <dbname>.pf 
(executed as local Windows Administrator in a proenv command prompt window)
 
After having configured all the databases for the second set of databases change the 'OpenEdgeDatabase' name to another name for example databasesForNode2
 
databasesForNode1 and databasesForNode2 need to use different ISCSI discs it is not possible for the databases of databasesForNode1 and databasesForNode2 to share the same ISCSI disk.
 
When other database ressources need to be added to either databasesForNode1 or databasesForNode2 you can either rename one of them temporarily to 'OpenEdgeDatabase' and use the command 'procluster <dbname> enable -pf <dbname>.pf' again, or add the new database ressources manually by using the existing database ressources as a template.
 
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:36 AM

Powered by