Isolate the component in which the issue is occurring. Is it an ODBC application, an ODBC driver, an ODBC Driver Manager, or a data source issue?
To troubleshoot the issue:
1. Test to see if your ODBC application is the source of the problem. To do this, replace your working ODBC application with a more simple application. If you can reproduce the issue, you know your ODBC application is not the cause.
On UNIX and Linux, you can use the example application that is shipped with your driver. See "The example Application" for details.
On Windows, you can use ODBC Test, which is part of the Microsoft ODBC SDK, or the example application that is shipped with your driver. See "ODBC Test" and "The example Application" for details.
On macOS, you can use iODBC Demo or iODBC Test, which are installed with the iODBC Administrator, or the example application that is shipped with your driver. See "iODBC Demo and iODBC Test" and "The example Application" for details.
2. Test to see if the data source is the source of the problem. To do this, use the native database tools that are provided by your database vendor.
3. If neither the ODBC application nor the data source is the source of your problem, troubleshoot the ODBC driver and the ODBC Driver Manager.
In this case, we recommend that you create an ODBC trace log to provide to Technical Support. See "ODBC Trace" for details.
On UNIX and Linux, you can use the example application that is shipped with your driver. See "The example Application" for details.
On Windows, you can use ODBC Test, which is part of the Microsoft ODBC SDK, or the example application that is shipped with your driver. See "ODBC Test" and "The example Application" for details.
On macOS, you can use iODBC Demo or iODBC Test, which are installed with the iODBC Administrator, or the example application that is shipped with your driver. See "iODBC Demo and iODBC Test" and "The example Application" for details.