This section describes general configuration requirements, for each component, for systems.
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 for Oracle system” to set up the primary and standby databases, Mirror Replication Agent, and Replication Server in a new Mirror Activator for Oracle 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.
The primary database must be configured as follows:
Mirror Replication Agent user login name added to the primary database, and the user must be granted appropriate permission to be able to perform task necessary to support replication. This user must also have read access to the mirrored redo log device
Maintenance User login name (as specified in the Replication Server create connection command) added to the primary database
Maintenance User login name added to the primary database
Configure to archive the log with automatic log archiving disabled
Configure to enable supplemental logging
The disk replication system must be configured as follows:
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 for Oracle system
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
Ready to begin synchronous replication of all primary log devices to the mirror log devices at the standby site
The mirror log devices at the standby site must be configured as follows:
Ready to receive a snapshot image from the disk replication system to materialize the mirror log devices from the primary database log devices
Ready to receive synchronous replication (or mirroring) of the primary log devices from the disk replication system
Mirror Replication Agent allowed local, read-only access at the standby site during synchronous replication from primary log devices
The Mirror Replication Agent instance must be configured as follows:
Connection configuration set correctly for network communications with the primary database, Replication Server, and RSSD
Initialized using the pdb_init command to validate the primary database is prepared for replication.
Initialized using the ra_init command to set up the RASD
Paths correctly defined for access to all mirror log devices
The pdb_init command will validate the primary database as well as setup the Replication System Agent Object table in the primary to support procedure replication.
The Replication Server must be configured as follows:
Mirror Replication Agent user login name, with connect source permission granted
Mirror Replication Agent user login name for the RSSD identified or created.
Database Replication Definition and Subscription defined for the primary and standby database.
The Heterogeneous Datatype Support Scripts must be applied.
The following list describes the minimum standby database configuration required to participate in the Mirror Activator for Oracle system:
All 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.
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.
