tteradata input Truncation Error

Highlighted
Four Stars

tteradata input Truncation Error

Hi

While reading data from tteradatainput ,I am getting the below error.

If i read 100 records then it works fine, it fails for around 90k records. Any help?

 

 

Starting job TestTrunc at 16:16 01/06/2018.

[statistics] connecting to socket on port 3804
[statistics] connected
2018-06-01 16:16:20|I6cAJs|I6cAJs|I6cAJs|11928|MSA|TestTrunc|_iiip8GXvEei_spld3uFkiw|0.1|Default||begin||
2018-06-01.16:16:24.189 TERAJDBC4 ERROR [main] com.teradata.jdbc.jdk6.JDK6_SQL_Connection@3532ec19 Read message 1: Bad response message header with invalid message length of 6362648 bytes
2018-06-01.16:16:24.357 TERAJDBC4 ERROR [main] com.teradata.jdbc.jdk6.JDK6_SQL_Connection@3532ec19 Read message 1 failed; closing socket due to: java.io.IOException: Bad response message header with invalid message length of 6362648 bytes
2018-06-01.16:16:24.414 TERAJDBC4 ERROR [main] com.teradata.jdbc.jdk6.JDK6_SQL_Connection@3532ec19 Packet receive Fri Jun 01 16:16:24 PDT 2018 socket orig=teradevl.ca.boeing.com local=0.0.0.0/0.0.0.0:64453 remote=teradevlcop1.ca.boeing.com/137.136.234.163:1025 keepalive=unavailable nodelay=unavailable receive=unavailable send=unavailable linger=unavailable traffic=unavailable concurrent=3 contimeout=10000 conwait=1000 connecttime=36 connecttotaltime=39 connectattempts=1 connectfailures=0 reconnectattempts=0 recoverable=false redrive=false failurecache={} cid=670002 sess=10111881 java.io.IOException: Bad response message header with invalid message length of 6362648 bytes   at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:768)   at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream(TDPacketStream.java:768)   at com.teradata.jdbc.jdbc_4.statemachine.StatementReceiveState.action(StatementReceiveState.java:141)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(StatementController.java:137)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.run(StatementController.java:128)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:387)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:329)   at com.teradata.jdbc.jdbc_4.TDStatement.doNonPrepExecuteQuery(TDStatement.java:317)   at com.teradata.jdbc.jdbc_4.TDStatement.executeQuery(TDStatement.java:1106)   at msa.testtrunc_0_1.TestTrunc.tTeradataInput_1Process(TestTrunc.java:1026)   at msa.testtrunc_0_1.TestTrunc.runJobInTOS(TestTrunc.java:10066)   at msa.testtrunc_0_1.TestTrunc.main(TestTrunc.java:9872)  
[FATAL]: msa.testtrunc_0_1.TestTrunc - tTeradataInput_1 [Teradata JDBC Driver] [TeraJDBC 15.10.00.14] [Error 804] [SQLState 08S01] Socket communication failure for Packet receive Fri Jun 01 16:16:24 PDT 2018 socket orig=teradevl.ca.boeing.com local=0.0.0.0/0.0.0.0:64453 remote=teradevlcop1.ca.boeing.com/137.136.234.163:1025 keepalive=unavailable nodelay=unavailable receive=unavailable send=unavailable linger=unavailable traffic=unavailable concurrent=3 contimeout=10000 conwait=1000 connecttime=36 connecttotaltime=39 connectattempts=1 connectfailures=0 reconnectattempts=0 recoverable=false redrive=false failurecache={} cid=670002 sess=10111881 java.io.IOException: Bad response message header with invalid message length of 6362648 bytes   at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:768)   at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream(TDPacketStream.java:768)   at com.teradata.jdbc.jdbc_4.statemachine.StatementReceiveState.action(StatementReceiveState.java:141)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(StatementController.java:137)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.run(StatementController.java:128)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:387)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:329)   at com.teradata.jdbc.jdbc_4.TDStatement.doNonPrepExecuteQuery(TDStatement.java:317)   at com.teradata.jdbc.jdbc_4.TDStatement.executeQuery(TDStatement.java:1106)   at msa.testtrunc_0_1.TestTrunc.tTeradataInput_1Process(TestTrunc.java:1026)   at msa.testtrunc_0_1.TestTrunc.runJobInTOS(TestTrunc.java:10066)   at msa.testtrunc_0_1.TestTrunc.main(TestTrunc.java:9872)  
java.sql.SQLException: [Teradata JDBC Driver] [TeraJDBC 15.10.00.14] [Error 804] [SQLState 08S01] Socket communication failure for Packet receive Fri Jun 01 16:16:24 PDT 2018 socket orig=teradevl.ca.boeing.com local=0.0.0.0/0.0.0.0:64453 remote=teradevlcop1.ca.boeing.com/137.136.234.163:1025 keepalive=unavailable nodelay=unavailable receive=unavailable send=unavailable linger=unavailable traffic=unavailable concurrent=3 contimeout=10000 conwait=1000 connecttime=36 connecttotaltime=39 connectattempts=1 connectfailures=0 reconnectattempts=0 recoverable=false redrive=false failurecache={} cid=670002 sess=10111881 java.io.IOException: Bad response message header with invalid message length of 6362648 bytes   at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:768)   at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream(TDPacketStream.java:768)   at com.teradata.jdbc.jdbc_4.statemachine.StatementReceiveState.action(StatementReceiveState.java:141)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(StatementController.java:137)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.run(StatementController.java:128)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:387)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:329)   at com.teradata.jdbc.jdbc_4.TDStatement.doNonPrepExecuteQuery(TDStatement.java:317)   at com.teradata.jdbc.jdbc_4.TDStatement.executeQuery(TDStatement.java:1106)   at msa.testtrunc_0_1.TestTrunc.tTeradataInput_1Process(TestTrunc.java:1026)   at msa.testtrunc_0_1.TestTrunc.runJobInTOS(TestTrunc.java:10066)   at msa.testtrunc_0_1.TestTrunc.main(TestTrunc.java:9872)  
    at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:94)
    at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:69)
    at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeIoJDBCException(ErrorFactory.java:207)
    at com.teradata.jdbc.jdbc_4.util.ErrorAnalyzer.analyzeIoError(ErrorAnalyzer.java:59)
    at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:919)
    at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream(TDPacketStream.java:768)
    at com.teradata.jdbc.jdbc_4.statemachine.StatementReceiveState.action(StatementReceiveState.java:141)
    at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(StatementController.java:137)
    at com.teradata.jdbc.jdbc_4.statemachine.StatementController.run(StatementController.java:128)
    at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:387)
    at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:329)
    at com.teradata.jdbc.jdbc_4.TDStatement.doNonPrepExecuteQuery(TDStatement.java:317)
    at com.teradata.jdbc.jdbc_4.TDStatement.executeQuery(TDStatement.java:1106)
    at msa.testtrunc_0_1.TestTrunc.tTeradataInput_1Process(TestTrunc.java:1026)
    at msa.testtrunc_0_1.TestTrunc.runJobInTOS(TestTrunc.java:10066)
    at msa.testtrunc_0_1.TestTrunc.main(TestTrunc.java:9872)
