Last updated on DECEMBER 07, 2008
Applies to:Oracle Communications Billing and Revenue Management - Version: 184.108.40.206.0
Information in this document applies to any platform.
There could be a scenario where two scheduled actions for same account have same when_t and created_t. The first scheduled action is closing service (by changing the status of the service). The second one is creating the new service using the same login.
pin_deferred_act finishes with an error in such a case because the jobs are executed with reverse order. The first executed action for new service creation is not finished because the login exists. The second executed action also has the error because of an existing scheduled action with status 10103 (an error).
Even if we try to change the number of threads for the pin_deferred_act process to 1, the problem would still surface.
How could one achieve that such deferred actions having the same when_t, created_t, etc are executed in the right sequence to prevent issues like above.
- Create a schedule action to close the service in the future
- Create a schedule action to create new service with the same login on the account . Ensure it has the same time(when_t) in the future as above
- Run deferred action for the scheduled objects
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