My Oracle Support Banner

Error When Applying DB Update During ODA Patching (Doc ID 2245250.1)

Last updated on MARCH 07, 2022

Applies to:

Oracle Database Appliance - Version All Versions and later
Information in this document applies to any platform.


While Applying the DB update using the below command

oakcli update -patch <version> --database -local

it could fail with below errors

INFO: 2017-03-09 08:49:54: Applying patch on <DB_HOME> Homes
INFO: 2017-03-09 08:49:54: It may take upto 15 mins. Please wait...
ERROR: 2017-03-09 08:50:12: Unable to apply db patch on the following Homes : <DB_HOME>
SUCCESS: 2017-03-09 08:50:12: Successfully started the Database consoles
SUCCESS: 2017-03-09 08:50:12: Successfully started the EM Agents

INFO: patching summary on local node
ERROR: 2017-03-09 08:50:15: Unable to apply the patch on <DB_HOME>

INFO: Executing /tmp/pending_actions on local node


 If you look at the actual patch update log(dbupdate_xxxxx.log) the errors reported are

> System initialization log file is <DB_HOME>/cfgtoollogs/opatchautodb/systemconfig2017-03-09_08-49-55AM.log.
> Failed:
> Verifying shared storage accessibility
> User equivalence is not set for nodes:
> Verification will proceed with nodes:
> Checking shared storage accessibility...
> "<DB_HOME>" is shared
> Shared storage check was successful on nodes "<HOSTNAME>2"
> Verification of shared storage accessibility was unsuccessful.
> Checks did not pass for the following node(s):
> The result of cluvfy command contain EFAIL NODE_STATUS::<HOSTNAME>1:EFAIL
> OPATCHAUTO-72050: System instance creation failed.
> OPATCHAUTO-72050: Failed while retrieving system information.
> OPATCHAUTO-72050: Please check log file for more details




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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