Oracle Database - Enterprise Edition - version 11.2.0.4.0
Symptoms
SQL> startup ORACLE instance started.
Total SystemGlobal Area 1286066176 bytes Fixed Size 2246032 bytes Variable Size 822086256 bytes Database Buffers 452984832 bytes Redo Buffers 8749056 bytes ORA-00205: error in identifying control file, check alert log for more info
alter_orcl.log:
Sat Nov 08 23:04:14 2025 Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_m000_5308856.trc (incident=4956): ORA-00227: corrupt block detected in control file: (block 1, # blocks 1) ORA-00202: control file: '/u01/app/oracle/oradata/orcl/control02.ctl' ORA-00227: corrupt block detected in control file: (block 1, # blocks 1) ORA-00202: control file: '/u01/app/oracle/oradata/orcl/control01.ctl' Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_4956/orcl_m000_5308856_i4956.trc
Solution
SQL>!ls -l /u01/app/oracle/oradata/orcl/ total 3351448 -rw-r----- 1 oracle oinstall 7716864 Nov 06 21:09 control01.ctl -rw-r----- 1 oracle oinstall 7716864 Nov 06 21:09 control02.ctl -rw-r----- 1 oracle oinstall 52429312 Nov 06 02:19 redo01.log -rw-r----- 1 oracle oinstall 52429312 Nov 06 21:00 redo02.log -rw-r----- 1 oracle oinstall 52429312 Nov 06 21:09 redo03.log -rw-r----- 1 oracle oinstall 566239232 Nov 06 21:05 sysaux01.dbf -rw-r----- 1 oracle oinstall 786440192 Nov 06 21:05 system01.dbf -rw-r----- 1 oracle oinstall 104865792 Nov 06 21:05 tbs_demo_1.dbf -rw-r----- 1 oracle oinstall 30416896 Nov 06 01:59 temp01.dbf -rw-r----- 1 oracle oinstall 78651392 Nov 06 21:05 undotbs01.dbf -rw-r----- 1 oracle oinstall 5251072 Nov 06 21:05 users01.dbf
According to the actual situation, fill in the data path, archiving mode, character set, etc.
Found some information in alert_.log and init.ora file.
-- The following are current System-scope REDO Log Archival related -- parameters and can be included in the database initialization file. -- -- LOG_ARCHIVE_DEST='' -- LOG_ARCHIVE_DUPLEX_DEST='' -- -- LOG_ARCHIVE_FORMAT=%t_%s_%r.dbf -- -- DB_UNIQUE_NAME="coco" -- -- LOG_ARCHIVE_CONFIG='SEND, RECEIVE, NODG_CONFIG' -- LOG_ARCHIVE_MAX_PROCESSES=4 -- STANDBY_FILE_MANAGEMENT=MANUAL -- STANDBY_ARCHIVE_DEST=?/dbs/arch -- FAL_CLIENT='' -- FAL_SERVER='' -- -- LOG_ARCHIVE_DEST_1='LOCATION=/arch001/coco' -- LOG_ARCHIVE_DEST_1='OPTIONAL REOPEN=300 NODELAY' -- LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM NOEXPEDITE NOVERIFY SYNC' -- LOG_ARCHIVE_DEST_1='REGISTER NOALTERNATE NODEPENDENCY' -- LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED NODB_UNIQUE_NAME' -- LOG_ARCHIVE_DEST_1='VALID_FOR=(PRIMARY_ROLE,ONLINE_LOGFILES)' -- LOG_ARCHIVE_DEST_STATE_1=ENABLE -- -- Below are two sets of SQL statements, each of which creates a new -- control file and uses it to open the database. The first set opens -- the database with the NORESETLOGS option and should be used only if -- the current versions of all online logs are available. The second -- set opens the database with the RESETLOGS option and should be used -- if online logs are unavailable. -- The appropriate set of statements can be copied from the trace into -- a script file, edited as necessary, and executed when there is a -- need to re-create the control file. -- -- Set #1. NORESETLOGS case -- -- The following commands will create a new control file and use it -- to open the database. -- Data used by Recovery Manager will be lost. -- Additional logs may be required for media recovery of offline -- Use this only if the current versions of all online logs are -- available. -- After mounting the created controlfile, the following SQL -- statement will place the database in the appropriate -- protection mode: -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "COCO" NORESETLOGS ARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 292 LOGFILE GROUP1'/database/datafile/coco/redo01.log' SIZE 50M BLOCKSIZE 512, GROUP2'/database/datafile/coco/redo02.log' SIZE 50M BLOCKSIZE 512, GROUP3'/database/datafile/coco/redo03.log' SIZE 50M BLOCKSIZE 512 -- STANDBY LOGFILE DATAFILE '/database/datafile/coco/system01.dbf', '/database/datafile/coco/sysaux01.dbf', '/database/datafile/coco/undotbs01.dbf', '/database/datafile/coco/users01.dbf', '/database/datafile/coco/tbs_coco01.dbf' CHARACTER SET ZHS16GBK ; -- Commands to re-create incarnation table -- Below log names MUST be changed to existing filenames on -- disk. Any one log file from each branch can be used to -- re-create incarnation records. -- ALTER DATABASE REGISTER LOGFILE '/arch001/coco/1_1_1091481483.dbf'; -- ALTER DATABASE REGISTER LOGFILE '/arch001/coco/1_1_1102940485.dbf'; -- Recovery is required if any of the datafiles are restored backups, -- or if the last shutdown was not normal or immediate. RECOVER DATABASE -- All logs need archiving and a log switch is needed. ALTERSYSTEM ARCHIVE LOG ALL; -- Database can now be opened normally. ALTER DATABASE OPEN; -- Commands to add tempfiles to temporary tablespaces. -- Online tempfiles have complete space information. -- Other tempfiles may require adjustment. ALTER TABLESPACE TEMP ADD TEMPFILE '/database/datafile/coco/temp01.dbf' REUSE; -- End of tempfile additions. -- -- Set #2. RESETLOGS case -- -- The following commands will create a new control file and use it -- to open the database. -- Data used by Recovery Manager will be lost. -- The contents of online logs will be lost and all backups will -- be invalidated. Use this only if online logs are damaged. -- After mounting the created controlfile, the following SQL -- statement will place the database in the appropriate -- protection mode: -- ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "COCO" RESETLOGS ARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 3 MAXDATAFILES 100 MAXINSTANCES 8 MAXLOGHISTORY 292 LOGFILE GROUP1'/database/datafile/coco/redo01.log' SIZE 50M BLOCKSIZE 512, GROUP2'/database/datafile/coco/redo02.log' SIZE 50M BLOCKSIZE 512, GROUP3'/database/datafile/coco/redo03.log' SIZE 50M BLOCKSIZE 512 -- STANDBY LOGFILE DATAFILE '/database/datafile/coco/system01.dbf', '/database/datafile/coco/sysaux01.dbf', '/database/datafile/coco/undotbs01.dbf', '/database/datafile/coco/users01.dbf', '/database/datafile/coco/tbs_coco01.dbf' CHARACTER SET ZHS16GBK ; -- Commands to re-create incarnation table -- Below log names MUST be changed to existing filenames on -- disk. Any one log file from each branch can be used to -- re-create incarnation records. -- ALTER DATABASE REGISTER LOGFILE '/arch001/coco/1_1_1091481483.dbf'; -- ALTER DATABASE REGISTER LOGFILE '/arch001/coco/1_1_1102940485.dbf'; -- Recovery is required if any of the datafiles are restored backups, -- or if the last shutdown was not normal or immediate. RECOVER DATABASE USING BACKUP CONTROLFILE -- Database can now be opened zeroing the online logs. ALTER DATABASE OPEN RESETLOGS; -- Commands to add tempfiles to temporary tablespaces.
***2023-11-2513:37:44.097 -- Online tempfiles have complete space information. -- Other tempfiles may require adjustment. ALTER TABLESPACE TEMP ADD TEMPFILE '/database/datafile/coco/temp01.dbf' REUSE; -- End of tempfile additions. --
