Converting a warm standby application to a Mirror Activator system

This section describes the setup and configuration tasks that are required to convert an existing Replication Server warm standby application to a Mirror Activator system.

If you are setting up a new Mirror Activator system (that is, using a primary database that was not previously configured for a warm standby application), see the Mirror Activator Administration Guide, Chapter 2, “Setting up and Configuring Mirror Replication Agent,” for complete setup and configuration tasks.

Table 3-2 provides a checklist of the tasks required to configure software components and set up the Mirror Activator system for replication when you convert an existing warm standby application to a Mirror Activator system.

The checklist in Table 3-2 assumes the following:

NoteIf the Replication Server and primary and standby databases were not previously configured for a Replication Server warm standby application, do not use the task checklist in Table 3-2. Instead, you must use the setup and configuration tasks described in “Setting up a new Mirror Activator system,” in Chapter 2 of the Mirror Activator Administration Guide.

When converting an existing warm standby application to a Mirror Activator system, you must perform all of the tasks in Table 3-2 in the order they are shown. If you deviate from this sequence, the results may be unpredictable, and you may have to back out of the entire process and start over.

Table 3-2: Tasks for converting a warm standby application to a Replication Server—Heterogeneous Replication Options system

Task

Description

1

Materialize the mirror log devices, and set up the disk replication system for synchronous replication to the mirror log devices.

2

Set up the Mirror Replication Agent configuration parameters for the Replication Server connection.

3

Stop and disable the Mirror Replication Agent thread in the primary database.

NoteYou must preserve the secondary truncation point when you disable the Mirror Replication Agent thread.

4

Initialize the primary database using the Mirror Replication Agent pdb_init command.

NoteAfter the primary database is initialized, you must not allow any DDL operations before it is quiesced in step 5.

5

Quiesce the primary database.

6

Initialize the Mirror Replication Agent using the ra_init command, and set the paths to the mirror log devices.

7

Resume update activity in the primary database after Mirror Replication Agent initialization is complete.

8

Resume the Mirror Replication Agent to put it in Replicating state.

The following sections contain detailed procedures for each setup and configuration task.