Synchronization Issue Between ECE and BRM in Case of dm_oracle Timeout
(Doc ID 2307573.1)
Last updated on FEBRUARY 01, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and laterOracle Communications BRM - Elastic Charging Engine - Version 11.3.0.0.0 and later
Information in this document applies to any platform.
Symptoms
On all versions of Oracle Communications Billing and Revenue Management (BRM) up to 7.5 PS20 and Oracle Communications Elastic Charging Engine (ECE), if the transaction of orders coming from Application Integration Architecture (AIA) is timed out due to the trans_timeout setting on the dm_oracle layer, account and services information between BRM and the ECE cache are no longer in sync. One can see that the account is with services on ECE, but same services are not on BRM.
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! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |