The RASD is usually updated automatically during normal
replication activity. The following procedure to force an update
of the RASD should only be used with the recommendation of Sybase
Technical Support when the RASD is suspected of being corrupt.
To update the RASD
Log in to the Replication Agent instance with the administrator login.
Use the following command to determine the state of the Replication Agent instance:
ra_status
If the Replication Agent is in Admin state, skip this step and go to step 4.
If the Replication Agent is in Replicating state:
Use the following command to suspend replication by the Replication Agent instance:
suspend
Use the following command to verify that the Replication Agent is in Admin state:
ra_status
Use the following command to re-initialize the Replication Agent and force it to update its RASD:
pdb_xlog init, force
The pdb_xlog init, force command
does not overwrite any marking information
or configurations. Also, it does not overwrite
any existing path information to the log device (or redo log in
Oracle) in the RASD, if all of the following log information in
the RASD matches that returned by the primary data server.The following
log information pertains only to Oracle:
Redo group number
Redo name
Redo path
For each log device or redo log identified in the RASD, if any item in the preceding list does not match the information returned by the primary data server, pdb_xlog init, force overwrites the RASD record for that log device or redo log with the information returned by the primary data server.
Resume replication in the Replication Agent:
resume
Verify that the Replication Agent is in Replicating state:
ra_status
If the Replication Agent does not return to Replicating state, see Chapter 4, “Troubleshooting Sybase Replication Agent,” for more information.
