Customerupdater Doesn’t Start With Continueonerror Set to True in Case of Data Inconsistencies
(Doc ID 2833455.1)
Last updated on JANUARY 14, 2022
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 12.0.0]
Information in this document applies to any platform.
Given the below scenario on environment running Elastic Charging Engine (ECE) 188.8.131.52.0 in which persistence is not enabled (NoSQL is used) and customerUpdater process was started with “continueCustomerLoaderOnError=true” flag
1. new test account created; information for the new account was loaded in ECE caches
2. created an inconsistency for the new account by updating one line in bal_grp_bals_t table with a non-existent balance id (1000259 doesn't exist in the system) for the new account
If trying to start customerUpdater with “continueCustomerLoaderOnError=true” flag while having this inconsistency, it is not able to start
It is expected that when starting customerUpdater with “continueCustomerLoaderOnError=true” flag it will start even there are some inconsistencies.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document