"No Context" Alarms when Stopping an Active VWS Node (Doc ID 2446339.1)

Last updated on MARCH 27, 2023

Applies to:

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC), when stopping an active Voucher and Wallet Server (VWS) node, the beVWARS processes on the newly active node will log the following alarm:

This may continue for hours and results in dropped calls, terminated data sessions, and Short Message Service (SMS) messages may not be delivered.

A "No context" alarm is thrown when a message from a billing client arrives at a beVWARS that refers to a reservation that does not exist.  For example:

1. A voice call starts and the BeClient on the Service Logic Controller (SLC) sends an Initial Request (IR) to the primary VWS which creates a reservation context
2. Before the reservation details are written to a sync file (and sent to the remote VWS), the Service Logic Execution Environment (SLEE) is stopped on the primary VWS
3. The BeClient(s) detect the socket closure and immediately fail over to the secondary VWS
4. The next time an update/terminate equivalent message is received from the network, the BeClient/SLC will send the respective Subsequent/Commit Reservation (SR/CR) message to the VWS
5. The now active VWS throws the "No context" alarm as the sync operation to create the reservation is still stuck on the now stopped VWS

Cause

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