Check for ODBC Errors

Check the ODBC errors returned by the SQLError function in all applications to determine whether one of them has encountered a problem that caused it to hang. Call SQLError after each ODBC call to identify error or warning conditions when they first happen. Examples of SQLError usage can be found in the demo programs and in Retrieving Errors and Warnings in the Oracle TimesTen In-Memory Database Error Messages and SNMP Traps.

If the problem is repeatable, use ttTraceMon to generate a SQL trace to determine where the application is hanging. See SQL Tracing for details. In more extreme cases, it may be helpful to generate a level 4 ERR trace for the application and review all of the errors messages that are pushed in the TimesTen direct driver. See ERR Tracing for details.