Bookshelf Home | Contents | Index | PDF |
Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts > Siebel Remote Data Store Components > Siebel Database ServerThe database server stores data for users, with both stationary and Mobile Web 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. 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. |
Siebel Remote and Replication Manager Administration Guide |