Hitachi Vantara Pentaho Community Forums
Results 1 to 10 of 10

Thread: Problem with "database join" step

  1. #1

    Unhappy Problem with "database join" step

    Hello,

    I'm running 2.5.1 and I still have the following problem: as you can see the attached transform I'm trying to read some data from a table, and make a lookup on the same table with data from the same columns !

    In the lookup step I get the following error:

    2007/09/24 13:16:38 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR (version 2.5.1, build 1 from 2007/09/24 12:50:22) : Because of an error, this step can't continue:
    2007/09/24 13:16:38 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR (version 2.5.1, build 1 from 2007/09/24 12:50:22) : ERROR executing query in part[OQ Set values]
    2007/09/24 13:16:38 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR (version 2.5.1, build 1 from 2007/09/24 12:50:22) :
    2007/09/24 13:16:38 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR (version 2.5.1, build 1 from 2007/09/24 12:50:22) : offending row : [DATA_IERI=2007/09/23 00:00:00.000, DITTA=1, DEPOSITO=19]
    2007/09/24 13:16:38 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR (version 2.5.1, build 1 from 2007/09/24 12:50:22) :
    2007/09/24 13:16:38 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR (version 2.5.1, build 1 from 2007/09/24 12:50:22) : Error setting value #2 [ 1] on prepared statement (Integer)
    2007/09/24 13:16:38 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR (version 2.5.1, build 1 from 2007/09/24 12:50:22) : java.sql.SQLException: General error
    2007/09/24 13:16:38 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR (version 2.5.1, build 1 from 2007/09/24 12:50:22) : General error


    I've tried to configure in the database step the data as Integer and as BigNumber, but with no results. I still get the same error.

    Do you think I should file a Bug Report ?

    Thank you very much.

    Best regards,
    Paolo
    Attached Files Attached Files

  2. #2
    Join Date
    May 2006
    Posts
    4,882

    Default

    Lose the quotes around ? ... why does everybody want to put quotes around parameter markers today?

    Regards,
    Sven

  3. #3

    Default

    Hi, Sven.

    I've removed the quotes around parameter 1 (don't know why had added them...), the error is for parameter 2 (the integer without quotes)

    I'm still getting the same error:

    2007/09/25 10:01:45 - Cerca max presenze per negozi esistenti di ieri.0 - Because of an error, this step can't continue:
    2007/09/25 10:01:45 - Cerca max presenze per negozi esistenti di ieri.0 - ERROR executing query in part[OQ Set values]
    2007/09/25 10:01:45 - Cerca max presenze per negozi esistenti di ieri.0 -
    2007/09/25 10:01:45 - Cerca max presenze per negozi esistenti di ieri.0 - offending row : [DATA_IERI=2007/09/24 00:00:00.000, DITTA=1, DEPOSITO=246]
    2007/09/25 10:01:45 - Cerca max presenze per negozi esistenti di ieri.0 -
    2007/09/25 10:01:45 - Cerca max presenze per negozi esistenti di ieri.0 - Error setting value #2 [ 1] on prepared statement (Integer)
    2007/09/25 10:01:45 - Cerca max presenze per negozi esistenti di ieri.0 - java.sql.SQLException: General error
    2007/09/25 10:01:45 - Cerca max presenze per negozi esistenti di ieri.0 - General error

    Thank you for your help.

    Best regards,
    Paolo

  4. #4
    Join Date
    May 2006
    Posts
    4,882

    Default

    Next question... is DITTA an integer in your table? Or more specifically what's the type of DITTA.

    Regards,
    Sven

  5. #5

    Default

    Right. Sorry I forgot to post the table layout (I've used the create DDL from database explorer in Spoon):

    CREATE TABLE UNIDW.VENDUTO_PRESENZE
    (
    DITTA INTEGER
    , DEPOSITO INTEGER
    , DATA DATE
    , ORA INTEGER
    , PRESENZE INTEGER
    , QTA_VENDUTA INTEGER
    , VALORE_VENDUTO NUMBER(15, 2)
    , NUMERO_SCONTRINI INTEGER
    , NCOUNTER INTEGER
    )
    ;



    Best regards,
    Paolo



    Ah, btw, I don't seem to get email notifications for new posts...

  6. #6
    Join Date
    May 2006
    Posts
    4,882

    Default

    Try again but don't use ODBC for Oracle.

    Regards,
    Sven

  7. #7

    Default

    Ehm, try again to give you the layout or just use another driver for Oracle altogether ?

  8. #8
    Join Date
    May 2006
    Posts
    4,882

    Default

    Don't use ODBC... first try Native... ODBC is known for its akward behaviour.

    Regards,
    Sven

  9. #9

    Default

    You're right...

    when I switched to native JDBC drivers the problem just disappeared !!!

    Thank you very much, Sven !

    Best regards,
    Paolo

  10. #10
    Join Date
    May 2006
    Posts
    4,882

    Default

    ODBC is the last option, use all other possible access methods before.

    Oracle in combination with ODBC is infamous for eating the error messages. I once had some people looking for a couple of hours on an Oracle problem which when they switched form ODBC to the native drivers was just a tablespace full problem, ODBC only returned "General error" without details.

    Regards,
    Sven

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.