Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts > Siebel Remote Data Store Components >

Siebel Database Server

The database server stores data for users, with both stationary and Mobile Web Clients.

The database server contains:

• Siebel applications metadata
• Siebel applications tables that store user data
• A master transaction log table that stores changes made since the last database extraction, provided that the changes are accomplished using Siebel software. Direct SQL modification of Siebel tables is not supported. SQL changes that are executed outside the Siebel application are not recorded in the Master Transaction Log and therefore will not be routed to mobile clients.

The Transaction Processor and Transaction Router components of Siebel Remote, which run on the Siebel Remote server, route the transactions from the master transaction log to the outbox directories of Mobile Web Clients. The Transaction Processor purges rows from the log after transactions from S_DOCK_TXN_LOG have been written into DX files in the txnproc directory. Do not directly modify the contents or structure of the master transaction log under any conditions.

CAUTION:  In a Microsoft SQL Server or DB2 environment, truncation of the S_DOCK_TXN_LOG table in a Server Database causes the txn_id values assigned to new transactions to be reset. However, the corresponding txn_id values in the S_DOCK_STATUS table are not reset. Consequently, new transactions inserted into the S_DOCK_TXN_LOG table will have a txn_id mismatch as compared to the values in the S_DOCK_STATUS table. The Transaction Processor will not process these transactions and will purge them from the S_DOCK_TXN_LOG table.

If the S_DOCK_TXN_LOG table is truncated, then all Mobile Web Clients must be reextracted and all existing transactions and local databases must be deleted before the these clients can be reinitialized. The re-extraction process resets the txn_id values in the S_DOCK_STATUS table, so that the values correspond with txn_id values in the S_DOCK_TXN_LOG table. The deletion of transactions and local databases is necessary to prevent mismatch errors between new S_DOC_STATUS txn_id values and older txn_id values in the local databases.

CAUTION:  After the installation of the Siebel database server, if your Siebel implementation uses both Siebel Remote and Oracle RAC, then you must disable the cache for sequence S_DCK_TXN_LOG_S for each instance of Oracle RAC. If this instruction is not followed, transaction ID gaps can result, causing Siebel Remote failures. For more information about this requirement, see Siebel Installation Guide for the operating system you are using.