Updating the RASD

The RASD is normally 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.

Once the data in the RASD is created by initializing the Replication Agent instance, the only way to update the RASD is to re-initialize the instance using the pbd_xlog command with the init and force keywords.

Before you re-initialize the Replication Agent, the primary database must be quiesced. The following procedure includes quiescing.

To update the RASD

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 continue with step 4.

If the Replication Agent is in Replicating state:

Use the following command to quiesce the Replication Agent instance:
```
quiesce
```
Use the following command to verify that the Replication Agent is in Admin state:
```
ra_status
```

Before you re-initialize the RASD, you must quiesce the primary database, or otherwise prevent any DDL operations that can change the database objects or schema.

Log in to the primary data server, using a user login that has appropriate permissions or authority, and then quiesce the primary database (or execute the commands necessary to prevent any DDL operations that change the database objects or schema).

Use the following command to re-initialize the Replication Agent and force it to update its RASD:

pdb_xlog init, force

The pbd_xlog init, force command does not overwrite any marking information or configurations. It also 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, pbd_xlog init, force overwrites the RASD record for that log device or redo log with the information returned by the primary data server.

After the Replication Agent is initialized, you must release the quiesce hold on the primary database to restore normal client access to the database. Use one of the following methods to do this:

Log in to the primary data server, using a user login that has appropriate permissions or authority, and then release the quiesce hold on the primary database (or execute the commands necessary to restore normal client access to the database).

Use the following command to resume replication in the Replication Agent:

resume

Use the following command to 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.