I've been trying to track down the source of high
'direct path read' and 'direct path write' waits. It
appears the waits are related to locally managed
temporary tablespaces. However, I'm puzzled by what
is reported in v$tempstat.
SQL> select FILE#, READTIM, WRITETIM, AVGIOTIM,
LSTIOTIM, MINIOTIM, MAXIORTM, MAXIOWTM
from v$tempstat;
FILE# READTIM WRITETIM AVGIOTIM LSTIOTIM MINIOTIM
MAXIORTM MAXIOWTM
----- ------- -------- -------- -------- ----------
---------- ----------
1 3 0 0 1 0
6393 78
2 2 252 443 636 0
1387 188
How could the values for MAXIORTM (maximum time spent
doing a single read) be substatially greater than
those reported for READTIM (time spent doing all
reads)?
This situtation persists even after all of the users
have logged out of the database, so it doesn't appear
to be a case of the read having not yet completed.
FYI: We're running Oracle 8.1.6.3 on Sun Solaris.
-Ed
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Ed Bittel
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
