This section shows an example of an RCM configuration file set up to support multiple databases in a warm standby environment. In a multiple database environment, an Adaptive Server contains more than one database involved in warm standby replication.
An Adaptive Server can contain several databases that are each being replicated to the standby Adaptive Server. When the active Adaptive Server fails, each database connection must be switched to the standby Adaptive Server.
Following are the results for each failover mode:
switch active – each database connection in the LOGICAL_CONNECTION parameter is switched to the standby Adaptive Server.
quiesce – by default all database queues in Replication Server are emptied before the database connections are switched to the standby Adaptive Server.
none – multiple databases are treated the same way as a single database—you are notified of the failure.
The section highlighted in bold is the only difference between this example and the previous example for switch active mode with a single logical database. See “switch active” for comparison.
# Open Switch Server OPENSWITCH = ws_os COORD_USER = os_coord COORD_PASSWORD = os_coord_pwd # Replication Server REP_SERVER = ws_rs RS_USER = sa #RS_PASSWORD - Replication Server password is blank # Active and Standby ASE Servers ACTIVE_ASE = BookServer ACTIVE_USER = sa #ACTIVE_PASSWORD - ACTIVE ASE password is blank STANDBY_ASE = StandbyBook STANDBY_USER = stndby_sa STANDBY_PASSWORD = booknut # On failover switch the flow of replication RS_FAILOVER_MODE = SWITCH # Identify the databases in the warm-standby environment LOGICAL_CONN = LDS.pubs3, LDS.sales, LDS.signings #DATABASES - Omitted, so RCM will use pubs3, sales, signings # The loss of the signings database will not trigger a failover REQUIRED_DBS = pubs3, sales APP_POOL = Application # Wait 5 minutes before starting the failover FAILOVER_WAIT = 300 # Provide Replication Server 2 minutes perform the switch active MONITOR_WAIT = 120
If you use this example configuration file in your environment and the active Adaptive Server fails, the RCM takes the same action as in the switch active mode example (see “switch active”), but switches all logical connections listed in the LOGICAL_CONN parameter. That is, the RCM switches the logical connections named “LDS.pubs3,” “LDS.sales,” and “LDS.signings” in the Replication Server (one connection for each database). Then the RCM starts a Replication Agent in the standby Adaptive Server for each of the pubs3, sales, and signings databases. The DATABASES parameter is omitted, so that the RCM uses the database names identified in the LOGICAL_CONN parameter when starting the Replication Agents on the standby Adaptive Server. In this example, the REQUIRED_DBS parameter does not include the signings database; therefore, a failure in that database does not trigger the failover process.
