My Oracle Support Banner

After Rollback 12.1.0.2.3 or Later GIPSU, Applying Database Patch Fails With CRS-2922 at Postpatch Step (Doc ID 2131772.1)

Last updated on FEBRUARY 18, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Note: This document applies to environment specifically whose current clusterware patch level is between 12.1.0.2.0 and 12.1.0.2.2 OCWPSU, and once 12.1.0.2.3 OCWPSU or later is applied and rolled back.
In most case, you will notice problem after rolled back GIPSU and try to apply database patch before applying GIPSU.

If your current clusterware patch level is 12.1.0.2.3 OCWPSU or later, you cannot try steps written in this note.

 On 12.1.0.2, clusterware environment.

Applying database patch on Grid home fails with following error

 But this environment has special characteristic described below.

Changes

 In this Grid home, GIPSU 12.1.0.2.3 or later is applied and rolled back to become pre 12.1.0.2.3 OCWPSU version.

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.