Hitachi Vantara Pentaho Community Forums
Results 1 to 9 of 9

Thread: Dimension Lokkup not working properly!!!

  1. #1
    Join Date
    Sep 2007
    Posts
    24

    Question Dimension Lokkup not working properly!!!

    hello all,
    i'm having the following error when using Dimension Lookup:

    /////////////////////////////////////////////////////////////////////

    Because of an error this step can't continue:
    2007/12/04 22:10:11 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : Error inserting 'unknown' row in dimension [EMP] : insert into EMP(EMPNO, null) values (0, 1)
    2007/12/04 22:10:11 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : ORA-01747: invalid user.table.column, table.column, or column specification
    2007/12/04 22:10:11 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : be.ibridge.kettle.core.exception.KettleDatabaseException:
    2007/12/04 22:10:11 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : Error inserting 'unknown' row in dimension [EMP] : insert into EMP(EMPNO, null) values (0, 1)
    2007/12/04 22:10:11 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : ORA-01747: invalid user.table.column, table.column, or column specification
    ////////////////////////////////////////////////////////////////////////////////

    i can't realy understand what to do for the Dimension Lookup to work very well.
    please, can anybody help me ?
    attached is the transformation i'm using.

    thankx to all.
    Attached Files Attached Files
    • File Type: ktr g.ktr (8.0 KB, 45 views)

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

    Default

    As pointed out before on the forum last week, you need to specify
    • start of date range field
    • end of date range field
    • the fields to insert or update
    Some basic knowledge of slowly changing dimensions is unfortunately required.

    Matt

  3. #3
    Join Date
    Jul 2007
    Posts
    2,498

    Default

    Quote Originally Posted by MattCasters View Post
    • start of date range field
    • end of date range field
    Matt
    Just to check, aren't this 2 optional? (defaulting to now(), when left blank?)
    Pedro Alves
    Meet us on ##pentaho, a FreeNode irc channel

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

    Default

    Not at all, you need those 2 fields in a slowly changing dimension.
    As the name says, it allows the attributes (name, address, etc) associated with the natural key (customer_id) to slowly change over time.
    That means that you need some way of keeping the versions apart. Simply adding a number is not enough. A certain version of a dimension entry (customer_id) has a time frame during which it was valid.
    That time frame is specified by the start and end of the date range fields. (start_date, end_date)

    All the best,
    Matt

  5. #5
    Join Date
    Sep 2007
    Posts
    24

    Exclamation Another strange Error using the Dimension Lookup

    Hello again,
    when using the dimension lookup too, i got this error too:

    //////////////////////////////////////////////////////////////////////////

    2007/12/05 07:05:07 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : Because of an error this step can't continue:
    2007/12/05 07:05:07 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : Error inserting row
    2007/12/05 07:05:07 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : ORA-00957: duplicate column name
    2007/12/05 07:05:07 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : be.ibridge.kettle.core.exception.KettleDatabaseException:
    2007/12/05 07:05:07 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : Error inserting row
    2007/12/05 07:05:07 - Dimension lookup/update.0 - ERROR (version 2.5.2, build 252005 from 2007/10/23 19:31:44) : ORA-00957: duplicate column name

    ////////////////////////////////////////////////////////////////////////////////

    please can anybody help me ?

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

    Default

    > ORA-00957: duplicate column name

    It means you specified the same column twice. if you want more advice, attach a transformation.

  7. #7
    Join Date
    Sep 2007
    Posts
    24

    Smile The Transformation of the Dimension

    Hello Matt
    attached is the transformation u asked about.
    hope to hear from u soon.

    Have a nice day.
    Attached Files Attached Files

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

    Default

    Mustafa, you specified the same fields for the keys as for the update fields.

    Matt

  9. #9
    Join Date
    Sep 2007
    Posts
    24

    Smile Can u specify More?

    Matt,
    I can't understand from the document what's the Key's for, and what's the Fields for ?
    can you specify plz?
    can you give me an example other than the one mensioned in the Documentation ?

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.