IT23441: DB2 MEMBER IS KILLED AND RESTARTED DUE TO GPFS MOUNT RESOURCE TEMPORARILY REPORTING OFFLINE

Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• In a Db2 pureScale environment, a GPFS mount resource as seen in
  the lssam output may report offline for a monitoring cycle due
  to being unable to access information contained within the
  /etc/filesystems (AIX) or /etc/fstab (Linux) file.
  
  Under normal circumstances, the mountVXXX_monitor.ksh script
  should not have any issue accessing information located within
  this file. If it is suspected that the mountVXXX_monitor.ksh
  script has unexpectedly exit with return code of 2 due to this,
  then investigate the system logs for messages reported by the
  mountVXXX_monitor.ksh script. The following should be seen if
  debug level system logging is enabled:
  
  Oct 13 20:43:02 host01 user:debug
  mountV111_monitor.ksh[6095034]: Returning 2 for mount
  /db2/gpfsmount1
  

Local fix

• Not Available. Contact IBM support.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users prior to Db2 v11.1 m3 fp3.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Please upgrade Db2 to v11.1 m3 fp3.                          *
  ****************************************************************
  

Problem conclusion

• Problem is first fixed in Db2 v11.1 m3 fp3.
  

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

• RA50 PSY

     UP

• RB10 PSY

     UP