RE: heavyweight OS monitoring as standard

From: Herring Dave - dherri <>
Date: Wed, 6 May 2009 08:14:34 -0500
Message-ID: <>

Thanks for pointing out OSW!

We've always used tools to match the OS ("collect" for Tru64, "nmon" for AIX, a home-grown sampler of /proc for Linux), then created .csv files, built external tables off the .csv files, then loaded the data into an Oracle db for historical analysis of the stats.

David C. Herring | DBA, Acxiom Automotive  

630-944-4762 office | 630-430-5988 cell | 630-944-4989 fax 1501 Opus Pl | Downers Grove, IL, 60515 | U.S.A. |  

-----Original Message-----

[] On Behalf Of Jeremy Schneider Sent: Tuesday, May 05, 2009 12:54 PM
Subject: heavyweight OS monitoring as standard

I'm at Collaborate right now, and we just finished the RAC SIG bird-of-a-feather session (it's a group discussion, and was quite good). Had an interesting point come up - we were discussing troubleshooting and asked how many people ran OSW as a standard practice on their clusters. (Metalink note 301137.1) I think about half the room raised their hands.

OSW is also included in RACDDT. (Metalink note 301138.1) And there's also a new tool from Oracle called IPD which seems to gather similar information into a little Berkeley DB (running processes, runqueues, etc): ad_homepage.html

How many people on this list install OSW as a standard practice on their database servers? Do you install some other heavy-weight monitoring tool as a standard? I always thought that most people only installed light-weight monitoring tools by default, would only install something like OSW and if there were problems since it captures so much data. But maybe this should become a standard practice for us; it would make troubleshooting machine crashes after the fact a *lot* easier.

Any thoughts?



Jeremy Schneider
Chicago, IL

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.

-- Received on Wed May 06 2009 - 08:14:34 CDT

Original text of this message