Job Rerate Status Not Updated From 2 To 3 (Doc ID 852131.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 03-Dec-2013

Symptoms

While doing rerating with pin_rerate utility, job rerate status is not getting updated from 2 to 3.

After processing the rerate jobs, status set to 2 (WAITING_STATUS_ACCOUNT_LOCKED). Then tried to process the queue events (pin_rerate -process queue). Here the status is not getting changed to 3 (ACCOUNT_LOCKED) in job_rerate_t table and events are not processed.

 

Steps To Reproduce:

1) Started both realtime pipeline and batch pipeline.

2) Created rerate job:
     $PIN_HOME/apps/pin_rerate> pin_rerate -t 01/01/2008 -a 1099551

3) Rerate job is created in job_rerate_t with status 1 (NEW).

4) Processed rerate jobs:
     $PIN_HOME/apps/pin_rerate> pin_rerate -process jobs

5) Rerate job status set to 2 (WAITING_STATUS_ACCOUNT_LOCKED) and queue event created in ifw_sync.

6) Received the acknowledgement and event created in ack_queue_t.

7) Process the queue:
     $PIN_HOME/apps/pin_rerate > pin_rerate -process queue

8) Once this is done, rerate job status has to be set to 3 (ACCOUNT_LOCKED).
     But the status is not changed and no errors in any log files (cm.pinlog, pin_rerate.pinlog, dm_ifw_sync.pinlog, pipeline logs).


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