Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 220.127.116.11.0
Checked for relevance on 27-Nov-2011
-- Problem Statement:
During realtime rerating, if a job failed during rerating, pin_rerate will create another rerating job automatically, its start time is not set to the same value as the original job but to the system time. So, the two job are using different event for rerating.
Pin_rerate should not create the new job automatically,because event the new job is exactly same as
the old one, it is possible that the new job failed again. Thus it will cause to create another job.
pin_rerate should not create the new job automaticaly. New job should get created with staus 1 and the PIN_FLD_START_T TSTAMP in /job_batch/rerate should be from billing cycle start date.
Steps To Reproduce:
The issue can be reproduced at the following steps:
1. Create one GSM account using the OOB "Standard GSM" plan.
2. Start OOB batch pipeline.
3. Rate 3 cdrs. Please note that B_NUMBER of one cdr file must be "004961099999" because one iScript plugin in the GSM rerating pipeline will raise one error based on this B_NUMBER.
4. Use pin_rel to load into BRM.
5. Config the rerating pipeline and make sure you configure one iScript plugin .
6. Start the rerating pipeline
7. Use the following command to manually create one rerating request, please make sure that you set up the start time to only include the three event loaded by pin_rel.
pin_rerate -t 01/08/2011 -a 3848553
8. run the command: pin_rerate -process jobs
9. run the command: pin_rerate -process queue
10. run the command: pin_rerate -rerate
11. You will found errors in pin_rerate.pinlog & cm.pinlog.
12. The origianl rerating quest status is set to 4.
13. But the pin_rerate also created another new job because the orinial job fails. And the new job's start time is the system time(not the start time in the original job) and it is obvious that both job will return the different event sets for rerating. This is not correct.
14. The expectation is that no automatic new job will be created because the new created job may fail again.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms