PCM_OP_READ_OBJ Not Working Properly With Certain Flags In BRM 7.2.1 (Doc ID 604032.1)

Last updated on SEPTEMBER 16, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.1.0.0 to 7.2.1.0.0 [Release 7.2.1]
Information in this document applies to any platform.
***Checked for relevance on 14-May-2013***
*** Checked for relevance on 02-27-2015 ***


Symptoms

When in an open READWRITE transaction, if an object is read and cached with  flag PCM_OPFLG_CACHEABLE (0x0400), the latest revision is retrieved;  if an earlier revision of the same object is read subsequently with flag PCM_OPFLG_USE_POID_NEAREST (0x8000),  the exact revision or the nearest should be returned. However the cached (latest) revision is retrieved in 7.2.1 Portal Server.

Steps to Reproduce Problem

1. Create an object which has auditable flag set for a field.  For example,  object /payinfo/dd and field PIN_FIELD_STATE as auditable.  Update this object several times.
2. In testnap run 'xop PCM_OP_TRANS_OPEN PCM_TRANS_OPEN_READWRITE 1'
3. Run robj with flag PCM_OPFLG_CACHEABLE  (0x0400)
4. Run robj with flag PCM_OPFLG_USE_POID_NEAREST (0x8000) and a specific revision

Example :

1. Input Flist (matt.dat)

0 PIN_FLD_POID POID [0] 0.0.0.1 /payinfo/dd 3471980377 2

Note the revision number is 2.

2. nap(25121)> r matt.dat 1

nap(25121)> xop PCM_OP_TRANS_OPEN PCM_TRANS_OPEN_READWRITE 1
xop: opcode 12, flags 0
# number of field entries allocated 20, used 1
0 PIN_FLD_POID POID [0] 0.0.0.1 /payinfo/dd 3471980377 2


3.  Read object with flag PCM_OPFLG_CACHEABLE:

nap(25121)> xop PCM_OP_READ_OBJ 0x400 1
xop: opcode 3, flags 1024
# number of field entries allocated 20, used 14
0 PIN_FLD_POID POID [0] 0.0.0.1 /payinfo/dd 3471980377 6
...


Revision 6 has been returned (the latest revision).

4. Read object with PCM_OPFLG_USE_POID_NEAREST

nap(25121)> xop PCM_OP_READ_OBJ 0x8000 1
xop: opcode 3, flags 32768
# number of field entries allocated 20, used 14
0 PIN_FLD_POID POID [0] 0.0.0.1 /payinfo/dd 3471980377 6
...

Revision 6 is returned again!  Here revision 2 should be returned.

nap(25121)> xop PCM_OP_TRANS_ABORT 0 1
xop: opcode 13, flags 0
# number of field entries allocated 20, used 1
0 PIN_FLD_POID POID [0] 0.0.0.1 /payinfo/dd 3471980377 2

 

Changes

 

Cause

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