Feb 03 2010

ORA-01122: database file xxx failed verification check

Error Message :
SQL> startup
ORACLE instance started.

Total System Global Area 2264924160 bytes
Fixed Size 2022408 bytes
Variable Size 150995960 bytes
Database Buffers 2097152000 bytes
Redo Buffers 14753792 bytes
Database mounted.
ORA-01122: database file 10 failed verification check
ORA-01110: data file 10: ‘/opt/oracle/xxxxx/xxxxx.dbf’
ORA-01207: file is more recent than control file – old control file

Suggestion:

1. Take a trace of controlfile.

SQL > alter database backup controlfile to trace;

2. You can find the file in userdump dest. Open the trace file and edit for neccesary changes.

You can create control file script using two methods depends on RESETLOGS/NORESETLOGS

3. Startup the database in nomount state.

SQL > startup nomount

4. Run the controlfile script create in step 2

SQL > @cfile.sql

5. Recover the db

SQL > recover database using backup controlfile

6. Open the database.

SQL > alter database open;

—– Recover and Open Database command varies depends on the method you are using to create control file. Best option is alwasy read through your Trace file.

For NORESETLOGS – You have to use the following Command
RECOVER DATABASE
ALTER DATABASE OPEN;
ALTER TABLESPACE TEMP ADD TEMPFILE ‘/xxx/xxxx/Temp01.dbf’ REUSE;

For RESETLOGS – You have to use the following Command
RECOVER DATABASE USING BACKUP CONTROLFILE
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE TEMP ADD TEMPFILE ‘/xxx/xxxx/Temp01.dbf’ REUSE;

One Response to “ORA-01122: database file xxx failed verification check”

  1. mudhalvan says:

    The above explained syntax went well and database is opened. I have used the NORESETLOGS but when using shutdown immediate i am getting following error.

    SQL> shutdown immediate
    ORA-00607: Internal error occurred while making a change to a data block
    ORA-00600: internal error code, arguments: [4193], [6179], [6757], [], [], [],
    [], []

    and database process get killed automatically.

    After check the document I understand it is because of inconsistent backup method so i should have went with RESETLOGS option.

Alibi3col theme by Themocracy