Troubleshooting Guide

First Failure Data Capture

First Failure Data Capture (FFDC) information is diagnostic information captured automatically by DB2 about an error when the error occurs. This information reduces the need to reproduce errors to get diagnostic information.

The information captured by FFDC includes the following:

db2diag.log

When an error occurs, the db2diag.log is updated with information about the error. For more details, see Interpreting the db2diag.log. For information on the DIAGLEVEL setting, which determines how much information is logged in the file, see Setting Configuration Parameters Affecting FFDC.

db2alert.log

If an error is determined to be an alert, then an entry is made in the db2alert.log file and to the operating system or native logging facility. See Alerts for more information.

Dump files

For some error conditions, extra information is logged in external binary dump files named after the failing process ID. These files are intended for DB2 Customer Support. See Dump Files, for more details.

Trap files

The database manager generates a trap file if it cannot continue processing because of a trap, segmentation violation, or exception. Trap files contain a function flow of the last steps that were executed before a problem occurred. See Trap Files, for more information.

This diagnostic information is contained in a single location (the DIAGPATH specified in the database manager configuration). It contains internal traces and dumps, which contain crucial information that may help you diagnose and fix problems.

Setting Configuration Parameters Affecting FFDC

The following database manager configuration parameters affect how much FFDC information is collected and where it is kept:

• DIAGLEVEL specifies the level of diagnostic information you will receive. The following data is captured for each DIAGLEVEL value:
  • DIAGLEVEL (0) - No diagnostic data (this level is not recommended)
  • DIAGLEVEL (1) - Severe errors only
  • DIAGLEVEL (2) - All errors (severe and not severe)
  • DIAGLEVEL (3) - All errors and warnings (the default value)
  • DIAGLEVEL (4) - All errors, warnings, informational messages, and other internal diagnostic information

  The default for DIAGLEVEL is 3. Change it to 4 during initial setup and during those times when you are experiencing problems.

• NOTIFYLEVEL specifies the type of errors that are written. The following valid values for this parameter are:
  • NOTIFYLEVEL (0) - No diagnostic data (this level is not recommended)
  • NOTIFYLEVEL (1) - Severe errors only
  • NOTIFYLEVEL (2) - All errors (severe and not severe) (the default value)
  • NOTIFYLEVEL (3) - All errors and warnings
  • NOTIFYLEVEL (4) - All errors, warnings, informational messages, and other internal diagnostic information

  The default for NOTIFYLEVEL is 2.

  For a satellite server, errors are written to a notification file called instance.nfy where the instance is the DB2 instance name. For all other database server types, the NOTIFYLEVEL parameter is only available on the Windows NT platform where the errors are written to the Windows NT event log.

  The error information can be written by DB2, the Capture and Apply programs associated with replication, and user applications. For a user application to write to the notification file or the Windows NT event log, it must use the db2AdminMsgWrite API. For more information about this API, see the Administrative API Reference.

• DIAGPATH specifies the fully qualified path where DB2 writes its diagnostic information. This directory contains dump, error log, the notify (.nfy) file when working with a satellite configuration, and alert log files, and is created automatically.

  Note:

  On Windows NT, other DB2 diagnostic information is found in the event log which can be reviewed through the Windows NT Event Viewer.

  The default for DIAGPATH is a null string. It is recommended that you use this default value or use a centralized location, especially if there are multiple database instances. By default, the FFDC information is placed in the following locations:

  • For Windows and OS/2:
    • If the DB2INSTPROF environment variable is not set: db2path\db2instance (where db2path is the path referenced in the DB2PATH environment variable, and db2instance is the environment variable containing the ID of the instance owner)
    • If the DB2INSTPROF environment variable is set: x:\db2instprof\db2instance (where x is the drive referenced in the DB2PATH environment variable, db2instprof is the instance profile directory, and db2instance is the environment variable containing the ID of the instance owner)
  • For UNIX-based environments: $HOME/sqllib/db2dump, where $HOME is the home directory of the instance owner.

  Note:

  You should clean out the DIAGPATH directory periodically.

To set these configuration parameters, use the UPDATE DATABASE MANAGER CONFIGURATION command from the command line processor.

Important: You must stop DB2 and start it again before any of these configuration changes take effect.

Examples

• To obtain the most diagnostic information, type:

  db2 "UPDATE DATABASE MANAGER CONFIGURATION USING DIAGLEVEL 4"
  

• To set the diagnostic path to a new directory called x:\tmp\errors, type:

  db2 "UPDATE DATABASE MANAGER CONFIGURATION USING DIAGPATH x:\tmp\errors"
  

• To reset the diagnostic path to the default, type:

  db2 "UPDATE DATABASE MANAGER CONFIGURATION USING DIAGPATH NULL"
  

For information on database manager administration commands, refer to the Administration Guide: Implementation, the Command Reference, and the Administrative API Reference manuals.