This section describes general configuration requirements, by component, for all Mirror Activator systems, including both new Mirror Activator systems, and warm standby applications converted to Mirror Activator 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 system” to set up the primary and standby databases, Mirror Replication Agent, and Replication Server in a new Mirror Activator system
See “Converting a warm standby application to a Mirror Activator system” to set up the primary database, Mirror Replication Agent, and Replication Server in an existing Replication Server warm standby application that you are converting to a 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
The primary database must be configured as follows:
Mirror Replication Agent user login name added to the primary data server and primary database, with the Replication role granted
Maintenance User login name (as specified in the Replication Server create connection command) added to the primary data server, with the Replication role granted
Maintenance User login name added to the primary database
Replication Server objects (tables and procedures) created and set up in the primary database, with appropriate permissions granted to the Maintenance User name in the primary database
Initialized to mark the entire database for replication (and to set the secondary truncation point, if the primary database was not previously configured for a warm standby application)
RepAgent thread stopped and disabled in the primary database (if the primary database was previously configured for a warm standby application)
See “Converting a warm standby application to a Mirror Activator system” for more information.
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 (to materialize the standby database for a new Mirror Activator system)
If you are converting a warm standby application to
a Mirror Activator system, you need not materialize the standby database.
Ready to copy a snapshot image of all primary log devices to the mirror log devices at the standby site
Ready to copy a snapshot image of all standby database data and log devices to the primary database devices (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 ra_init command to set up the RASD
Paths correctly defined for access to all mirror log devices
The Replication Server must be configured as follows:
Mirror Replication Agent user login name, with connect source permission granted
Logical (warm standby) connection defined for the primary and standby databases
Database connections defined for the primary and standby databases (as the active and standby for the logical connection)
If you are converting a warm standby application to a Mirror Activator system, you need not change the standby database configuration.
The following list describes the minimum standby database configuration required to participate in the Mirror Activator 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 data server, with the Replication role granted
Maintenance User login name added to the standby database
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
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). When you use snapshot materialization for the standby database, its name, device configuration, and options must exactly match those of the primary database.
