Authentication errors

EM_SSOLOGONFAIL(244)

This error indicates that the LDAP logon failed. Common causes and resolutions:

1. Incorrect LOGDATA format. LOGDATA parameters must be space-separated, not comma-separated. Correct: authcid=user password=pass. Incorrect: authcid=user,password=pass.

2. LDAP server unreachable. Verify that the Teradata Gateway can reach the LDAP server. This is a server-side configuration issue; contact your DBA.

3. User not mapped. The LDAP user must be mapped to a Teradata database user. Verify the mapping exists on the Teradata server.

   Be sure to:

   • Replace your_username with your LDAP username

   SELECT * FROM DBC.LogonRulesV WHERE UserName = 'your_username';

4. Wrong credentials. Verify the LDAP username and password are correct by testing with BTEQ directly.

   Be sure to:

   • Replace your_hostname, your_username, and your_password with your actual values

   bteq <<EOF .LOGMECH LDAP .LOGON your_hostname/your_username,your_password .LOGOFF .QUIT 0 EOF

5. LDAP mechanism not installed. Ensure the LDAP mechanism module is installed and configured on the Teradata Gateway. Contact your DBA to verify the tdgss configuration includes LDAP support.

BADLOGON(303)

This error indicates an invalid .LOGON command format. Verify that:

• The hostname is correct and reachable

• The username does not contain special characters that need escaping

• The JDBC URL is properly formatted with commas separating parameters

Error 8017: UserId, Password or Account is invalid

This error indicates that the username or password is incorrect, or the account does not exist on the Teradata server.

1. Verify the username and password are correct by logging in with BTEQ directly.

   Be sure to:

   • Replace your_hostname with your Teradata server hostname

   • Replace your_username and your_password with your credentials

   echo ".LOGON your_hostname/your_username,your_password" | bteq

2. Confirm the user account exists and is not locked on the Teradata server.

3. Check that the hostname in the JDBC URL resolves to the correct Teradata server.

4. If a non-default port is in use, include it in the URL.

   Be sure to:

   • Replace your_hostname and your_database with your actual values

   liquibase.command.url=jdbc:teradata://your_hostname:1025/DATABASE=your_database

5. Ensure there are no extra spaces or special characters in the password.

BTEQ authentication failure

Error:

*** Logon Failed ***

*** Error: Invalid username or password

Cause: The credentials in your Liquibase connection configuration are incorrect or cannot be used to authenticate through BTEQ.

Solution:

1. Verify your credentials work with BTEQ directly.

Be sure to:

• Replace your_hostname with your actual Teradata server hostname

• Replace your_username and your_password with your credentials

bteq .LOGON your_hostname/your_username,your_password

2. Check your liquibase.properties.

Be sure to:

• Replace your_hostname, your_database, and your_username with your actual values

url=jdbc:teradata://your_hostname/DATABASE=your_database username=your_username password=your_password

3. For LDAP authentication, include LOGMECH=LDAP in the JDBC URL:

url=jdbc:teradata://your_hostname/DATABASE=your_database,LOGMECH=LDAP

BTEQ executor errors

BTEQ execution timed out

Error:

ERROR: BTEQ execution timed out after 300 seconds

Cause: The operation took longer than the configured timeout.

Solution:

Increase the timeout for long-running operations:

liquibase.bteq.timeout=600

Or disable the timeout entirely:

liquibase.bteq.timeout=-1

Permission errors

Error:

*** Error: User does not have CREATE TABLE privilege

Cause: The database user lacks the required permissions for the operations in your changesets.

Solution: Grant the necessary privileges to your database user:

• CREATE TABLE / DROP TABLE for DDL operations

• INSERT / UPDATE / DELETE for DML operations

• EXECUTE for macros and procedures

• SELECT for queries