IBM Support

ODBC trace for App Connect Enterprise or IBM Integration Bus

Troubleshooting


Problem

IBM App Connect Enterprise (ACE) and its predecessor, IBM Integration Bus (IIB), supports Open DataBase Connectivity (ODBC).
Use this process to capture a trace of ODBC for the purpose of providing to IBM Support for analysis.

Resolving The Problem

  1. Locate the file 'odbcinst.ini' contained in the ODBCSYSINI directory path.
  2. Under the stanza '[ODBC]', change 'Trace=no' to 'Trace=yes'.
  3. [Optional] Enable timestamps in the trace by setting 'TraceOptions=3'.
  4. [Optional] Modify the 'TraceFile' file path value to a preferred value.
  5. Restart the Int. Server to pick up the change.

To stop ODBC tracing, change 'Trace=no' and restart the Int. Server.

Example odbcinst.ini file

[ODBC]
;# To turn on trace set Trace=yes
Trace=no
TraceFile={A Directory with plenty of free space to hold trace output}/odbctrace.out
;# Threading is not a configurable property
Threading=2
  1. Locate 'ODBC Data Source Administartor(64-bit)' or 'ODBC Data Sources(64-bit)'.
    This can be found by searching on the Start menu, or through "Control Panel"\"System and Security"\"Administrative Tools"
  2. Select the 'Tracing' tab.
  3. [Optional] Modify the Log File Path to a custom path and file name.
  4. Click the 'Start Tracing Now' button.
  5. Click 'OK'.

To stop ODBC tracing, go to the same panel and click the 'Stop Tracing Now' button and then click 'OK'.

  1. Edit the BIPDSNAO file in the component dataset and under the stanza entry [COMMON], change APPLTRACE=0 to APPLTRACE=1.
  2. Remove the comment from the COMPDIR variable declaration and the APPLTRC DD from the steps EGNOENV and EGENV, in the started task JCL.
  3. Stop and restart the Int. Node after you have made all the changes to the BIPDSNAO file and the started task JCL.
  4. Click the 'Start Tracing Now' button.
  5. Click 'OK'.

To stop ODBC tracing, change APPLTRACE=0 and restart the Int.Node.

Notes:

By default, the trace output file is written to {component_HFS}/output/, into a file labelled 'db2appltrace'.
The 'db2appltrace' filename will also include the eight character Int. Server label as well as a unique number representing the address space.
This unique number is the SE number in the Int. Server address space and can be found in the JOBLOG.
If the Int. Server label is not unique, look for the value of SE in the JOBLOG and then locate the corresponding ODBC trace file.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"ODBC;Trace","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"ODBC;Trace","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"All Versions","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 October 2023

UID

swg21177048

Page Feedback