Pivotal Knowledge Base

Follow

DataDirect ODBC Driver 7.1 Misses query Failures

Environment

  • DataDirect 7.1 Greenplum Wire Protocol ODBC driver
  • Pivotal Greenplum Database (GPDB) 4.3.x

Symptom

In some cases, a Greenplum query fails, but the loading software does not catch this error and raise that the loading flow succeeds.

Error Message

Example of errors in Greenplum that were not caught by the loading software:

ERROR: 22011: negative substring length not allowed
There was an error in the SELECT query because of the input data.
The transformation substr (b.des_opzione,1,length(b.des_opzione)-3)
failed because the field b.des_opzione was Null and thus,
length(b.des_opzione)-3 was < 0.
ERROR: 53000: workfile per query size limit exceeded
A GPDB query failed because of the size of spill files. 

Cause 

The driver was misinterpreting the error message header and mistakenly specifying this particular message as a warning.

Resolution

This is a bug in the Datadirect ODBC driver and its fixed with hotfix versions 07.15.0187 and 07.01.0094

Please see the following article CONNECT FOR ODBC GREENPLUM DRIVER REPORTS A CERTAIN ERROR AS A WARNING

Comments

Powered by Zendesk