Knowledge base

Enabling connection tracing to help diagnose network issues

Purpose

This article explains how to enable connection tracing to help diagnose network related issues.

Explanation

IBM includes two different trace utilities that may be useful when trying to track down connection related issues in XCB. Both programs are located in the main Client Access folder (normally %ProgramFiles%\IBM\Client Access).

Database driver trace utility

The CWBMPTRC command starts or stops .NET Database Driver tracing. When you enable tracing, the system logs all database requests as well as their results.

Enabling/disabling Tracing

Make sure you DISABLE tracing after you are done with it - the trace files can easily be gigabytes in size otherwise. There are 3 different traces that you can run (together or individually):

  • l - does error tracing
  • t - does command tracing
  • a - does diagnostic tracing

To enable a trace, enter a '+' before the trace name, and to disable enter a '-' in front of the trace name.

Example:

cwbmptrc +l +t will enable both error and command tracing

cwbmptrc -l -t will disable tracing for both errors and commands.

Trace files

By default, the error trace is stored in: C:\Documents and Settings\All Users\Documents\IBM\Client Access\iDB2Log.txt

By default, the command trace is stored in: C:\Documents and Settings\All Users\Documents\IBM\Client Access\iDB2Trace.txt

Additional information

Connection tracing takes substantial disk space and severely affects the processing speed of the system.  Make sure to disable it once diagnostics have been completed.

Difficulty

  • Advanced - Pour yourself a stiff drink.

Categories

Applies to

General information

  • Last updated: 4/3/2015

Any feedback is appreciated