Siebel Remote and Replication Manager Administration Guide > Administering Siebel Remote > Administering the Remote Client >

Refreshing the Local Database of a Remote Client


Occasionally, it might be necessary for you to refresh the local database for a remote client. For example, if a system preference parameter on the Siebel Server changes, then a refresh or reextract is necessary to make sure the new settings to take effect. For more information, see Process of Configuring System Preferences for the Siebel Server.

To refresh the local database of a remote client

  1. If transactions are ready for loading to the remote client, then inform the user to synchronize.
  2. Make sure Transaction Merger successfully applied transactions to the server database.

    To determine when transactions from a particular remote client are processed, you can do any of the following:

    • To determine if Transaction Merger successfully applied transactions for the remote client, use the Server Manager or the Siebel Client Status screen.
    • Inspect the inbox directory of the remote client on the Siebel Server. There must not be any files that contain the .dx extension in the inbox directory.
  3. Run Database Extract for the remote client.

    Make sure the Save Transactions parameter is TRUE.

    For more information, see Extracting the Server Database.

  4. Notify the user to reinitialize the local database on the remote client.

    For more information, see Initializing the Local Database.

Siebel Remote and Replication Manager Administration Guide Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.