392 IBM Content Manager OnDemand Guide
Table 18-5   Information to collect for DB2
Setting the CLI trace for DB2
We list two methods to turn on the CLI trace for DB2. One method is to edit the db2cli.ini 
file directly. The other method is to use the DB2 command line.
The examples show the common options for the DB2 CLI trace. The IBM Support team might 
suggest a different option to collect information that is appropriate to your situation. Modify 
these options as advised.
In both cases, the trace file that is collected (as shown in Example 18-1 on page 393 and 
Example 18-2 on page 393) is in the /tmp/db2trace.dmp file.
File Description
db2diag.log This file is the DB2 diagnosis file. It is in the $HOME/sqllib/db2dump 
directory, where $HOME is the home directory of the DB2 instance.
CLI trace (Open Database 
Connectivity (ODBC))
This file contains the call-level interface (CLI) trace file for diagnosing 
SQL statements. The CLI trace option must be turned on to collect the 
file. (See “Setting the CLI trace for DB2” on page 392.)
Text summary Collect a text summary of the application group and folder with the 
database problem by logging on to the Content Manager OnDemand 
server through the Content Manager OnDemand Administrator Client.
Content Manager
OnDemand system log
Gather the Content Manager OnDemand system log messages 
10 minutes before and after the database problem.
SQLCODE error message If the SQLCODE error message is available, collect this information to 
determine whether the problem is from Content Manager OnDemand 
or the database. 
DB2 configuration report of 
the Content Manager 
OnDemand instance
This report is generated by the db2 command: 
db2 get db cfg for instance_name
ars.ini If you cannot determine the database engine, check the path of the 
ars.ini file. In UNIX System Services, run set > /tmp/set.txt and 
send a binary copy of the ars.ini file to IBM Support.
ars.cfg Send a binary copy of the ars.cfg file to IBM Support.
cli.ini Verify the contents of the cli.ini file. Verify that MVSDEFAULTSSID=xxxx 
points to the correct DB2 Subsystem ID. Also, check whether the value 
can be set within your installation by a DSANOINI DD statement in JCL or 
as a hierarchical file system (HFS) file.
On Windows and other 
platforms
For Windows, collect the Content Manager OnDemand server 
configuration settings:
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\OnDemand
For all other platforms, collect the ars.ini, ars.cfg, ars.cache, and 
ars.dbfs files.
Application group report The application group ID is the name of the related DB2 tables.