Error When Applying DB Update During ODA Patching

Asset ID:	1-72-2245250.1
Update Date:	2017-03-19
Keywords:

Solution Type Problem Resolution Sure

Solution 2245250.1 : Error When Applying DB Update During ODA Patching

Applies to:

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

Symptoms

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 /u01/app/oracle/product/12.1.0.2/dbhome_1 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 : /u01/app/oracle/product/12.1.0.2/dbhome_1
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 /u01/app/oracle/product/12.1.0.2/dbhome_1

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 /u01/app/oracle/product/12.1.0.2/dbhome_1/cfgtoollogs/opatchautodb/systemconfig2017-03-09_08-49-55AM.log.
>
> Failed:
> Verifying shared storage accessibility
>
> WARNING:
> User equivalence is not set for nodes:
> oda0
> Verification will proceed with nodes:
> oda1
>
> Checking shared storage accessibility...
>
> "/u01/app/oracle/product/12.1.0.2/dbhome_1" is shared
>
>
> Shared storage check was successful on nodes "oda1"
>
> Verification of shared storage accessibility was unsuccessful.
> Checks did not pass for the following node(s):
> oda0
> NODE_STATUS::oda1:SUCC
> NODE_STATUS::oda0:EFAIL
> The result of cluvfy command contain EFAIL NODE_STATUS::oda0:EFAIL
> OPATCHAUTO-72050: System instance creation failed.
> OPATCHAUTO-72050: Failed while retrieving system information.
> OPATCHAUTO-72050: Please check log file for more details

Cause

This is caused due to missing SSH user equivalence for the oracle user. In this case from oda1 to oda0 server.

Solution

You need to make sure that the SSH user equivalence is set correctly for the oracle user.

Run the below command as oracle user to verify,

$cluvfy comp admprv -n all -o user_equiv -verbose

If there are any errors, please refer to the below document to re-setup SSH user equivalence for the oracle user

How to reconfig ssh user equivalence Setup Post-Installation on ODA (Doc ID 1568647.1)

References

<NOTE:1568647.1> - How to reconfig ssh user equivalence Setup Post-Installation on ODA

Attachments

This solution has no attachment