GI OPatch升级 The opatch Component check failed. This patch is not applicable for...

Oracle11gr2RAC(11204)打补丁11.2.0.4.8,系统为:SuSE11sp3 X86_64

通过/u01/app/11.2.0/grid/OPatch/opatch auto /tmp/21523375 -ocmrf /tmp/ocm.rsp 同时对ORACLE_HOME,GI_HOME同时升级。出现如下报错:

jason1:/u01/app/11.2.0/grid/OPatch # /u01/app/11.2.0/grid/OPatch/opatch auto /tmp/21523375 -ocmrf /tmp/ocm.rsp

Executing /u01/app/11.2.0/grid/perl/bin/perl /u01/app/11.2.0/grid/OPatch/crs/patch11203.pl -patchdir /tmp -patchn 21523375 -ocmrf /tmp/ocm.rsp -paramfile /u01/app/11.2.0/grid/crs/install/crsconfig_params

This is the main log file: /u01/app/11.2.0/grid/cfgtoollogs/opatchauto2016-01-20_12-38-42.log

This file will show your detected configuration and all the steps that opatchauto attempted to do on your system:

/u01/app/11.2.0/grid/cfgtoollogs/opatchauto2016-01-20_12-38-42.report.log

2016-01-20 12:38:42: Starting Clusterware Patch Setup

Using configuration parameter file: /u01/app/11.2.0/grid/crs/install/crsconfig_params

The opatch Component check failed. This patch is not applicable for /u01/app/oracle/product/11.2.0/dbhome_1

The opatch Component check failed. This patch is not applicable for /u01/app/oracle/product/11.2.0/dbhome_1

Conflict check failed for oracle home  /u01/app/oracle/product/11.2.0/dbhome_1

Conflict check failed

ERROR: Conflict-Check has failed . Please refer to /u01/app/11.2.0/grid/cfgtoollogs/opatchauto2016-01-20_12-38-42.log for details

opatch auto failed.

jason1:/u01/app/11.2.0/grid/OPatch #

查看opatchauto2016-01-20_12-38-42.log日志,发现如下报错。

2016-01-20 12:39:40: Running as user oracle: /u01/app/oracle/product/11.2.0/dbhome_1/OPatch/opatch prereq CheckComponents -ph /tmp/21523375/21352635 -oh /u01/app/oracle/product/11.2.0/dbhome_1 -customLogDir /u01/app/11.2.0/grid/cfgtoollogs/opatchauto/core

2016-01-20 12:39:40: s_run_as_user2: Running /bin/su oracle -c ‘ /u01/app/oracle/product/11.2.0/dbhome_1/OPatch/opatch prereq CheckComponents -ph /tmp/21523375/21352635 -oh /u01/app/oracle/product/11.2.0/dbhome_1 -customLogDir /u01/app/11.2.0/grid/cfgtoollogs/opatchauto/core ‘

2016-01-20 12:39:41: Removing file /tmp/file9jNagp

2016-01-20 12:39:41: Successfully removed file: /tmp/file9jNagp

2016-01-20 12:39:41: /bin/su exited with rc=1

2016-01-20 12:39:41: The opatch Component check failed. This patch is not applicable for /u01/app/oracle/product/11.2.0/dbhome_1

2016-01-20 12:39:41: The component check failed with following error

2016-01-20 12:39:41: Input custom log directory "/u01/app/11.2.0/grid/cfgtoollogs/opatchauto/core" does not exists or not a valid directory.

 OPatch failed with error code 1

..............................省略.................................................

根据日志提示切换到oracle用户下执行以下语句

/u01/app/oracle/product/11.2.0/dbhome_1/OPatch/opatch prereq CheckComponents -ph /tmp/21523375/21352635 -oh /u01/app/oracle/product/11.2.0/dbhome_1 -customLogDir /u01/app/11.2.0/grid/cfgtoollogs/opatchauto/core

报错提示没有权限,查看该目录权限,发现只有grid用户拥有权限,修改权限。

jason1:/u01/app/11.2.0/grid # ll -ld cfgtoollogs

drwx------  7 grid oinstall     4096 Jan 20 12:40 cfgtoollogs

jason1:/u01/app/11.2.0/grid # chmod 777 cfgtoollogs/

jason1:/u01/app/11.2.0/grid # ll -ld cfgtoollogs/

drwxrwxrwx 7 grid oinstall 4096 Jan 20 12:44 cfgtoollogs/

