No, this is not a bug in the Teradata JDBC Driver.
If an application calls the executeBatch method without having called the addBatch method, then the Teradata JDBC Driver will throw the exception you listed. An application should only call the executeBatch method if the application actually added one or more rows to the batch by calling the addBatch method.
You mentioned "odi". Are you referring to Oracle Data Integrator? If you are experiencing this problem with Oracle Data Integrator, then you should report the problem to Oracle.
Thanks for the info, we were able to get to the bottom of this. Teradata does in fact implement this different than other JDBC providers (oracle). Oracle throws no error at all, anyway the root bug was with groovy's withBatch implementation.
See discussion here: