You can replicate Adaptive Server logins from one master database to another. The master database replication is limited to DDL, and the system commands used to manage logins and roles. Master database replication does not replicate data from system tables, nor replicate data or procedures from any other user tables in the master database.
Both the source Adaptive Server and the target Adaptive Server must be the same hardware architecture type (32-bit versions and 64-bit versions are compatible), and the same operating system (different versions are also compatible).
Do not initialize the active and standby databases with a load from another master database. To synchronize the syslogins, suids and roles at each master, use bcp to refresh the appropriate tables or manually synchronize the IDs and roles prior to setting up your replication.
For a list of supported DDL and system procedures that apply to the master database, see “Restrictions and requirements when using sp_reptostandby” and “Supported DDL commands and system procedures”.
Replication Server versions 12.0 and later support master database replication in a warm standby environment, and in an MSA environment in Replication Server 12.6 and later. The primary or active Adaptive Server must be version 15.0 ESD #2 or later.
See “Replicating the master database in an MSA environment” in Replication Server Administration Guide Volume 1 for information about master database replication in an MSA environment.
Setting up master database replication in a warm
standby environment
Set up the active master database and the standby master database in the Replication Server as warm standby pair. Do not “initialize the standby with dump and load” nor “use the dump marker to start replicating to standby”. To synchronize the syslogins and suids at each master, use bcp or manually synchronize the IDs.
See “Setting up ASE warm standby databases” for more information on setting up a warm standby environment.
Mark the master database on both the active and the standby database to send system procedures:
sp_reptostandby master, ‘all’
Stop the RepAgent on the active master database:
sp_stop_rep_agent master
Configure the Replication Agents on both the active and the standby databases to send warm standby transactions:
sp_config_rep_agent master, ‘send warm standby xacts’, ‘true’
Restart the RepAgent on the active master database:
sp_start_rep_agent master
Resume the DSI connections to both the active and the standby master databases on the Replication Server:
resume connection to active_ds.master go resume connection to standby_ds.master go
Verify the status of warm standby:
admin logical_status
