HI
We need some help (ACE 11.0.0.3): How do I interpret an OBDC HY004?
This error is generating a lot of noise, even though the data is successfully written to the Oracle DB. We have checked the check the esql code and we don't believe that there is a datatype mismatch.
...
Child SQL exception' ['HY004', 0, '[IBM][ODBC Oracle Wire Protocol driver]Invalid SQL data type.']
...
2020-04-22 15:42:16.882156 11464 (00082) ImbOdbcConnectionInfo::checkGetTypeInfoFailure (00002CC8-5EA0C848-00000002) , 'Assuming SQL type is not supported by this database. Processing will continue.', 'SQL_BLOB'
2020-04-22 15:42:16.882164 11464 (00082)} ImbOdbcConnectionInfo::checkGetTypeInfoFailure (00002CC8-5EA0C848-00000002)
2020-04-22 15:42:16.882182 11464 (00082){ ImbOdbcConnectionInfo::checkGetTypeInfoFailure (00002CC8-5EA0C848-00000002) , -1, 'SQL_TIMESTAMP'
2020-04-22 15:42:16.882208 11464 (00083) ImbOdbcStatement::checkRcInner (00002CC8-5EA0C848-00000002) , 'SQL_ERROR HSTMT: SQLSTATE', 'HY004'
2020-04-22 15:42:16.882214 11464 (00083) ImbOdbcStatement::checkRcInner (00002CC8-5EA0C848-00000002) , 'SQL_ERROR HSTMT: NATIVE ERROR', 0
2020-04-22 15:42:16.882220 11464 (00083) ImbOdbcStatement::checkRcInner (00002CC8-5EA0C848-00000002) , 'SQL_ERROR HSTMT: MSG', '[IBM][ODBC Oracle Wire Protocol driver]Invalid SQL data type.'
...
2020-04-22 15:42:16.882286 11464 (00085) ImbExceptionLog::FileDestination::writeException (00002CC8-5EA0C848-00000002) , 'Exception log entry: ', '2020-04-22 22:42:16.882275 11464 THROWN BIP2322E DatabaseException ImbOdbcStatement::checkRcInner 'Child SQL exception' ['HY004', 0, '[IBM][ODBC Oracle Wire Protocol driver]Invalid SQL data type.'] DataFlowEngine/MessageServices/ImbOdbc.cpp:4038
'
The best xref I can find for HY004 is "
Invalid SQL data type"
- SQLBindParameter
The value specified for the argument ParameterType was neither a valid ODBC SQL data type identifier nor a driver-specific SQL data type identifier supported by the driver.
- SQLGetTypeInfo
The value specified for the argument DataType was neither a valid ODBC SQL data type identifier nor a driver-specific data type identifier supported by the driver.
Thanks
------------------------------
Hirschel Wasserman
------------------------------