Long MFile Compilation Time after Mass Rating Data Import
(Doc ID 2117610.1)
Last updated on MARCH 19, 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.
On all versions of Oracle Communications Network Charging and Control (NCC), after importing a large amount of rating information into Charging Control Services (CCS), the compilation of new Memory Files (MFiles) by the ccsMFileCompiler starts taking an unacceptably long time on the Voucher and Wallet Server (VWS) nodes.
The actual amount of data resulting in an "unacceptable" amount of time to compile an MFile is based on the hardware which the VWS' are running on and business decisions.
The amount of time taken to compile an MFile can be verified in the ccsMFileCompiler log:
<USERNAME>@vws01:/IN/service_packages/CCS/tmp$ tail -f ccsMFileCompiler.log
Jan 19 16:17:17.213276 ccsMFileCompiler(14122) NOTICE: Compiling MFile prefix /IN/service_packages/CCS/MFile (+change_date), db ID 6018
Jan 19 16:17:17.230428 ccsMFileCompiler(14122) NOTICE: Compiling MFile /IN/service_packages/CCS/MFile/20160119161707
Jan 19 16:18:46.925606 ccsMFileCompiler(14122) WARNING: No TariffNameCodes defined in database
Jan 20 06:50:48.709513 ccsMFileCompiler(14122) NOTICE: Connection to BE <IPADDRESS>-<PORTNUMBER> is established.
Jan 20 06:50:48.798517 ccsMFileCompiler(14122) NOTICE: Informed beServer of MFile change
In this example we can see the MFile took almost 15 hours to compile.
Large amount of rating information imported into CCS.
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