EBS adpatch的时候报ORA-03113: end-of-file on communication channel
EBS adpatch的时候报ORA-03113: end-of-file on communication channel从adpatch的日志中看到
================adpatch.log======================================Running utl_recomp.recomp_parallel(4), if it existsOWNER NUM_INVALID------------------------------ -----------SERVICES24PROJMFG 24PSBEXCEL 1DLD 4RE 1MOBILEADMIN 4CA 2DGRAY24MJORDAN1PSTOCKMAN 1PUBLIC 1102RALFRED1HERMAN 1APPS 5132FEDERAL1JPALMER1FLOWS_010500 217 rows selected.Elapsed: 00:00:00.15PL/SQL procedure successfully completed.Elapsed: 00:00:00.01STATUS_MESSAGE------------------------------------------------------------------------------Running UTL_RECOMP.RECOMP_PARALLEL...declare*ERROR at line 1:ORA-03113: end-of-file on communication channelERROR:ORA-03114: not connected to ORACLE================adpatch.log======================================
根据NOTE:1125213.1的说法需要查看<RDBMS ORACLE_HOME>/admin/<SID_HOST>/diag/rdbms/prod/<SID>/trace/alert_<SID>.log
The first recommended action to take when investigating these errors is to check the RDBMS alert_<SID>.log. This log will help to identify if the problem is with the RDBMS or with something else, such as the application code. Open the alert<SID>.log,possible locations of that log file are:
R12 on 11g database: <RDBMS ORACLE_HOME>/admin/<SID_HOST>/diag/rdbms/prod/<SID>/trace/alert_<SID>.log
===============alert_instance.log==============================Errors in file /u01/oracle/mc3yd213/db/tech_st/11.1.0/admin/mc3yd213_bej301441/diag/rdbms/mc3yd213/mc3yd213/trace/mc3yd213_pmon_13565.trc:ORA-00470: LGWR process terminated with errorPMON (ospid: 13565): terminating the instance due to error 470===============alert_instance.log==============================关于ORA-00470: LGWR process terminated with error，根据http://www.itpub.net/thread-502105-1-1.html
需要edit the init parameter file in the database(Using 11gR1 follow doc.761570.1)，
/d01/oracle/VIS/db/tech_st/11.1.0/dbs/initVIS.ora
增加
_disable_logging=false重启数据库
addbctl.sh stopaddbctl.sh start
sqlplus / as sysdbaSQL> show parameter _disable_loggingNAME TYPE VALUE------------------------------------ ----------- ------------------------------_disable_logging boolean FALSE
再重新打patch就没有问题了
相关的文章
http://msutic.blogspot.jp/2009/03/be-aware-of-disablelogging-true.html
http://kevinclosson.wordpress.com/2007/07/21/manly-men-only-use-solid-state-disk-for-redo-logging-lgwr-io-is-simple-but-not-lgwr-processing/
转载请注明出处：http://blog.iyunv.com/pan_tian/article/details/7612482
======EOF======
页:
[1]