Pin_monitor_balance Throws Error for Writeoff Reversal Events
(Doc ID 2936383.1)
Last updated on DECEMBER 26, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Symptoms
While running pin_monitor_balance, some of the events /event/billing/writeoff/tax_billinfo and /event/billing/writeoff_reversal are failing. One observes that the input for write fields is not constructed fully. PIN_FLD_SUB_BALANCES array is truncated in the input for write fields.
When performs a read object for the events which are failing, it also shows that the PIN_FLD_SUB_BAL_IMPACTS arrays are truncated in the robj output
For example, the event /event/billing/writeoff_reversal 336732048759853761 has 404 PIN_FLD_MONITOR_IMPACTS arrays and only 97 PIN_FLD_MONITOR_SUB_BAL_IMPACTS arrays, but the last array is truncated and it does not have PIN_FLD_SUB_BALANCES array in it.
While checking the BALANCES_LARGE CLOB in event_essentials_t table, the data is intact. However, while trying to read the object, the data is getting truncated.
See below error in connection manager (CM) pinlog and dm_oracle.pinlog:
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 |