If you encounter difficulties or problems with Connector/ODBC,
start by making a log file from the
Manager and Connector/ODBC. This is called
tracing, and is enabled through the ODBC
Manager. The procedure for this differs for Windows, Mac OS X
To enable the trace option on Windows:
Tracing tab of the ODBC Data Source
Administrator dialog box lets you configure the way ODBC
function calls are traced.
When you activate tracing from the
Tracing tab, the
Manager logs all ODBC function calls for all
subsequently run applications.
ODBC function calls from applications running before tracing is activated are not logged. ODBC function calls are recorded in a log file you specify.
Tracing ceases only after you click
Now. Remember that while tracing is on, the log
file continues to increase in size and that tracing
affects the performance of all your ODBC applications.
To enable the trace option on Mac OS X 10.3 or later, use the
Tracing tab within ODBC
Open the ODBC Administrator.
Enable Tracing check box.
Enter the location to save the Tracing log. To append information to an existing log file, click the Choose... button.
To enable the trace option on Mac OS X 10.2 (or earlier) or
Unix, add the
trace option to the ODBC
On Unix, explicitly set the
option in the
Set the tracing
OFF by using
odbc.ini as shown
TraceFile = /tmp/odbc.trace Trace = 1
TraceFile specifies the name and full
path of the trace file and
Trace is set
can also use
OFF. If you are using
unixODBC, then follow the instructions
unixODBC calls at
To generate a Connector/ODBC log, do the following:
Within Windows, enable the
Connector/ODBC option flag in the Connector/ODBC
connect/configure screen. The log is written to file
C:\myodbc.log. If the trace option is
not remembered when you are going back to the above
screen, it means that you are not using the
myodbcd.dll driver, see
Section 22.214.171.124.3, “Troubleshooting ODBC Connection Problems”.
On Mac OS X, Unix, or if you are using a DSN-less
connection, either supply
the connection string, or set the corresponding
keyword/value pair in the DSN.
Start your application and try to get it to fail. Then check the Connector/ODBC trace file to find out what could be wrong.
If you need help determining what is wrong, see Section 126.96.36.199, “Connector/ODBC Community Support”.