alter database force open with _ALLOW_RESETLOGS_CORRUPTION = TRUE

This is a two-part question.

I have a partially restored database where I have some new, and some older datafiles.  Together I have them all.  No archivelogs, no anything.  This is the path I must take!

I have to do a force open of the database with _ALLOW_RESETLOGS_CORRUPTION = TRUE

This is ok, and I will have a inconsistent database afterwards.  However, there is not much data added in the database between the datafiles I have, perhaps nothing if I am real lucky.  Is it possible to make this inconsistent database consistent in some way afterwards, and then go through the database and check for concistency errors (added data in some tables and then remove it etc.)

If not, I have to export all tables, rebuild the database, import tables and rebuild indexes.  This is a rather complex database with lots of users/stored procedures/views etc. so the rebuild will take for ages.   Any short-cuts that can be taken here, for instance exporting out the build of the database in script format or something from the corrupt database?

This is urgent as the dabase is a production database and is down for the moment.


Thanks,

MortenStart Free Trial