Email: service@parnassusdata.com 7 x 24 online support!

    You are here

    • You are here:
    • Home > Blogs > PDSERVICE's blog > Oracle 在崩溃后打开数据库生成ORA-1122 ORA-01122: 数据库文件 验证失败, ORA-1110, ORA-01207: 文件比控制文件更新 - 旧的控制文件

Oracle 在崩溃后打开数据库生成ORA-1122 ORA-01122: 数据库文件 验证失败, ORA-1110, ORA-01207: 文件比控制文件更新 - 旧的控制文件

Oracle 在崩溃后打开数据库生成ORA-1122 ORA-01122: 数据库文件 验证失败, ORA-1110, ORA-01207: 文件比控制文件更新 - 旧的控制文件

如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!

诗檀软件专业数据库修复团队

服务热线 : 13764045638 QQ号:47079569 邮箱:service@parnassusdata.com

 

ORA-01122: 数据库文件  验证失败

oerr ora 1122
01122, 00000, "database file %s failed verification check"
// *Cause:  The information in this file is inconsistent with information
//         from the control file. See accompanying message for reason.
// *Action: Make certain that the db files and control files are the correct
//         files for this database.
 
ORA-01207: 文件比控制文件更新 - 旧的控制文件
 
oerr ora 1207
01207, 00000, "file is more recent than control file - old control file"
// *Cause:  The control file change sequence number in the data file is 
//         greater than the number in the control file. This implies that
//         the wrong control file is being used. Note that repeatedly causing
//         this error can make it stop happening without correcting the real
//         problem. Every attempt to open the database will advance the
//         control file change sequence number until it is great enough.
// *Action: Use the current control file or do backup control file recovery to 
//         make the control file current. Be sure to follow all restrictions 
//         on doing a backup control file recovery.
 

 

 

适用于:

Oracle Database – Enterprise Edition – 版本8.0.3.0 及以上
本文信息适用于任何平台。

症状

ORA-1122 :database file %s failed verification check
ORA-1110 : datafile :
ORA-1207: ORA 1207 file is more recent than control file

原因

本文信息与控制文件的信息不一致。
数据文件头CHECKPOINT 计数超过控制文件CHECKPOINT计数。

解决方案

1.Mount数据库
SQL> Startup mount

2. 保存控制文件中的信息:

SQL> Alter database backup controlfile to trace;

3. 通过user_dump_dest中生成的跟踪文件创建control file creation脚本。

使用Noresetlogs选项

4. 关闭数据库并在NOMOUNT 模式下启动它

SQL> shutdown abort
SQL> startup nomount

5. 创建控制文件

使用以上‘backup controlfile to trace’ 命令生成的脚本。

请参见:
Note 735106.1 – How to Recreate a Controlfile

6.恢复数据库

SQL> recover database;

7. 打开数据库

SQL> Alter database open;

参考

NOTE:735106.1 – How to Recreate a Controlfile