sql problem

From: Stephens, Chris <Chris.Stephens_at_adm.com>
Date: Tue, 16 Mar 2010 14:58:21 -0500
Message-ID: <D95BD5AFADBB0F4E9BB6C53F14D3A050049EB39F73_at_JRCEXC1V1.research.na.admworld.com> Red Hat Linux

I found a very simple query that is consuming a ton of I/O resources. Depending on the bind value, the query should be using an index. I've set the statistics_level to 'ALL' in the database since the sql is issued from a canned application and I haven't been able to get a hold of the users to actually trace a session. The column is a timestamp datatype. I was hoping to get the value used for :1 with the following:

SQL: select * from table(dbms_xplan.display_cursor('3wc8wxtk6cnjz',2,'allstats +peeked_binds'));

SQL_ID 3wc8wxtk6cnjz, child number 2

SELECT t_stamp, DPT_102, PT_104, PT_102, PT_108, PT_115, PT_117, PT_106, PT_110, DPT_101 FROM PGREACTOR2SEC WHERE t_stamp >= :1 ORDER BY t_stamp

Plan hash value: 2198310677

| Id  | Operation                   | Name                                                             | Starts | E-Rows | A-Rows |   A-Time   | Buffers | Reads  |

| 1 | TABLE ACCESS BY INDEX ROWID| PGREACTOR2SEC | 46 | 1 | 6220K|00:00:33.26 | 1410K| 13161 | |* 2 | INDEX RANGE SCAN | PGREACTOR2SEC_T_STAMP_NDX | 46 | 1 | 6220K|00:00:07.46 | 634K| 959 |

Peeked Binds (identified by position):

   1 - (TIMESTAMP): [Not Printable]

Predicate Information (identified by operation id):

   2 - access("T_STAMP">=:1)

Here the index is used but that isn't always the case. Is there any other way other than 100046 trace to get the bind value?

Also, there isn't much SQL being executed in this database. Is there a way to get Oracle to evaluate the value of the bind variable on each execution to ensure an appropriate execution plan?


This message is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email reply.

Received on Tue Mar 16 2010 - 14:58:21 CDT

Original text of this message