Archives of the TeradataForum
Message Posted: Wed, 05 Sep 2012 @ 21:59:46 GMT
There seem to be a couple of errors that you are hitting and I think I can help with some of them.
1) CLI 224 TPT_INFRA: TPT05004: CLI error 224 in connecting session (function ConnectSession). MTDP: EM_NOHOST(224): name not in HOSTS file or names database.
This error happens because your hosts file or dns table does not have the required entry.
Your logon statement in BTEQ should look something like: .logon teradata-machine-name/userid,password;
The ' teradata-machine-name' value is either an ip address or the prefix to the hosts file/dns entry. Assume that I have coded the logon string as:
Then my hosts file/dns entry needs to be mytdsyscop1 184.108.40.206 (or whatever the ip address is). The CLI software adds 'cop1' to the name that you provide to try and find the first ip-address to connect to.
2) ODBC "not enough information" 1: In odbcDriverConnect("DSN=teradataDSN") : [RODBC] ERROR: state 28000, code 0, message [Teradata][ODBC Teradata Driver] Not enough information to log on
Either in your odbc dsn definition or in your connection string you need to provide the hosts file entry/dns entry/ipaddress and the username and the password. I'm guessing that one or more of these is missing.
Try following the above and see what happens.
Ward Analytics Ltd - Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|