Filter
Top Products
APPENDIX B Upgrading Servers with Replicated Databases
Installation Guide 131
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 to step 3.
3 Shut down all applications that use the databases you are upgrading.
4Use the
admin who command in Replication Server to find the existing
Data Server Interface (DSI) connections to the data server being upgraded.
5 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
6 Leave the DSI connections to the RSSD databases running.
Draining the transaction logs for primary databases
For each primary database you are upgrading, ensure that Replication Server
completely processes the pre-upgrade log.
To drain the transaction logs:
1 Wait for all remaining transactions to be replicated.
2 Run the following Replication Server command:
1> admin who, sqm
2> go
3 Find the entry that corresponds to the inbound queue for this database by
looking for the Info field for the queue_number:queue_type entry. For an
inbound queue, the queue type is 1. Note the Last Seg.Block entry for the
queue.
4 Open a queue dump file by executing the following Replication Server
command:
1> sysadmin dump_file, "file_name"
2> go
where file_name is the name of the file to which you will dump the queue.