1.
在运行提交concurrent request之后,经常会出现“Inactive Manager”的警告的黄色状态,在这种情况下,可以通过重新启动(adcmctl命令)来达到解决问题
- Stop the concurrent manager using "adcmctl.sh stop apps/"
- Start the concurrent manager using "adcmctl.sh start apps/"
If the above does not help, please try to run "cmclean.sql" from Note: 134007.1 - CMCLEAN.SQL - Non Destructive Script. to Clean Concurrent Manager Tables
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=134007.1
2. 在通过adtrtal.sh start 来启动应用层的服务的时候,曾经遇到过OPMN managed的那些service没有办法启动,日志中会有如下的内容:
Web Application Services OACORE OC4J Instance r12dv_apg007 adoacorectl.sh Failed
Web Application Services FORMS OC4J Instance r12dv_apg007 adformsctl.sh Failed
Web Application Services OAFM OC4J Instance r12dv_apg007 adoafmctl.sh Failed
解决办法是:
- Open a new shell and set your apps environment
- cd $ADMIN_SCRIPTS_HOME
- adopmnctl.sh stop
- Check if it is really down: ps -ef | grep -i opm
- Delete the following:
$ rm -fr $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/*
$ rm -fr $INST_TOP/ora/10.1.3/j2ee/oafm/persistence/*
$ rm -fr $INST_TOP/ora/10.1.3/j2ee/forms/persistence/*
然后重新运行adstrtal.sh start这个命令。
3. ebs 实例的dbc file的位置:
11i: $FND_TOP/secure
R12: $FND_SECURE
4. 在打patch过程之中如果失败了,可以使用$AD_TOP/bin目录下面的adctrl.sh命令来查看各个worker的信息,以及对这各个worker进行操作。
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/25441646/viewspace-698010/
,如需转载,请注明出处,否则将追究法律责任。