Urgent! Online redo log files corruption

Hi everyone,

I am not sure if there are any people in this list at this hour of the day. But we are facing a terrible situation here on the production system. And I will need some advice.

For whatever reason, the production database crashed with online redo log file corruption. Oracle support told me that there is only two option: 1) restore and recover the database using the full backup 2) force the database open with the hidden paramter but HAVE TO export the database and rebuild it afterward as the database will NO LONGER under support license after the database open this way.

We are currently performing a cold backup on the database before we move on to either option. I was thinking about several different possible ways as well. But wondering if they are possible.

1. can I force the database open with that hidden parameter, but instead of rebuilding the whole database from export/import. I just mount the database, change it to noarchivelog, do several log switches, then change it back to archivelog? It is suppose to clear out the corrupted online redo log file

Had anyone in the lists have some experience or comment to share? Received on Sun Oct 22 2000 - 03:19:17 CDT