Collection Job is Failing in The Secondary Schema (Doc ID 1340947.1)

Last updated on SEPTEMBER 02, 2016

Applies to:

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

Symptoms

pin_collect job is failing in the scendary schema.

Steps followed:
1)  Enable Revenue Assurance by setting "- pin_mta enable_ara 1" in pin_billd/pin.conf
2)  Execute 'perl pin_multidb.pl -R all' from primary schema and restart cm
3)  Create CC (Credit Card) account in secondary database on Jun/01
4)  Move pvt (pin_virtual_time) to Jul/01 and execute 'pin_bill_accts -verbose'
5)  Verify bill gets generated
6)  Move pvt to Jul/04 and executed pin_collect from pin_billd directory
pin_collect -verbose -active -pay_type 10003 -start 1000 -vendor fusa

Following error observed in cm.pinlog:

D Tue Mar 27 14:07:24 2012 brmslap2 cm:23158 fm_act_find.c:1066 1:brmslap2:pin_collect:23157:1:0:1309019261:0
error doing /uniqueness lookup
<location=PIN_ERRLOC_DM:4 class=PIN_ERRCLASS_SYSTEM_DETERMINATE:1 errno=PIN_ERR_STORAGE:43>
<field num=PIN_FLD_POID:7,16 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>
D Tue Mar 27 14:07:24 2012 brmslap2 cm:23158 fm_act_find.c:1180 1:brmslap2:pin_collect:23157:1:0:1309019261:0
retrying /uniqueness lookup at primary db

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