Oracle applications suffer from the above error quite many times (depending upon how frequently the reports.log file reaches 2.0GB) and many important programs like “AutoInvoice Master” and associated ones will tend to complete with error status. This is due to the size limitation set on “reports.log” file by Oracle application architecture.
Please follow the below to address this situation effectively
Oracle Application Object Library – Version: 12.0.0 to
This problem can occur on any platform.
When attempting to run a concurrent program which is
accessing file “reports.log” in directory
$INST_TOP/logs/appl/conc/log then following error occurs:
emsg:was terminated by signal 25
Run a concurrent program which is accessing file
“reports.log” in directory $INST_TOP/logs/appl/conc/log for its
File size of “reports.log” has reached its maximum
limit at operating system which is 2GB. If
$INST_TOP/logs/appl/conc/log/reports.log will be huge — 2GB in size, then
reports can not append anything else to it and hence concurrent program
accessing reports.log for its execution will errored out.
To implement the solution, please execute the following
1. Stop the concurrent manager.
2. Rename/Truncate existing “reports.log” in directory
$INST_TOP/logs/appl/conc/log/reports.log and create a empty
3. Start the concurrent manager.
4. Retest the issue.
5. Migrate the solution as appropriate to other
Note : Truncation of
file “reports.log” is a regular maintenance work for application
DBA’s. Make sure that reports log file size should not increase its maximum
limit of 2 GB. There is no purge concurrent program to truncate file
“reports.log”. This maintenance needs to be done manually and regularly
depending on number of concurrent program which uses “reports.log”.
You can safely truncate “reports.log”.