Billing Transaction RollBack Is Causing Bill Tables Corruption
Last updated on JULY 28, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 and later
Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 184.108.40.206.0 version,
On BRM -ECE implementation, If EM Gateway is crashed in the middle of pin_bill_day execution, the transaction rollback issued by billing opcode is causing corruption on BRM tables.
In /account class, in the NEXT_ITEM_POID_LIST field, an item that did not exist is referenced.
In /billinfo class, the fields LAST_BILL_T, NEXT_BILL_T and FUTURE_BILL_T updated with erroneous dates .
The original value of LAST_BILL_T, NEXT_BILL_T and FUTURE_BILL_T should be same.
The issue can be reproduced at will with the following steps:
1) Create an account
2) Running Billing for the account, in the middle of billing, abruptly close connection with emGateway (for testing purpose, may be by manually killing the process)
3) The LAST_BILL_T, NEXT_BILL_T and FUTURE_BILL_T for billinfo_t were changed but not generated the bill, then the original value of LAST_BILL_T, NEXT_BILL_T and FUTURE_BILL_T is also lost.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms