用户运行concurrent requests(并发请求)报错——日志文件最大超过2g

用户在运行并发请求的时候,发现并发请求无法运行,在日志文件发现如下内容:


Concurrent Processing - Concurrent Reports Failing With Errors REP-0004,REP-0082 and REP-0104 (Doc ID 844976.1)

To Bottom



Modified: 09-Jul-2013Type:PROBLEM

In this Document

Symptoms

 

Changes

 

Cause

 

Solution

 

 

InformationCenter, Diagnostics, & Community

 

References


APPLIES TO:

Oracle Application ObjectLibrary - 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

Whenattempting to run any concurrent requests of the type Oracle Reports(rdf) , the following error is encountered in the concurrent request logfile:

REP-0004: Warning: Unableto open user preference 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:

 

OtherSymptoms

In12.1.1  all the reports are failing with following errors:

American_America.UTF8

'.,'

stat_low = 9
stat_high = 0
emsg:was terminated by signal 9
Enter Password:&nbsp;

+---------------------------------------------------------------------------+
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 yourconcurrent request 123456.

 

CHANGES

Therehas been no change in the environment.

CAUSE

Reports.log locatedunder $APPLCSF/$APPLLOG has reached the maximum file size limit of 2GB.

SOLUTION

Toimplement 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 shouldnot 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".

InformationCenter, Diagnostics, & Community

  • E-Business Concurrent Processing Information Center Document 1304305.1
    Please reference this document regularly to review current offerings for Concurrent Processing needs.

·        Diagnostics
For additional help, please refer to one of the followingdocuments on diagnostics to address current needs. Providing diagnostic outputon an issue for support when logging a service request is very helpful.

Document179661.1 for 11i or Document421245.1 for Rel 12.x

·        Core Concurrent Processing Community
Visit the CoreConcurrent Processing communityfor help from industry experts or to share knowledge.

REFERENCES

BUG:8512690 - REPORTS COMPLETE IN ERROR STATE.

时间: 2024-10-25 19:27:54

用户运行concurrent requests(并发请求)报错——日志文件最大超过2g的相关文章

arm-Liunx驱动死机,经常运行一段时间,报错重启问题

问题描述 Liunx驱动死机,经常运行一段时间,报错重启问题 驱动程序运行一段时间之后,就容易报这种错误重启. [ 122.377666] Unable to handle kernel paging request at virtual address 4d118106 [ 122.384417] pgd = d497c000 [ 122.387603] [4d118106] *pgd=00000000 [ 122.391150] Internal error: Oops: 5 [#1] PR

ssh开发-配置ssh 五个重要的包我都引入了,为什么运行tomcat的时候还是报错

问题描述 配置ssh 五个重要的包我都引入了,为什么运行tomcat的时候还是报错 严重: Exception starting filter struts2java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory at org.apache.struts2.dispatcher.FilterDispatcher.(FilterDispatcher.java:149) at sun.reflect.NativeCo

ssl- https双向认证请求报错,bad_certificate

问题描述 https双向认证请求报错,bad_certificate javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.Alerts.getSSLException(Alerts.java:154) at sun.security.ssl.

httpclient请求报错javax.net.ssl.SSLException

问题描述 httpclient请求报错javax.net.ssl.SSLException 有没有大神知道如何解决 javax.net.ssl.SSLException: Received fatal alert: protocol_version 解决方案 http://blog.csdn.net/lihenair/article/details/17441169 看下是一个原因不?> 解决方案二: 你的ssl版本是不是不能被服务器接受,安全问题等 解决方案三: 看着像是SSL安全问题呀

p2p-JXTA在运行HelloWorld程序的时候报错

问题描述 JXTA在运行HelloWorld程序的时候报错 在运行HelloWorld程序的时候,NetWorkManager的对象manager调用startNetwork方法的时候总会报错,大家遇到过这种情况吗,引用的是2.5的库,库的引用应该没问题 Hisos 2015/5/14 星期四 上午 7:58:27Starting JXTA五月 14 2015 7:54:03 上午 net.jxta.platform.NetworkManager configure信息: Loading exi

ssl-Java发送https请求报错

问题描述 Java发送https请求报错 KeyStore trustStore = KeyStore.getInstance(KeyStore.getDefaultType()); FileInputStream instream = new FileInputStream(new File(KEYSTORE_FILE_PATH)); // // try { // trustStore.load(instream, KEYSTORE_PASSWORD.toCharArray()); // }

5 internal error-QT程序调试时报错,但程序运行时则不确定报错,是什么原因?

问题描述 QT程序调试时报错,但程序运行时则不确定报错,是什么原因? 调试时报错信息Internal error: pc 0x3ff in read in psymtab, but not in symtab. 解决方案 你有指针方面的问题,调试的时候,编译器会将堆上的内存初始化成特殊值,并且库有一些断言捕获你的代码的异常.发布版为了性能没有这样的初始化,也不执行断言. 所以调试运行往往能发现更多的问题.好好利用调试的这个便利特性检查下你的代码. 解决方案二: http://www.cnblog

通过myeclipse运行tomcat时出现以下报错,不知道是什么问题。

问题描述 通过myeclipse运行tomcat时出现以下报错,不知道是什么问题. 可以通过网页打开,所以应该不是端口占用问题?不知道什么问题,求大神解答!! 2013-5-14 17:55:53 org.apache.catalina.core.AprLifecycleListener init 信息: Loaded APR based Apache Tomcat Native library 1.1.20. 2013-5-14 17:55:53 org.apache.catalina.cor

odl adsal northbound-karaf中运行feature:install odl-adsal-northbound就报错

问题描述 karaf中运行feature:install odl-adsal-northbound就报错 karaf中运行feature:install odl-adsal-northbound就报错 Refreshing bundles org.apache.aries.util (9) Error executing command: Can't install feature odl-adsal-northbound/0.0.0: Could not start bundle mvn:or