> Why is the Parse Count So High even when Unique index is being used ?
>
> NOTE Unique index IDX_INTEREST_DETAILS_TABLE on IDT
> ( entity_id, entity_type, interest_ind, interest_type, serial_num )
>
> Am a Novice of sorts
>
> **************************************************************************
> ******
>
> select entity_id ,entity_type ,interest_ind ,interest_type ,serial_num
> from
> IDT where ((ENTITY_ID=:b0 and ENTITY_TYPE=:b1) and ENTITY_CRE_FLG='N')
>
>
>
> call count cpu elapsed disk query current
> rows
> ------- ------ -------- ---------- ---------- ---------- ----------
> ----------
> Parse 122 0.06 0.02 0 0 0
> 0
> Execute 122 0.00 0.00 0 0 0
> 0
> Fetch 122 0.04 0.63 178 1042 0
> 0
> ------- ------ -------- ---------- ---------- ---------- ----------
> ----------
> total 366 0.10 0.65 178 1042 0
> 0
>
> Misses in library cache during parse: 0
> Optimizer goal: CHOOSE
> Parsing user id: 12 (TBAGEN)
>
> Rows Execution Plan
> ------- ---------------------------------------------------
> 0 SELECT STATEMENT GOAL: CHOOSE
> 18 TABLE ACCESS (BY ROWID) OF 'INTEREST_DETAILS_TABLE'
> 19 INDEX (RANGE SCAN) OF 'IDX_INTEREST_DETAILS_TABLE' (UNIQUE)
>
>
> **************************************************************************
Received on Wed Oct 25 2000 - 05:41:43 CDT
