 |
 |
Archives of the TeradataForum
Message Posted: Fri, 14 Nov 2008 @ 08:31:14 GMT
| Subj: | | Re: Multiload using wrong logicalhostid |
| |
| From: | | Young, Mark |
Thankyou to those who provided information. I have since discovered what was causing this issue and wanted to share this with the forum in case
anyway else encounters this problem in the future.
We originally had two networks connected to our system, one using HOSTID 40 and the other using HOSTID 50. We had the network cables from the
second network removed and cabled into the first network. What didn't occur was a reconfiguration of Teradata and so HOSTID 50 still remained. We
had applied a logonrule to HOSTID, revoking all access as soon as we no longer wanted connection to the second network. Unfortunately for us,
without the HOSTID 90 being removed any requests to the DBCCOP entries pointing at these interfaces defaulted to HOSTID 50 and not HOSTID 40 as we
thought would happen.
ODBC was not affected until we rolled out DNS changes pointing to new cop entries and had these addresses added into the ODBC config. CLI was
affected as I believe that Teradata handles the access to a particular cop entry itself and automatically rotates between the different cop
entries in sequential order. Hence when we had added the additional cop entries, Teradata still had them pointing to HOSTID 50.
Cheers,
Mark Young
| |
