RE: Routine Checks
- From: "Mercadante, Thomas F \(LABOR\)" <Thomas.Mercadante@xxxxxxxxxxxxxxxxx>
- To: <sacrophyte@xxxxxxxxx>, <niall.litchfield@xxxxxxxxx>, "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 16 Aug 2006 09:13:01 -0400
Charles,
Thanks for the advice. Do you use EM10gR2 to monitor or manage any 9i
databases? Did you stop using the 9i console?
Thanks
Tom
--------------------------------------------------------
This transmission may contain confidential, proprietary, or privileged
information which is intended solely for use by the individual or entity to
whom it is addressed. If you are not the intended recipient, you are hereby
notified that any disclosure, dissemination, copying or distribution of this
transmission or its attachments is strictly prohibited. In addition,
unauthorized access to this transmission may violate federal or State law,
including the Electronic Communications Privacy Act of 1985. If you have
received this transmission in error, please notify the sender immediately by
return e-mail and delete the transmission and its attachments.
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Charles Schultz
Sent: Wednesday, August 16, 2006 9:07 AM
To: niall.litchfield@xxxxxxxxx; oracle-l
Subject: Re: Routine Checks
On the subject of EM10gR2:
We had an Oracle instructor who told us to forget about trying to use
EM10gR1, as it was "not ready" for public consumption. So we waited for
R2 and were glad we did. Most things work quite well, and there are a
few quirks here and there (especially where the documentation says one
thing and EM says another). Due to EM's micromanagement style, we have
not turned on any of the email alerts until we have a good grasp of what
exactly we want to be notified of, but we do use it as a Monitor to
gauge overall system health and to drill down quickly on problem areas.
I do not believe we have come across any critical components that
outright fail. We have a couple SRs with Oracle Support about issues
with the OMS and the agent core dumping or hanging, but that does not
directly affect the performance of the target database, only the
monitoring thereof.
On 8/16/06, Niall Litchfield <niall.litchfield@xxxxxxxxx> wrote:
As some of you will have picked up I am in a relatively new position.
One of the things sadly lacking is any sort of pro-active monitoring
routine. This is something that I want to introduce, but my experience
of, for example, daily checks is that they tend not to happen after a
while. So I guess my question is what would you add to/remove from a
list of daily checks for all production databases that read.
1) database up
2) application up
3) alert.log errors
4) audit trails
5) backup success/failure
6) dr logs applied (where applicable)
7) failed jobs
and for a weekly list
1) db size
2) object size
3) availability
4) listener.log errors
5) redo/transaction volume
You'll see that I'm mainly coming at this from a security and
availability standpoint - I don't see that performance is amenable to
routine system wide checks.
A related question is how many of you are using, specifically, 10gR2 EM
to automate these sorts of things. We have a pretty dire EM10gR1
implementation that I wish to redo and 10gR2 looks an order of magnitude
better than R1, but any gotchas - like it doesn't work - would be nice
to know ahead of time.
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
--
Charles Schultz
Other related posts:
