Updating the log device repository

Mirror Replication Agent stores information about primary log devices in its RASD when you initialize the Mirror Replication Agent instance. Log device information in the RASD is referred to as the log device repository.

Unlike other information in the RASD, you can update the log device repository at any time using the ra_updatedevices command.

If any log device is added, dropped, extended, or moved at the primary database, the Mirror Replication Agent log device repository must be updated.

Sybase recommends that you coordinate all log device changes at the primary database with updating the Mirror Replication Agent log device repository.

When you update the log device repository, Mirror Replication Agent does the following:

Deletes the entire log device repository in the RASD

Queries the primary database for information about all of the log devices

Re-populates its log device repository in the RASD with current information about the log devices

If the path for a log device at the primary site is different from the path for the corresponding mirror log device at the standby site, you must use ra_devicepath to modify the path returned by the primary database and recorded in the RASD.

When you invoke ra_updatedevices, any log device path that you modified previously with ra_devicepath is overwritten with the current path specified in the primary database.

The primary database need not be quiesced when you update the Mirror Replication Agent log device repository.

To update the log device repository

Use the following command to determine the state of the Mirror Replication Agent instance:

ra_status

If the Mirror Replication Agent is in Admin state, skip this step and continue with step 4.

If the Mirror Replication Agent is in Replicating state:

Use the following command to quiesce the Mirror Replication Agent instance:
```
quiesce
```
If the log device changes at the primary database are urgent, you can use suspend, instead of quiesce, to stop replication in the Mirror Replication Agent immediately.
Use the following command to verify that the Mirror Replication Agent is in Admin state:
```
ra_status
```

If you coordinate log device changes at the primary database with updating the Mirror Replication Agent log device repository, make the log device changes at the primary database after the Mirror Replication Agent is in Admin state.

After you verify that the Mirror Replication Agent is in Admin state, use the following command to update the log device repository in the RASD:

ra_updatedevices

If you need to modify the default path for a log device (that is, the device path returned by the primary data server), use ra_devicepath.

Use the following command to change a default log device path:

ra_devicepath device, dev_path

where:

device is the device name or device ID.
dev_path is the path that the Mirror Replication Agent must use to connect to the mirror primary database log device at the standby site.

You must invoke ra_devicepath once for each mirror log device whose path you need to modify.

Use the following command to start replication in the Mirror Replication Agent instance:

resume

You can update the log device repository as often as necessary to accommodate log device changes at the primary database.