Oracle Requiring Old Redo Log !?

Hi Folks,

I have some strange problem (aren't they all?): I run an oracle database that is directly attached to a managed standby database. Everything fine here.

Last week, a developer accidentally dropped a table in the production database and I now have to restore it. I thought nothing easier than that, since I have a cold backup of the standby database that was taken before the accident, I planned to simply apply the redo log files until the drop.

Copied the backup to the test server, mounted the database, next redo log to apply is #28893 according to archive log list - perfect. Copied the archived redo log files (until the drop, up to #35469) to the server and typed in RECOVER STANDBY DATABASE. Now this is weird: Oracle requires archived redo log file #17440 to be applied. According to murphy's laws, exactly this one is missing! I'm kinda-puzzled by this since my understanding suggests that a cold standby database backup should be consistent and should not require any previously taken redo log file to be applied... or am I missing something here?

I read something about "dropping and re-creating" the missing redo log... with many warnings not "to try this at home" :-)

I hope somebody out there can give my some clue... BTW this is an Oracle 8.1.6 on a RedHat 6.2 box with all current OS upgrades applied.

1k thx in advance,
good night

    -hannes erven Received on Mon Mar 12 2001 - 15:27:13 CST