Archives of the TeradataForum
Message Posted: Wed, 31 Jul 2002 @ 19:22:51 GMT
| Subj: | | Re: Long Logon times via CLIv2 |
| |
| From: | | Dieter N�th |
| | I have 6 machines that I logon to. Do you set it to one less than the machine with the most cop entries or the total number of cop
entries? | |
When you got 6 Teradatas, you probably don't use DBCcopxx at all. It's the logical name of a Teradata sytem used in your
bteq/fastload...
logons: .logon foo/username,password
System Name foo with 4 nodes -> set foo=4
another system named bar with 20 nodes -> set bar=20
CLI is trying to resolve the ip-addresses of all nodes of a system. This is fast for the existing nodes foocop1 to foocop4, but
then the non-existent node foocop5 is causing the trouble. Depending on your name resolving (hosts, Wins, DNS etc.) this may be very slow,
i've seen delays of > 100 seconds.
You typically don't have the same problem with odbc, because the addresses are resolved when you add a new DSN.
Dieter
| 
