 |
 |
Archives of the TeradataForum
Message Posted: Fri, 05 Mar 2004 @ 16:57:46 GMT
Subj: | | Connection Pooling with a Node Down |
|
From: | | Claybourne Barrineau |
All,
Today, we have a node down on production. Some of our windows based applications are still attempting to log users on to the "down" node
(which is resulting in a failed log-in due to a time-out error.) In order to avoid this, we are having to go to each of the windows servers and
re-configuring the ODBC driver to avoid using the "down" node. This is an ugly, retroactive solution to the problem. Can anyone think of a more
elegant, proactive solution?
Thanks,
Clay
| |