My Oracle Support Banner

CustomerInBrmTransactionLock Events Are Not Being Deleted On Disaster Recovery(DR) Site (Doc ID 2646107.1)

Last updated on FEBRUARY 24, 2021

Applies to:

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

Symptoms

CustomerInBrmTransactionLock is created when the account is created on ECE(Elastic Charging Engine) cache (BRM(Billing and Revenue Management) request through EMGateWay or Customer Updater), after transaction is commited, the lock is released which reflects in the cache on the primary site. But this is not propagated to the secondary site.

Steps to reproduce the issue:

1.Start primary and secondary site cluster - DR(Disaster Recovery)  setup with Primary and Secondary.
2.Configure ECE and BRM CM(Connection Manager) with post_commit enabled.
   ECE Configuration post_commit.
   Enable the Server -> brmPostCommitEnabled="true"
   BRM Configuration Post Commit.
   Add the 2 entries in cm's/pin.conf
   - cm em_group ece PCM_OP_ECE_POST_COMMIT
   - cm ece_post_commit_enabled 1
   Restart the BRM services.
3. Trigger few adjustment or any BRM operations which will trigger sync to ECE.
4. Compare the CustomerInBrmTransactionLock between both the sites.

Primary Site:
---------------

CohQL> select value(),key() from CustomerInBrmTransactionLock;
Results
 
CohQL> select count() from CustomerInBrmTransactionLock;
Results
0

Secondary Site:
------------------
CohQL> select count() from CustomerInBrmTransactionLock;
Results
5
 
CohQL> select value(),key() from CustomerInBrmTransactionLock;
Results
["4221794", CoherenceAssociatedKey{associatedKey=4221794,id=4221794}]
["4220690", CoherenceAssociatedKey{associatedKey=4220690,id=4220690}]
["4226493", CoherenceAssociatedKey{associatedKey=4226493,id=4226493}]
["2190040", CoherenceAssociatedKey{associatedKey=2190040,id=2190040}]
["4222403", CoherenceAssociatedKey{associatedKey=4222403,id=4222403}]

CustomerInBrmTransactionLock Cache entry is set to null (or removed) in primary site post commit, but is not reflected in secondary site.

Question : How to release above locks in Secondary site?

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.