Hitachi Vantara Pentaho Community Forums
Results 1 to 2 of 2

Thread: Dimension lookup/update step creating multiple indexes on the same column

  1. #1
    Join Date
    Dec 2010
    Posts
    4

    Default Dimension lookup/update step creating multiple indexes on the same column

    Using Oracle sql the lookup/update step generates a create table query in which an index is made for the technical key field ( Primary key (id_column_name) ).

    In the next step an index is trying to be made for the same column resulting in ORA-01408:such column list already indexed.

    I can't see where I went wrong. Anybody any ideas?

    Also: why a bitmap index???



    CREATE TABLE dim_sivvpa
    (
    id_vektisprestatie INTEGER
    , version INTEGER
    , date_from DATE
    , date_to DATE
    , SRT_CD_PRST VARCHAR2(3)
    , CD_PRST VARCHAR2(12)
    , OMS VARCHAR2(200)
    , DAT_STRT DATE
    , DAT_END DATE
    , PRIMARY KEY (id_vektisprestatie)
    )
    ;CREATE INDEX idx_dim_sivvpa_lookup
    ON dim_sivvpa
    (
    SRT_CD_PRST
    , CD_PRST
    )
    ;
    CREATE BITMAP INDEX idx_dim_sivvpa_tk
    ON dim_sivvpa
    (
    id_vektisprestatie
    )
    ;

    Thanks in advance,
    Ben
    Last edited by benslag; 02-21-2011 at 08:12 AM.

  2. #2
    Join Date
    Nov 1999
    Posts
    9,729

    Default

    I guess it tries to tell you to use a bitmap index if you can and a primary key if you can't.
    Bitmap indexes are optimal for joining dimensions to fact tables, hence the proposal.

    The generated SQL is a proposal, you can change it to your liking.
    If you feel that this PDI shouldn't propose one or the other, by all means voice your opinion and file JIRA case. :-)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.