My Oracle Support Banner

Unstable Behavior Of Preselect_customers.sh When DbFetchSize Is Greater Than Number Of Accounts (Doc ID 2359164.1)

Last updated on FEBRUARY 23, 2018

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.4.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.3.0.4.0 version, Customer data management

Scenario:

Customer are using preselect_customers.sh to sync migrated account deployed via CMT tool into ECE Cache. By Default keeping the dbFetchSize as 1000.

Its observed that when the number of accounts is 1001 , the script created one fetch_index in ECE_WORK_ITEM_DETAIL_T and ECE_WORK_ITEM_SUMMARY_T.
But when the number of account is less than 1000(example : 822) and dbFetchSize is 1000 than 888 fetch_index is created in ECE_WORK_ITEM_DETAIL_T and ECE_WORK_ITEM_SUMMARY_T instead of 1.

Number of Accounts in BRM : 1048


Actual Result:
SELECT max(fetch_index) FROM ECE_WORK_ITEM_SUMMARY_T;
1048

Expected result:
SELECT max(fetch_index) FROM ECE_WORK_ITEM_SUMMARY_T;
1




Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.