Siebel Remote and Replication Manager Administration Guide > Extracting and Initializing a Remote Database > Options for Extracting the Server Database >

Extracting a Database for Use with Siebel Tools


This topic describes requirements that you must meet if you extract a database that you use with Siebel Tools.

Requirement to Maintain a Single Database for Siebel Tools and the Remote Client

If you use Siebel Tools to access the local database, then Siebel Tools does not automatically connect to the server database when you use the remote client. You must maintain only one local database for use with Siebel Tools and with the remote client. This configuration is necessary to make sure the user can use the remote client to view any modification that you make in Siebel Tools. You must make sure you connect Siebel Tools and the remote client to the same local database.

For more information, see the Siebel Installation Guide for the operating system you are using and Using Siebel Tools.

Requirement to Use the Standard Routing Model When Using Siebel Tools

If you use Siebel Tools with an extracted database, then you must use the Standard Routing Model. You cannot use the Selective Retrieval routing model in this situation.

Strings That Siebel Remote Does Not Send to the Local Database

Siebel Remote does not send some strings to the local database. These strings reside in the S_MSG table. For example, some workflow processes include steps that use the Error Code property. When Siebel Remote extracts the server database for a local developer, it does not correctly route the records in the S_MSG table that the Error Code property uses.

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