My Oracle Support Banner

Pipeline crashes due to Overflow In Division (Doc ID 2072953.1)

Last updated on AUGUST 21, 2018

Applies to:

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

Symptoms

On all versions of Oracle Communications Billing and Revenue Management (BRM) up to 7.5.0.13, inclusive, the pipeline can crash due to a decimal overflow exception in certain discount configurations.  For example, in the trigger conditions there are Ebal()s used which are specific to the scenario.

Example stack trace:

----------------- lwp# 160 / thread# 160 --------------------
ffffffff774dce5c waitid (0, 1635, ffffffff247fe8d0, 3)
ffffffff774cb8e8 waitpid (1635, ffffffff247feb50, 0, 0, ffffffff68e61f00, 0)
+ 64
ffffffff774be648 system (ffffffff247fecf0, 1b08, 1800, 0, ffffffff7763e000,
ffffffff247febb8) + 394
ffffffff7ea1dd80 printExceptionReport (ffffffff7ea8aee8, 1af,
ffffffff7eb8b1c8, 0, 1ae, 1ad) + 1f8
ffffffff7ea1deb4 printStackTrace (0, 10055c988, 16d37c, ffffffff7eb8b1c8, 0,
1dc0dc03e0) + 6c
ffffffff7cd091bc
__1cDOMFVDiagnosticDataHandlerRgetDiagnosticData6MrknDBASGString_5bi_b_
(1002fe510, ffffffff7ce5fef0, ffffffff247ff478, 80, 1, ffffffff7ce51e48) +
37c
ffffffff7cd0a054
__1cDOMFVDiagnosticDataHandlerThandleCriticalError6M_rnLRWTValSlist4nDBASGStatus_nDstdJallocator4n0D______ (1002fe510, ffffffffffefd5f8, ffffffff247ff478,
ffffffff790103b0, 147e3c
, 102800) + 4c
ffffffff7b65895c __1cDLOGGPlugInOreceiveMessage6MrknDBASHMessage__v_
(1002fe090, ffffffff7b7cde40, 5b63f3d40, 1002fe510, 1559fbe40, 1002fe510) +
124
ffffffff7e582128 __1cDBASQRegisteredObjectIwriteLog6Mrkn0AGStatus__v_
(ffffffff7e76f088, 1559fbe40, 1b08, 5, 1ce504, ffffffff7b7ce498) + 38
ffffffff7e525bf8 __1cDBASGThreadPhandleException6Mrkn0AGString_4_v_
(1559fbec8, 1559fbe40, ffffffff247ff758, 1559fbe10, ffffffff247ff778,
1ae528690) + 420
ffffffff7e525558
__1cDBASGThreadUinvalidStateCallback6MrknKRWRunnable_nQRWExecutionState__v_
(1559fbec8, ffffffff247ffbd8, ffffffff247ff850, ffffffff7e7505f8, 173144,
124400) + bd8
ffffffff7e52ac78
__1cPRWTFunctor2MImp4CrknKRWRunnable_nQRWExecutionState_nDBASGThread_CvC2n0B__Drun6kM2n0B__v_ (1ae5208f0, ffffffff7e524980, 400, 1559fbec8, 1ae551400, 0) +
18
ffffffff78d2c87c
__1cWRWTMaskedCallbackList24nLRWMutexLock_CrknKRWRunnable_nQRWExecutionState__2f6M2n0C_L_v_ (1ae5513a0, ffffffff247ffbd8, ffffffff7e52ac60, 400, 108cf4,
400) + 88
ffffffff78d27ee4 __1cNRWRunnableImpQ_invokeCallbacks6MnQRWExecutionState__v_
(1a25bd550, 1, ffffffff247ffbd8, ffffffff790103b0, 10924c, 1ae4d7720) + 60
ffffffff78d2a960
__1cNRWRunnableImpZ_setExecutionStateNoGuard6MnQRWExecutionState__1_
(1a25bd550, 400, 0, 400, 10924c, 4) + 14
ffffffff78d273dc __1cNRWRunnableImpEexec6M_v_ (1a25bd550, 1a25bd550,
ffffffff247ffd88, ffffffff247ffd80, 1a25bd598, ffffffff247ffdc0) + 184
ffffffff78d4cb30 __1cLRWThreadImpEexec6M_v_ (1a25bd550, 1, ffffffff7764a300,
ffffffff247ffe98, ffffffff7764bf98, ffffffff54a9c800) + 20
ffffffff78d4cac4 RWThreadImp_entry (1a25bd550, 800000, 0, 0,
ffffffff78d4cac0, 1) + 4
ffffffff774d8afc _lwp_start (0, 0, 0, 0, 0, 0)

Cause

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
Symptoms
Cause
Solution
References


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