RE: HA Architecture Plus + Reporting Purposes

  • From: Michael Dinh <mdinh@xxxxxxxxx>
  • To: "'tim@xxxxxxxxx'" <tim@xxxxxxxxx>, "avadhanimys@xxxxxxxxx" <avadhanimys@xxxxxxxxx>, ora-apps-dba <ora-apps-dba@xxxxxxxxxxxxx>, oracle-l <oracle-l@xxxxxxxxxxxxx>, "oaugnetdba-on@xxxxxxxx" <oaugnetdba-on@xxxxxxxx>
  • Date: Wed, 7 Dec 2011 13:24:26 -0800

I have not used DG for reporting purposes because the standby created is 
primarily use for backup since the servers and storage is not at the same 
capacity as standby.

However, with redo at 200M and 100-150 log switches per day, standby was able 
to catch up after 3 days of down time applying logs in less than a day.

That's a good and fuzzy feeling.

Golden Gate will come at an additional cost.


Michael Dinh

Disparity Breaks Automation (DBA)

Confidence comes not from always being right but from not fearing to be wrong - 
Peter T Mcintyre
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Tim Gorman
Sent: Wednesday, December 07, 2011 1:14 PM
To: avadhanimys@xxxxxxxxx; ora-apps-dba; oracle-l; oaugnetdba-on@xxxxxxxx
Subject: Re: HA Architecture Plus + Reporting Purposes

Options 1 and 2 are the only viable HA/reporting solutions in your list.

Despite what Oracle asserts in their marketing, RAC is not an high-availability 
solution, it is a scalability solution for situations when it is not possible 
to scale non-RAC within a server. Oracle tries to differentiate between 
"disaster recovery" (DR) and "high availability" (HA) in order to prevent 
DataGuard and GoldenGate from cannibalizing RAC, but DR and HA are really the 
same thing to a database. After all, what parts of DR would you give up and 
still be able to call the result "HA"?

Good luck,


-----Original Message-----
From: Avadhani mys [mailto:avadhanimys@xxxxxxxxx]
Sent: Wednesday, December 7, 2011 01:35 PM
To: 'ora-apps-dba', 'oracle-l', oaugnetdba-on@xxxxxxxx
Subject: HA Architecture Plus + Reporting Purposes

Hi Gurus,We are planning to propose a solution to avoid bottleneck 
onperformance from reporting[Discoverer Reports] job runs on a database.As we 
are aware that with any High Availability Architecture, therewill be single 
point of DB connection for any reporting job runs. Weare thinking about 3 
strategies to propose listed below. Can youplease shed light on 
Advantages/Disadvantages of each approach basedon your experience or any 
approach which can solve/address HighAvailability and Performance.1) Data Guard 
- Pure Disaster Recovery Solution. Leverage ActiveStandby for Reporting 
purposes (Partial only for 100% read onlyreports)2) Golden Gate Replication 
Technology to replicate Data Secondarysite and using Secondary site for 
reporting purposes.3) RAC - High Availability Solution with additional node to 
be usedfor Reporting purposes.4) RAC - High Availability Solution with Golden 
Gate ReplicationTechnology to replicate Data Secondary site real time for 
reportingpurposes. Any HA/D
 R gains from this point?Your help will be really helpful in determining the 
best feasible approach.Thanks in 



Other related posts: