Archives of the TeradataForum
Message Posted: Tue, 21 Feb 2012 @ 13:47:06 GMT
I faced the same issue for Linux 32 ODBC driver , this is due to the version of the ODBC, it is happening due to the ODBC Driver's connect logic prematurely assumed that the connection is successful. When the database is down or some invalid ip is given in odbc.ini, the driver assuming the connection was successful, because the select returning a value >0, which indicates the socket is writable. Since connection was assumed successful, driver proceeds further and core dumping at some other socket call.
Check your version of and make sure it is 12.00.00.03 or 13.00.00.01 ODBC drivers.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|