Re: Oracle 9.0.1.0.0 and the indexes ...

I try to solve this problem this way :

CREATE TABLE LEDGER.LELACC00 (

        ID CHARACTER ( 10 ) NOT NULL,
        ACCOUNTDOMAINID CHARACTER ( 10 ),
        LEDGERPARTNERID CHARACTER ( 10 ),
        LEDGERACCOUNTNO VARCHAR ( 64 ),
        LEDGERSUBACCOUNTNO VARCHAR ( 64 ),
        PARENTLACCID CHARACTER ( 10 ),
        IVDESCRIPTIONS VARCHAR ( 200 ),
        ACCOUNTCHARACTER CHARACTER ( 1 ),
        BCRID CHARACTER ( 10 ),
        CONSTRAINT SQL030323184752320 PRIMARY KEY (ID)
        ) IN FRUSERSPACE1;

CREATE INDEX LEDGER.TC_LELACC008 ON LEDGER.LELACC00
(LEDGERPARTNERID)PCTFREE 0;
EXPLAIN PLAN FOR select * from LEDGER.LELACC00 where ledgerPartnerId='FT00AM72Nv'

there are two record into plan_table ( select * from plan_table )

--



(1.)


STATEMENT_ID    (null)
TIMESTAMP               2003-06-16 13:32:30.0
REMARKS                 (null)
OPERATION               TABLE ACCESS
OPTIONS                 FULL
OBJECT_NODE             :Q4352000
OBJECT_OWNER            LEDGER
OBJECT_NAME             LELACC00
OBJECT_INSTANCE 1
OBJECT_TYPE     (null)
OPTIMIZER       ANALYZED
SEARCH_COLUMNS  (null)
ID              1
PARENT_ID       0
POSITION                1
COST            1
CARDINALITY     1
BYTES           70
OTHER_TAG       PARALLEL_TO_SERIAL
PARTITION_START (null)
PARTITION_STOP  (null)
PARTITION_ID    (null)
OTHER           SELECT /*+ NO_EXPAND ROWID(A1) */ A1."ID",A1."ACCOUNTDO-
MAINID",A1."LEDGERPARTNERID",A1."LEDGERACCOUNTNO",A1."LEDGERSUBACCOUNTN-
O",A1."PARENTLACCID",A1."IVDESCRIPTIONS",A1."ACCOUNTCHARACTER",A1."BCRI-
D" FROM "LEDGER"."LELACC00" PX_GRANULE(0, BLOCK_RANGE, DYNAMIC)  A1
WHERE A1."LEDGERPARTNERID"='FT00AM72Nv'        QC (RANDOM)
DISTRIBUTION    QC (RANDOM)
CPU_COST        (null)
IO_COST         1
TEMP_SPACE      (null)



(2.)


STATEMENT_ID    (null)
TIMESTAMP               2003-06-16 13:32:30.0
REMARKS                 (null)
OPERATION               TABLE ACCESS
OPTIONS         (null)
OBJECT_NODE             (null)
OBJECT_OWNER            (null)
OBJECT_NAME             (null)
OBJECT_INSTANCE (null)
OBJECT_TYPE     (null)
OPTIMIZER       CHOOSE
SEARCH_COLUMNS  (null)
ID              1
PARENT_ID       (null)
POSITION                1
COST            1
CARDINALITY     1
BYTES           70
OTHER_TAG       (null)
PARTITION_START (null)
PARTITION_STOP  (null)
PARTITION_ID    (null)
OTHER           (null)
DISTRIBUTION    (null)
CPU_COST        (null)
IO_COST         1
TEMP_SPACE      (null)


.. so i think no index using in this table, because cause of other
tables I found TABLE ACCESS + BY INDEX ROWID, INDEX + RANGE SCAN in
OPERATION + OPTIONS pairs.

Anybody know what's wrong with this index ?

Thank you for any information !
Joseph G.

--
Posted via http://dbforums.com