ccsBeResync Mixes up the Primary and Secondary VWS Connections
(Doc ID 2091452.1)
Last updated on FEBRUARY 28, 2019
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.
In all versions of Oracle Communications Network Charging and Control (NCC) up to and including 220.127.116.11, 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):
where the Domain ID can be found from:
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.
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:
beID : 1
Primary BE IP : W.X.Y.Z
Primary BE Port : 1500
Secondary BE IP : W.X.Y.Z
Secondary BE Port : 1500
New VWS domain/pair added.
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