Skip to main content

ORA-00214: Controlfile Version Inconsistent on Startup or Shutdown

This error is giving because Oracle detects an inconsistency between the mirrored copies of the control file.
All copies of the control file must have the same internal sequence number for oracle to start up the database.

Solution

To fix the error you have to start your database with single copy of the control file and then shut the database down and then copy the good copy of control file onto the other mirror copies.

Step 01 - If database is still up do a shutdown immediate.

Step 02 -
If you use pfile then edit the CONTROL_FILES parameter from init.ora and modify it to include just one copy of control file.
You may want to issue create pfile from spfile to create a pfile before editing this parameter.

Step 03 -
Start the database in restricted mode. startup restrict or mount the database. startup mount
If it is fine go to step 04.

Step 04 - Shut the database down.
SQL>shutown

Step 05 -
Copy the good mirrored copy of the control file that you just used to bring the database up onto all other copies, as originally listed in the CONTROL_FILES parameter of your init.ora file.

Step 06 -
Edit the init.ora file's CONTROL_FILES parameter to include all mirror copy again.
Issue create spfile from pfile command in SQL prompt if you are using spfile to start the database.

Step 07 -
Start the database.

Comments

Popular posts from this blog

Top 5 Performance Tuning Tricks Every Oracle DBA Should Know!

Performance tuning in Oracle Database often focuses on obvious areas like indexes, SQL rewrites etc. But some of the most impactful improvements can come from lesser known techniques. Here are 5 such tuning tricks that can make a real difference in production environments.   Use SQL Plan Baselines to Stabilize Performance Even properly tuned queries in Oracle Database can suddenly degrade when execution plans change due to statistics refreshes or system upgrades. Using SQL Plan Baselines helps maintain stable and efficient execution plans, preventing unexpected performance regressions especially in highly changing workloads. SELECT * FROM DBA_SQL_PLAN_BASELINES; So, don’t just capture baselines, but periodically change them to allow the optimizer to adopt better plans when appropriate. Use Automatic Indexing Automatic Indexing is a useful feature in Oracle Database that can improve performance with minimal effort.  It was introduced in Oracle Database 19c and enhance...

Setting ORACLE_SID

The  Oracle System ID  ( S ID ) is used to uniquely identify a particular database on a system How to set ORACLE_SID: Windows: set ORACLE_SID=orcl Unix/ Linux: export ORACLE_SID=orcl SID is case sensitive in Unix / Linux environments. How to check the current ORACLE_SID: Windows: Go to the commnand prompt and type as C:\> set ORACLE_SID (This will show if any ORACLE_SID is already set). C:\> set (To know all the parameters set) Unix/ Linux: echo $ORACLE_SID

Building Continuous Data Trust with Oracle GoldenGate Veridata 26c

Today I'll discus on how we can build continuous data trust with Oracle GoldenGate Veridata 26c! As we accelerate towards hybrid and multi cloud architectures , one challenge keep coming up. That is "H ow do you trust your data across all these platforms?" With increasing data movement, replication, and transformation, even small changes can lead to major business risks. This is where Oracle GoldenGate Veridata 26c comes in handy! Rather than just validating data occasionally, the focus now is on continuous data trust . What is Veridata? It is a tool to compare data across different systems. It ensures source and target databases are in sync. It works during , Data migration, Replication setups, Ongoing operations. What’s new in Veridata 26c? 1. Support for Modern Architectures Built for hybrid, multi-cloud, and lakehouse environments with support for heterogeneous databases. 2. Continuous Data Validation Enables ongoing validation to detect data drift and inconsisten...