Archives of the TeradataForum
Message Posted: Thu, 19 Feb 2009 @ 20:44:36 GMT
<-- Anonymously Posted: Thu, 19 Feb 2009 15:26 -->
ODBC tries to resolve the name given in the DSN. If it cannot resolve or connect then it appends cop1 to it and tries to again, and it repeats the same until the name resolution to copx fails. Since it goes in sequential order always the connect to first node will be a success. This is what happened when you configured ODBC DSN only with TDPROD01.
If a DSN is configured with multiple copnames or addresses, ODBC randomly chose one of them to connect. This is what happened when you allowed ODBC DSN setup to resolve the copnames, as it saved DSN with multiple host addresses. This is the best way to configure a DSN.
It is never the case ODBC can chose least busiest node. Even in the second case above, it is just a random selection.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|