Data Guard Broker : 11g and 12c

vault-154023_640I’ve been using standby databases, on and off, since Oracle 8i. I first wrote about Data Guard for Oracle 9i. I’ve had an article on 11gR2 Data Guard for ages, but up until recently I’ve always used the manual setup.

We’ve got a project coming up that *may* use Data Guard and *may* be installed by a 3rd party, so I figured I better get up to speed with the Data Guard Broker, in case they go that route. It’s been on my list of things to look at since 10g, but I’ve never got round to it until now. 🙂

At this point, I still don’t know if the project will use 11g or 12c, so I had a play with both, which resulted in a couple of overview articles.

From the overview perspective, the usage is pretty much the same. I really only did the 11g one in case that’s the route this project goes. I didn’t bother putting the 11g one on the front page of the website, because I consider it a “backfill” article. 🙂

After having a play with the broker, I actually quite like it. It definitely feels like a simpler and neater solution than doing all the configuration manually.

Remember, this Data Guard stuff is for EE installations. If you use SE, you might want to take a look at Dbvisit, who have a product that allows you to manage standby databases for Oracle SE.

Cheers

Tim…

PS. I’m not sponsored by Dbvisit and I have no business links with them. I just think they are a great bunch of people and I like what they do.

Author: Tim...

DBA, Developer, Author, Trainer.

3 thoughts on “Data Guard Broker : 11g and 12c”

  1. Hi Master !
    Your article stands always the first point-of-reference for learning any new stuff with Oracle for me! Thanks for that Oracle 12c Dataguard Broker !!!
    (I’ve not done much practise with Performance Tuning and I realised searching for PT topics on your site, but I can be wrong too) Not sure you like to have a link dedicated with all the links related to just Oracle Performance topics you wrote already, especially with CBO topics (From 10g or 11g onwards) as you have for PL/SQL, CBO etc. It would be surely useful for any new learner to get good foundation with Performance Tuning.

    Cheers,
    Praveen
    PS : Last week I had an interview with a company located in Stuttgart, Germany. For the first time I heard about Dataguard Broker related questions. I assume it’s because of Oracle 12c. Often Dataguard was asked. I’m excited to practise with Oracle 12c !

  2. Praveen: I don’t really have any straight performance tuning articles on the website. I talk about a number of features that relate to performance tuning, but not in the sense you are discussing.

    The problem with writing about performance tuning is it is very hard to write short-snappy articles on the subject. There are so many interrelationships that it becomes very easy to write an article full of lies and untruths.

    If people ask, I typically say read Troubleshooting Oracle Performance (TOP) by Christian Antognini.

    https://antognini.ch/top/

    I really like this book because Christian has done a great job in making it really easy to read, without making it overly simplified! There are of course many other books too, but I think this one is probably easier to get into than most.

    Cheers

    Tim…

  3. Hi Master,
    Thanks to correct me. Yes, I meant a link to the features related to Monitoring/Troubleshooting !
    If I was unclear with my wish, I meant creating a link clubbed with all other links of the articles you wrote already : Explain Plan, DBMS_XPLAN, AWR, ADDM, ASH, ADR Utility, TKPROF, TRACE 10046, etc.

    When I read your article ‘Trace 10046…’ I came to know that ‘Trace Analyzer’. Searching that on MOS, I came to know about ‘SQL Health Script ‘. So, that’s why I say, your articles always enhances my knowledge !
    Thanks to tell me your opinion about the book. When I googled, I found that many did say that. Great, you also suggest it !
    He got Second Edition now !!! I’m excited to read his second edition book too. Not ordered it yet.
    Cheers,
    Praveen

Comments are closed.