Updates (re-initializes) the log device repository in the RASD.
ra_updatedevices
When ra_updatedevices is invoked, Mirror Replication Agent does the following:
Deletes all of the data in its log device repository
Queries the primary database for information about all of its log devices
Re-populates the log device repository in the RASD with current information about primary database log devices returned by the primary database
If any log device is added, dropped, extended, or moved at the primary database, you must:
Stop replication (using quiesce or suspend) to put the Mirror Replication Agent instance in Admin state
Invoke ra_updatedevices to update the log device repository in the RASD
See “Updating the log device repository” for more information.
The primary database need not be quiesced when you update
the log device repository.
If the primary data server writes to a new (or altered) log device before you update the log device repository, the Mirror Replication Agent instance will stop replication processing and go to Admin state.
Sybase recommends that you coordinate all log device changes at the primary database with updating the Mirror Replication Agent log device repository.
Because Mirror Replication Agent re-creates the entire log device repository when you invoke ra_updatedevices, any log device path that you modified previously (using ra_devicepath) is overwritten with the current log device information from the primary database.
If you need to alter the “default” path
for a log device (that is, the log device path returned by the primary
database), you must use the ra_devicepath command after you
invoke ra_updatedevices.
Each log device path can be altered by the ra_devicepath command, to “re-map” the current path recorded in the RASD to point to the corresponding mirror log device at the standby site. Mirror Replication Agent uses the log device paths recorded in its RASD to find the mirror log devices, from which it reads the primary database transaction log.
The ra_updatedevices command is valid only when the Mirror Replication Agent instance is in Admin state.
