My Oracle Support Banner

After Partitioning The Database Some Bill, Item and Events Objects Are Not Visible Anymore (Doc ID 1078583.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

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


After upgrading from non-partitioned to partitioned database some bill, items and event objects created before partitioning update are not visible to BRM anymore although they exist in DB.

This sounds like the same issue mentioned in <> .

--Steps to Reproduce:
1) Install the 7.3.1_PartitionUpg_linux_32_opt.bin.
2) Run the required steps to partition event, item and bill objects.
3) Verify partitions have been created.
4) Read all items for an existing account using the following search flist.

0 PIN_FLD_RESULTS ARRAY [0] allocated 1, used 1
0 PIN_FLD_POID POID [0] /search/pin -1 0
0 PIN_FLD_ARGS ARRAY [1] allocated 1, used 1
1 PIN_FLD_ACCOUNT_OBJ POID [0] /account 2159123 0
0 PIN_FLD_TEMPLATE STR [0] " select X from /item where F1 = V1 order by created_t "

5) Verify output flist is
nap(23316)> search 1
# number of field entries allocated 20, used 1
0 PIN_FLD_POID POID [0] /search/pin -1 0
nap(23316)> q

The user has manually verified the items exist is the DB. This sounds close to the issue mentioned in <> . The patch with fix for that bug does not exist for Linux(Redhat).

--Recent Changes:
upgraded to partitioned DB

--The Expected Result:
Items and bills can be found the normal way (e.g. tesnap ).

--The Actual Result:
Items and bills cant be found.


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.