Oracle ORA-1122, ORA-1110, ORA-1207 file is more recent than control File Processing Method

 

When starting the database, we may encounter the following errors:

ORA-1122: database file % s failedverification check

A ORA-1110: datafile:

ORA-1207: ora 1207 file is more recent thancontrol File

 

The main reason for the ORA-1207 is that the database suddenly loses power, when the restart, it will be easy to encounter this error.

 

The following is an explanation of this error on MOS:

The informationin this file is inconsistent with information from the control file.

The datafileheader checkpoint count is beyond the controlfile checkpoint count.

The control file records all information about the entire database, including data files and log files.

 

During database operation, control files will be constantly updated due to check points and other reasons. At the same time, the control files will be updated during database shutdown and restart, but the database server suddenly loses power, the current database information cannot be updated to the control file in a timely manner. After the database is started again, this error occurs when Oracle checks whether the control file information is consistent with other files.

 

The solution provided on MOS is to recreate the control file:

 

1. Mount the database
SQL> startup Mount

2. Save the information from the control file:
SQL> alter Database Backup controlfile to trace;

3. Create a control file creation script from the tracefile generated inuser_dump_dest.

Use the noresetlogs Option

-- Note that noresetlogs is used here.

 

4. shutdown the database and start it in nomount Mode

SQL> shutdown abort
SQL> startup nomount

5. Create the control file
Use the script generated by the 'backup controlfile to track' commandabve.

Please refer:
Note735106.1-how to recreate a controlfile

6. Recover the database
SQL> recover database;

7. Open the database
SQL> alter database open;

 

Note:

Here, we back up the contents of the control file to the trace file on the premise that the database must be in the mount or open state. If it doesn't even work with the mount, we will be in trouble to generate the control file.

SQL> alter Database Backup controlfileto trace;

Description in [ID 735106.1] of MOS:

If there is no control file content, we also have two ways to handle ORA-1207 errors, one is to use restore, the other is to retrieve control files from backup, if none of these two items exist, we must manually write the control file content.

 

The content of the control file is in a certain format, and we only need to create it according to the specified format.

 

For details, refer:

Oracle Control File

Http://blog.csdn.net/tianlesoftware/article/details/4974440

 

 

After recreating the control file, we need to add the temp tablespace and check whether there is a read-only tablespace, because the reconstruction control file will affect the two tablespaces. For more information, see:

Test the impact of Oracle reconstruction control file on read-only and temporary tablespaces

Http://blog.csdn.net/tianlesoftware/article/details/7231680

 

 

 

Refer:

How to recreate a controlfile [ID 735106.1]

ORA-1122, ORA-1110, ORA-1207 while open thedatabase after crash [ID 283927.1]

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Skype: tianlesoftware

QQ: tianlesoftware@gmail.com

Email: tianlesoftware@gmail.com

Blog: http://www.tianlesoftware.com

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

LinkedIn: http://cn.linkedin.com/in/tianlesoftware

 

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940