RE: Data Guard Management Interfaces

  • From: "Sais, Gene" <Gsais@xxxxxxxxxxxxxxxxxxxx>
  • To: "'Brandon.Allen@xxxxxxxxxxx'" <Brandon.Allen@xxxxxxxxxxx>, "'oracle-l@xxxxxxxxxxxxx'" <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 29 Jul 2010 17:36:07 +0000

I use ksh shell scripts and sqlplus.  I did use OEM Grid which was quite buggy. 
 I am running 10.2.3 RAC & AIX 5.3.

From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Allen, Brandon
Sent: Thursday, July 29, 2010 1:27 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Data Guard Management Interfaces

Hi List,

I'm just getting started with Data Guard and curious which management interface 
those with extensive experience would recommend?  I am very comfortable with 
the command line and use SQL*Plus for 99% of my DBA tasks.  I'm not currently 
running Grid Control - I just start up DB Control briefly when needed and then 
shut it back down.  Am I better off just using the SQL*Plus commands for DG, or 
should I use the command-line version of DG Broker (DGMGRL), or is it worth 
setting up Grid Control just for the convenience of the GUI for managing Data 
Guard?  Based on my previous experience testing Grid Control (more trouble than 
it's worth in my opinion), and comfort level with the command-line, I'm leaning 
towards one of the CLI options - either SQL*Plus or DGMGRL.  Eventually I'll 
probably take the time to learn them both and decide for myself which one I 
like better, but I'm just curious which one you Data Guard experts would 
recommend to start with and any major pros or cons of any of them.

I'm running Oracle 10.2.0.4 on AIX6.1 and just setting up a simple 
configuration with one physical standby.

Thanks,
Brandon


________________________________
Privileged/Confidential Information may be contained in this message or 
attachments hereto. Please advise immediately if you or your employer do not 
consent to Internet email for messages of this kind. Opinions, conclusions and 
other information in this message that do not relate to the official business 
of this company shall be understood as neither given nor endorsed by it.

Other related posts: