Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!wn11feed!worldnet.att.net!128.230.129.106!news.maxwell.syr.edu!postnews1.google.com!not-for-mail
From: adamm@wazamatta.com (Adam Monsen)
Newsgroups: comp.databases.oracle.server
Subject: is it possible to query an oracle database to find out how hard it's working?
Date: 2 Feb 2004 14:33:53 -0800
Organization: http://groups.google.com
Lines: 13
Message-ID: <9b12ed8d.0402021433.208be14c@posting.google.com>
NNTP-Posting-Host: 65.197.174.84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1075761233 28729 127.0.0.1 (2 Feb 2004 22:33:53 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 2 Feb 2004 22:33:53 +0000 (UTC)
Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:253492

The only measure (that I've heard) of how hard an Oracle database is
working is the current CPU load on the box.

For instance, a DBA would tell me: "spiffy, the Oracle server has two
0% idle CPUs! We need to kill some sessions or tune queries."

I assume they're getting the information by running 'top' or 'sar'
from a shell on spiffy.

Is there an SQL query or PL/SQL code block that could be run to
determine some measure of how busy a database server is? This would be
quite useful to predetermine if some expensive queries would be
possible before actually starting them.