Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: oracle full table scan
To answer the original question ...
SELECT usr.name oowner, ob.name oname
FROM ( SELECT obj
FROM sys.X_$BH WHERE TO_NUMBER(bitand(flag, POWER(2,19))) > 0 GROUP BY obj) bh, sys.obj$ ob, sys.USER$ usr
2. FTS can happen for many reasons ... if Oracle is performing FTS on a small table, that's the way to do it. Remember when you create an index Oracle had to perform 2 IOs, one for INDEX lookup and (if required) one for Table lookup. Sometimes associated costs dictate that a FTS is cheaper than the combined cost (of index lookup and table lookup), so Oracle prefers that.
One upon a time, I used to think on the same lines, but the bright minds on this list have time and again proven that FTS, isn't a bad thing after all. Sometimes it is, but not ALL the times.
Creating indexes is not the solution, a careful analysis of the logic implemented in the SQL is also required, and you will be surprised that, just by making the query changes, the performance gain can be achieved.
PS: Stephane, you probably have this on the top of your "Oracle Myth" list
... right?
YMMV
Raj
> Dear All,
>
> is there any way to find which tables (table name) are
suffering from
> full table scan ,so that i can create indexes on them to enhance the
> performance.
>
>
> Thanks
>
> Arvind
> --
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Jamadagni, Rajendra INET: Rajendra.Jamadagni_at_espn.com Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (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).Received on Thu Apr 03 2003 - 07:28:39 CST
- text/plain attachment: ESPN_Disclaimer.txt