If you are experiencing installation problems and cannot
determine the cause of the problem, collect diagnostic data that either
you or IBM Software
Support can use to diagnose and resolve the problem.
To collect diagnostic data for installation problems:
- Optional: Repeat the installation attempt with
tracing enabled. For example:
On Linux and UNIX operating systems
db2setup -t /filepath/trace.out
On Windows operating systems
setup -t \filepath\trace.out
- Locate the installation log files.
- On Windows, the default
file name is "DB2-ProductAbbreviation-DateTime.log".
For example: DB2-ESE-Wed Jun 21 11_59_37 2006.log.
The default location for the installation log is the "My
Documents"\DB2LOG\ directory.
Note: If DB2® is installed using SYSTEM user,
for example using Microsoft Systems
Center Configuration Manager (SCCM) or Tivoli®, an install log is not created. The
SYSTEM user does not have a "My Documents" folder
for the install log to be created in. In order to view the install
log, use the -l option of the setup command to
create the log file in a different location.
- On Linux and UNIX, the default file names are db2setup.log, db2setup.his,
and db2setup.err.
If you recreated the problem
with tracing (or debug mode) enabled, additional files might be created,
such as: dascrt.log, dasdrop.log, dasupdt.log, db2icrt.log.PID, db2idrop.log.PID, db2iupgrade.log.PID,
and db2iupdt.log.PID, where PID is
the process ID.
The default location for
all of these files is the /tmp directory. For
the trace file (trace.out), there is no default directory if not given,
so you must specify the file path to the folder in which the trace
output file was created.
- Optional: If you intend to submit the data to IBM Software Support, collect data
for DB2 as well. See "Collecting
data for DB2" for additional
information.