Siebel Remote and Replication Manager Administration Guide > About Siebel Remote >

Other Considerations for Design and Development

This topic describes some of the other items that you can consider that this chapter does not describe elsewhere.

Modification of the S_DOCK_TXN_LOG Table

The Transaction Processor and the Transaction Router server components run on the Siebel Server and routes transactions from the master transaction log to the outbox directory on the remote client. The Transaction Processor purges rows from the log after Siebel Remote writes transactions from the S_DOCK_TXN_LOG table to DX files in the txnproc directory.

CAUTION:  Do not directly modify the contents or structure of the master transaction log under any circumstances.

In a Microsoft SQL Server or DB2 environment, truncation of the S_DOCK_TXN_LOG table in a server database causes Siebel Remote to reset the txn_id values that are assigned to new transactions. Siebel Remote does not reset the corresponding txn_id values in the S_DOCK_STATUS table. In this situation, new transactions that Siebel Remote inserts in the S_DOCK_TXN_LOG table contain a txn_id mismatch when compared to the values in the S_DOCK_STATUS table. The Transaction Processor does not process these transactions. It purges them from the S_DOCK_TXN_LOG table.

If Siebel Remote truncates the S_DOCK_TXN_LOG table, then you must reextract all remote clients and delete all existing transactions and local databases before you reinitialize these clients. The reextraction 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. Deleting transactions and local databases is necessary to prevent mismatch errors between new S_DOC_STATUS txn_id values and older txn_id values that exist in the local databases.

Modification of a Siebel Table Directly Through SQL

Siebel CRM does not support modifying a Siebel table directly through SQL. Siebel CRM does not record SQL changes in the Master Transaction Log (S_DOCK_TXN_LOG) for SQL changes that run outside of the Siebel application. Siebel Remote does not route them to the remote client.

Support for Oracle Real Application Clusters with Siebel Remote

Siebel Remote does not support usage of Active Oracle Real Application Clusters (Oracle RAC) because Oracle RAC requires the sequence cache to be disabled. Disabling the sequence cache causes Oracle RAC to not scale properly.

Getting Help from Oracle

If you require help from Oracle you can create a service request (SR) on My Oracle Support. Alternatively, you can phone Global Customer Support directly to create a service request or get a status update on your current SR. Support phone numbers are listed on My Oracle Support. You can also contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.