Upgrade Guide for Microsoft Windows > Preupgrade Tasks > Preparing a Database for Upgrade >

Preparing Mobile and Dedicated Users for the Upgrade

Complete the following actions before beginning the upgrade of either a development environment or a production environment:

  1. Perform a partial synchronization for mobile users, sending all transactions to the server database.

    CAUTION:  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.

  2. Verify that Mobile Clients have synchronized and that all changes have been merged into the server database:
    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.

      Microsoft Windows inboxes are at SIEBEL_ROOT\siebsrvr\docking\MOBILEUSERNAME.

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

    2. Log onto a Siebel eBusiness 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 Clients with the 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 Server Administration Guide.
  4. Disconnect all Web Clients from the Siebel Server by stopping the appropriate Application Object Managers, as described in Siebel Server Administration Guide.
  5. 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 Oracle 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.


 Upgrade Guide for Microsoft Windows
 Published: 20 October 2003