Siebel Remote 7.x and 8.x Transaction Gaps and Data Routing
(Doc ID 477585.1)
Last updated on FEBRUARY 01, 2022
Applies to:Siebel Remote - Version 7.0.4  to 8.1  [Release V7 to V8]
Information in this document applies to any platform.
Area(s):Assignment Manager / Territory Assignment, EIM / Enterprise Integration Manager, Remote/Replication/Anywhere
Release(s):V6 (Siebel 2000-Enterprise), V7 (Enterprise), V6 (Siebel 2000-MidMarket), V7 (MidMarket)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:transaction, gap pause, _gap_pause_, bulk, data, missing, transactions, detect, BatchSize
This document was previously published as Siebel Technical Note 499.
During normal Siebel application operations, transaction gaps are created in the Siebel Remote transaction queue. If the gap lasts longer than the wait period, the transaction represented by the gap will be skipped over and transactions will not be routed to respective mobile clients on the application server. This technical note discusses transaction gaps, their causes, and recommendations on how to minimize impact on a Siebel Remote deployment.
This document is informational and intended for any user.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document