You can replicate Adaptive Server logins from one master database to another. 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, or 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).
For a list of supported DDL and system procedures that apply to the master database, see “Restrictions and requirements when using sp_reptostandby” on page 66 and “Supported DDL commands and system procedures” on page 66 in the Replication Server Administration Guide Volume 2.
Replication Server versions 12.0 and later support master database replication with warm standby, and with MSA in Replication Server 12.6 and later. The primary or active Adaptive Server must be version 15.0 ESD #2 and later.
See “Replicating the master database in a warm standby environment for ASE” on page 91 in the Replication Server Administration Guide Volume 2 for information about master database replication in a warm standby environment.
Setting up a master database replication in an MSA environment
User rs_init to set up the primary and replicate master databases.
Use bcp or manually synchronize syslogins and suids at each master database. Do not use dump and load to materialize the replicate master database.
Mark the primary master database:
sp_reptostandby master, ‘all’
Stop the RepAgent on the primary master database:
sp_stop_rep_agent master
Configure the replication primary master database to send warm standby transactions:
sp_config_rep_agent master,‘send warm standby xacts’,‘true’
Restart the RepAgent on the primary master database:
sp_start_rep_agent master
Create a database replication definition to replicate the system procedures:
create database replication definition master_dbrep with primary at PDS.master replicate system procedures
Create a database subscription for each subscribing master database; do not materialize the data:
create subscription master_dbsub1 for database replication definition master_dbrep with primary at PDS.master with replicate at RDS.master without materialization