SYMPTOM:
"Unable to get catalog string" error message appears when running reports against Teradata version 14 on a UNIX/Linux Intelligence Server in Strategy.
Error Message
QueryEngine encountered error: FetchScroll. Error type: Odbc success with info. Odbc operation attempted: SQLFetchScroll. Unable to get catalog string.
CAUSE:The " Unable to get catalog string" error indicates that the Teradata ODBC driver on the Intelligence Server is attempting to post an error or ODBC result code but is unable to find the error message catalog file. For this reason, it is not easy to identify the actual error or message returned by the database.
ACTION:The NLSPATH variable is used by the Teradata driver to locate the catalog of messages and match the codes recevied to their description messages. Locate the file "tdodbc.cat" file in the Teradata driver installation on the UNIX/Linux server and set the environment variable NLSPATH to that location. For example, if the "tdodbc.cat" file is located in "/opt/teradata/client/lib/odbc/tdodbc.cat", use the command shown below to set the proper value.
setNLSPATH=/opt/teradata/client/lib/odbc/%N.cat
Once this is setup, the driver should return the correct error code messages and with that information, further troubleshooting can be done according to the message received.
WORKAROUND:It is possible to research the ODBC error code (provided in the error message) online. In the case of the example below, ODBC code 08S01 corresponds to a "Communication link error" indicating that the server got disconnected from the database.
Error Message
Unable to get catalog string.
WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability
