Oracle Technical Track

ORA-01206: File is not part of this database - wrong database id

1 min read

Jun 15, 2007 12:00:00 AM

This was posted yesterday on Oracle-L by Li Li. I feel I should blog about it to spread the word, especially since not everyone in this world performs test-restores. Li was executing a test-restore and hit a problem at the end of the point-in-time recovery phase:

ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
 ORA-01122: database file 9 failed verification check 
 ORA-01110: data file 9: 'H:\xxx\xxx\xxx.dbf'
 ORA-01206: file is not part of this database - wrong database id

Datafile 9 was a read-only tablespace, and the source database was actually created with RMAN DUPLICATE. Datafile 9 was read-only during that duplicate operation, and the status hadn't changed since then. As you can imagine, the read-only datafiles were not changed and their headers still contained the DBID of the database that was the source of the RMAN DUPLICATE. A similar situation could probably happen if tablespaces were imported using transportable tablespaces feature, and left read only. The fix in this case is to make tablespaces read-write for a moment, and then change back to read-only. The read-write operation will write new datafile headers and, consequently, put there the "right" DBID. IMPORTANT -- this has to be done before backup and not after a disaster strikes. This case just emphasizes again the most important rule of any backup/recovery strategy is to do regular test-restores. If it's too late and something hit the fan -- well, you probably have a chance to offline drop those tablespaces and, hopefully, be able to import them back, if those are transportable tablespaces, and the metadata dump file is still available. Another idea would be to offline datafiles and then online them after OPEN RESETLOGS. Should someone try that -- let us know if it works.

On this page

Ready to unlock value from your data?

With Pythian, you can accomplish your data transformation goals and more.

Speak with Pythian consultants now →

What We Do

ORA-01206: File is not part of this database - wrong database id

Share this

Share this

More resources

Opening the Door Without the Keys

Data Guard Broker—ORA-16714: The Value of Property LogFileNameConvert Is Inconsistent with the Database Setting

Oracle Database 12c: Network Recovery in RMAN

Ready to unlock value from your data?