Radius CDR File Rotation Mechanism Has Issue At Higher Load (Doc ID 787510.1)

Last updated on JULY 26, 2017

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 and later
Oracle Solaris on SPARC (32-bit)
Sun Solaris SPARC (32-bit)

Symptoms


Let us consider, Radius is having the following CDR names and rotation logic .As per above configuration, Raidus will rotate CDR file to .log file (CURRENT to .log file) . At normal load it is working fine . When the load is high, say, 100 Radius messages per second , issue may be observed in the rotation mechanism .

After sending messages 100 per second, for one minute, two files are created; one is .log file and another is CURRENT as shown below . That is, CURRENT file never rotated and new CURRENT file is generated for the next minute .

cdr_Test_%b_%d_%y_%H:%M_%N.log

 

Example:
cdr_Test_Feb_04_09_10:14_5.log
cdr_Test_Feb_04_09_10:14_5.log._just_log_5__CURRENT

After generating log file, batch controller may pick the log file for rating by UEL, as per the setup .
But, as the CURRENT file is not rotated, it will not genearte .log file .

-- Steps To Reproduce:
1) Configure Radius with the following rotation mechanism .
       cdr_Test_%b_%d_%y_%H:%M_%N.log

2) Send requests at higher rate using any simulators for around 10 min .

3) One may see that two files are created for one minute , CURRENT and .log file .

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms