Dump files are created when an error occurs for which there is additional information that would be useful in diagnosing a problem (such as internal control blocks). Every data item written to the dump files has a timestamp associated with it to help with problem determination. Dump files are in binary format and are intended for DB2 Customer Service representatives. They should be collected and sent along with the db2diag.log file.
When a dump file is created or appended to, an entry is made in the
db2diag.log file indicating the time and the type of data
written. These db2diag.log file entries resemble the
following:
1997-03-16-11.53.18.001160 Instance:payroll Node:000 PID:44829(db2agent (SAMPLE)) Appid:*LOCAL.payroll.970317140834 relation_data_serv sqlrerlg Probe:17 Database:SAMPLE DIA9999E An internal return code occurred. Report the following : "0xFFFFE101". Dump File: /home/db2/sqllib/db2dump/56772.000 Data : SECTION STMT (1) |
Legend:
Notes:
Dump File: /home/db2/sqllib/db2dump/56772.010 Data : SECTION STMT
DB2 core files are located in the path $HOME/db2dump/core_directory, where core_directory is the core path directory name. There is one directory for each process. Directory names start with the letter "c", followed by the process identifier (pid) number of the affected process. A name extension provides the node number (for multinode systems with a db2nodes.cfg file).
For example: