To add databases, you must create connections in the Replication Server for the primary and standby databases. You should also create database replication definitions and replication subscriptions in Replication Server.
You must have “sa” permission in the
Replication Server to perform these procedures.
To create database connections in Replication
Server
For ASE: Use the Replication Server utility rs_init to add connections to Replication Server. The utility rs_init does not support non-ASE databases.
For Oracle and Microsoft SQL Server: Use the following procedure to create Oracle database connections.
Log in to the Replication Server with a user login that has “sa” permission.
Create a database connection for the primary database. For example, for an Oracle primary database, use the following:
create connection to pds.pdb set error class oracle_error_class set function string class rs_oracle_function_class set username "ma_maint" set password "ma_maint_pwd" with log transfer on, dsi_suspended
For a Microsoft SQL Server primary database, use the following:
create connection to pds.pdb set error class rs_sqlserver_error_class set function string class rs_sqlserver_function_class set username "ma_maint" set password "ma_maint_pwd" with log transfer on, dsi_suspended
Where:
pds is the name of the primary data server.
pdb is the name of the primary database.
ma_maint is the Maintenance User login for the primary database.
ma_maint_pwd is the password for the Maintenance User.
For an Oracle primary database, the pds and pdb values
are usually the server host name and Oracle SID, respectively.
If the oracle_error_class does not exist in your Replication Server, you can create it using the following scripts from the Mirror Replication Agent installation:
Apply script $SYBASE/MA-15_1/scripts/oracle /oracle_create_error_class_1_rs.sql to Replication Server
Apply script $SYBASE/MA-15_1 /scripts/oracle /oracle_create_error_class_2_rssd.sql to the RSSD
Apply script $SYBASE/MA-15_1 /scripts/oracle /oracle_create_error_class_3_rs.sql to Replication Server
Also apply the following additional script from the
Mirror Replication Agent installation to your Replication Server,
after editing the script to include your primary database connection
name:
$SYBASE/MA-15_1/scripts/oracle /oracle_create_rs_sequence_repdef.sql
Create a database connection for the standby database. For example, for an Oracle standby database, use the following:
create connection to sds.sdb set error class oracle_error_class set function string class rs_oracle_function_class set username "ma_maint" set password "ma_maint_pwd"
For a Microsoft SQL Server standby database, use the following:
create connection to sds.sdb set error class rs_sqlserver_error_class set function string class rs_sqlserver_function_class set username "ma_maint" set password "ma_maint_pwd"
Where:
sds is the name of the standby data server.
sdb is the name of the standby database.
ma_maint is the Maintenance User login for the standby database.
ma_maint_pwd is the password for the Maintenance User.
If the oracle_error_class does
not exist in your Replication Server, you can create it using the
following scripts from the Mirror Replication Agent installation:
Apply script $SYBASE/MA-15_1 /scripts/oracle /oracle_create_error_class_1_rs.sql to Replication Server
Apply script $SYBASE/MA-15_1 /scripts/oracle /oracle_create_error_class_2_rssd.sql to the RSSD
Apply script $SYBASE/MA-15_1 /scripts/oracle /oracle_create_error_class_3_rs.sql to Replication Server
To create database replication definitions in
Replication Server
Replication Server requires a Database Replication Definition to identify the database objects that are to be replicated from the primary database.
Log in to the Replication Server with a user login that has “sa” permission.
Create a database replication subscription for the primary database:
create database replication definition pds_repdef with primary at pds.pdb replicate DDL go
where:
pds is the name of the primary data server.
pdb is the name of the primary database.
To create database replication subscriptions in
Replication Server
A Database Subscription identifies the standby database that will receive the replicated transactions.
Log in to the Replication Server with a user login that has “sa” permission.
Create a database replication definition for the standby database:
create subscription pds_sub for database replication definition pds_repdef with primary at pds.pdb with replicate at sds.sdb without materialization go
Where:
pds is the name of the primary data server.
pdb is the name of the primary database.
sds is the name of the standby data server.
sdb is the name of the standby database.
Replication Server requires a unique function replication
definition to support Oracle sequence replication.