ORA-01221错误解析

该ORA-01221错误常见于版本8i，10g之后较少出现。

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

服务热线： 13764045638 QQ号:47079569 邮箱：[email protected]

Error:  ORA 1221 
Text:   datafile <name> is not the same file to a background process 
-------------------------------------------------------------------------------
Cause:  When the database writer opens the datafile, it is accessing a 
        different physical file than the foreground doing the recovery.
        The time-stamp set in the file header by the foreground was not found 
        by the background.
        It may be that the background process could not read the file at all.
Action: Look in the DBWR trace file for the error it received when attempting 
        to read the file header.
        Reconfigure the operating system as needed to have the filename 
        successfully access the same file when opened by a background process.

Hdr: 4395739 10.1.0.3 RDBMS 10.1.0.3 RECOVERY PRODID-5 PORTID-219 ORA-1221
Abstract: AFTER RESIZING A DATAFILE, OTHER DATAFILE IS CORRUPT ORA-1237 ORA-1221

If datafile is resized beyond space available, error occurs, database crashes
and a different datafile shows ORA-1221 corruption

Hdr: 706775 8.0.3.2.0 RDBMS 8.0.3.2.0 PRODID-5 PORTID-89 ORA-1221
Abstract: ORA-470, ORA-449 AND ORA-1221 ON STARTUP


Symptom(s)
~~~~~~~~~~

When recreating a controlfile, you receive the following errors:

ORA-01503: CREATE CONTROLFILE failed
ORA-01227: log  is inconsistent with other logs

When trying to open the database after a failed controlfile creation you may receive:

ORA-01221: data file 1 is not the  same file to a background process


Change(s)
~~~~~~~~~~

You issued exec sys.dbms_backup_restore.zerodbid(fno => 0) while the database was open.


Cause
~~~~~~~
Database Corruption Will Occur During the Cloning Process when the Above Command 
is Performed with the Database Mounted.

The function dbms_backup_recovery.zeroDbid must never be invoked while the database is open 
as this could damage it (impossible to mount and dismount the database).

(Internal Note)





Fix
~~~~

Recreate the controlfile with the SET DATABASE option:

CREATE CONTROLFILE REUSE SET DATABASE "RPT1" RESETLOGS ARCHIVELOG

Comments

Leave a Reply Cancel reply