A guaranteed synchronization state between the replication source and target databases lets you perform critical administrative actions on databases and can help expedite replication processes, such as transition, that require synchronization.

Administrative actions that require replication synchronization include:
  • Using a replication target database as a clone of a production database
  • Running read-only reporting clients on a replication target database without concern for inconsistent data
To ensure synchronization:
  1. Make sure that:
    • The replication source database and replication server are running.
    • All of the configured targets are available and connected to the source.
    • The replication agent process on the target is available.
  2. On the replication source database, issue a PROSHUT command with the following syntax:
    proshut -shutdownTimeout db-name -replSync

    The system default timeout is ten minutes. Use the optional -shutdownTimeout parameter to specify a timeout value that allows active users to finish. If the synchronization does not complete in time, the operation prompts you to either extend the time limit or force shutdown, which may cause inconsistent data or synchronization failure.

For example, this command shuts down sourcedb in 40 minutes:
proshut -shutdownTimeout 40m sourcedb -replSync

If the command completes successfully, it returns messages like the following:

BROKER  0: (20258) Database broker has verified that all written AI locations were sent to replication target databases.
RPLS    1: (10436) The source database source and the target database /largedisk/lopez/REPLSETUP_1TARG/Target/target on host localhost are synchronized.
RPLS    1: (20257) Replication server has verified that all connected replication target databases are synchronized with the replication source database.

For more information, see PROSHUT command.