Rebuild Queues from Offline Database Logs

You can recover data from off-line database logs.

You use the rebuild queues command only after you have restarted the Replication Server in standalone mode. Executing rebuild queues in standalone mode puts Replication Server in recovery mode.

In recovery mode, the Replication Server allows only RepAgents in recovery mode to connect. If a RepAgent that is not in recovery mode attempts to connect, Replication Server rejects it with following error message:

Rep Agent not in recovery mode

If you use a script that automatically restarts RepAgent and connects it to the Replication Server, you must start RepAgent using the for_recovery option. RepAgents are not allowed to connect in normal mode.

This figure illustrates the progression from normal mode to standalone mode to recovery mode using the rebuild queues command.

Enter Recovery Mode with the Rebuild Queues Command
Figure 7-2 illustrates the progression from normal mode to standalone mode to recovery mode with the rebuild queues command. As shown in the figure, from the normal mode, the dash M flag is use to restart the Replication Server in standalone mode. To enter the recovery mode, rebuild queues command is used. This also shows RepAgent attempt to connect to the Replication Server in recovery mode.

Figure 7-2 illustrates the progression from normal mode to standalone mode to recovery mode with the rebuild queues command. As shown in the figure, from the normal mode, the dash M flag is use to restart the Replication Server in standalone mode. To enter the recovery mode, rebuild queues command is used. This also shows RepAgent attempt to connect to the Replication Server in recovery mode.

Replication Server Standalone Mode
Standalone mode allows you to review the contents of the stable queues because no messages are being written to or read from the queues.

Parent topic: Rebuild Stable Queues

Related concepts

Replication Server Standalone Mode