 |
 |
Archives of the TeradataForum
Message Posted: Sat, 08 Nov 2008 @ 06:46:14 GMT
| Subj: | | Multiload using wrong logicalhostid |
| |
| From: | | Mark Young |
Hi all,
I am hoping that someone can help me out with an issue we have experienced. We have had a logicalhostid (50) define on our Teradata system
that has had all access revoked against it for over two months and yet we have one client who all of a sudden in the last week has multiload jobs
that are trying to logon to this hostid and getting rejected. The client can logon using SQL Assistant and connects to the correct hostid (40) and
looking at the log file from the multiload job, it looks like the control sessions logon to hostid 40, but when the time comes to connect the
multiple load sessions, they try to connect to hostid 50 and get rejected due to user is revoked error.
Can anyone provide some insight into this. I know that SQL Assistant uses ODBC and multiload uses CLI. If I ping dbccop1, we get the IP address
associated with the LAN connection that only has logicalhostid 40 associated with it. Even if we add the IP address into the hosts file, it still
does not help.
Cheers,
Mark Young
| |