Caused by: java.io.IOException: Bad response message header with invalid message length of 6362648 bytes
    at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:768)
    ... 11 more
Exception in component tTeradataInput_1 (TestTrunc)
java.sql.SQLException: [Teradata JDBC Driver] [TeraJDBC 15.10.00.14] [Error 804] [SQLState 08S01] Socket communication failure for Packet receive Fri Jun 01 16:16:24 PDT 2018 socket orig=teradevl.ca.boeing.com local=0.0.0.0/0.0.0.0:64453 remote=teradevlcop1.ca.boeing.com/137.136.234.163:1025 keepalive=unavailable nodelay=unavailable receive=unavailable send=unavailable linger=unavailable traffic=unavailable concurrent=3 contimeout=10000 conwait=1000 connecttime=36 connecttotaltime=39 connectattempts=1 connectfailures=0 reconnectattempts=0 recoverable=false redrive=false failurecache={} cid=670002 sess=10111881 java.io.IOException: Bad response message header with invalid message length of 6362648 bytes   at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:768)   at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream(TDPacketStream.java:768)   at com.teradata.jdbc.jdbc_4.statemachine.StatementReceiveState.action(StatementReceiveState.java:141)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(StatementController.java:137)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.run(StatementController.java:128)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:387)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:329)   at com.teradata.jdbc.jdbc_4.TDStatement.doNonPrepExecuteQuery(TDStatement.java:317)   at com.teradata.jdbc.jdbc_4.TDStatement.executeQuery(TDStatement.java:1106)   at msa.testtrunc_0_1.TestTrunc.tTeradataInput_1Process(TestTrunc.java:1026)   at msa.testtrunc_0_1.TestTrunc.runJobInTOS(TestTrunc.java:10066)   at msa.testtrunc_0_1.TestTrunc.main(TestTrunc.java:9872)  
    at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:94)
    at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:69)
    at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeIoJDBCException(ErrorFactory.java:207)
    at com.teradata.jdbc.jdbc_4.util.ErrorAnalyzer.analyzeIoError(ErrorAnalyzer.java:59)
    at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:919)
    at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream(TDPacketStream.java:768)
    at com.teradata.jdbc.jdbc_4.statemachine.StatementReceiveState.action(StatementReceiveState.java:141)
    at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(StatementController.java:137)
    at com.teradata.jdbc.jdbc_4.statemachine.StatementController.run(StatementController.java:128)
    at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:387)
    at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:329)
    at com.teradata.jdbc.jdbc_4.TDStatement.doNonPrepExecuteQuery(TDStatement.java:317)
    at com.teradata.jdbc.jdbc_4.TDStatement.executeQuery(TDStatement.java:1106)
    at msa.testtrunc_0_1.TestTrunc.tTeradataInput_1Process(TestTrunc.java:1026)
    at msa.testtrunc_0_1.TestTrunc.runJobInTOS(TestTrunc.java:10066)
    at msa.testtrunc_0_1.TestTrunc.main(TestTrunc.java:9872)
