Error
While starting an Oracle RAC database using srvctl, the startup failed with:
PRCR-1079: Failed to start resource ora.RACDB.db
CRS-5076: Startup of database resource ‘ora.RACDB.db’ is failing because
DB_UNIQUE_NAME ‘RAC_DB’ is not expected
Description
This error occurs when there is a mismatch between the DB_UNIQUE_NAME stored in Oracle Clusterware (OCR) and the DB_UNIQUE_NAME defined in the database SPFILE.
Oracle Clusterware strictly validates this parameter during database startup. If the value in the SPFILE does not match the value registered in OCR metadata, Clusterware blocks the startup and raises CRS-5076.
In this case:
| Component | Value |
| DB registered in Clusterware | RACDB |
| db_unique_name in SPFILE | RAC_DB |
Because these values differ, Clusterware refused to start the database.
Follow the steps to resolve the cluster error:-
Step 1 – Error During Startup
srvctl start database -d RACDB
Error observed:
- PRCR-1079
- CRS-5076
- CRS-2674 / CRS-2632 (resource placement failure)
Both RAC instances failed to start.
Step 2 – Verify DB_UNIQUE_NAME in Clusterware and Database
Check Clusterware configuration:
$ srvctl config database -d RACDB -a
Database unique name: RACDB
Database name:
Oracle home: /opt/oracle/product/19.0.0.0
Oracle user: oracle
Spfile: +DATA02/RACDB/PARAMETERFILE/spfileracdb.ora
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Database instances: RACDB1 , RACDB2
Disk Groups: RACDB1, RACDB1
Mount point paths:
Services:
Type: RAC
Database is enabled
Database is administrator managed
ORACLEHOST01(RACDB1)$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 – Production on Fri Jan 23 10:15:42 2026
Version 19.22.0.0.0
Copyright (c) 1982, 2024, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 – Production
Version 19.22.0.0.0
SQL> show parameter unique
NAME TYPE VALUE
———————————— ———– ——————————
db_unique_name string RAC_DB
Step 3 – Re-register Database with Correct DB_UNIQUE_NAME
Since the SPFILE value is correct, Clusterware configuration must be corrected.
ORACLEHOST01(RACDB1)$ srvctl remove database -d RACDB
Remove the database RACDB? (y/[n]) y
Database RACDB removed
ORACLEHOST01(RACDB1)$ srvctl add database -d RAC_DB -oraclehome /usr/local/oracle/19.3.0.0 -spfile +DATA02/RACDB/PARAMETERFILE/spfileracdb.ora
ORACLEHOST01(RACDB1)$ srvctl add instance -d RAC_DB -instance RACDB1 -node ORACLEHOST01
ORACLEHOST01(RACDB1)$ srvctl add instance -d RAC_DB -instance RACDB1 -node ORACLEHOST02
Step 4 – Start the Database
Shut down the database from both a node by manually and start with srvctl command.
ORACLEHOST01 (RACDB1)$ srvctl start database -d RAC_DB
ORACLEHOST01(RACDB1)$ srvctl status database -d RACDB
Instance RACDB1 is running on node ORACLEHOST01
Instance RACDB2 is running on node ORACLEHOST02
Conclusion: –
The issue was caused by a DB_UNIQUE_NAME mismatch between:
- Oracle Clusterware configuration (OCR)
- Database initialization parameter (SPFILE)
Oracle RAC enforces strict validation of db_unique_name. When values differ, database startup fails with CRS-5076.
