pin_deferred_act Execution Not Grouping Threads Per Account
Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0]
Information in this document applies to any platform.
The pin_deferred_act application does not process schedule actions pertaining to one account by one single thread.
This means the pin_deferred_act utility is distributing the schedulers to differents threads, even if they are belonging to a single account. Hence we cannot guarantee the sequence of these actions.
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