Upgrade Guide for DB2 UDB for z/OS > Preparing Application Data for Upgrade >

Preparing Mobile User Data for the Database Upgrade

Upgrades: All upgrades.

Environments: All environments.

This topic applies primarily to developers running the Mobile Web Client in the development environment and to end users in the production environment. This topic applies to the production test environment only if it has Mobile Web Client users.

This topic is part of an upgrade process. See How to Perform the Upgrade.

After synchronizing, mobile users must make no further changes to their local databases until the upgrade has been completed. Any changes made during the upgrade are lost when they are reinitialized following the upgrade.

Complete the following steps before beginning the upgrade of either a development environment or a production environment.

To prepare mobile users for the database upgrade

1. Perform a partial synchronization for mobile users, sending all transactions to the Siebel Database Server.
2. Verify that Mobile Web Clients have synchronized and that all changes have been merged into the Siebel Database Server as follows:
   1. Check that no transaction files remain in the synchronization inbox and outbox for any mobile user. The synchronization inbox for each user is on the Siebel Server:

      Windows: SIEBEL_ROOT\docking\MOBILEUSERNAME.

      UNIX: $SIEBEL_ROOT/docking/MOBILEUSERNAME.

      Transaction files are in the format number.dx; for example, 00000023.dx.

   2. Log onto a Siebel Business application, such as Call Center, as the Siebel administrator. Use the Server Administration - Server Tasks screen to make sure that each Transaction Merger task has successfully completed.
   3. Verify that Workflow Monitor and Workflow Action agents have processed all pending requests. If Workflow Manager has completed successfully, the S_ESCL_REQ table should not have any rows.
3. To prevent synchronization of Mobile Web Clients with the Siebel Database Server, stop or disable all Siebel Remote components on all Siebel Servers, as described in Siebel Remote and Replication Manager Administration Guide and in Siebel System Administration Guide.
4. Disconnect all Web Clients from the Siebel Server by stopping the appropriate Application Object Managers, as described in Siebel System Administration Guide.
5. Upgrades from Release 7.5.x and earlier. Make sure that Dedicated Web Clients have disconnected from the Siebel Database Server.

   The method you use to do this depends on your database. For example, with an IBM RDBMS, you would stop the primary listener. However, all RDBMS types require starting the database in restricted mode. Refer to the documentation that you received from your RDBMS vendor for more information.