Problem While Calling PCM_OP_PYMT_COLLECT After Upgrade from 6.7FP1 to 7.3.1 (Doc ID 806902.1)

Last updated on JULY 19, 2012

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.1 [Release 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 19-Jul-2012***


Symptoms

-- Problem Statement:
Upgraded to 7.3.1 from 6.7 FP1, getting below error in dm_oracle while call PCM_OP_PYMT_COLLECT.

E Wed Apr 08 12:30:42 2009 <machine1> dm:742 dm_subr.c(116):2204
1:api1:UnknownProgramName:0:http-8080-Processor39:100895:1239165736:0
ORACLE error: do_sql_insert: PINStmtExecute: code 1, op 0
=ORA-00001: unique constraint (PIN2.I_ITEM_NO__ID) violated
"insert into item_t ( poid_DB, poid_ID0, poid_TYPE, poid_REV, name, status, closed_t,effective_t, opened_t, due_t, account_obj_DB, account_obj_ID0, account_obj_TYPE, account_obj_REV,item_no, gl_segment, currency, disputed, recvd, adjusted, transfered, writeoff, bal_grp_obj_DB,bal_grp_obj_ID0, bal_grp_obj_TYPE, bal_grp_obj_REV, billinfo_obj_DB, billinfo_obj_ID0,
billinfo_obj_TYPE, billinfo_obj_REV, ar_billinfo_obj_DB, ar_billinfo_obj_ID0,
ar_billinfo_obj_TYPE, ar_billinfo_obj_REV, created_t, mod_t, read_access, write_access,archive_status, ar_bill_obj_DB, ar_bill_obj_ID0, ar_bill_obj_TYPE, ar_bill_obj_REV, bill_obj_DB,bill_obj_ID0, bill_obj_TYPE, bill_obj_REV, currency_operator, currency_rate, currency_secondary,
delta_due, due, event_poid_list, item_total, service_obj_DB, service_obj_ID0, service_obj_TYPE,service_obj_REV ) values ( :poid_DB, :poid_ID0, :poid_TYPE, :poid_REV, :name, :status, :closed_t,:effective_t, :opened_t, :due_t, :account_obj_DB, :account_obj_ID0, :account_obj_TYPE,:account_obj_REV, :item_no, :gl_segment, :currency, :disputed, :recvd, :adjusted, :transfered,
:writeoff, :bal_grp_obj_DB, :bal_grp_obj_ID0, :bal_grp_obj_TYPE, :bal_grp_obj_REV,:billinfo_obj_DB, :billinfo_obj_ID0, :billinfo_obj_TYPE, :billinfo_obj_REV, :ar_billinfo_obj_DB,:ar_billinfo_obj_ID0, :ar_billinfo_obj_TYPE, :ar_billinfo_obj_REV, :created_t, :mod_t,
:read_access, :write_access, :archive_status, :ar_bill_obj_DB, :ar_bill_obj_ID0,:ar_bill_obj_TYPE, :ar_bill_obj_REV, :bill_obj_DB, :bill_obj_ID0, :bill_obj_TYPE, :bill_obj_REV,:currency_operator, :currency_rate, :currency_secondary, :delta_due, :due, :event_poid_list,
:item_total, :service_obj_DB, :service_obj_ID0, :service_obj_TYPE, :service_obj_REV )"
E Wed Apr 08 12:30:42 2009 jar-radius dm:742 dm_do_ops.c(73):2026
1:api1:UnknownProgramName:0:http-8080-Processor39:100895:1239165736:0
ERROR do_create_create sql_insert err=1(PIN_ERR_NO_MEM)

Additional information from the production data dump listed below:
.
select max(to_number(substr(item_no,4,10))) from item_t where poid_type like
'/item/payment%'; --->196157
.
select header_num from data_t where name like
'%PIN_SEQUENCE_TYPE_PAYMENT%';--> 196149
---------

As you can see from above, the header_num (sequence) is less than max item_no.

-- Steps To Reproduce:
1. Take a data dump from production when it is up and running.
2. Do a upgrade.
3. call PCM_OP_PYMT_COLLECT





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