I am not able to Login to Teradata 6.1/6.2 using BTEQ. I am able to login using Teradata 5.1 But I am able to login to Teradata 6.1/6.2 through Teradata SQL Assistant. I included the following entry in the host file in the Windows folder
Then i made a file like .logon teradata/Username,Password; Using BTEQWIN i given the command like .run file=path of the above file
I am getting the following error message *** Error 3004 User identification is not authorized. *** Error: Logon failed! *** Total elapsed time was 3 seconds. Teradata BTEQ 08.02.04.00 for WIN32. Enter your logon or BTEQ command: *** Warning: EOF on INPUT stream. Teradata BTEQ 08.02.04.00 for WIN32. Enter your logon or BTEQ command:
Can anyone help me out to login through BTEQ. Can any one clarify me why "User identification is not authorized" message appears while connecting using BTEQ where i was able to login using Teradata SQL Assistant.
Weird thing is, with the same user id and password, I'm able to logon some of the times. Sometimes I have to retry many times or wait for 15 to 20 minute before I can successfully logon again. It seems some resource was locked. Does anyone know what's wrong? Thanks.
A likely explanation: The same TDPID, but with more COPs, is defined to point to a different Teradata system (in your hosts file or nameserver/DNS). That's easy enough to check: "ping TDPIDcop2" (or one number higher than the highest "cop" you defined).
CLIv2 will enumerate and attempt to resolve the "cop" suffix names in sequence until it gets a failure, then randomly pick one from the list to use as the starting point. If "cop1" points to system A but cop2 through copN point to system B, that could explain the behavior you observe.
You can't. You have to fix your hostname-to-IP resolution (hosts file, DNS, etc.) so that TDPIDcop1, TDPIDcop2, ..., TDPIDcop(N) all point to IP addresses on the same system, and TDPIDcop(N+1) is not defined.
Note that if TDPIDcop1 is defined but not reachable or not responding within the connection timeout, the driver should attempt to connect to another "cop". You'd see a delay, but not a "3004" error.
Thanks for your advice. I think it's really because of wrong definition of the cop(s). I updated the host file such that both cop1 and cop2 points to the same cop1 IP address. After this change, I'm able to logon successfully everytime.