[Db2] How to collect db2support (for Windows platforms)

Answer

1. Logon to the database server as administrator user.
2. Open "DB2 Command Window - Administrator"
3. Run db2support command as below:
   db2support [outputdir] -s -d [database] -c -f > db2support.log 2>&1
   Where  [outputdir] is the path name to place output file (for example C:\home\db2inst1\db2support)
   note: The path name should not contain blanks.
   Where [database] is the target database name to collect data.
   In V10.5 or later, you can specify multiple database name, delimited by comma. If you want to collect information for all databases listed in the database directory, you can specify '-alldbs' option instead of '-d' and database name.
   In V10.1 or before, you can specify only one database name for each execution of db2support utility. You need to run db2support utility multi-times for each database, if you need to gather information about multiple databases.
4. Please provide following files to IBM technical support.
   db2support.zip, db2support.log, db2diag.log

• If you are partitioned database environment with multiple node, run the db2support utility in catalog node and the node where the problem has happened.
• When db2support utility does not complete for long time (for example 5 minutes), terminate the utility by pressing Ctrl+C.
• If you cannot connect to the database, please use  -nco option instead of -c option.
• If the target database is on zSeries (S/390) or iSeries (AS/400), or you want to collect client/gateway information only, please remove "-d [database] -c" option.
• In DB2 V11.1 Mod 3 Fix Pack 3, there is known problem which can cause critical impact on Db2. If you are running with this level, please refer following technote and follow the workaround.
  Running db2support on Db2 V 11.1 Mod 3 Fix Pack 3 can remove critical database files with potential result of corruption / database outage
  With the length of output-path longer than instance-name + 9, where "instance-name" is the short instance name (e.g. "DB2").
  e.g.:db2support C:\temp\db2support -s -d [database] -c -f > db2support.log 2>&1

• IC72657, IC72525
  Applicable level: V9.7 Fix pack 3, V9.5 Fix Pack 6 or 7 (The crash should only happen in the Windows environment even single node.
  Problem: db2support command with -d option may crash
  Workaround: Run db2support without -d -c option.
  Solution: IC72657 was fixed in V9.7 Fix pack 4 or later, and IC72525 was fixed in V9.5 Fix pack 8 or later.
• IC80746
  Applicable leve: V9.7 Fix pack 5
  Problem: db2support may take long time due to db2dart.
  Workaround: please add -st "values 1" option like as follows.
  $ db2support . -d [database] -c -st "values 1" -
  Solution: IC80746 was fixed in V9.7 Fix pack 6 or later.
• IC76948
  Applicable level: V9.7 Fix pack 4 Data Server Client
  Problem: db2support process may abnormally terminate.
  Workaround: None. Avoid running db2support utility when you encountered the problem.
  Solution: IC76948 was fixed in V9.7 Fix pack 5 or later.
• IT07419
  Applicable level: FP6 of before in V10.5
  Problem: db2support utility may hang due to LIST TABLESPACE SHOW DETAIL command does not complete, which was issued as part of db2support utility.
  Workaround: None. Please apply V10.5 FP7 or later.
• IC91469 (V9.7) / IC91488 (V10.1) / IC95240 (V10.5)
  Applicable level: FP8 or before in V9.7 / FP2 or before in V10.1 / FP2 of before in V10.5
  Problem: db2support may hang when database was specified in -d option, due to lock contention while collecting catalog information.
  Workaround: Specify -nco option instead of -c option.
  Solution: IC91469 was fixed in V9.7 Fix pack 9 or later, IC91488 was fixed in V10.1 Fix pack 3 or later, and IC95240 was fixed in V10.5 Fix pack 3 or later.