Archives of the TeradataForum

Message Posted: Mon, 09 May 2005 @ 14:26:32 GMT

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

It is possible that the IP address of your DBS changed and that the ODBC DSN has saved the old IP address. Maybe the apps that work specify the DBS name specifically during logon, while the ones that fail do not. (If the system name is not specified the driver will probably 'optimize' by using the saved IP address.)

You could try deleting and recreating the DSN - if you are able to do that. This time make sure you check the "Do not resolve alias name" checkbox.

On the other hand the message implies that the problem is in CLI. CLI0126 is an invalid length specification - which does not seem to make sense in this situation unless you have a mis-matched set of Teradata dlls. (CLI, TDGSS, ODBC - but then nothing would work.)

We also have a MOSI error 126 - which basically just tells you that there was an 'internal error'.

Reinstalling SQL Assistant seems unlikely to help (Although upgrading to 7.0 might provide you with some useful extra features.)

It is more likely that ODBC and/or CLI should be reinstalled. (Although these also seem to be working.)

Mike Dempsey
Teradata Client Tools

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