Opatch Failed With Error Code 20

[Tijuana Strauhal]

Hasanyone seen this error for Grid Infrastructure 12.1.0.2 - "OPatch failed with error code 15"? This is a new GI install and I was running through the pre-checks prior to patching the home with the latest PSU. The error was received when the GI inventory was being validated. I've searched MOS and Google and came up empty.

When trying to execute "opatch lsinventory", "opatch lsinventory -detail" or "opatch apply" and this command does not show progress or hangs. And it is cancelled manually, it shows the following error:

In this Document

SymptomsChangesCauseSolution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

[FINE] All the required patch(es) are present in the Oracle Home.

[FINE] Running prerequisite check "CheckMultipleTranslationPatches"

[SEVERE] OUI-67073:UtilSession failed: null

[INFO] Stack Description: java.lang.RuntimeException: null

In this Document

Symptoms Apply a patch to an ORACLE_HOME may results in one of the belong warnings/errors :ChangesCauseSolutionReferences My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

The error message indicates that some files or executables within your Oracle Home directory are currently in use. Specifically, the file ORAEVRUS19.dll is active.

Found in the log c:\opt\oracle\cfgtoollogs\opatch\opatch_.log

Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.

First, as a best practice, I downloaded the latest version of AutoUpgrade tool, available at that time, I have placed it under $ORACLE_HOME/rdbms/admin (replacing the existing one). Well, as I already have a config file that I used for the same database family in DEV, I go for the same file, when I was executing the upgrade in TST environment, so I followed my internal notes expecting I would have the same behavior I had in DEV (success). But, clearly, it was not the case.

Then you start your database with the original OH, in my case 12cR2 (12.2), and execute the AutoUpgrade tool with mode ANALYZE to check you you have everything fine to proceed with the upgrade, I can tell you, the tool is very smart and detects a bunch of misconfiguration that can cause abend of the upgrade, and with mode FIXUPS you can fix many things. So, I ran the ANALYZE mode:

So, As I mentioned, the AutoUpgrade creates a restore point, it was really easy to revert the failed upgrade in minutes. So, I had a previous version that I used a couple of days before, and I used it, no issues on analyze mode for this database, and voil: the same error at the same point on the upgrade. I could immediately look to my own belly instead of blaming the tool and I started to dig a bit more based on the e-mail that I exchanged with Mike.

3a8082e126