Account Remains Locked Even After Comprehensive Rerating Process Is Completed

(Doc ID 1207243.1)

Last updated on JANUARY 29, 2011

Applies to:

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


In a comprehensive rerating scenario, the account remains locked even after rerating is done and the job status is updated to -1.

Steps to reproduce:

Before we begin, ensure to setup the system for comprehensive rerating.
  1. create a /gsm/telephony product, with a cycle forward event and delayed session event
  2. create an account with above product
  3. processed a cdr , this is rated fine
  4. move ahead couple of days (pin_virtual_time)
  5. now run comprehensive rerating with the below steps :
  6. pin_rerate -a <account_poid> -t <dd/mm/yyyy>
  7. pin_rerate -process jobs 
  8. pin_rerate -process queue
  9. rate a CDR, it gives below error in stream log . This is as expected :
        " This Account is currently being Rerated, edr is rejected." .
  10. pin_rerate -rerate
  11. rate a CDR again, it gives error in stream log :
        " This Account is currently being Rerated, edr is rejected.".

    Note: This is the problem. It is expected that the CDR is rated fine.
  12. pin_rerate -process queue
  13. pin_rerate -process recycle
  14. check the /job/rerate status and it is -1, as expected
  15. rate a CDR again, it gives same error in stream log. It is expected that the account is unlocked and CDR is rated fine.
Note: If we do not rate a CDR in step 9, and just do rerating in straight steps, then no issue, i.e., if no events arrive until the rerating process is completed, then the account will be unlocked just fine.


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