Silent Failures In Replication After SmsMaster DB Disconnection
(Doc ID 2756620.1)
Last updated on DECEMBER 29, 2023
Applies to:Oracle Communications Network Charging and Control - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On Oracle Communications Network Charging and Control Applications (NCC), 220.127.116.11.0 version,
Below Errors were observed on the smsMaster node between the application node and the database, which caused some disconnections to the database.
Initially, there was an error with the smsMaster:
This also appeared to resolve itself, some nodes performed enhance resyncs etc. Ultimately the replication queue looked fine and all nodes appeared in sync from the perspective of the smsMaster - however, single row updates to some nodes (a subset of the ones that reported the MFile refresh above) were not correctly applied and went directly into queuedOrders.dat and were never processed. There were no errors reported at this time either - the last message in the updateLoader was a disconnection and then a message saying the master node had been reached.
This was ultimately resolved by performing a resync on the affected SLC nodes, but they would like to know what could have happened in the meantime. What does the updateLoader base its decision on for whether to queue orders or apply them to the database and could this get stuck?
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