Diagnostic tools

When you encounter a problem, you can use the following:

All diagnostic data including dump files, trap files, error logs, notification files, and alert logs are found in the path specified by the diagnostic data directory path (diagpath) database manager configuration parameter: If the value for this configuration parameter is null, the diagnostic data is written to one of the following directories or folders:
- For Linux^® and UNIX^® environments: INSTHOME/sqllib/db2dump, where INSTHOME is the home directory of the instance.
- For supported Windows^® environments:
  - If the DB2INSTPROF environment variable is not set then x:\SQLLIB\DB2INSTANCE is used where x:\SQLLIB is the drive reference and the directory specified in the DB2PATH registry variable, and the value of DB2INSTANCE has the name of the instance.
    Note: The directory does not have to be named SQLLIB.
  - If the DB2INSTPROF environment variable is set then x:\DB2INSTPROF\DB2INSTANCE is used where DB2INSTPROF is the name of the instance profile directory and DB2INSTANCE is the name of the instance (by default, the value of DB2INSTDEF on Windows 32-bit operating systems).
For Windows operating systems, you can use the Event Viewer to view the administration notification log.
The available diagnostic tools that can be used include db2trc, db2pd and db2support.
For Linux and UNIX operating systems, the ps command, which returns process status information about active processes to standard output.
For UNIX operating systems, the core file that is created in the current directory when severe errors occur. It contains a memory image of the terminated process, and can be used to determine what function caused the error.

Parent topic: Troubleshooting

Related concepts
Obtaining a DB2 trace using db2trc