Re: Dataguard Exadata -> Database Appliance

  • From: Fuad Arshad <fuadar@xxxxxxxxx>
  • To: "Chris.Stephens@xxxxxxx" <Chris.Stephens@xxxxxxx>, "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 15 Apr 2014 08:18:00 -0700 (PDT)

Chris,
Should work without issues. Yes you will have to patches same across ODA and Exa
This whitepaper will help
http://www.oracle.com/technetwork/database/features/availability/maa-wp-dr-dbm-130065.pdf



________________________________
 From: "Stephens, Chris" <Chris.Stephens@xxxxxxx>
To: "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx> 
Sent: Tuesday, April 15, 2014 10:09 AM
Subject: Dataguard Exadata -> Database Appliance
 


 
I was just asked by management whether it would be possible to run Dataguard 
from Exadata (Primary) to a Database Appliance (Standby).  I can’t think of a 
reason why that wouldn’t be possible.
 
I’m not sure that’s the question they are actually asking though which is:  
Would it be justifiable for us to save some money and run our standby on 
cheaper hardware (and consequently software licensing)?
 
I don’t think processing power differences will be a problem for quite some 
time.  The biggest drawback I can think of is that all of a sudden you have to 
keep OS/GI (running RAC)/RDBMS versions and patching at the same level.
 
What else am I not thinking of?  …how bad of an idea is it?
 
I would have even really considered it as a possibility but then I don’t pay 
the bills or have to justify them either.
 
Thanks for any help with this.
 
Chris
 
CONFIDENTIALITY NOTICE:
This message is intended for the use of the individual or entity to which it is 
addressed and may contain information that is privileged, confidential and 
exempt from disclosure under applicable law. If the reader of this message is 
not the intended recipient
 or the employee or agent responsible for delivering this message to the 
intended recipient, you are hereby notified that any dissemination, 
distribution or copying of this communication is strictly prohibited. If you 
have received this communication in error,
 please notify us immediately by email reply.

Other related posts: