RE: Reading UNDO and displaying it in v$session
- From: "Milen Kulev" <makulev@xxxxxxx>
- To: <yong321@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 4 Apr 2008 06:57:57 +0200
Hello Yong,
Thanks fot the link. It seems that oracle is not updating the information
Of ROW_WAIT_OBJ_*# consistently.
Best Regrads. Milen
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Yong Huang
Sent: Thursday, April 03, 2008 8:48 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: Reading UNDO and displaying it in v$session
Jonathan Lewis posted a message about this problem before having the same
suspicion.
http://groups.google.com/group/comp.databases.oracle.server/browse_frm/thread/4ba9035dd2c70992
Yong Huang
> From: "kyle Hailey" <kylelf@xxxxxxxxx>
>
> ROW_WAIT_OBJ#
> ROW_WAIT_FILE#
> ROW_WAIT_BLOCK#
> don't seem to be as dependable as P1 and P2 for IO events. Not sure
> why. My guess is that sometimes when they are not filled out, then the
> values are left over from previous usage (like a db file sequential
> read from UNDO in your case) What are the value of P1 and P2 for your
> direct path write temp waits ( ie your File and Block)?
>
> Best
> Kyle
____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total
Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