jason1:/u01/app/11.2.0/grid #

修改为目录权限后,再次执行打补丁成功。同样方法查看jason2节点,修改对应目录权限

jason2:/u01/app/11.2.0/grid # ll -ld cfgtoollogs

drwx------  7 grid oinstall     4096 Jan 20 12:40 cfgtoollogs

jason2:/u01/app/11.2.0/grid # chmod 777 cfgtoollogs/

jason2:/u01/app/11.2.0/grid # ll -ld cfgtoollogs/

drwxrwxrwx 7 grid oinstall 4096 Jan 20 12:44 cfgtoollogs/

jason2:/u01/app/11.2.0/grid #

opatch成功!

时间: 2025-02-01 02:45:05

GI OPatch升级 The opatch Component check failed. This patch is not applicable for...的相关文章

Applying GI PSU "opatch auto" fails with "The opatch Component check failed"

Applying GI PSU using "opatch auto" fails with "The opatch Component check failed" (文档 ID 1169036.1) APPLIES TO: Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterInformation in this document applies to any platform.***C

【Oracle】OPatch升级

在进行PSU升级过程中,opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./12419378 检测报错: Invoking prereq "checkconflictagainstohwithdetail" The location "./9352164/README.html" is not a directory or a valid patch zip file. Prereq "c

一次误操作导致的gi psu升级失败

oracle使用opatch auto的方式安装gi psu时需要一个节点一个节点来,昨晚的升级中,因为误操作而是两节点同时安装gi psu,最终在补丁安装完成后,无法拉起crs. 选择进行补丁的rollback,结果悲剧的发现rollback的前提是需要crs启动的状态,无奈之下只能进行备份文件的恢复了. 不过因为意识的疏忽,压缩$oracle_home目录和$grid_home目录时没有使用root用户,导致部分文件没有备份出来. 以后打类似的psu,有两个注意点: 第一,一定要一个节点一个

解决npm 的 shasum check failed for错误

使用npm安装一些包失败,类似如下报错情况: C:\Program Files\nodejs>npm update npm npm ERR! Windows_NT 10.0.14393 npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "update" &quo

浏览器运行java插件报错:Algorithm constraints check failed: MD5withRSA

今天使用kvm管理机房机器的时候发现一只连不上,报以下错误: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Algorithm constraints check failed: MD5withRSA 我确认我已经把域名添加到例外了,但是还是不行.之前是可以的,同事现在也可以,可能是最近我更新过. goog

mysqlbinlog备份时候报错Sanity check failed

今天在复习mysql的二进制日志时候,发现出了点问题,如下: mysqlbinlog -uroot -proot /usr/local/mysql/data/node1.000004 --start-datetime="2016-05-04 13:30:00" --stop-datetime="2016-05-04 13:45:00" > a.sql ERROR: Error in Log_event::read_log_event(): 'Sanity ch

Check failed: error == cudaSuccess (10 vs. 0) invalid device ordinal

ubuntu14.04 caffe 运行别人的程序,报错Check failed: error == cudaSuccess (10 vs. 0)  invalid device ordinal.根据网上的说法,GPU内存不够,可是batch大小改为1了还是不行.问了博士师兄才发现,在该行上面有一行,写着using GPUs 1.而我只有一个GPU,如图2,我把solver_48.prototxt中最后一行的device_id改为0,接着运行,见图1,这个错误就没有啦--当然我的又报了别的错..

网卡mtu 值不同导致rac 2节点ASM不能同时启动 ORA-27550: Target ID protocol check failed.

在安装完10205 rac 后准备配置 asm dg ,发现节点二上的ASM 没法启动: en12 为private 网卡 en13 为 public 网卡 ---->> 查看 oracle asm alert log 报错显示: LMD0 started with pid=6, OS id=565728 LMS0 started with pid=7, OS id=491812 MMAN started with pid=8, OS id=594200 DBW0 started with p

caffe运行错误: im2col.cu:61] Check failed: error == cudaSuccess (8 vs. 0) invalid device function

错误: im2col.cu:61] Check failed: error == cudaSuccess (8 vs. 0)  invalid device function 原因:由于Makefile.config里面只对cuda8.0一下的架构编译cuda程序,所以采用cuda8.0后cuda程序没有被编译 解决:修改Makefile.config中的 CUDA_ARCH 添加 -gencode arch=compute_61,code=sm_61 计算能力可以参考下面链接添加合适的架构参数