SAS Connectivity to teradata not working after updating teradata client to 16.10

[SangaviS]

Our users are getting the following CLI error while trying to connect to any Teradata database after the Teradata client got updated to 16.10 over the weekend. Could someone please help me resolve  this ?

ERROR: CLI error trying to establish connection: 523 586

[JBailey]

Hi @SangaviS 

Installing a new TTU (Teradata Tools and Utilities) means the Teradata environment variables will need to be updated. I have no way of knowing your current SAS configuration, but you may need to update !SASROOT/bin/sasenv_local or your personal environment variables. This doc may be of assistance.

This document can help you with configuring SAS on UNIX/Linux.

http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf

Best wishes,
Jeff

[AnandVyas]

Hi @SangaviS,

Is the connection working outside of SAS? Did you try connecting via BTEQ? Since you haven't mentioned the SAS Version, Hope you have checked the compatibility depending on your SAS Version.


DBMS Products Required:
• Teradata Database version 13.10 or later
• Teradata CLIv2 client libraries, TTU 13.10 or later for Linux (64-bit libraries)
For SAS 9.4M3
DBMS Products Required:
• Teradata Database version 14.10 or later
• Teradata CLIv2 client libraries, TTU 14.10 or later (64-bit libraries)
For SAS 9.4M4 and Later
DBMS Products Required:
• Teradata Database version 15.10 or later
• Teradata CLIv2 client libraries, TTU 15.10 or later (64-bit libraries)

Thanks!

[SangaviS · Accepted solution]

Thanks everyone for your valuable responses!

Apparently the issue was because the Teradata Client 16.10 upgrade modified the following symbolic links under /usr/lib64

Below is the summary that I documented for this

Issue: The below CLI error occurs while connecting to a database

ERROR: CLI error trying to establish connection: 523 586

ERROR: CLI error trying to establish connection: 523 80

Root Cause:

                             The Teradata client 16.10 upgrade modified the symbolic links under /usr/lib64 that were essential for any odbc connections

 Resolution Steps:

• Added DriverUnicodeType=1 to the corresponding DSN entry in odbc.ini file (523 586)

• Reverted the symbolic link change that was made by the upgrade (523 80)

Before:

/usr/lib64/libodbcinst.so -> /p01/app/ncr/teradata/client/16.10/lib64/libodbcinst.so

/usr/lib64/libodbc.so -> /p01/app/ncr/teradata/client/16.10/lib64/libodbc.so

After:

/usr/lib64/libodbcinst.so -> libodbcinst.so.2.0.0

/usr/lib64/libodbc.so -> libodbc.so.2.0.0

Preventive measure:

Set the parameter ShareLibs=no in ttu_install.cfg file for the affected servers so that the symbolic links defined in the path /usr/lib64 are not modified.