Timed Out Wallet Reservations On Secondary VWS Node (Doc ID 2206899.1)

Last updated on DECEMBER 02, 2016

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.

Symptoms

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:

Oct 26 07:57:07 vws02 beVWARS: [ID 675952 user.error] beVWARS(21987) ERROR: Timed out 1 wallet reservation:[clientId 1, clientMsgId 2], current time 20151026075707, expired 20151026075704 (3 seconds ago), message timestamp 20151025075634.362458, not from beServer.

FOREWORD:
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.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms