Replication Agent Configuration Requirements

Observe these requirements when configuring Replication Agent.

Primary Database

Configure the primary database:
  • Add the Replication Agent user login name to the primary database, and grant the user appropriate permission to be able to perform tasks necessary to support replication.

  • Add the Maintenance User login name (as specified in the Replication Server create connection command) to the primary database.

  • (Oracle only): Enable supplemental logging.

Replication Agent

Configure the Replication Agent instance:
  • Make sure that the connection configuration is set correctly for network communications with the primary database, Replication Server, and RSSD.

  • (Microsoft SQL Server) Initialize each primary database server. Also, configure the database to allow a remote TCP/IP connection and to allow a remote DAC connection.

  • Use the ra_admin init command to initialize Replication Agent. This command validates that the primary database is prepared for replication, sets up Replication Agent system objects in the primary database, and initializes the RASD (Oracle and Microsoft SQL Server only).

Replication Server

Configure the Replication Server:
  • Use the Replication Agent user login name, with connect source and create object permission granted.

  • Identify or create the Replication Agent user login name for the RSSD.

  • Define the database replication definition and subscription for the primary and standby database.

  • Apply the heterogeneous datatype support scripts at the RSSD.

  • (Oracle) If Replication Server is version 15.0 or earlier, apply the scripts distributed with Replication Agent to correctly define the Oracle error class.

RSSD

If the Replication Server version is 15.2 or later and you have already created a connection using the Replication Server create connection command with the using profile clause, your RSSD objects have already been loaded by the connection profile, and you can skip these instructions. If your Replication Server is version 15.0 or earlier, correctly define the Oracle error class in both Replication Server and the RSSD:
  • At Replication Server, execute the $SYBASE/RAX-15_5/scripts/oracle/oracle_create_error_class_1_rs.sql script.

  • At the RSSD database, execute the $SYBASE/RAX-15_5/scripts/oracle/oracle_create_error_class_2_rssd.sql script.

  • At Replication Server, execute the $SYBASE/RAX-15_5/scripts/oracle/oracle_create_error_class_3_rs.sql script.

Multiple Replication Agents

In a Replication Server Multi-Path Replication™ scenario, multiple Replication Agent for Oracle instances are grouped together and share common system resources to coordinate in a Multi-Path Replication solution:
  • Every Replication Agent for Oracle instance in a Replication Agent group must have the same value set for the ra_admin_owner and ra_admin_prefix parameters.
  • Each Replication Agent for Oracle instance in a Replication Agent group must have a unique value set for the ra_admin_instance_prefix parameter. This parameter is used to distinguish Replication Agent for Oracle instances within a group.

To avoid DDL synchronization errors with multiple Replication Agents, use the all, marked, and unmarked keywords with the pdb_setrepddl command.

See the Replication Agent Reference Manual and Replication Agent Primary Database Guide for details about these parameters and command keywords.