RE: OEM GC High Availability and Downtime
- From: "Storey, Robert \(DCSO\)" <RStorey@xxxxxxxxxxxxxxxxxx>
- To: "oracle-l-freelists" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 24 Jun 2010 10:21:49 -0500
What about using RAC or Dataguard to provide redundancy to the
repository?
Not sure there is anything that you can do for the agents, but, if you
have multiple OMS's talking to a repository that was covered by
Dataguard, you could switchover to the other repository.
Or, if you just want constant uptime on it, why not implement a RAC for
the repository.
Just first thoughts to pop in my head.
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Guillermo Alan Bort
Sent: Thursday, June 24, 2010 9:55 AM
To: oracle-l-freelists
Subject: OEM GC High Availability and Downtime
List,
We are implementing GC for database monitoring for over 2500
databases, however there is concern of the possible downtimes of Grid,
during which the databases will not be monitored.
I can think of two possible scenarios:
1) Planned outage: in order to apply a patch, the entire OEM needs to be
shut down.
2) Emergency outage: Media Failure, Hardware Failure, Power Failure,
Oracle Bug, etc.
The HA strategy is having several OMS across different locations
(three, actually) however I am concerned about the repository.
It is very unlikely that an emergency outage will affect all three
OMS, however it might affect the repository... and the planned outage in
several situations will require a full shutdown of all OMS, Agents and
Repository.
My question is: have you ever dealt with this issue? How did you
solve it? did you just accept the outage? did you find an alternative?
TIA
Alan.-
Other related posts:
