Title: RE: Common Oracle RDBMS Misconceptions - standby db?
I guess that's the scenario I was thinking of, Stephane. Primary completely hosed and needing modification in one way or the other... and several hours between failover and switching back with the possibility of a few lost
Title: RE: Common Oracle RDBMS Misconceptions - standby db?
Thank you Jeremiah for your explanation. But to clarify, you can't have both databases open at the same time, can you? That's where I hosed stuff up the first time, and I realized why it didn't work immediately after seeing my error
tears of happiness
thank you, thank you, thank you...
/tears of happiness
--- Jeremiah Wilton [EMAIL PROTECTED] wrote:
With graceful standby failover (I demo'd it last
year at OOW), you can switch
back and forth, back and forth as many times as you
want without recopying any
database.
Also check out the notes on metalink: #90817.1. It states all the steps and
concept clearly!
Winnie
--
\ /~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~`~~``~
(@ @) @}-`-,-`-,--- Winnie Liu ---'-,-'-,-{@`~`~
/ V \ Oracle Database Administrator`~`~
On Tue, 26 Jun 2001, Stephane Faroult wrote:
But in practice, why would you switch to the standby database, unless
the primary database is crashed or worse?
- Hardware replace/repair
- Move to a larger host
- O/S upgrade
- File layout revision
- Planned/impending infrastructure outage
-
and apply the
logs, and put into managed recovery mode.
Mike
From: Koivu, Lisa [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: RE: Common Oracle RDBMS Misconceptions - standby db?
Date: Tue, 26 Jun 2001 11:12:24 -0800
OK. I admit my
Title: RE: Common Oracle RDBMS Misconceptions - standby db?
OK. I admit my knowledge on standby is minimal, having only read up on it, fiddled with it and used the idea sparingly for migrations.
However, Jeremiah, I'm very curious. You state that 'Must reinstantiate standby after failover
With graceful standby failover (I demo'd it last year at OOW), you can switch
back and forth, back and forth as many times as you want without recopying any
database.
Basically, when you fail over to a standby, you shut down the primary, apply all
the archived redologs to the standby, then copy
But in practice, why would you switch to the standby database, unless
the primary database is crashed or worse? You know how it is in a
production environment, the database crashes. Even if failover is easy,
you always have to instruct users to connect as scott/tiger@backup
instead of
-L [EMAIL PROTECTED]
Subject: RE: Common Oracle RDBMS Misconceptions - standby db?
Date: Tue, 26 Jun 2001 15:21:00 -0800
With graceful standby failover (I demo'd it last year at OOW), you can
switch
back and forth, back and forth as many times as you want without recopying
any
database.
Basically
]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: Common Oracle RDBMS Misconceptions - standby db?
Date: Tue, 26 Jun 2001 16:27:34 -0800
But in practice, why would you switch to the standby database, unless
the primary database is crashed or worse
11 matches
Mail list logo
