Multiple ccsBeAvd Processes on the VWS' which Never Exit/Finish
(Doc ID 2403737.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), the ccsBeAvd process runs periodically and is responsible for purging the E2BE database of redeemed vouchers which are older than the configured retention period. More details on ccsBeAvd can be found in the Voucher Manager Technical Guide.
A problem exists with the ccsBeAvd process where an endless number of instances can be started (if left long enough) which never exit. Over time, this will lead to a degraded Voucher and Wallet Server as resources are wasted on the hung/idle ccsBeAvd processes.
This can be confirmed by running ps and searching for instances of ccsBeAvd eg.
At any given time, there should be either none or at most 1 instance of ccsBeAvd running as confirmed by the attempt to use Process ID (PID) files to ensure only a single instance is up at a time:
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