My Oracle Support Banner

Core In Pipeline During Business Event Processing (Doc ID 1548965.1)

Last updated on MARCH 22, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.


Pipeline produces core while processing business events in multi threading in DAT_listerner setup

Attempt to exit due to signal caught: SIGBUS


This above message occurred when pipeline generated core.

Our DAT_Listener settings are as follows:
EnableInterLeavingStatistics = False

ProcessAllEvents = False

InterleavingReqd = True

MaxNumEvents = 10000 # suggested min. value 900
MinNumEvents = 1000 # suggested min. value 300
CheckInterval = 120 # suggested min. value 60 [sec]
MaxEventProcessTime = 120 # suggested min. value 60 [sec]
MaxCDRProcessTime = 3600 # suggested min. value 300 [sec]
 when pipeline switched to process business event from IFW_SYNC table it generated core and business event processing stopped.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.