The default DB2® diagnostic data directory path setting of the diagpath database manager configuration parameter collects all diagnostic information within a single diagnostic data directory. You can split the diagnostic data directory path so that separate directories are created and named according to the database partition server, database partition, or both. In this way, diagnostic dump files, previously stored in a single directory, are now stored in separate directories according to the database partition server or database partition from which the diagnostic data dump originated.
You will be able to split a diagnostic data directory path to separately store diagnostic information according to the database partition server or database partition from which the diagnostic data dump originated.
Restrictions
Splitting a diagnostic data directory path, to keep multiple sources of diagnostic information separated, is mostly useful in partitioned database environments.
DB2 Version 9.7 Fix Pack 1 or a later fix pack is required.
db2 get dbm cfg | grep DIAGPATH
A
successfully split diagnostic data directory path returns the values $h, $n,
or $h$n with a preceding blank space.
For example, the output returned is similar to the following:Diagnostic data directory path (DIAGPATH) = /home/usr1/db2dump/ $h$n
To merge separate db2diag log files to make analysis and troubleshooting easier, use the db2diag -merge command. For additional information, see: "db2diag - db2diag logs analysis tool command" and "Analyzing db2diag log files using db2diag tool".