Does anyone know what would cause, or how to correct a Socket Error? Below are the details of the error message:
Is this error repeatble or occurring at random? if occurring at random intervals try to increase the "concurrent" limit from 3 to 10. if you hit this error every single time, try uninstall reinstall the JDBC driver and check if the installation is ok then retry. If you again have the same problem open a ticket with GSC. - Thanks, Sankar
(1) The socket connection is originating and ending at the same IP I don't think that could be a net work issue!!
(2) 'database restart' error most likely reported as an error of 'database restart' not 'socket error'.
(3) Any 'abort session' by user likely be reported as 'session aborted by peer' error..
Thanks for the replies. This is a process being run by a 3rd Party company supporting a Teradata process. This error has occurred every night that they have tried to run the process. My impression is that they are moving a large amount of data while doing this.
Once again, please discount what "TDDeveloper" said.
The "orig" in the error message refers to the "original" Teradata Database hostname specified by the application; it does not mean "originating".
TDDeveloper -- please refrain from posting incorrect information, or you will be banned from the forums.
We saw this error on a customer's site when running a query like "select A.DatabaseName,A.TableName,A.TableKind FROM DBC.TablesV A WHERE TableKind = 'T' OR TableKind = 'O'". We suspect it is the size of data returned caused the error, will modify the query to limit the resultset.
Teradata JDBC Driver 14.00.00.21 has been released and is now available for download here on Developer Exchange.
Teradata JDBC Driver 14.00.00.21 contains the fix for JDBC DR 155367.