1. Remote and Replication Manager Administration Guide
  2. Requirements for Extracting the Server Database

Requirements for Extracting the Server Database

Perform or review all of the items that this topic describes before you extract the server database, as described in Extracting the Server Database. If you do not do this, then it might be necessary for you to reextract the server database for all users, which can be a time consuming and tedious task.

Do all the following tasks before you extract the server database:

  • Make sure the same conflict resolution rule is in effect for the local databases and for the server databases to maintain integrity across databases. You can specify the rule as part of the initial Siebel Remote implementation on your server database before you run a database extract for any client so that Siebel Remote copies the rule consistently to all remote clients.

  • Set the Intersection Table Conflict Resolution field before you extract any remote client. If you modify this field after extraction, then you must reextract all remote clients. If you do not reextract all clients, then server data and client data might diverge.

  • Set the Intersection Table Merge Rule field before you extract any remote client. If you modify this field after extraction, then you must reextract all clients. If you modify this field after extraction, and if you do not reextract all clients, then server data and client data might diverge.

  • Make sure you test time filtering thoroughly before you use it in a production environment. Make sure the cutoff dates you choose for time filtering allow the necessary data to reach the test remote clients. Deploying an incorrect cutoff date can prevent stable but necessary data from reaching the remote client. Price lists or rate lists are examples of this data. If you must choose an earlier cutoff date after you deploy Siebel Remote to a production environment, then it might be necessary for you to reextract all remote clients.

  • If you modify the server database schema after you deploy Siebel Remote to a production environment, then you must run the Generate New Database server component and reextract all remote clients, or you must use a Siebel Anywhere kit to distribute this modification to all remote clients. It is strongly recommended that you do this even if this modification only affects a private dock object because individual tables in a private dock object might become visible to a remote client at a later time. Problems might occur if the server database structure does not match the local database structure.

  • Define all positions and routing models before you deploy Siebel Remote to a production environment. If you must modify the Position for a user or a routing model, then you must reextract the server database to the remote client so that Siebel Remote deletes the records that it must not display to the user, according to the modified position. This configuration also improves Transaction Router performance because a reporting hierarchy reorganization for your company creates many transactions on the Siebel Server, and these transactions might cause a backlog.

  • Set the routing group before you deploy Siebel Remote to a production environment. If you modify the routing group from Standard to Full Copy after deployment, then you must reextract all remote clients that are associated with the regional node.

  • You must not rename or delete any DX files that exist in the siebsrvr\docking\client\inbox folder. If you rename or delete these files, then you will lose the transactions and you must reextract the remote client.

  • When the Enable Incremental Indexing system preference is set to True, the Transaction Processor component (alias TxnProc) runs automatically. The TxnProc component has the status Running and the MobileSync component group has the status Online. In this case, you must stop TxnProc before you run the Database Extract component (alias DbXtract) for the first time. After DbXtract has completed, then you can restart TxnProc.

    Caution: If you do not stop TxnProc before running DbXtract for the first time, then some transactions might not be routed to remote clients. For more information about using the Enable Incremental Indexing system preference, see Siebel Search Administration Guide and Siebel Marketing Installation and Administration Guide.