Timed Out Wallet Reservations On Secondary VWS Node
(Doc ID 2206899.1)
Last updated on SEPTEMBER 18, 2020
Applies to:Oracle Communications Network Charging and Control - Version 5.0.2 to 6.0.0 [Release 5.0 to 6.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC), there may be uncommited/timed out reservations left on the secondary Voucher Wallet Server (VWS) Node
The error message is printed on the beVWARS log file:
On each chargeable event (voice/sms/data/named event) a reservation is created on the Primary VWS Node and synchronized on the Secondary VWS Node throughout the synchronization mechanism.
Synchronization enables the VWS to replay operations in the event of a failure and maintain redundancy in the event of a failure. It can be viewed as two continuous streams containing all reservations, updates, and deletions made on one VWS to the other.
Reservation: means the minimum charge to be reserved from a particular balance type to pay for the charged event. The Billing Engine uses rating tables together with Reservation Config settings to calculate this amount based on:
- The balance of the subscriber's account;
- The value of outstanding reservations;
- Pending updates.
Please consult OCNCC documentation for more details about the Synchronization and Reservation Mechanisms.
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