(mysql.info.gz) MyODBC trace

Info Catalog

(mysql.info.gz) Remote connection

(mysql.info.gz) MyODBC Configuration

(mysql.info.gz) MyODBC Tested Applications

 
 23.1.9.7 Getting an ODBC Trace File
 ...................................
 
 If you encounter difficulties or problems with MyODBC, you should start
 by making a log file from the `ODBC Manager' (the log you get when
 requesting logs from `ODBC ADMIN') and MyODBC.
 
 To get an ODBC trace through Driver Manager, do the following:
 
    * Open ODBC Data source administrator:
 
        1. Click `Start', point to `Settings', and then click `Control
           Panel'.
 
        2. On computers running Microsoft Windows 2000, XP, or 2003,
           double-click `Administrative Tools', and then double-click
           `Data Sources (ODBC)', as shown below.
 
           [image src="Images/mydsn-icon.png" text=""]
           On computers running an earlier version of Microsoft Windows,
           double-click `32-bit ODBC' or `ODBC' in the Control Panel.
 
        3. The `ODBC Data Source Administrator' dialog box appears, as
           shown below:
 
           [image src="Images/mydsn.png" text=""]
        4. Click Help for detailed information about each tab of the
           ODBC Data Source Administrator dialog box.
 
 
    * Enable the trace option.  The procedure for this differs for
      Windows and Unix.
 
      To enable the trace option on Windows:
 
        1. The `Tracing' tab of the ODBC Data Source Administrator
           dialog box enables you to configure the way ODBC function
           calls are traced.
 
        2. When you activate tracing from the `Tracing' tab, the `Driver
           Manager' will log all ODBC function calls for all
           subsequently run applications.
 
        3. ODBC function calls from applications running before tracing
           is activated are not logged. ODBC function calls are recorded
           in a log file you specify.
 
        4. Tracing ceases only after you click `Stop Tracing 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.
 
           [image src="Images/mydsn-trace.png" text=""]
 
      To enable the trace option on Unix:
 
        1. On Unix, you need to explicitly set the `Trace' option in the
           `ODBC.INI' file.
 
           Set the tracing `ON' or `OFF' by using `TraceFile' and
           `Trace' parameters in `odbc.ini' as shown below:
 
                TraceFile  = /tmp/odbc.trace
                Trace      = 1
 
           `TraceFile' specifies the name and full path of the trace file
           and `Trace' is set to `ON' or `OFF'. You can also use `1' or
           `YES' for `ON' and `0' or `NO' for `OFF'.  If you are using
           `ODBCConfig' from `unixODBC', then follow the instructions
           for tracing `unixODBC' calls at HOWTO-ODBCConfig
           (http://www.unixodbc.org/config.html).
 
 
      To generate a MyODBC log, do the following:
 
        1. Ensure that you are using the driver debug DLL (that is,
           `myodbc3d.dll' and not `myodbc3.dll' for MyODBC 3.51, and
           `myodbcd.dll' for MyODBC 2.50).
 
           The easiest way to do this is to get `myodbc3d.dll' (or
           `myodbcd.dll') from the MyODBC 3.51 distribution and copy it
           over the `myodbc3.dll' (or `myodbc.dll'), which is probably
           in your `C:\windows\system32' or `C:\winnt\system32'
           directory. Note that you probably want to restore the old
           `myodbc.dll' file when you have finished testing, as this is
           a lot faster than `myodbc3d.dll' (or `myodbcd.dll'), so do
           keep a backup copy of original DLLs.
 
        2. Enable the `Trace MyODBC' option flag in the MyODBC
           connect/configure screen. The log will be 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 above). On Linux or
           if you are using DSN-Less connection, then you need to supply
           `OPTION=4' in the connection string.
 
        3. Start your application and try to get it to fail.  Then check
           the MyODBC trace file to find out what could be wrong.
 
           If you find out something is wrong, please send a mail
           message to <myodbc@lists.mysql.com> (or to <support@mysql.com>
           if you have a support contract from MySQL AB) with a brief
           description of the problem, with the following additional
           information:
 
              * MyODBC version
 
              * ODBC Driver Manager type and version
 
              * MySQL server version
 
              * ODBC trace from Driver Manager
 
              * MyODBC log file from MyODBC driver
 
              * Simple reproducible sample
 
 
      Remember that the more information you can supply to us, the more
      likely it is that we can fix the problem!
 
      Also, before posting the bug, check the MyODBC mailing list
      archive at `http://lists.mysql.com/'.
 
 

Info Catalog

(mysql.info.gz) Remote connection

(mysql.info.gz) MyODBC Configuration

(mysql.info.gz) MyODBC Tested Applications