beSync Crashing on Active VWS when Standby VWS Started
(Doc ID 2736399.1)
Last updated on DECEMBER 15, 2020
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 126.96.36.199.0 [Release 4.3 to 12.0.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC), the beSync process is responsible for maintaining synchronicity of the beVWARS data (and in turn, the BE_* database tables).
When a stopped Voucher Wallet Server (VWS) is started, the beSync process on the active VWS can be SIGABRT'd by the watchdog, leaving behind a core file. This affects all versions of NCC up to and including 188.8.131.52.
This causes the formerly stopped VWS (which is out-of-date) to go "running" and start processing realtime traffic with outdated information. As a result, double charges and funds may be granted which exceed the subscriber's available funds which can result in the bucket go negative due to the updates written to the sync files still residing on previously active VWS which crashed.
For example, a subscriber may have exhausted all their funds for a balance type while one VWS node was down and these charges written to sync files. When the offline node is started, the beSync on the active VWS crashes before the sync file containing the charge is sent/processed by the previously stopped node. Due to the beSync crashing, the previously stopped node goes "running" (to ensure there is no full outage) and starts handling realtime traffic. The same subscriber can now use their previously exhausted funds again as the session/charges which exhausted the funds are still stuck on the crashed VWS. Once they both go back online and are fully synced, the subscriber's funds have gone negative due to both charges being committed.
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