Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
If there is a difference with the db_name parameter when opening the Oracle database, you receive an error as follows. “ORA-00205: error in identifying control file, check alert log for more info”
In the Alert log file, there are errors like ORA-00202 and ORA-01103.
If the DB_NAME parameter in the parameter file is corrected as it should, there will be no problems.
1 2 3 4 5 6 7 8 9 | SQL> startup ORACLE instance started. Total System Global Area 2.1475E+10 bytes Fixed Size 22787792 bytes Variable Size 3087010096 bytes Database Buffers 1.8321E+10 bytes Redo Buffers 44318720 bytes ORA-00205: error in identifying control file, check alert log for more info |
The errors in the Alert.log file will be as follows.
1 2 3 4 | 2019-06-18T20:39:50.213758+03:00 Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_m000_350626.trc: ORA-01103: database name 'ORCLì÷.' in control file is not 'ORCL' ORA-00202: control file: '+DATA/orcl/controlfile/current.480.947371313' |
Change DB_NAME Parameter To Solve the Error
To resolve the problem, the DB_NAME parameter must be set properly.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | SQL> STARTUP NOMOUNT; ORACLE instance started. Total System Global Area 2.1379E+10 bytes Fixed Size 2262384 bytes Variable Size 2550139536 bytes Database Buffers 1.8790E+10 bytes Redo Buffers 36073472 bytes SQL> ALTER SYSTEM SET DB_NAME=NEONATAL SCOPE=SPFILE sid='*'; System altered. SQL> SHUT IMMEDIATE; ORA-01507: database not mounted ORACLE instance shut down. |
The database will then open successfully.
1 2 3 4 5 6 7 8 9 10 | SQL> startup ORACLE instance started. Total System Global Area 2.1475E+10 bytes Fixed Size 22787792 bytes Variable Size 3087010096 bytes Database Buffers 1.8321E+10 bytes Redo Buffers 44318720 bytes Database mounted. Database opened. |
