This section describes the configuration requirements for each component.
For detailed setup and configuration procedures:
See “Setting up Mirror Replication Agent connectivity” to configure the Mirror Replication Agent connection parameters.
See “Setting up a new Mirror Activator system” to set up the primary and standby databases, Mirror Replication Agent, and Replication Server in a new Mirror Activator system.
Refer to the documentation provided by your disk replication system vendor (and/or device vendor) to set up and configure the disk replication system and mirror log devices.
Configure the primary database as follows:
Add the Mirror 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
Create and setup Replication Server objects (tables and procedures) in the primary database, with appropriate permissions granted to the Maintenance User name in the primary database
For Oracle only: Configure to enable supplemental logging
The disk replication system must be configured as follows:
Make sure it is ready to copy a snapshot image of all primary database data and log devices to the standby database data and log devices, if disk replication will be used to materialize the standby database for a new Mirror Activator system
Make sure it is ready to copy a snapshot image of all standby database data and log devices to the primary database devices, if disk replication will be used to materialize the primary database for failback
Make sure it is ready to begin synchronous replication of all primary log devices to the mirror log devices at the standby site
Configure the mirror log devices at the standby site as follows:
Make sure it is ready to receive synchronous replication (or mirroring) of the primary log devices from the disk replication system
Make sure that Mirror Replication Agent is allowed local, read-only access at the standby site during synchronous replication from primary log devices
Configure the Mirror Replication Agent instance as follows:
Make sure that the connection configuration is set correctly for network communications with the primary database, Replication Server, and RSSD
Initialize by using the pdb_init command to validate that the primary database is prepared for replication.
The pdb_init command will validate the primary database as well as setup the Replication Agent system objects in the primary to support procedure replication.
Initialize by using the ra_init command to set up the RASD
Make sure the paths are correctly defined for access to all mirror log devices
Configure the Replication Server as follows: Use the
Mirror Replication Agent user login name, with connect source and create object permission granted
Identify or create the Mirror 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
The following list describes the minimum standby database configuration required to participate in the Mirror Activator system:
All the data server options and configuration parameters exactly match those of the primary data server.
The database name, data and log device configuration, and all database options exactly match those of the primary database.
Maintenance User login name (as specified in the Replication Server create connection command) added to the standby database, with the required permissions granted.
Replication Server database objects (tables and procedures) created and set up in the standby database, with appropriate permissions granted to the Maintenance User name in the standby database.
For Oracle only: DDL user login name added to the standby database and granted permissions required to execute replicated DDL commands.
Materialization populates the standby database with all of the contents of the primary database, including the Maintenance User login name and Replication Server database objects (which are required in the primary database). If you use snapshot materialization for the standby database, its name, device configuration, and options must exactly match those of the primary database.
