In this Document
Symptoms |
Changes |
Cause |
Solution |
Information Center, Diagnostics, & Community |
References |
Applies to:
Oracle Application Object Library - Version 12.0.0 to 12.1.3 [Release 12 to 12.1]Information in this document applies to any platform.
Checked for relevance on 25-SEP-2012
Symptoms
When attempting to run any concurrent requests of the type Oracle Reports (rdf) , the following error is encountered in the concurrent request log file:
REP-0082: Error executing SCA utility.
REP-0104: Unable to delete file '<Name.rdf>'.
scaba 5
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-159:
Other Symptoms
In 12.1.1 all the reports are failing with following errors:
'.,'
stat_low = 9
stat_high = 0
emsg:was terminated by signal 9
Enter Password:
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
Program was terminated by signal 9
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 123456.
Changes
There has been no change in the environment.
Cause
Reports.log located under $APPLCSF/$APPLLOG has reached the maximum file size limit of 2GB.
Solution
To implement the solution, please execute the following steps:
1. Stop the concurrent managers using adcmctl.sh.
2. Remove the reports.log file in log directory (under $APPLCSF/$APPLLOG).
3. Restart the concurrent managers.
4. Submit Concurrent request of type RDF from Oracle Applications and ensure it completes normal.
Truncation of file "reports.log" is a regular maintenance work of Application DBA. 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".
Information Center, Diagnostics, & Community
- E-Business Concurrent Processing Information CenterDocument 1304305.1
Please reference this document regularly to review current offerings for Concurrent Processing needs. -
Diagnostics
Document 179661.1 for 11i or Document 421245.1 for Rel 12.x
For additional help, please refer to one of the following documents on diagnostics to address current needs. Providing diagnostic output on an issue for support when logging a service request is very helpful.
-
Core Concurrent Processing Community
Visit the Core Concurrent Processing community for help from industry experts or to share knowledge.