These SQL statements only reveal the bind variables used, and not their actual values.
To get a more realistic explain plan, ask your developers to provide you with the actual literal values used in the SQL statement, and then prepare a script that contains the following:
connect username/password SET TIMING ON SET LINESIZE 200 SET PAGESIZE 0 var b9 number; var b8 number; var b7 number; var b6 varchar2(3); var b5 varchar2(3); var b4 varchar2(4); var b3 varchar2(1); var b2 varchar2(2); var b1 varchar2(2); exec :B9 := 12345; exec :B8 := 6127737; exec :B7 := 2013; exec :B6 := 'KOC'; exec :B5 := 'PPQ'; exec :B4 := 'OOPQ'; exec :B3 := '7'; exec :B2 := 'YM'; exec :B1 := 'WT'; EXPLAIN PLAN FOR SELECT ... FROM ... WHERE COL1 NOT IN (:B6, :B5, :B4) AND COL2 = :8 AND COL3 = :9; SELECT * FROM table(DBMS_XPLAN.DISPLAY);
Run the script using sqlplus.
Such a script can also come in handy if you're asked to perform changes to the tables' structure, and then execute the actual script to see how much time it takes to execute.
In this case, remove the EXPLAIN PLAN clause and the call to DBMS_XPLAN.DISPLAY, and you'll have all you need to execute the actual SQL statements you're tuning.
No comments:
Post a Comment