Starting with Version 9.7 Fix Pack 1, you can specify to
store DB2® diagnostic data in
separate directories named according to the physical host, database
partition, or both by setting the enhanced diagpath database
manager configuration parameter. Separate db2diag log
files can later be merged together using the db2diag -merge command.
The benefits of splitting the diagnostic data into separate
directories are as follows:
- Diagnostic logging performance can be improved because of less
contentions on the db2diag log file if you split
the diagnostic data per host or per database partition.
- Storage management can be under more granular control.
To split the diagnostic data into separate directories,
set the
diagpath database manager configuration
parameter to one of the following values:
- Split default diagnostic data directory path according to physical
host:
db2 update dbm cfg using diagpath '"$h"'
- Split your own specified diagnostic data directory path according
to physical host:
db2 update dbm cfg using diagpath '"pathname $h"'
- Split default diagnostic data directory path according to database
partition:
db2 update dbm cfg using diagpath '"$n"'
- Split your own specified diagnostic data directory path according
to database partition:
db2 update dbm cfg using diagpath '"pathname $n"'
- Split default diagnostic data directory path according to physical
host and database partition:
db2 update dbm cfg using diagpath '"$h$n"'
- Split your own specified diagnostic data directory path according
to physical host and database partition:
db2 update dbm cfg using diagpath '"pathname $h$n"'
Merging separate db2diag log files
can, at times, make analysis and troubleshooting easier. In that case,
you can use the db2diag -merge command.
DB2 Version 9.7 for Linux, UNIX, and Windows