You must suspend transaction processing and replication activities before upgrading a replicated database.
Make sure that no users create subscriptions for data in the
database you are upgrading until the upgrade procedure is finished.
-
Before beginning the upgrade,
verify that subscriptions created by the create subscription command,
with primary data in the databases being upgraded, have reached
the “valid” state at the primary Replication Server. Use
the check subscription command to find the “valid” state.
-
Defer the upgrade process while the subscriptions are being
created so that Replication Server does not attempt to access the
database being upgraded.
-
Execute rs_helproute in
each Replication Server System Database (RSSD) being upgraded.
-
The status of all existing routes should be “Active.” If
any routes are not active, resolve them before continuing. See the
Replication Server documentation for help in diagnosing and fixing
the problem with the route, and then go on to the next step which is to shut down all applications that use the databases you are upgrading.
-
Shut down all applications
that use the databases you are upgrading.
-
Use the admin who command in
Replication Server to find the existing Data Server Interface (DSI)
connections to the data server being upgraded.
-
Suspend all DSI connections to the non-RSSD
databases you are upgrading by entering the following command in
Replication Server for each database:
1> suspend connection to dataserver.database
2> go
-
Leave the DSI connections to the RSSD databases
running.