ODBC trace for WebSphere Message Broker or IBM Integration Bus

Technote (troubleshooting)


Problem(Abstract)

This procedure is typically run to track down problems in IBM Integration Bus (IIB) or Websphere Message Broker (WMB) with database connectivity such as user access and dropped database connections. Gathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time.

Resolving the problem


Depending on the platform you are using, use the procedure below to initiate trace for ODBC activity.

Windows

  • Use the Tracing tab of the ODBC function, as follows:
    • Click Start > Settings > Control Panel > Administrative Tools.
    • Double-click Data Sources.
    • Select the Tracing tab. The Log File Path displays the default path and file name (/sql.log) trace information is written to.
    • Click the Start Tracing Now button.
    • Click OK.
    • To stop ODBC tracing, go to the same panel and click the Stop Tracing Now button, then click OK.

UNIX
For WMB V7
  • Edit the odbc.ini (V7) file to initiate trace for ODBC activity (look for environment variable ODBCINI for V7):
    • Under the stanza entry [ODBC] change Trace=0 to Trace=1
    • Enable timestamp in the ODBC trace by setting TraceOptions=3 in the odbc.ini file
    • Optionally, modify the TraceFile file path value to a preferred value.
    • Restart the broker.
      All trace records go to one file, which can be confusing with multiple flows or execution groups.
      Disable the trace by changing Trace=0 to Trace=1 in the odbc.ini file and restart the broker
For WMB V8 and IIB V9
  • Edit the odbcinst.ini file to initiate trace for ODBC activity (look for environment variable ODBCINI and ODBSYSINI):
  • Under the stanza entry [ODBC] change Trace=no to Trace=yes
  • Enable timestamp in the ODBC trace by setting TraceOptions=3 in the odbc.ini file
  • Optionally, modify the TraceFile file path value to a preferred value.
  • Restart the broker.
    All trace records go to one file, which can be confusing with multiple flows or execution groups.
    Disable the trace by changing Trace=yes to Trace=no in the odbcinst.ini file and restart the broker
z/OS
  • Edit /component_HFS/dsnaoini (V6.1 and V7) and BIPDSNAO file (for V8.0 and V9.0) to initiate application trace for ODBC activity:
    • Under the stanza [COMMON] change APPLTRACE=0 to APPLTRACE=1
    • Optionally, modify the APPLTRACEFILENAME file path to a preferred value. All trace records go to one file, which can be confusing with multiple flows or execution groups.
Trace information is output to the file install_dir, which should help you to diagnose the problem.

After a PMR is open, submit the ODBC trace file to IBM Support for problem determination.

For a listing of all technotes, downloads, and educational materials specific to ODBC connections, refer to Knowledge Collection: Database Connectivity / ODBC / JDBC for WebSphere Message Broker or search the WebSphere Message Broker support site.

Cross reference information
Segment Product Component Platform Version Edition
Business Integration IBM Integration Bus Database AIX, HP-UX, Linux, Solaris, Windows, z/OS 9.0 All Editions

Product Alias/Synonym

WMB MB Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Message Broker
DB Connectivity / ODBC / JDBC

Software version:

7.0, 8.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows, z/OS

Reference #:

1177048

Modified date:

2014-02-12

Translate my page

Machine Translation

Content navigation