RE: Semi-OT: Shell Scripting for dummies
- From: Herring Dave - dherri <Dave.Herring@xxxxxxxxxx>
- To: "hurleyjohnb@xxxxxxxxx" <hurleyjohnb@xxxxxxxxx>, "SUzzell@xxxxxxxxxx" <SUzzell@xxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>, "Finn.Jorgensen@xxxxxxxxxxxxxxxxx" <Finn.Jorgensen@xxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Mar 2013 21:45:24 +0000
I agree we should avoid reinventing the wheel and not scripting something that
a tool you use already provides, but at the same time I've learned that I can't
fully trust a tool to monitor everything for me. I've found situations where
OEM/GC/EM stopped running jobs on some targets without any warning, stopped
reading the alert log, and other various things. I found a problem recently on
the other side of the street where sendmail stopped working on a number of
servers, which is really nasty because by NOT receiving any email alerts you
think all is fine. In this case cron-scheduled jobs weren't the only answer.
In the end I have sanity checks for both EM and cron-scheduled jobs.
But back to the original poster, along with learning all you can about grep,
sed, and awk (previously suggested) I'd also spend time learning all you can
about regular expressions. In terms of a resource for helping with shell
scripting I recommend "Unix Power Tools" published by O'Reilly.
Dave Herring
DBA
Acxiom Corporation
EML dave.herring@xxxxxxxxxx
TEL +1 630.944.4762
3333 Finley, Downers Grove, IL 60515, U.S.A
www.acxiom.com
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of John Hurley
Sent: Friday, March 22, 2013 3:45 PM
To: SUzzell@xxxxxxxxxx; oracle-l@xxxxxxxxxxxxx; Finn.Jorgensen@xxxxxxxxxxxxxxxxx
Subject: RE: Semi-OT: Shell Scripting for dummies
Finn:
# But really you should look into installing OEM12c and getting away from the
custom scripting as much as you can.
... Dunno I really have to look at Kellyn Pot'vins hotsos presentation to
understand probably ( just been busy )
If using OEM12c doesn't that necessarily imply that some set of oracle
processes/agents/etc are executing and responding?
I am an old grumpy dba dinosaur but tend to drive stuff via cron and do my
alerting "outside of" depending on anything from the oracle stack to use.
Nothing too much wrong with basic ksh shell scripting to diagnose oracle
related stuff in my opinion.
What if various things are down for various reaons?
The book you cited is very good!
--
//www.freelists.org/webpage/oracle-l
***************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be legally
privileged.
If the reader of this message is not the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.
If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.
Thank You.
****************************************************************************
--
//www.freelists.org/webpage/oracle-l
Other related posts:
