Oracle EBS Concurrent Manager 始终无法启动的一个解决方法

举报
fancanny 发表于 2019/01/18 09:45:03 2019/01/18
【摘要】 Concurrent Manager无法启动的解决 EBS 主页 > System Administration(或System Administrator) > Oracle Applications Manager > Concurrent Managers > Site Map > Diagnostics and Repair > Concurrent Manager Recovery

EBS V12.2.4 版本,Clone 的系统,其 Concurrent Manager 始终无法启动:

运行 /jit/jit13/fs1/inst/apps/JIT13_fxsljit04/admin/scripts/adcmctl.sh status apps/passwords

出现信息:You are running adcmctl.sh version 120.19.12020000.3

Internal Concurrent Manager is Not Active at this time.

adcmctl.sh: exiting with status 0

adcmctl.sh: check the logfile /jit/jit13/fs1/inst/apps/JIT13_fxsljit04/logs/appl/admin/log/adcmctl.txt for more information …

将 Profile: Concurrent:GSM Enabled 从 Y 改为 N, 也没有解决问题

在 $APPLCSF/$APPLLOG/JIT13_0228.mgr (/jit/jit13/fs_ne/inst/JIT13_fxsljit04/logs/appl/conc/log/SID_DATE.mgr)中出现如下错误信息:

sh: line 68: 18223 Segmentation fault

FNDLIBR FND CPMGR "FNDCPMBR sysmgr=\"\" sleep=30 pmon=4 quesiz=1 diag=N logfile=/jit/jit13/fs_ne/inst/JIT13_fxsljit04/logs/appl/conc/log/JIT13_0227.mgr "

<<STOP $unpw STOP

The JIT13_0227@JIT13 internal concurrent manager has terminated with status 139 - giving up.

此问题查阅了大量资料,花了很长时间才解决;

详细信息可见:https://community.oracle.com/message/12922099#12922099

Concurrent Processing - Concurrent Manager Recovery Troubleshooting Wizard (Doc ID 134007.1)

问题解决后,偶然发现通过 google 搜索 internal concurrent manager is not active at this time (google 直接跳出这个问题)

这么好的 google 却被封了,一声叹息。

解决方法:

EBS 主页 -> System Administration(或者System Administrator) -> Oracle Applications Manager > Concurrent Managers 

    > Site Map > Diagnostics and Repair > Concurrent Manager Recovery

【版权声明】本文为华为云社区用户原创内容,转载时必须标注文章的来源(华为云社区)、文章链接、文章作者等基本信息, 否则作者和本社区有权追究责任。如果您发现本社区中有涉嫌抄袭的内容,欢迎发送邮件进行举报,并提供相关证据,一经查实,本社区将立刻删除涉嫌侵权内容,举报邮箱: cloudbbs@huaweicloud.com
  • 点赞
  • 收藏
  • 关注作者

评论(0

0/1000
抱歉,系统识别当前为高风险访问,暂不支持该操作

全部回复

上滑加载中

设置昵称

在此一键设置昵称,即可参与社区互动!

*长度不超过10个汉字或20个英文字符,设置后3个月内不可修改。

*长度不超过10个汉字或20个英文字符,设置后3个月内不可修改。