RE: database monitoring tools
- From: "Jesse, Rich" <Rich.Jesse@xxxxxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 9 Feb 2006 10:35:25 -0600
Am I the only one to think that OEM 10g Grid Control is not a solid
product?
Has no one else had the 375+ "WARNING: Subscription for node down event
still pending" messages/day in their listener.log?
Has no one else needed to "reset" a target due to errors in OEM? Once a
target is deleted (required to "reset" confusion between an Agent and
the EMS), it doesn't appear to be able to be re-addeded by dynamic
discovery. And there also doesn't appear to be a way to delete the list
of deleted targets. In order to initiate dynamic discovery on the Agent
side, it must be re-effing-installed.
Has no one else noticed that the Agent's processes regularly cause forty
SYS/PUBLIC objects to become invalid, flagging a policy violation in EM.
The workaround is to drop that policy.
Has no one else been annoyed at having to install three new Oracle Homes
on the Console server just to get the thing running?
This does not make my life easier -- it makes it harder. I would much
rather pay to run a reliable GUI on a stupid Winders box than have to
deal with wondering why I didn't get notified of a DB down, or having to
spend weeks figuring out how to avoid getting paged constantly due the
amount of errors OEM Grid generates.
Or has 10gR2 improved this at all?
Rich
p.s. Apologies for rehashing some of my post from 06/2005.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Arnold, Sandra
Sent: Thursday, February 09, 2006 10:12 AM
To: Ron.Reidy@xxxxxxxxxxxxxxxxxx; dbritnel@xxxxxxxxxxxx;
oracle-l@xxxxxxxxxxxxx
Subject: RE: database monitoring tools
I have just installed and implemented OEM Grid Control v2. It is still
early to tell but so far I am impressed with what I have seen so far.
I am running the Repository db, OEM Server, etc on Red Hat Linux. In
addition, I have the agent installed on 3 Sun Solaris servers. One
version 5.9 64-bit and two version 5.10 64-bit.
Sandra Arnold
Senior Oracle DBA
NCI Information Systems
US DOE OSTI
Oak Ridge, TN
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Reidy, Ron
Sent: Thursday, February 09, 2006 10:58 AM
To: dbritnel@xxxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: database monitoring tools
OEM GridControl v2.
--
Ron Reidy
Lead DBA
Array BioPharma, Inc.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Doug Britnell
Sent: Thursday, February 09, 2006 8:53 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: database monitoring tools
Hi all,
First post.
Am looking for advice/recommendations on 3rd party monitoring tools
specifically for 10g.
Here's a list of some of the things I'd like to monitor...many instances
across many servers
a.. object next extent fail
a.. storage report
a.. instance status
a.. log switches summary
a.. users in a locked state
a.. mount point nearing full
a.. Wait States
a.. Logical vs Physical reads per Tablespace
a.. SQL*Net
a.. Rollback/Undo Statistics
a.. Rollback/Undo Contention
a.. Get/Hit Ratio
a.. Pin Hit Ratio
a.. Library Cache
a.. Buffer Cache
Thanks,
Doug Britnell
--
//www.freelists.org/webpage/oracle-l
This electronic message transmission is a PRIVATE communication which
contains
information which may be confidential or privileged. The information is
intended
to be for the use of the individual or entity named above. If you are
not the
intended recipient, please be aware that any disclosure, copying,
distribution
or use of the contents of this information is prohibited. Please notify
the
sender of the delivery error by replying to this message, or notify us
by
telephone (877-633-2436, ext. 0), and then delete it from your system.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
