INDEX_OWNER INDEX_NAME COLUMN_NAME COLUMN_POSITION
—————————— —————————————- —————————————- —————
sachin I_COMMPART_T_CAID_CRDT_PRC_CID COMM_ADDRESS_ID 1
sachin I_COMMPART_T_CAID_CRDT_PRC_CID CREA_DATE 2
sachin I_COMMPART_T_CAID_CRDT_PRC_CID PARTY_ROLE_TYPE_CODE 3
sachin I_COMMPART_T_CAID_CRDT_PRC_CID COMM_ID 4

sachin I_COMMPART_T_CAID_MKTPL_ID COMM_ADDRESS_ID 1
sachin I_COMMPART_T_CAID_MKTPL_ID MKPLACE_ID 2

sachin I_COMMPART_T_COMM_ID COMM_ID 1

sachin I_COMMPART_T_CREA_DATE CREA_DATE 1

sachin I_COMMPART_T_LAST_UPDATED_DATE LAST_UPDATED_DATE 1

sachin PK_COMM_PARTICIPANTS_T COMM_PARTICIPANT_ID 1

sachin U_COMMPART_T_CID_CAID_PRID_CD COMM_ID 1
sachin U_COMMPART_T_CID_CAID_PRID_CD COMM_ADDRESS_ID 2
sachin U_COMMPART_T_CID_CAID_PRID_CD PARTY_ROLE_ID 3
sachin U_COMMPART_T_CID_CAID_PRID_CD COMM_PARTICIPANT_TYPE_CODE 4

and explain plan

——————————————————————————————————————————————
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | Pstart| Pstop |
——————————————————————————————————————————————
| 0 | SELECT STATEMENT | | 10 | 350 | 114 (3)| 00:00:02 | | |
|* 1 | VIEW | | 10 | 350 | 114 (3)| 00:00:02 | | |
|* 2 | COUNT STOPKEY | | | | | | | |
| 3 | VIEW | | 249 | 5478 | 114 (3)| 00:00:02 | | |
|* 4 | SORT ORDER BY STOPKEY | | 249 | 7968 | 114 (3)| 00:00:02 | | |
| 5 | NESTED LOOPS | | 249 | 7968 | 113 (2)| 00:00:02 | | |
| 6 | VIEW | VW_NSO_1 | 249 | 1992 | 62 (2)| 00:00:01 | | |
| 7 | SORT UNIQUE | | 249 | 13944 | | | | |
|* 8 | FILTER | | | | | | | |
| 9 | NESTED LOOPS | | 249 | 13944 | 62 (2)| 00:00:01 | | |
| 10 | TABLE ACCESS BY INDEX ROWID | COMM_ADDRESSES | 1 | 33 | 1 (0)| 00:00:01 | | |
|* 11 | INDEX UNIQUE SCAN | UNIQ_COMMADDR_LOWERADDR | 1 | | 1 (0)| 00:00:01 | | |
|* 12 | INDEX RANGE SCAN | I_COMMPART_T_CAID_CRDT_PRC_CID | 249 | 5727 | 61 (2)| 00:00:01 | | |
|* 13 | TABLE ACCESS BY GLOBAL INDEX ROWID| COMMUNI | 1 | 24 | 1 (0)| 00:00:01 | ROWID | ROWID |
|* 14 | INDEX UNIQUE SCAN | PK_COMMUNI | 1 | | 1 (0)| 00:00:01 | | |
——————————————————————————————————————————————
1 - filter(”RNUM”>:7)
2 - filter(ROWNUM<=:6)
4 - filter(ROWNUM<=:6)
8 - filter(:2=:2 AND INTERNAL_FUNCTION(”CP”.”CREA_DATE”)<:3)
13 - filter(”MKPLACE_ID”=:4 AND “RESPONSE_STATUS_TYPE_CODE”=:5 AND (”PARENT_COMM_ID” IS NULL OR “PARENT_COMM_ID”=0))
14 - access(”COMM_ID”=”$nso_col_1″)

The to_date function should have allowed the the index on CRE_DATE to be used. Perhaps the variables passed to the query were not selective enough to make the optimizer want to use the index. You can try running a 10053 trace to see what decisions the optimizer made, including if it evaluated the index at all and why it didn’t decide to use it.

Kerry

select * from ( select comm_dates.*, ROWNUM rnum from (select comm_id, comm_date_utc from communi where comm_id in ( select
distinct cp.comm_id from comm_parti cp, com_add ca where ca.comm_address_id = cp.comm_address_id and
ca.lwr_mail_add = :1 and cp.CREA_DATE >= :2 and cp.CREA_DATE < :3 ) and mkplace_id in ( :4 ) and
response_status_type_code in ( :5 ) and (parent_comm_id is null or parent_comm_id = 0) order by comm_date_utc desc ) comm_dates
where ROWNUM :7

——————————————————————————-
FINDINGS SECTION (4 findings)
——————————————————————————-

1- Restructure SQL finding (see plan 1 in explain plans section)
—————————————————————-
The predicate “CP”.”CREA_DATE”>=:B1 used at line ID 12 of the execution
plan contains an implicit data type conversion on indexed column
“CREA_DATE”. This implicit data type conversion prevents the optimizer
from selecting indices on table “SACHIN”.”comm_parti_T”.

Recommendation
————–
- Rewrite the predicate into an equivalent form to take advantage of
indices.

Rationale
———
The optimizer is unable to use an index if the predicate is an inequality
condition or if there is an expression or an implicit data type conversion
on the indexed column.

changed the column predicate but explain plan shows no improvement, what I am missing here ?

select * from ( select comm_dates.*, ROWNUM rnum from (select comm_id, comm_date_utc from communi where comm_id in ( select
distinct cp.comm_id from comm_parti cp, com_add ca where ca.comm_address_id = cp.comm_address_id and
ca.lwr_mail_add = :1 and cp.CREA_DATE >= TO_DATE(:2) and cp.CREA_DATE < TO_DATE(:3) ) and mkplace_id in ( TO_NUMBER(:4) ) and
response_status_type_code in ( TO_NUMBER(:4) ) and (parent_comm_id is null or parent_comm_id = 0) order by comm_date_utc desc ) comm_dates
where ROWNUM :7

thanks in advance ..

Try pasting the script into a file and executing it with @.

@create_tuning_task — for example

Kerry

SQL> SET LONG 10000;
SQL> SET PAGESIZE 9999
SET LINESIZE 155
SQL> SQL> set verify off
SQL> col recommendations for a150
SQL> accept task_name -
> prompt ‘Task_Name: ‘
Task_Name: DECLARE ret_val VARCHAR2(4000);
SQL> BEGIN
2 ret_val := dbms_sqltune.create_tuning_task(task_name=>’&&Task_name’, sql_id=>’&sql_id’, time_limit=>&time_limit);
3 dbms_sqltune.execute_tuning_task(’&&Task_name’);
4 END;
5 /
Enter value for sql_id: dt7vf07d0kj4n
Enter value for time_limit: 10
ret_val := dbms_sqltune.create_tuning_task(task_name=>’ DECLARE ret_val VARCHAR2(4000);’, sql_id=>’dt7vf07d0kj4n’, time_limit=>10);
*
ERROR at line 2:
ORA-06550: line 2, column 1:
PLS-00201: identifier ‘RET_VAL’ must be declared
ORA-06550: line 2, column 1:
PL/SQL: Statement ignored

Thanks also for the positive feedback.

Kerry