ccsBeResync Mixes up the Primary and Secondary VWS Connections (Doc ID 2091452.1)

Last updated on JANUARY 20, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.3 [Release 4.3 to 5.0]
Information in this document applies to any platform.

Symptoms

In all versions of Oracle Communications Network Charging and Control (NCC) up to and including 5.0.3.0, it is possible for the ccsBeResync tool to get the connections to the primary and secondary beServers reversed and can result in the "correct" Voucher Wallet Server (VWS) being overwritten with data from the "wrong" VWS when using the "-m <primary|secondary" switch.

To verify if this affects your VWS domain, run the following query on the Service Management Server (SMS):

SQL> SELECT CLIENT_PORT,COMM_ADDRESS FROM CCS_DOMAIN_NODES WHERE DOMAIN_ID = <Domain ID>;

where the Domain ID can be found from:

SQL> SELECT DOMAIN_ID,NAME FROM CCS_DOMAIN;

If the returned CLIENT_PORT and COMM_ADDRESS for the given domain are in reversed order, ie. the secondary VWS is listed first then the primary second, then this issue affects this VWS domain.

Do not run a ccsBeResync until Oracle Support has been consulted via a Service Request in My Oracle Support.  Once the data has been overwritten, there is no recovery.

Another way to check this is to run the ccsBeResync with the "-r" switch (report mode) which will print the connection details without running an actual resync:

ccsBeResync Configuration
-------------------------
 beID                   : 1
 ...
 Primary BE IP          : W.X.Y.Z
 Primary BE Port        : 1500
 Secondary BE IP        : W.X.Y.Z
 Secondary BE Port      : 1500

Changes

New VWS domain/pair added.

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