首页 > Linux操作系统 > Linux操作系统 > 关闭Concurrent Mananger或Server Crash后还是运行状态的Concurrent Request如何处理

关闭Concurrent Mananger或Server Crash后还是运行状态的Concurrent Request如何处理

原创 Linux操作系统 作者:tolywang 时间:2012-05-03 09:30:51 0 删除 编辑

Concurrent Requests Stuck in Running Status After Server Crashed [ID 152763.1] 

修改时间11-JAN-2011 类型 PROBLEM 状态 ARCHIVED

•fact: Oracle Application Object Library
•symptom: Concurrent requests stuck in Running status
•change: Server crashed
•cause: Either the server crashed or the concurrent manager was shutdown
while concurrent requests were running.    Thus the phase_code column of the
FND_CONCURRENT_REQUESTS table still holds a value of 'R' for Running.



1.  First, run the cmclean.sql script. found in Metalink Note:134007.1.

2.   If this doesn't resolve the issue, then Shut down the concurrent managers
then check for any FNDLIBR processes running at the OS level.   There should
not be any.  If there are FNDLIBR processes, then kill them at the OS level.
If this doesn't resolve the issue then ...

3.  try the following SQL update command after making a note of the request ID
number of the problem concurrent requests:
SQL> update fnd_concurrent_requests
set set status_code='X', phase_code = 'C'
where request_id = ;

或者直接登入EBS系统在concurrent mananger 的界面中查找对应的request ID , 一个一个设置为cancel .


来自 “ ITPUB博客 ” ,链接:,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
Oracle , MySQL, SAP IQ, SAP HANA, PostgreSQL, Tableau 技术讨论,希望在这里一起分享知识,讨论技术,畅谈人生 。


  • 博文量
  • 访问量