IBM Support

[Db2] output path of db2diag.log and administration notification log file

Question & Answer


Question

This document describes where you can find Db2 diagnostic log file (db2diag.log) and administration notification log file for each platform / version of Db2.

Answer

DIAGPATH database manager configuration parameter specifies the diagnostic data directory path for Db2 diagnostic information. Please see "a. Default diagnostics data directory path" to find default path.
Note: The administration notification log will always be reported in the Windows event log as Application log in a Windows environment. 

a. Default diagnostic data directory path
  • UNIX/Linux environment
    1. V9.7 or earlier versions
          $INSTHOME/sqllib/db2dump
      $INSTHOME is the home directory of the instance owner.
      For example, if $INSTHOME is /home/db2inst1, the default diagnostic data directory path will be /home/db2inst1/sqllib/db2dump.
    2. V10.1 or later versions with non-ESE instance or non-pureScale instances
      Same as V9.7
    3. V10.1 or later versions with ESE instance or pureScale (DSF) instances
      Note: ESE instance is created by default in V10.5 or later even if you use Workgroup Server Editions.
          $INSTHOME/sqllib/db2dump/DIAGnnnn
      $INSTHOME is the home directory of the instance owner, and nnnn is the 4-digit node/member number. If you are running ESE instance with a single node, it will always be DIAG0000.
      For example, if $INSTHOME is /home/db2inst1 and the member number is 1 (the second member), the default diagnostic data directory path will be /home/db2inst1/sqllib/db2dump/DIAG0001.
      Note: There is a known problem APAR IT22555 in ESE environment, where the default diagnostic data directory path will incorrectly be set as sqllib/db2dump (where it should really be sqllib/db2dump/DIAGnnnn).
  • Windows environment
    1. V9.1 or earlier versions
          %DB2PATH%\[instance]
      %DB2PATH% is the path where Db2 is installed.
      For example, if %DB2PATH% is C:\Program Files\IBM\SQLLIB and instance name is DB2, the default diagnostic directory path will be C:\Program Files\IBM\SQLLIB\DB2.
    2. V9.5 or V9.7 (Windows XP, Windows Server 2003, or earlier)
          %ALLUSERSPROFILE%\Application Data\IBM\DB2\[DB2 copy name]\[instance]
      example:
      C:\Documents and Settings\All Users\Application Data\IBM\DB2\DB2COPY1\DB2
    3. V9.5 or V9.7 (Windows Vista, Windows Server 2008, or later)
          %ALLUSERSPROFILE%\IBM\DB2\[DB2 copy name]\[instance]
      example:
      C:\ProgramData\IBM\DB2\DB2COPY1\DB2
    4. V10.1 or later versions with non-ESE instance
      The same path as V9.5 or V9.7 for your appropriate Windows operation system.
    5. V10.1 or later versions with ESE instance
      Note: ESE instance is created by default in V10.5 or later even if you use Workgroup Server Editions.
      The same path as V9.5 or V9.7 version with the subdirectory DIAGnnnn.
      nnnn is a 4-digit node number. If you are running ESE instance with a single node, it will always be DIAG0000.

      Table 1. Summary of path to diagnostic data in Windows.
      Windows XP, Windows Server 2003 or before Windows Vista, Windows Server 2008 and later
      V9.5 or V9.7 %ALLUSERSPROFILE%\Application Data\IBM\DB2\[DB2 copy name]\[instance] %ALLUSERSPROFILE%\IBM\DB2\[DB2 copy name]\[instance]
      V10.1 or later non ESE
      ESE %ALLUSERSPROFILE%\Application Data\IBM\DB2\[DB2 copy name]\[instance]\DIAGnnnn %ALLUSERSPROFILE%\IBM\DB2\[DB2 copy name]\[instance]\DIAGnnnn

b. The diagnostic data directory path if changed from the default
You can find out the DIAGPATH database manager configuration parameter using the GET DATABASE MANAGER CONFIGURATION command.
In a UNIX/Linux environment, run the command as the instance owner. In a Windows environment, run it from the command window.

[UNIX/Linux]
$ db2 get dbm cfg | grep DIAGPATH
  Diagnostic data directory path      (DIAGPATH) = /home/db2inst1/sqllib/db2dump/ $m
  Current member resolved DIAGPATH               = /home/db2inst1/sqllib/db2dump/DIAG0000/



[Windows]
C:\>db2 get dbm cfg | findstr DIAGPATH
 Diagnostic data directory path      (DIAGPATH) = C:\PROGRAMDATA\IBM\DB2\DB2COPY1\DB2\ $m
 Current member resolved DIAGPATH               = C:\PROGRAMDATA\IBM\DB2\DB2COPY1\DB2\DIAG0000\

To confirm the value of the DB2INSTPROF registry variable, run db2set command  by a user ID with SYSADM authority.
C:\>db2set -all | findstr DB2INSTPROF
[i] DB2INSTPROF=C:\PROGRAMDATA\IBM\DB2\DB2COPY1

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;9.5;9.1;10.1;10.5;11.1;11.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Historical Number

14BE816259E15404492577EB001F059A

Document Information

Modified date:
04 December 2019

UID

ibm11086387