SYMPTOM

Failed to execute freeform SQL if the query contains “{ts” and “}” characters.
For example, executing the following SQL in DB Query Tool:
select {ts'2020-05-05 05:46:21'}

CAUSE

NoScan='Yes' in registry or “Disable Parsing” checked in ODBC Data Source Administrator means the driver skips parsing the query string, queries are sent directly to the database, and “{ts” and “}” are not stripped first.
However, the “{ts” and “}” is not valid SQL token in the Teradata database.

ACTION

Uncheck “Disable Parsing” in ODBC Data Source Administrator or set NoScan='0' in the registry will solve the problem.

Uncheck “Disable Parsing” in ODBC Data Source Administrator

Use Teradata Database ODBC Driver 17.10 DSN as an example.
Go to ODBC Data Source Administrator (64-bit) -> System DSN -> <your DSN name> -> Configure -> Options

Set NoScan='0' in Registry

Go to Registry Editor -> Computer\HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI\<your DSN name> -> Set NoScan='0'

Note

The "NoScan" value set in Registry takes precedence over the “Disable Parsing” value set in ODBC Data Source Administrator.