EBS APPS 204ERROR:log-->failed to start a managed process after the maximum re try limit

X_FOCUS

于 2013-12-25 13:50:12 发布

阅读量2.4k

点赞数

CC 4.0 BY-SA版权

分类专栏： EBS

本文链接：https://blog.youkuaiyun.com/x_focus/article/details/17553779

EBS 专栏收录该内容

34 篇文章

订阅专栏

本文详细介绍了在Oracle R12环境中，当尝试启动OACore组件时遇到adopmnctl.sh退出状态206的错误情况。通过分析日志文件，我们发现与OC4J和oafm相关的过程在达到最大重试限制后失败。提供了解决方案，包括清理特定目录的内容，以解决此问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Solutions to Oracle Apps Errors
 adopmnctl.sh: exiting with status 206
We may face this issue while starting up the oacore component in our R12 environment. There
might not errors logged in any of the log files except the error status code of 206 returned by
opmnctl.sh .
Error Details :
ias - component/process -type/process - set:
OC4J/oacore/default_group/
Error
--> Process (index=1,uid=32979870,pid=13697)
failed to start a managed process after the maximum retry limit
Log:
/d01/oracle/PROD/INSTANCE_NAME/i nst/apps/INSTANCE_NAME_SERVER_NAME/logs/ora/10.1.
3/opmn/OC4J~oacore~default_group~1
ias - component/process -type/process - set:
OC4J/oafm/default_group/
Error
--> Process (index=1,uid=32979871,pid=13716)
failed to start a managed process after the maximum re try limit
Log:
/d01/oracle/PROD/INSTANCE_NAME/inst/apps/instance_name_server_name/logs/ora/10.1.3/
opmn/OC4J~oafm~default_group~1
03/31/11-07:12:49 :: adopmnctl.sh: exiting with status 206
Expected Solution:
cd $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/persistence/
rm -rf *
cd $ORA_CONFIG_HOME/10.1.3/j2ee/oafm/persistence/

rm -rf *