Incorrect DAT_Listener Behavior
(Doc ID 1549297.1)
Last updated on APRIL 11, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.4.0]
Information in this document applies to any platform.
Listener's interleaving is not working as expected because of an inconsistent gv$aq state and some known database performance issue in querying gv$aq before 11g.
We have the below DAT_Listener settings:
With the above mentioned configuration, it is expected to dequeue when number of events is 100000 in queue or when pipeline rating has been continuously running for 20mins.
But we have observed that Business Event processing is getting started at every 5-6 mins interval. And during this time we don't have enough messages in Sync table (i.e. 100000 enqueued messages are not present in sync table), so as per the expected behavior, pipeline should not trigger business event processing. What could be the reason that pipeline is triggering business event processing even when it's not meeting any of the conditions required for start of business event processing.
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