Prepaid Charging Domain Screens Dont Validate Port Entries Leading To Critical beSync Error "CRITICAL: FATAL ERROR in beSync: Escher error: Message content error: Map key [TRAN] does not exist, exiting."
(Doc ID 1524321.1)
Last updated on AUGUST 19, 2019
Applies to:
Oracle Communications Network Charging and Control - Version 2.2.0 and laterOracle Solaris on SPARC (64-bit)
Symptoms
On all versions of NCC (Network Charging and Control), when attempting to add or edit a UBE-type VWS (Voucher Wallet Server) Billing Domain, it is possible to enter the same Client and Internal TCP port.
The Client port identifies the port which the beServer listens on and which the beClients connect to.
The Internal port identifies the port which the VWS nodes use to communicate between each other via the beSync mechanism.
If the Internal and the Client port on the same node are the same value, then the following error occurs in the beSync log when starting up:
For example:
Changes
Addition of new VWS pair(s) or alterations to existing VWS pair(s).
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |