My Oracle Support Banner

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

Last updated on FEBRUARY 25, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.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:

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.