Suspending Replication and Transaction Activity in the Database

Suspend replication and transaction activity in the database. Replication activity includes creating and dropping both routes and subscriptions.

1. Verify that the subscriptions you have created with primary data in the databases being upgraded, have reached a “valid” state at the primary Replication Server.
   Do not upgrade while the subscriptions are being created.
   Make sure no users create subscriptions for the data in the database you are upgrading until the upgrade procedure is finished.
2. Run rs_helproute in each RSSD being upgraded to determine its status.
   The status of all routes should be “Active.” See Replication Server Administration Guide Volume 1 > Managing Routes to resolve route problems.
3. Shut down the applications that are using the databases you are upgrading.
4. Use the admin who command in Replication Server to identify the existing Data Server Interface (DSI) connections to the data server being upgraded.
5. Suspend all DSI connections to databases you are upgrading. For each database, issue:

   suspend connection to dataserver.database