Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: [Microsoft][ODBC Driver Manager] Invalid string or buffer length

  1. #1
    Join Date
    Apr 2014

    Default [Microsoft][ODBC Driver Manager] Invalid string or buffer length

    Hey, I'm hoping someone can help out here, as I'm pretty exhausted trying to find a solution. Any help is greatly appreciated!

    I'm trying to extract some data from Access to SQL Server. I've defined 8 different ODBC connections on the server, and this job runs for each. It knows how to swap them out, so assume that all works. I'm getting the following error on *some* tables, but not all:
    ERROR 09-04 23:26:23,340 - MS Access <TableName> - org.pentaho.di.core.exception.KettleDatabaseException: 
    Couldn't get row from result set
    Unable to get value 'String(7)' from database resultset, index 0
    [Microsoft][ODBC Driver Manager] Invalid string or buffer length
        at org.pentaho.di.core.database.Database.getRow(
        at org.pentaho.di.core.database.Database.getRow(
        at org.pentaho.di.trans.steps.tableinput.TableInput.processRow(
        at Source)
    Caused by: org.pentaho.di.core.exception.KettleDatabaseException:
    I'm hesitant to point to any environment issues, as when I Play this through spoon, it works *perfectly* all the time.

    Can anyone think of what is different between Spoon and Kitchen?

    Here's the command line from kitchen.bat that's getting run:

    "C:\Program Files\Java\jre7\bin\java.exe" -Xmx512m "-Djava.library.path=libswt\win64" "-DKETTLE_HOME=D:\KettleHome" "-DKETTLE_REPOSITORY=" "-DKETTLE_USER=" "-DKETTLE_PASSWORD=" "-DKETTLE_PLUGIN_PACKAGES=" "-DKETTLE_LOG_SIZE_LIMIT=" -jar "C:\Kettle\pdi-ce-4.4.0-stable\data-integration\launcher\launcher.jar" -lib ..\libswt\win64 -main /rep:ValidRepName /job:"JobName"

    And some software information:
    -OS Version: Win Server 2008 R2 64-bit
    -PDI Version: 4.4 Stable CE
    -JRE Version: 7 build 51

  2. #2
    Join Date
    Apr 2008


    Not saying that this is the cause, but the Sun JDBC-ODBC bridge is "iffy"
    If you are pulling data from Access, I would use the Access Input step.
    For output to SQL Server, I would not use ODBC, but pushing directly through JDBC

  3. #3
    Join Date
    Nov 2008


    I have used the JDBC-ODBC bridge driver on Access files in the past with some success. I recall getting this type of error when the data was corrupt or invalid but I don't remember getting different results in Spoon versus Kitchen.

    Also, I see the JDBC-ODBC bridge driver will not be included in Java 8. It might be a good time to move gutlez recommended.
    Java 1.7 (64 bit)
    MySQL 5.6 (64 bit)
    Windows 7 (64 bit)

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.