Re: database could not be started

quarkman <quarkman_at_myrealbox.com> wrote in message news:<oprtnqk2wfzkogxn_at_haydn>...

> I don't know why suddenly 'resetlogs' is considered so evil! You would have
> to type 'recover database until cancel'...'cancel'...'alter database open
> resetlogs'. I make that a massive 9 words of typing!

Resetlogs becomes evil when you attempt to switch back from a standby database. At least in 8i, it means the difference between many hours of backing up and moving files and restoring, versus e-shipping a few archived logs over from the standby host (I'm referring to the "Graceful Switchover and Switchback" paper on metalink, where the big trick is avoiding resetlogs). In the case of the project I'm working on now, it would be quicker to put someone on a plane with a tape for the switchback, since the communications link will be loaded with people doing work on the standby. All because of resetlogs.

I'm curious if 9 is any different (that is, whether you have to play games to fool Oracle to do a switchback).

I know this swerves the thread, and agree with everything else you said.

jg

--
@home.com is bogus. "Note: After you activate the standby database,
you lose all
transactions from unarchived logs at your original production
database. Because the standby redo logs are reset at activation, you
cannot apply logs archived before activation." - 8i Standby Database
Concepts, on a page with more than one error.