MTA Runs Until Log File size Is Less Than 2 GB
(Doc ID 1273721.1)
Last updated on DECEMBER 04, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management(BRM), 18.104.22.168.0 version,
The MTA application runs until the log file is less than 2 GB. When log file size exceeds 2 GB the applications don’t respond and then exit with an error.
Steps to Reproduce:
Run MTA application on large number of accounts (thousands of accounts) with loglevel 3 in MTA pin.conf file.
In this case the environment have approximately 7000 accounts. All accounts have 1 DOM.
Settings for logging MTA:
Actions to reproduce:
Run pin_bill_day when delay period is over. All accounts must be billed.
During execution file /opt/portal/7.3/var/pin_billd/pin_mta.pinlog grows up till 2 Gb.
Then calling pin_bill_accts causes message to stdout: "File size limit exceeded". There are no messages about error in log-file for MTA or cm.pinlog. The Application doesn't terminate nor finish.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!