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: full-scan vs index for "small" tables

Re: full-scan vs index for "small" tables

From: Nigel Thomas <nigel_at_preferisco.com>
Date: Wed, 28 Jun 2006 07:18:20 -0700 (PDT)
Message-ID: <20060628141820.99353.qmail@web54713.mail.yahoo.com>


Connor wrote:
>>In my experience, [spinning in memory] is all too common... in particular queries to dual
>>- heaps and heaps of
>>select user from dual
>>...dual...dual....dual....dual....dual.....aarrrggghhh!

I'll vouch for that; my top SQL by executions is:

    select 'x' from dual;

with 311,972 executions in a recent load test; next SQL has 95,921. This was just under 10% of total executes and 44% of all parses. The statement is issued by the (Oracle 10.1.0.4) JDBC driver whenever we get a connection out of the pool.  

It's allegedly fixed in JDBC 11 (yes, 11) see bug 4601037 and my writeup of the conversation with Oracle at http://preferisco.blogspot.com/2006/04/is-this-oracle-wtf.html.  

Regards Nigel    

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jun 28 2006 - 09:18:20 CDT

Original text of this message

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