Last updated on JANUARY 05, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
On BRM 7.5PS4, Collections Opcode
Getting coredumps while passing missing POID values in Collections opcode PCM_OP_COLLECTIONS_GROUP_GET_BILLINFO input flist.
This is the order of events:
1) 6 tables were truncated at 10:03 in Production environment.
2) Nobody realized that this happened and system continued to work and new orders were processed and new accounts (including records in /billinfo, /service, etc.) were created.
3) After several hours was realized that something is not OK with BRM and it was shut down (let's say at 13:30)
4) DB was restored as it was at 9:57 (so a few minutes before the disaster). This is a consistent image and everything is perfect at BRM DB level
5) BRM is restarted and new requests come from external systems (FMW/AIA). But some of these commands refer to objects that were created in step 2. However, those objects do not exist anymore in DB because it was restored so everything that was created in step 2 does not exist. The problem is that other systems (AIA XREF tables which link Siebel IDs to BRM ones) are not aware about the facts that those objects do not exist anymore because they were created after the restore point and were lost when DB was restored.
coredump got generated when collections opcode is called for objects that do not exist or with a NULL POID_ID.
The issue is that instead of core, just an error should have been raised.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms