RE: Some Dataguard is good, lots more must be better?

From: <Jay.Miller@xxxxxxxxxxxxxxxx>
To: <oracle-l@xxxxxxxxxxxxx>
Date: Tue, 19 Sep 2006 14:25:48 -0400

You don't have to rebuild the standby after the primary is
upgraded/patched.  Basically, you just install the patch and then let
the apply run.

You don't even need to rebuild the standby after failover if you have
time/opportunity to do a graceful failover.



Thanks,
Jay Miller
Sr. Oracle DBA
x68355
 

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Laimutis Nedzinskas
Sent: Tuesday, September 19, 2006 1:55 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Some Dataguard is good, lots more must be better?

To sum up:
- the biggest work you have to do is to create standby for each one of
80 primaries. This can be automated to some level but even if you are
going to use OEM it is going to be at least 80xN mouse clicks.
- you have to rebuild standby after primary is upgraded/patched. This is
not a big work work compared to the upgrade process itself, some extra
10% may be. 
- rebuilding standby after failover: this can be mostly automated. Even
DG should be able to do this actually.

What you get: 
- the posibility to lag behind the primary (which violates data
protection however)
- independancy from the System Administrator and platform he
administrates




 

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Closson
Sent: 19. september 2006 17:36
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Some Dataguard is good, lots more must be better?

 >>>alternative DR solutions. For people that do care about near 
>>>continuous availability DG is really quite cheap - even if you didn't

>>>buy EE and is (reasonably) easy to manage. It helps that it is a 
>>>somewhat old and reliable technology as well.

...the thread I started was about the practicality of using DG for a lot
of databases.  Maybe there is nobody on list that has more than, say, 10
database that need DR, but does the comment "(reasonably) easy to
manage" hold fast if we are talking about providing DR for, say, 10 or
20 databases?

One of our accounts has over 80 databases that need DR and I must say
that in my mind chewing on crushed glass would bring more pleasure than
trying to deal with 80 primary/standby DG relationships... It just seems
to me that at some number of databases, the only humanly possible way to
get DR would be at the storage level... thoughts ?

--
//www.freelists.org/webpage/oracle-l


Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer
--
//www.freelists.org/webpage/oracle-l


--
//www.freelists.org/webpage/oracle-l

References:
- RE: Some Dataguard is good, lots more must be better?
  - From: Laimutis Nedzinskas

RE: Some Dataguard is good, lots more must be better?

Other related posts: