DB2 FOR LUW / DB2FORLUW / 970 - DB2

In an integrated HA environment, if there are multiple 
filesystems exist on the same vg on AIX systems, the TSA move 
request may hang. TSA move will call the mountV9x_stop.ksh 
script on all the mount points in parallel. 
 
In the mountV9x_stop.ksh script, umount and varyoffvg commands 
are issued in a loop until varyoffvg is successful. 
 
In a scenario where there are multiple fs on the same vg, one 
mountV9x_stop.ksh script may be calling varyoffvg while the 
other mountV9x_stop.ksh may be issuing lslv prior to a umount 
attempt. Since varyoffvg is being invoked in a loop, this will 
block the lslv calls. This subsequently blocks the lslv, umount 
code path in the rest of the mountV9x_stop.ksh scripts, so those 
mount points are still mounted. This in turn causes varyoffvg 
call to fail. 
 
This race condition is sometimes seen in an environment where 
there are over 4 filesystems per vg. 
 
During this scenario, any lslv or lsvg command will hang.

In an integrated HA environment, if there are multiple 
filesystems exist on the same vg on AIX systems, the TSA move 
request may hang. TSA move will call the mountV9x_stop.ksh 
script on all the mount points in parallel. 
 
In the mountV9x_stop.ksh script, umount and varyoffvg commands 
are issued in a loop until varyoffvg is successful. 
 
In a scenario where there are multiple fs on the same vg, one 
mountV9x_stop.ksh script may be calling varyoffvg while the 
other mountV9x_stop.ksh may be issuing lslv prior to a umount 
attempt. Since varyoffvg is being invoked in a loop, this will 
block the lslv calls. This subsequently blocks the lslv, umount 
code path in the rest of the mountV9x_stop.ksh scripts, so thos 
mount points are still mounted. This in turn causes varyoffvg 
call to fail. 
 
This race condition is sometimes seen in an environment where 
there are over 4 filesystems per vg. 
 
During this scenario, any lslv or lsvg command will hang.

No known workaround. Please contact with the IBM db2support.

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

This APAR is first fixed in the DB2 V9.7fp4

No known workaround. Please contact with the IBM db2support

forerunner  : APAR is sysrouted TO one or more of the following: IC71894 IC72005 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

14.10.2010
29.04.2011
29.04.2011

9.7.FP4