Archives of the TeradataForum

Message Posted: Mon, 13 Jun 2016 @ 08:08:56 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hi

We've had a similar problem too on 14.10 using the .NET Data Provider 14.11. On the 16th of February 2016 we began to experience timeouts in a client service. According to the Teradata team and the Windows platform Operations team, nothing had been changed or upgraded at this point.

At random intervals we got timeouts when trying to open a connection. Always 30 seconds after request was issued.

Error message:

     [.NET Data Provider for Teradata] [100038] Command did not complete within the time specified (timeout).
     [Teradata Database] [3110] The transaction was aborted by the user.
     [Socket Transport] [115003] The receive operation timed out.

Setting Connection Timeout would not have any effect, as these errors was caused by a command timeout.

Again, this is strange since opening a connection should not execute a command at all, just open a connection.

We also tried to add "Command Timeout=3600;" ?to the connection string, but this version of the driver did not accept this option.

The solution was to upgrade the Teradata .NET Data Provider to version 15.11. Then we were able to set the command timeout in the connection string and the timeouts disappeared.

Best regards,

Kaare Wehn

	<Prev	Next>		<<First	<Prev	Next>	Last>>