Archives of the TeradataForum

Message Posted: Mon, 31 Jan 2005 @ 19:25:41 GMT

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

Thanks for your response Mike. Thanks for the dialog, however, I'm not sure we have isolated the problem or resolved the issue just yet...

We have disabled logon encryption (temporarily), so I do not think that is the problem for the long connect times? (I hope)

In our ODBC Source configurations, we have hard-coded the IP addresses to all three of our nodes. And we have checked the box that says "Do not resolve alias names to IP addresses". None of the nodes reside in our DNS.

All Teradata access is through IP addressing directly. However, some local client host files do have cop entries for those using Teradata Manager (for example), but I do not think that any of the servers using Cognos have any cop entries at all...since I think ODBC does not use those when using IP addressing directly.

So I'm afraid we are considering rolling back to the earlier version of the ODBC driver until we can isolate why the connect times are so much slower with the newer drivers. I suspect I might have to open an incident with the GSC!

Best Regards,

Michael E. McBride

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