Caused by: java.io.IOException: Bad response message header with invalid message length of 6362648 bytes
    at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:768)
    ... 11 more
Data truncation
2018-06-01 16:16:24|I6cAJs|I6cAJs|I6cAJs|MSA|TestTrunc|Default|6|Java Exception|tTeradataInput_1|java.sql.SQLException:[Teradata JDBC Driver] [TeraJDBC 15.10.00.14] [Error 804] [SQLState 08S01] Socket communication failure for Packet receive Fri Jun 01 16:16:24 PDT 2018 socket orig=teradevl.ca.boeing.com local=0.0.0.0/0.0.0.0:64453 remote=teradevlcop1.ca.boeing.com/137.136.234.163:1025 keepalive=unavailable nodelay=unavailable receive=unavailable send=unavailable linger=unavailable traffic=unavailable concurrent=3 contimeout=10000 conwait=1000 connecttime=36 connecttotaltime=39 connectattempts=1 connectfailures=0 reconnectattempts=0 recoverable=false redrive=false failurecache={} cid=670002 sess=10111881 java.io.IOException: Bad response message header with invalid message length of 6362648 bytes   at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:768)   at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream(TDPacketStream.java:768)   at com.teradata.jdbc.jdbc_4.statemachine.StatementReceiveState.action(StatementReceiveState.java:141)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(StatementController.java:137)   at com.teradata.jdbc.jdbc_4.statemachine.StatementController.run(StatementController.java:128)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:387)   at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:329)   at com.teradata.jdbc.jdbc_4.TDStatement.doNonPrepExecuteQuery(TDStatement.java:317)   at com.teradata.jdbc.jdbc_4.TDStatement.executeQuery(TDStatement.java:1106)   at msa.testtrunc_0_1.TestTrunc.tTeradataInput_1Process(TestTrunc.java:1026)   at msa.testtrunc_0_1.TestTrunc.runJobInTOS(TestTrunc.java:10066)   at msa.testtrunc_0_1.TestTrunc.main(TestTrunc.java:9872)  |1
[ERROR]: msa.testtrunc_0_1.TestTrunc - talendLogs_DB - Data truncation
2018-06-01 16:16:24|I6cAJs|I6cAJs|I6cAJs|11928|MSA|TestTrunc|_iiip8GXvEei_spld3uFkiw|0.1|Default||end|failure|3963
[statistics] disconnected
Job TestTrunc ended at 16:16 01/06/2018. [exit code=1]

Highlighted
Moderator

Re: tteradata input Truncation Error

Hello,

What's your Teradata version? Could you please indicate on which talend build version you got this issue?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Four Stars

Re: tteradata input Truncation Error

You mean the Teradata Driver ? It is 15.10 ([Teradata Database] [TeraJDBC 15.10.00.33])

I am not sure on how to check the enterprise Teradata version. 

 

I am using Talend Real time big data platform 6.4.1

Highlighted
Six Stars

Re: tteradata input Truncation Error

Hi,

 

Can you tell me the resolution for this issue, if it is fixed.

 

we are now migrating the Teradata 15 version to 16 version, unfortunately facing similar issue in Talend 6.4.1

 

I have performed below once to fix the issue, but issue is re-occurring again,

 

1. Removed the jars of older version in talend studio/workplace from the  lib/java folders and placed new Teradata 16 version --> didn't worked.

2. Used tLibraryLoad component in Talend studio 6.4.1 to load the latest version --> Didn't worked.

3. I have manually edited the .java file for all the tTeradata components and started the Talend studio, then at runtime the job it asked for a new version jar.

    for once it worked, but after restarting the studio again the version is showing as 15 only.

every day, we cannot go and edit the .java file right.

So, I would like to have a permanent solution for this.

 

After importing the new Teradata version also, it is showing again the older version after restarting or re-opening the Talend studio, so is it a bug of Talend studio 6.4 or am I missing anything.

 

Kindly provide any other suggestions for this issue.

 

Best Regards,

Meena P.

Highlighted
Four Stars

Re: tteradata input Truncation Error

Please also delete the files from the Nexus repository

 

2019 GARTNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog

Put Massive Amounts of Data to Work

Learn how to make your data more available, reduce costs and cut your build time

Watch Now