Re: Questionable V$SQLAREA Statistics

2002-07-02 Thread Danisment Gazi Unal (ubTools)
Hi, You should not compare tkprof outputs with V$SQL,V$SQLAREA. Because, recursive/child statistics are included in their parent statements in these views. But, tkprof substructs recursive statistics. I mean tkprof reports real values for statements, but dictionary doesn't. regards... Orr,

Questionable V$SQLAREA Statistics

2002-07-01 Thread Orr, Steve
Here's the scene: 1) I have a 400,000 row table table which is cached. 2) I have a query against that table and no other with one column referenced in the WHERE clause. (This column is indexed and of course I don't really need the index since the table is cached but it's there so ho hum...) 3)

RE: Questionable V$SQLAREA Statistics

2002-07-01 Thread Khedr, Waleed
What is the degree of parallelism on this table? Waleed -Original Message- Sent: Monday, July 01, 2002 4:39 PM To: Multiple recipients of list ORACLE-L Here's the scene: 1) I have a 400,000 row table table which is cached. 2) I have a query against that table and no other with one

Re: Questionable V$SQLAREA Statistics

2002-07-01 Thread Greg Moore
What version of Oracle? 1) I have a 400,000 row table table which is cached. How has the table been cached? Alter table XXX cache? Or with a KEEP buffer? -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Greg Moore INET: [EMAIL PROTECTED] Fat City Network

Re: Questionable V$SQLAREA Statistics

2002-07-01 Thread Stephane Faroult
Orr, Steve wrote: Here's the scene: 1) I have a 400,000 row table table which is cached. 2) I have a query against that table and no other with one column referenced in the WHERE clause. (This column is indexed and of course I don't really need the index since the table is cached but

RE: Questionable V$SQLAREA Statistics

2002-07-01 Thread Orr, Steve
The degree is 4 and it is cached via alter table, not the KEEP buffer. On Oracle 8.1.7.2 on Linux RedHat 7.2 Thanks for clues... -Original Message- Sent: Monday, July 01, 2002 3:08 PM To: Multiple recipients of list ORACLE-L What is the degree of parallelism on this table? Waleed

Re: Questionable V$SQLAREA Statistics

2002-07-01 Thread Tim Gorman
Steve, Query V$SESSION_EVENT for the SID of that session. If you see the wait-event db file scattered read change during the query, then it truly is doing I/O, like it or not. It is more likely that the CACHE attribute is not working as you've apparently assumed it does, rather than there

Re: v$sqlarea statistics

2001-10-24 Thread BINAY . KUMAR
Hi Deepak, Can you elaborate what is consistent gets - Eric, here's a high level from my understanding on this issue: Buffer gets {also called Logical IO's} These happen as oracle scans blocks of data in the buffercache(in-mem scans). Many people believe that since these are

Re: v$sqlarea statistics

2001-10-24 Thread Deepak Thapliyal
Binay, from what i understand, these type of block reads relate to read consistancy .. meaning that if oracle wants to read block x but it finds that it is dirty , it reads from the rollback segments to give you the point in time snapshot as it existed at the time when you had first started the

v$sqlarea statistics

2001-10-23 Thread Erik Williams
I am trying to identify the most harmful statements in an application. From the Oracle Performance and Tuning Tips and Techniques book, I found two statements. Both are looking at the statements contained in the v$sqlarea. The first looks at statements with a high number of buffer gets and the

Re: v$sqlarea statistics

2001-10-23 Thread Deepak Thapliyal
Eric, here's a high level from my understanding on this issue: Buffer gets {also called Logical IO's} These happen as oracle scans blocks of data in the buffercache(in-mem scans). Many people believe that since these are memory reads, they are inexpensive. I have seen the contrary in many cases

Re: v$sqlarea statistics

2001-10-23 Thread Connor McDonald
Some reasons for the difference: a) A single disk read could get more than 1 block b) queries may already find blocks in the cache and thus not need a disk read c) a query may revisit the same block over and over without ever going back to disk The reason we look at both is 'disk_reads' tell us