Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: ((Re)): problem interpreting wait events

Re: ((Re)): problem interpreting wait events

From: Wolfgang Breitling <breitliw_at_centrexcc.com>
Date: Mon, 23 Aug 2004 14:06:44 -0700
Message-ID: <1093295204.412a5c6437943@webmail.hosting.telus.net>


No, you are querying the correct view, you just haven't looked at the columns and their description. dba_extents shows you extents. It has the block id of the first block of the extent and the size of the extent in blocks (column blocks). It does not list every block of the extent, which is what you expect. You have to look for the segment where your block from p2 is >= block_id and < block_id + blocks. When you do that you will find that a) you do get a segment name back
and
b) you will have performance problem on anything but mickey-mouse systems

Quoting ryan gaffuri <ryan.gaffuri_at_comcast.net>:

> i don't have a problem with performance. I think I am checking the wrong
> data dictionray view. I took the p2 value from db file sequential read and I
> thought I could use the block_id in dba_extents. When I query on it, I get
> 'no rows selected', so I think I am using the wrong view.
>
> anyone know which one to use for this?

-- 
regards

Wolfgang Breitling
Oracle 7,8,8i,9i OCP DBA
Centrex Consulting Corporation
www.centrexcc.com

----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Received on Mon Aug 23 2004 - 16:03:27 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US