Not Possible To Create Rerate Job By Pin_rerate (Doc ID 1168177.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

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

Symptoms

When trying to create new rerate job by using pin_rerate, it finished with error "Account poid is not valid", as reported in the pin_rerate.pinlog fragment below:

...
D Tue Jul 27 19:12:56 2010 milton pin_rerate:7514 pin_rerate.c:3118 1:milton:pin_rerate:7514:1:7:1280250776:5
pin_rerate account validation input flist
# number of field entries allocated 20, used 1
0 PIN_FLD_POID POID [0] 0.0.0.1 /account -1137647319 0
D Tue Jul 27 19:12:56 2010 milton pin_rerate:7514 pin_rerate.c:3121 1:milton:pin_rerate:7514:1:4:1280250776:6
pin_rerate account validation return flist
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] 0.0.0.1 /account -1137647319 0
0 PIN_FLD_ERR_BUF ERR [0]
<location=PIN_ERRLOC_DM:4 class=UNKNOWN:0 errno=PIN_ERR_NOT_FOUND:3>
<field num=0:0,0 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>
E Tue Jul 27 19:12:56 2010 milton pin_rerate:7514 pin_rerate.c:3132 1:milton:pin_rerate:7514:1:4:1280250776:6
Account poid is not valid
...


At the end of attached log file pin_rerate.pinlog.gz you can find that supplied input account poid was converted to some dummy number (-1137647319) and that is probably the reason why message "Account poid is not valid" was raised.

Investigation shows that pin_rerate is not able to accept longer number as input account (-a) poid parameter (probably only int32 number can be supplied).

Supplied input parameters to pin_rerate were:
pin_rerate –reason 55 –t 07/24/2010 –a 3157319977


Steps to reproduce:
1. Find in database account with poid_id0 > 3000000000.
2. Create rerate job for this account by using pin_rerate
Pin_rerate –reason 55 –t <……..> -a 3100000000

Currently there is more than 1 million of accounts on production environment with poid_id0 longer than 3000000000.

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