My Oracle Support Banner

ODA Patching From 18.X to 18.7 Can Fail as One Node May End Up in a Rolling Status (Doc ID 2655543.1)

Last updated on FEBRUARY 08, 2022

Applies to:

Oracle Database Appliance Software - Version 18.3.0.0.0 ODAVP to 18.7.0.0.0 ODAVP [Release 12.2]
Information in this document applies to any platform.

Symptoms

When upgrade from 18.X to 18.7 on ODA GI Patching completed successfully, but CRS status did not return to Normal mode.

Further investigation shows that kfod op=patches output had one extra patch on node0 even though opatch lspatches outputs were identical.

For Example: one node output using kfod op=patches has 28887509 but the other node does not.

Changes

 Upgrade from 18.X -> 18.7

Cause

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
Symptoms
Changes
Cause
Solution
References


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