Hitachi Vantara Pentaho Community Forums
Results 1 to 5 of 5

Thread: Error -- version 3.0.2, build 538

  1. #1
    Join Date
    Sep 2008
    Posts
    3

    Default Error -- version 3.0.2, build 538

    Hi,

    I'm a real newbie to Pentaho and ETLs in general. I actually just run ETLs but haven't really built any. I'm getting an error (please see below for a portion of the error) in one of my transformation and have no clue how to resolve it -- (our ETL "maintenance" person is out right now). The transformation consists of 5 table inputs, then each one hops to their own Select/Rename Values object for mapping, and then finally they all hop into a table output.

    Please let me know if more info. is required. Thanks in advance for any help

    ggseven



    2008/09/02 09:38:35 - krs_stg_pipeline_dtl.0 - ERROR (version 3.0.2, build 538 from 2008/02/06 13:13:19) : Because of an error, this step can't continue:
    2008/09/02 09:38:35 - krs_stg_pipeline_dtl.0 - ERROR (version 3.0.2, build 538 from 2008/02/06 13:13:19) : Error batch inserting rows into table [krs_stg_pipeline_dtl].
    2008/09/02 09:38:35 - krs_stg_pipeline_dtl.0 - ERROR (version 3.0.2, build 538 from 2008/02/06 13:13:19) : Errors encountered (first 10):
    2008/09/02 09:38:35 - krs_stg_pipeline_dtl.0 - ERROR (version 3.0.2, build 538 from 2008/02/06 13:13:19) : Data truncation: Out of range value adjusted for column 'AGENT_ID' at row 1
    2008/09/02 09:38:35 - krs_stg_pipeline_dtl.0 - ERROR (version 3.0.2, build 538 from 2008/02/06 13:13:19) :
    2008/09/02 09:38:35 - krs_stg_pipeline_dtl.0 - ERROR (version 3.0.2, build 538 from 2008/02/06 13:13:19) :
    2008/09/02 09:38:35 - krs_stg_pipeline_dtl.0 - ERROR (version 3.0.2, build 538 from 2008/02/06 13:13:19) : Error updating batch
    2008/09/02 09:38:35 - krs_stg_pipeline_dtl.0 - ERROR (version 3.0.2, build 538 from 2008/02/06 13:13:19) : Data truncation: Out of range value adjusted for column 'AGENT_ID' at row 1

  2. #2

    Default

    I imagine your problem has nothing to do with Pentaho, rather data and your database settings.

    I know this problem exists in MySQL (as the output database). Are you using floating point numbers for AGENT_ID?

    Try searching for the error "Data truncation: Out of range value adjusted for column" in relation to your database type(MySQL, Oracle, Access), and check your data and database settings are correct.

  3. #3
    Join Date
    Sep 2008
    Posts
    3

    Default

    Quote Originally Posted by JBarclay View Post
    I imagine your problem has nothing to do with Pentaho, rather data and your database settings.

    I know this problem exists in MySQL (as the output database). Are you using floating point numbers for AGENT_ID?

    Try searching for the error "Data truncation: Out of range value adjusted for column" in relation to your database type(MySQL, Oracle, Access), and check your data and database settings are correct.

    Thanks for the response. Yes I believe too that my problem is with the data and not Pentaho.

    Actually I think it's a problem with a query which has input date variables (I believe I've pinpointed it). I use the following date logic in my query:

    WHERE t.start_time BETWEEN to_timestamp(?, 'YYYY/MM/DD HH24:MI:SSxFF') AND to_timestamp(?, 'YYYY/MM/DD HH24:MI:SSxFF')

    And I've got a Get Variables object which pulls the dates from another transformation which sets the variables.

    It's either that or maybe like you say a field such as AGENT_ID which might have a floating point issue or something which I wasn't aware about...

  4. #4

    Default

    "Data truncation: Out of range value adjusted for column 'AGENT_ID' at row 1"

    That's the last line of the error code. The advice I gave you was all based on that.

    Whether or not you have other issues (such as date), you also have an issue with AGENT_ID, as previously mentioned.

  5. #5
    Join Date
    Sep 2008
    Posts
    3

    Default

    Thanks for the clarification. Yes, it appears actually Agent_ID is the big "problem child" (and not my date input variables)...For the first time, there were some records populated for AgentID from our input data source with negative numbers; our output tables were not set up to handle negative numbers for this particular field. We had to make sure they were "signed". (it's something so "small" if you think about it but it affects a lot)

    Thanks again,

    ggseven

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.