Please see my other blog for Oracle EBusiness Suite Posts - EBMentors

Search This Blog

Note: All the posts are based on practical approach avoiding lengthy theory. All have been tested on some development servers. Please don’t test any post on production servers until you are sure.

Sunday, May 27, 2012

OPatch failure issue while patching RAC (11.2.0.3)

While patching the RAC/DB you may face different issues on Windows because of the .dll files being used. Here is the process how I got rid of such failure.
While performing the acfsroot install, it failed as below.

%ORACLE_HOME%\bin\acfsroot install


By process explorer I found which process is the cause of it and I killed it and started the acfsroot install again






%ORACLE_HOME%\bin\acfsroot install
ACFS-9300: ADVM/ACFS distribution files found.
ACFS-9307: Installing requested ADVM/ACFS software.
ACFS-9308: Loading installed ADVM/ACFS drivers.
ACFS-9327: Verifying ADVM/ACFS devices.
ACFS-9157: Detecting driver 'oracle oks'.
ACFS-9157: Detecting driver 'oracle advm'.
ACFS-9157: Detecting driver 'oracle acfs'.
ACFS-9309: ADVM/ACFS installation correctness verified.

The same happened while patching the RDBMS Home, many files were active although all the services stopped but still some dlls were being used by OS.
> opatch apply


Just kill the associated processes by process explorer.


You could also see wmiprvse.exe process locking the drivers. wmiprvse.exe is the Windows Management Instrumentation (WMI) service and should not be allowed to manage the GI drivers. To avoid such failures either reconfigure WMI to prevent this or disable and stop the WMI service on all nodes.  This should release the lock on the drivers and allow the patch/upgrade to proceed.


Note: sometimes the process that you kill will keep starting automatically and patching will be continuously failed. In this case just kill the process and immediately try to rename the Oracle Home being patched (eg; RDBMS home in my case) and then check if there is any process using dll file if existing kill that. After this rename the Oracle home to original and try patching (it worked for me). In worse case you may need to restart the machine being patched.

Ref:1348111.1

No comments: