Re: command line vs grid control

ivl5@xxxxxxxxxxx wrote:

Perhaps we should define "monitoring" more precisely but it's hardly
an ability to select from dba_hist views. Anyway any decent custom
monitoring scripts save point-in-time measurements as historical data.
Or you can fall back to Staspack. It doesn't equal AWR or Diagnostics
Pack but certainly covers "monitoring" bit.

Waking up all night long and sniffing the air might be considered by
some less expensive than buying a smoke alarm.

I understand your point but to me it is the point of a dinosaur. Your
scripts are not version aware and will require rewrites with every
upgrade. Your scripts are far less capable than the grid. Your scripts
are incapable of real-time monitoring. Your scripts have no metadata
repository with which to compare previous results. And if you are like
99% of all DBAs I know you will not submit your scripts to testing in
an independent test environment to make sure they are sound. You will
just throw them over the cubicle wall onto the production server and
assume they work because you wrote them.

More developers were used to build the 10g Grid Control than
to build the 10g database. How far do you think you are going
to get duplicating that with a shell script unless you violate
your employer's license agreement.

Apparently you didn't read my reply so I'll repeat once more:
_No_need_to_duplicate_everything_in_OEM;_it_contains_much_more_than_just_monitoring.
OP talks "monitor my database, routine work". This can continue to be
done with his existing scripts.

The monitoring portion alone exceeds anything you are capable of writing.

And the point of this exercise would be what? To save your employer
money or to avoid learning something new?

Is it still "You can not monitor a database using shell/perl scripts
any longer"?

From my standpoint that is the case. Just as I would say that anyone
using shell/perl scripts to perform a backup should be trained or
terminated.
--
Daniel A. Morgan
University of Washington
damorgan@xxxxxxxxxxxxxxxx (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
.

Relevant Pages

  • Re: command line vs grid control
    ... Assuming some version of Oracle more recent than 9.2.0.8 you can not ... monitor a database using shell/perl scripts any longer. ... required to duplicate the functionality of the OEM grid control ... monitoring scripts save point-in-time measurements as historical data. ...
    (comp.databases.oracle.server)
  • Re: Basic Scripts for Database Administration
    ... monitoring, tablespace monitoring, load monitoring? ... Oracle has put a lot of work into the 10g and 11g "rewritten" OEM ... canned from oracle before deciding that you want to use custom scripts ... I would have done the space screens ...
    (comp.databases.oracle.server)
  • Notice Of SSH Interop Issues
    ... environment with a Linux-driven monitoring service called Nagios, ... Critical, and 3 means unknown. ... vanilla /bin/sh scripts) never returned a retcode of 3 no matter what. ... all reported properly for days with a loglevel of debug but began ...
    (SunManagers)
  • RE: email content monitoring / effectiveness
    ... Then run some scripts to ... email content monitoring / effectiveness ... > Our mail systems are predominately MS Exchange 2000. ... > Do you Yahoo!? ...
    (Security-Basics)
  • Re: Handling of daily and weekly mails
    ... getting about 100 mails a week from the PERIODICscripts. ... by the FreeBSD project that the baseline system comes with a working monitoring system built-in. ... particularly special to run Nagios on. ...
    (freebsd-questions)