My Oracle Support Banner

Considerations for Improving beSync Performance (Doc ID 2501121.1)

Last updated on OCTOBER 09, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.

Goal

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communication Convergent Charging Controller (OC3C or 3C), the beSync process on the Voucher [and Wallet] Servers (VS' or VWS') is a critical process to the operation of the VS/VWS.

It is responsible for ensuring any changes to Wallets, Buckets, Balance, and Vouchers that are done on 1 node is synchronized to the remote node to provide continuity of service should the clients fail-over between the 2 nodes.

If the beSync does not start or crashes for whatever reason, the beServer on the same node will not accept incoming connections and will not take any real time traffic.  If both beSyncs in a VWS pair do not start, then all subscribers on the VWS pair will not be able to use any rated services.

This article will offer suggestions to tune configuration parameters to improve the performance of the beSync processes.

Solution

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
Goal
Solution
 Increase the Size of the Sync Files
 Check the Performance of the "sync" Directory
 Tune beSync Parameters

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