IT29348: DB2SUPPORT MIGHT NOT COLLECT DB2DIAG.N.LOG IN DIAGPATH.

APAR status

• Closed as program error.

Error description

• The db2support tool might not collect db2diag.n.log in the
  DIAGPATH if no "db2diag.log" exists on the path.
  The following scenario illustrates how the problem happens.
  
  1. Update DIAGSIZE and DIAGPATH.
  
  $ db2 attach to <instance_name>
  $ db2 update dbm cfg using DIAGSIZE 10
  $ db2 update dbm cfg using DIAGPATH /work/db2dump
  
  2. Run db2support to collect diagnostics.
  
  $ db2support . -f
  
  The db2support.zip file does not contains DB2DUMP directory.
  

Local fix

• Please create "db2diag.log" file in the DIAGPATH.
  For example:
  $ touch <diag_path>/db2diag.log
  If the file already exists please use the same command to change
  the creation timestamp of the file to the current time.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Users on DB2 v111 FP5 and earlier                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to db2 v111 m4 FP6 or apply any Local Fix available. *
  ****************************************************************
  

Problem conclusion

• First Fixed in db2 v111 m4 FP6
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels