Can Not Exclude The Closed Accounts Loading Into Pipeline In-Memory
Last updated on JULY 26, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.3.0]
Information in this document applies to any platform.
User is unable to exclude the closed accounts loading into pipeline in-memory
As per the document -
When you start Pipeline Manager, DAT_AccountBatch loads all accounts into memory. This can affect start-up performance when there are a great number of accounts. To improve Pipeline Manager start-up performance, you can reduce the number of accounts loaded into memory by specifying not to load closed accounts.
To not loading closed accounts, you set the ClosedAccountDelay entry in the DAT_AccountBatch registry. Specify the number of days prior to the current date for which closed accounts are not loaded:
ClosedAccountDelay = number_of_days
But, it does not work irrespective of the day offset set to this parameter as it always picks up the closed account. The log file says - 0 closed accounts excluded.
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