SYMPTOM:
When executing a report in either Strategy Developer 10.x against a warehouse residing on a Teradata V2R6.x database, the following error occurs:
QueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Character string truncated Parcel kind or ordering is invalid.
The DSSError logs report the following:
2007-08-30 15:02:08.953-05:00 Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Character string truncated Parcel kind or ordering is invalid. Connection String: DSN=xxxx;UID=xxxx;AUTHENTICATION=;. SQL Statement:
.
2007-08-30 15:02:08.968-05:00 QueryEngine encountered error: Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Character string truncated Parcel kind or ordering is invalid.
When the report SQL is checked it appears as normal, sometimes an empty SQL pass is seen, and running the SQL in ODBC Test Tool results in correct results.
CAUSE:
This error is caused by a user defined SQL statement containing an empty line.
In this example, the report had an empty Post SQL statement:
Blank entry in 'Report Post Statement 1'
ACTION:
Check all VLDB properties for SQL statements which could contain a blank line. This can occur at the following three levels:
