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" (document ID 1169036.1)

Applies to:oracle database-enterprise edition-version 11.2.0.3 and later Information in this document applies to any platform. Checked for relevance on 11-mar-2013*** Symptoms Applying Grid Infrastructure PSU using "Opatch Auto" fails with "the Opatch Component check failed" For example: 11.2.0.1 Example: # Opatch Auto/haclu/home Executing/usr/bin/perl/haclu/64bit/crs112/opatch/crs/patch112.pl-patchdir/haclu-patchn home-paramfile/haclu/ 64bit/crs112/crs/install/crsconfig_params 2010-07-29 05:37:28:parsing the host name 2010-07-29 05:37:28:checking for Super User privileges 2010-07-29 05:37:28:user has super User privileges Using configuration parameter file:/haclu/64bit/crs112/crs/install/crsconfig_params The Opatch Component check failed. This patch was not applicable for/haclu/64bit/app/oracle/product/11.2.0 The Opatch Component check failed. This patch was not applicable for/haclu/64bit/app/oracle/product/11.2.0 The Opatch applicable check failed for/haclu/64bit/app/oracle/product/11.2.0. The patch is not applicable for/haclu/64bit/app/oracle/product/11.2.0 The Opatch applicable check failed for/haclu/64bit/app/oracle/product/11.2.0. The patch is not applicable for/haclu/64bit/app/oracle/product/11.2.0 Prepatch execution for DB home ... failed 11.2.0.3 Example: #/u01/app/11.2.0/grid/opatch/opatch AUTO/PATCH-OCMRF/PATCH/OCM.RSP Executing/u01/app/11.2.0/grid/perl/bin/perl/u01/app/11.2.0/grid/opatch/crs/patch11203.pl-patchdir/-patchn Patch -ocmrf/patch/ocm.rsp-paramfile/u01/app/11.2.0/grid/crs/install/crsconfig_params /u01/app/11.2.0/grid/crs/install/crsconfig_params /u01/app/11.2.0/grid/crs/install/s_crsconfig_defs This is the main log file:/u01/app/11.2.0/grid/cfgtoollogs/opatchauto2013-05-30_07-40-32.log This file would show your detected configuration and all the steps, Opatchauto attempted to doing on your system:/u01/app /11.2.0/grid/cfgtoollogs/opatchauto2013-05-30_07-40-32.report.log 2013-05-30 07:40:32: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 was 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 Conflict-check has failed. Refer To/u01/app/11.2.0/grid/cfgtoollogs/opatchauto2013-05-30_07-40-32.log for details The Opatch auto log may show ZOP-45: Zop-45:the Patch (ES) is not applicable on the Oracle Home because some required components is not installed (or) Langua GES not supported. Changes Applying Grid Infrastructure PSU using "Opatch Auto" Cause There is several possibilities that can cause this: 1). "Opatch Auto <UNZIPPED_PATCH_LOCATION>". The directory where patch is unzipped are not supplied as <UNZIPPED_PATCH_LOCATION> 2). Patch is downloaded and unzipped to an existing and Non-empty directory. 3). Opatch executable is not installed and launched from $GRID _home/opatch. 4). $OH/.patch_storage cannot be created. 5). Listener is running from DB home 6). "Opatch" directory in DB home was owned by Root:oinstall instead of 7). GI User and RDBMS user is different. Workaround is to apply manually (note:1210964.1. This is an internal note that is contacted by Oracle support to get assistance). Solution 1). Make sure the <path> after "Opatch auto <path>" are pointed the directory where patch is unzipped. 2). Make sure the patch is downloaded and unzipped to an empty directory. 3). Opatch should is installed in $GRID _home/opatch.  It should not being installed outside of $GRID _home. Use the syntax given in readme unzip <opatch zipfile>-D $GRID _home to install Opatch to $GRID _home. Launch Opatch directly from $GRID _home/opatch. i.e. CD $GRID _home/opatch ./opatch Auto This would cause an issue a fixed in bug:10009350. Workaround for Bug 10009350 is: As Root User: CD $GRID _home/crs/install ./rootcrs.pl-patch Instead, one should include the $GRID _home/opatch in the path, and launch Opatch from the unzipped patch directory. 4). If Opatch complain $ORACLE _home/.patch_storage cannot be created, manually create. Patch_storage and give Read-write-e Xecute permission for the normal user (who operates Opatch) 5). Check If there is listener running out of a DB home, if so shutdown listener from DB home. 6). For each home to be patched, the "Opatch" directory in DB home must is owned by See:document 1553964.1 "This Patch was not applicable" encountered and Using ' Opatch auto ' Where ' Opatch ' Directory is N OT owned by If above steps has been examined, but is still getting "Opatch applicable check failed", please contact Oracle Suppo Rt. 7). If GRID User and RDBMS user is different, workaround was to apply manually (note:1210964.1.  This is an internal note that is contacted by Oracle support to get assistance). For Oracle Restart Environment, one can use note 1089476.1. referencesnote:1082394.1-11.2.0.1.x Grid Infrastructure PSU Known Issues note:1553964.1-"This Patch was not applicable" encountered the while Using ' Opatch auto ' Where ' Opatch ' Directory was not owne D By:

This article is from "Technical achievement dream!" "Blog, be sure to keep this provenance http://dreamsanqin.blog.51cto.com/845412/1736868

Applying GI PSU "Opatch Auto" fails with "the Opatch Component check failed"