After you have switched to the new active database, you must decide what to do with the old active database. You can:
Bring the database online as the new standby database and resume the connection so that Replication Server can apply new transactions, or
Drop the database connection using the drop connection command, and add it again later as the new standby database. If you drop the database, any queued messages for the database are deleted. Refer to Chapter 3, “Replication Server Commands,” in the Replication Server Reference Manual for more information about drop connection command.
If the old active database is undamaged, you can bring it back online as the new standby database by entering:
resume connection to data_server.database
where data_server.database is the physical database name of the old active database.
You may need to resolve paper-trail transactions in the database in order to avoid duplicate transactions. Depending on your applications, you may need to do this before you bring the old active database back online as the new standby database.
Because paper-trail transactions must be re-executed in the new active database, you must prepare the new standby database so that it can receive the transactions again when they are delivered through the replication system.
To resolve the conflicts, you can:
Undo or reverse the duplicate transactions in the new standby database, or
Ignore the duplicate transactions and deal with them later.
