Programming

OPatch Failed with Error Code 73 – Explained

The error message ‘OPatch failed with error code 73’ is an Oracle database error and it mostly occurs while installing or applying a patch.

OPatch Failed with Error Code 73 (Title Image)

Variations of ‘OPatch Failed with Error Code 73’ Error Message:

This error message has several variations; therefore, it occurs in various other scenarios with different forms. So, let’s see those variations first before getting to the fix of this error message. Because, this way, you can easily relate to your use case and solve the ‘OPatch failed with error code 73’ error message.

  • Sometimes, this error code occurs while running the command OPatch lsinventory. In this case, the users have reported the error message in the following way:
OPatch failed with error code 73 Isinventory
  • In some cases, this error code occurs while upgrading the OJVM from version 19.3 to 19.7 and applying the patch ‘30805684: OJVM RELEASE UPDATE 19.7.0.0.0. In that case, the users have reported the following issue with this error message:
Prerequisite check ‘CheckActiveFilesAndExecutables’ failed

OPatch failed with error code 73 utilsession failed
  • Sometimes, this error message occurs while installing the SBP of 11024. In this case, the error code shows the following message:
LsInventorySession failed: OPatch failed to locate Central Inventory.
  • In some cases, this error message occurs while applying the patch number 29859180 on a system running Windows operating system. In that case, users have reported the following error message:
OPatch failed with error code = 73 Windows 2012 r2

OPatch failed with error code = 73 windows 2016

OPatch failed with error code 73 windows
  • Sometimes, users have faced this error message while trying to fix the security vulnerabilities for Oracle WebLogic on the Windows system. In that case, the users have reported the following error message:
OPatch failed with error code 73 WebLogic 12.2.1.4
  • In some cases, users have faced this error message while trying to apply WLS patches on a Windows server. In this case, the system gives the following error message:
OPatch failed to locate Central Inventory
  • Sometimes, users have faced this error message while upgrading Oracle from version 10 to 11.2.0.3.1.

What Causes this Error Message?

  • If this error message occurs in Oracle Home, then one of the following can be the probable causes of this issue.
    • Oracle Home dir. path does not exist in Central Inventory.
    • Oracle Home is a symbolic link.
    • Oracle Home inventory is corrupted.
  • If this error message occurs while upgrading the patch of OJVM from version 19.3 to 19.7, then this error could be due to an already connected session to sqlplus binaries.
  • If this error message occurs while installing the SBP of 11204, then one of the following can be the cause of this issue.
    • Corruption of Central Inventory.
    • The ‘oraInst.loc’ file specified is not valid.

How to Solve OPatch Failed with Error Code 73?

Changing the Oracle Home Location

verified solution

As mentioned, sometimes this error message can also occur due to the improper location of the Oracle Home. So, if your inventory load has failed and OPatch is unable to load inventory for the given Oracle Home, then check whether your Oracle Home location is correctly set or not. If not, then change it and your error message will be fixed.

Talha Saeed

I am a BSCS graduate and a technology nerd who now loves working and writing about computers and other tech-related stuff. In my free time, I like watching Netflix and playing Cricket 22 and The Witcher 3 (Wild Hunt).
Back to top button