Bookshelf Home | Contents | Index | PDF |
Siebel Deployment Planning Guide > Application-Level Deployment Planning > Planning Batch Processing When Using Siebel RemoteLong-running batch jobs can create transaction gaps in the Master Transaction Log for the Siebel Remote module for Oracle's Siebel Business Applications. 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 more information to help you to understand gaps in the Master Transaction Log, see 477585.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Technical Note 499. For an example with Siebel Assignment Manager, gaps in the Master Transaction Log can occur as follows:
Conditions That Can Cause Missed TransactionsThe following conditions in Assignment Manager can cause increased commit times. Longer commit times increase the risk that the Transaction Processor wait-time expires before the commit occurs and that Transaction Processor fails to process all of the transactions in the transaction log. Increasing the Assignment Manager Batch Commit ParameterThe default batch commit size (BatchSize) for Assignment Manager is 100. After processing 100 rows, transactions are committed to the database. If the batch commit size is increased, then this increases the risk of exceeding the wait-time. Increased Number of Batch Assignment ThreadsWhen multiple Assignment Manager threads are logging transactions, this creates a latency in accessing the transaction log table. This latency increase the risk of exceeding the wait-time. Complicated Assignment RulesWhen Assignment Manager has to resolve complicated assignment rules, this can increase commit times. Longer commit time together with the preceding conditions can increase the risk of exceeding the wait-time. Avoiding Missed TransactionsTo avoid exceeding the Transaction Processor wait-time during batch processing, adopt the following best practice recommendations. Experiment with applying them in combination to achieve the best performance while minimizing the risk of exceeding the wait-time. Monitor the Transaction Processor LogsAs you apply the best practices techniques described as follows, use the Transaction Processor logs to see the result and help you to optimize system performance. Transaction Processor writes these warning messages to its log file when it skips transactions: GenericLog: GenericError: 0003-11-18 17:04:51 WARNING: A transaction gap has been detected after transaction 122. Probable Cause: There maybe long-running transactions in your system which are not committing transactions within the specified duration (600 sec) Recommendation: Reduce the batch size of your transactions. This will allow the transactions to be committed to the database within the wait-time window. If skipped transactions occur while a batch job is running, then investigate the cause. The skipped transactions might not have been routed to mobile users. If so, then the mobile users might have to re-extract the database. Set a Lower BatchSize for Assignment ManagerSetting a lower BatchSize value reduces the number of records processed before each commit. Reducing this figure reduces the commit times and the risk of exceeding the wait-time. If your performance goals require you to increase the BatchSize parameter, then do so only after analyzing the number of Assignment Manager threads that you have under average and peak workloads. The fewer Assignment Manager threads, the higher that you can set the BatchSize parameter. You can get performance statistics on threads by raising the Assignment Manager log level. For information about raising the log level, see Siebel System Monitoring and Diagnostics Guide. Serialize Batch JobsConsider staggering the start time of batch jobs. Running batch jobs in staggered or serial order can reduce the risk of exceeding the wait time. |
Siebel Deployment Planning Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |