Forcing DB open ??!

Question

I have done a stupid thing, and deleted the online redo logs.
We are running 8.1.6 on Linux RH7, and I managed to reinstate the files and they appear to be OK. That is, I managed to 'undelete' all of the online and archived logs EXCEPT for the current one. When I try to start the DB, the following happens :
SVRMGR> startup force
ORACLE instance started.
Total System Global Area 150523888 bytes
Fixed Size 69616 bytes
Variable Size 133505024 bytes
Database Buffers 16777216 bytes
Redo Buffers 172032 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SVRMGR> alter database open resetlogs;
alter database open resetlogs
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
SVRMGR> recover database;
ORA-00283: recovery session canceled due to errors
ORA-00316: log 1 of thread 1, type 0 in header is not log file
ORA-00312: online log 1 thread 1: '/u05/tmp/redo_backup_01.log'
SVRMGR> select * from v$log;
GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHAN FIRST_TIM
1 1 2500 512000 1 NO CURRENT 339758 15-DEC-00
2 1 0 512000 1 YES UNUSED 0 15-DEC-00
3 1 2499 512000 1 YES INACTIVE 339048 15-DEC-00
3 rows selected.
The problem is that the current sequence is 2500, but doing a strings on the log file 1 shows that it is still pointing to sequence 2497.
I could not find a sequence 2500 in any of the deleted files.
Instead of attempting recovery, I am now trying to bring the DB up even if the data is corrupt. Is there any way to do this?
Any assistance would be greatly appreciated.
TIA
Dale

Answer 1

because your database files have a different SCN or fuzzy bit set, the files must be recovered to the last consistent state. because of your witchcraft with the redologfiles, the server cannot find what it wants to do the recovery. There is a way to open the database, but only to make an export and drop the datbase, because consistency can NOT be guaranteed.
** DO THIS AT YOUR OWN RISC **
** THIS IS NOT SUPPORTED BY ORACLE **
put the following line in the init.ora file of your datbase:
allowresetlogs_corruption=true
and start the datbase. the database will open now. make an export of all relevant data, and drop the database (!!)
not only your data can be corrupted, but internal oracle data also. this is why you must drop the database when you've made your export.
null