Share this article
Improve this guide
OPatch Failed With Error Code 73? How to Fix it
Make sure the updates apply to the current installation
4 min. read
Updated onOctober 4, 2023
updated onOctober 4, 2023
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
Oracle is a popularRelational Database Management System (RDBMS)developed by the Oracle Corporation. It’s used extensively worldwide, but some administrators came acrossOPatch failed with error code 73while installing a patch or during an Oracle upgrade.
The problem is widely reported for certain updates, but it’s usually an issue at the user’s end to blame for the inability to apply interim patches.
For those wondering what is error code 73, it indicates that the patch is incompatible with the current installation or another process is blocking it. Here are the common reasons behind it:
How do I fix OPatch failed with error code 73?
Before we head to the slightly complex solutions, try these quick ones first:
If none work, move to the fixes listed next.
1. Terminate all other Oracle processes
Often, when you seeOPatch failed with error code 73 19c, it’s another Oracle process to blame, and terminating it should get things running.
2. Reconfigure the permissions
Alternatively, you could modify the ownership for the subdirectory oforaInventoryand configure it correctly.
3. Re-register Oracle Home
WhenOPatch LsInventoryreturns theOPatch failed with error code 73message, it’s likely that we are pointing to an incorrect OPatch inventory location or that Oracle Home is not attached to it.
To fix things, run the following commands:% cd $ORACLE_HOME/oui/bin %./attachHome.sh
4. Manually move the files
When the CPU patches are not being installed, manually move the following files from the OPatch installation directory to the dedicated OPatch directory:
5. Change the location of Oracle Home
A system administrator reported getting theOPatch failed with error code 73message with Weblogic 12c when Oracle Home was not set up correctly. Simply changing its location did the trick.
It should initially be in:/oracle/DRD/11203
Move Oracle Home to:/oracle/DRD/112_64
And do make sure that theORACLE_HOMEenvironment variable is stored in the same directory as Oracle.
6. Use the ignoreSysPrereqs switch
7. Contact Oracle support
When nothing else works, the last option is tocontact Oracle support. Maybe it’s a bug in the latest patch, and if others, too, have reported the same, the support team would know.
Even otherwise, they are well equipped to handle such queries and know what issues could trigger theOPatch failed with error code 73message.
While there are a lot of underlying causes behind the error, including a few patch conflicts, things are usually easy to fix.
Remember, it’s better to download updates over a stable andfast Internet connectionto avoid missing critical files or corrupting any in the process.
Tell us what helped you fix the error in the comments section below.
More about the topics:installation error,Oracle
Kazim Ali Alvi
Windows Hardware Expert
Kazim has always been fond of technology, be it scrolling through the settings on his iPhone, Android device, or Windows PC. He’s specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
Long-time Windows user, Kazim is ready to provide a solution for your every software & hardware error on Windows 11, Windows 10 and any previous iteration. He’s also one of our experts in Networking & Security.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Kazim Ali Alvi
Windows Hardware Expert
Kazim is specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem.
Reviewed byAlex Serban
