My Oracle Support Banner

PROT-23: failed to back up Oracle Cluster Registry during clusterware upgrade (Doc ID 2600174.1)

Last updated on JULY 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 18.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Exadata  RAC with 8 DB nodes.

Upgrading the clusterware from 12.2 to 18c and rootupgrade fails in the first as below.

rootupgrade.sh output:

-----------------------

 

root@Node1 grid]# ./rootupgrade.sh
Performing root user operation.

The following environment variables are set as:
  ORACLE_OWNER= oracle
  ORACLE_HOME= /<19c_GI_HOME>

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Relinking oracle with rac_on option
Using configuration parameter file: /19c_GI_HOME>/crs/install/crsconfig_params
The log of current session can be found at:
 /<ORACLE_BASE>/crsdata/Node1/crsconfig/rootcrs_Node1_2019-10-13_11-38-54PM.log
2019/10/13 23:39:02 CLSRSC-595: Executing upgrade step 1 of 18: 'UpgradeTFA'.
2019/10/13 23:39:02 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.
2019/10/13 23:39:02 CLSRSC-4012: Shutting down Oracle Trace File Analyzer (TFA) Collector.
2019/10/13 23:40:42 CLSRSC-4013: Successfully shut down Oracle Trace File Analyzer (TFA) Collector.
2019/10/13 23:40:42 CLSRSC-595: Executing upgrade step 2 of 18: 'ValidateEnv'.
2019/10/13 23:40:43 CLSRSC-595: Executing upgrade step 3 of 18: 'GetOldConfig'.
2019/10/13 23:40:43 CLSRSC-464: Starting retrieval of the cluster configuration data
2019/10/13 23:40:49 CLSRSC-692: Checking whether CRS entities are ready for upgrade. This operation may take a few minutes.
2019/10/13 23:40:54 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.
2019/10/13 23:42:27 CLSRSC-693: CRS entities validation completed successfully.
2019/10/13 23:42:33 CLSRSC-515: Starting OCR manual backup.
PROT-23: failed to back up Oracle Cluster Registry<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
PROC-60: The Oracle Cluster Registry backup file '<+DG_NAME>/Node1/OCRBACKUP/Node1_backup18.0.0.0.0.ocr.438.1021592566' is corrupt.
2019/10/13 23:42:43 CLSRSC-183: OCR manual backup operation failed (error code 60)
Died at <GI_HOME/crs/install/oraocr.pm line 1541.

Able to execute ocrcheck successfully without any issues.

issue still persists even after restarting the CRS and local Node.

Changes

 

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


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