16.10 - Common BTEQ Error Messages and Related Directory Setup Problems - Teradata Database

Teradata Database Security Administration

prodname
Teradata Database
vrm_release
16.10
created_date
June 2017
category
Administration
Security
featnum
B035-1100-161K
Error Message Problem Solution
CLI error: External authentication failed by gateway. LDAP cannot authenticate the user with the information provided in the logon. A common cause of failure is that the LDAP logon contains a Teradata username and/or password.

Confirm that the directory username and password are entered correctly, and that the account specification, if used, is valid.

If the logon appears to be correct, you can use tdsbind to identify other possible problems. See Working with Tdsbind.

Gateway error: User, account, or password information is invalid. The user, account, or password is invalid.
DBS error: User identification is not authorized. The Teradata Database user (tdatUser object) mapped to the directory user does not exist in the database. Do either one of the following:
  • Remap the directory user.
  • Create the user in the database.
DBS error: Profile ‘xxx’ does not exist. The mapped Teradata profile (profile_name) does not exist.
  • The profile may not exist in the database or the directory.
  • The profile may be misnamed in the directory.
  • The logon user may not be mapped to the profile.
Take one of these actions depending on the details of the problem, if the:
  • Profile does not exist, create it in the database.
  • Profile directory object does not exist, create the object it in the directory.
  • Profile directory object is misnamed, rename the profile object in the directory.
  • User is not mapped to the profile, remap the user to the profile.