1. Deployment Planning Guide
  2. Planning Batch Processing When Using Siebel Remote

Planning Batch Processing When Using Siebel Remote

Long-running batch jobs can create transaction gaps in the Master Transaction Log for the Siebel Remote module for Oracle’s Siebel CRM. If the wait-time for the missing transactions expires, then the Transaction Processor component skips the missing transactions. The skipped transactions are not routed to mobile users.

Batch jobs could be performed by Siebel Assignment Manager, Siebel EIM, or other components.

For an example with Siebel Assignment Manager, gaps in the Master Transaction Log can occur as follows:

  1. Assignment Manager is processing a batch of transactions.

  2. Assignment Manager obtains a group of transaction IDs. These are issued in numeric, sequential order.

  3. Assignment Manager then commits these transactions. This process takes several minutes.

  4. In the meantime, another process obtains a transaction ID.

  5. The process commits the transaction and writes it to Siebel Remote’s Master Transaction Log. A sequence gap is created because the Assignment Manager transactions have not yet been written to the Master Transaction Log.

  6. Transaction Processor detects the gap and waits a specified period called the wait-time (default is 600 seconds).

  7. The wait-time expires before Assignment Manager completes the commit operation and writes the missing transactions to the Master Transaction Log.

  8. When the wait-time expires, Transaction Processor skips the missing transactions and moves on to the transaction from the other process.

  9. Transaction Processor logs information about the missing transactions. The Assignment Manager transactions are not routed to mobile users, even though they are later written to the Master Transaction log.

This topic contains the following information: