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.