DB2 FOR LUW / DB2FORLUW / 970 - DB2

"Stuck Online" indicates that there was an error occurred while 
trying stop the resource. If the following conditions are  met 
TSA controlled  HA-DB2 Resoruce may become 'stuck online' due to 
a defect ( A new email notification for instance owner id is not 
properly handled) in db2V95_stop.ksh script. 
 
 
1. The instance Owner ID has new email. 
2. The following statments  are listed  in porfile file of 
instance ID 
 
  [...] 
  if [ -s "$MAIL" ] # This is at Shell startup. In normal 
  then echo "$MAILMSG" # operation, the Shell checks 
  fi # periodically. 
  [...]

"Stuck Online" indicates that there was an error occurred while 
 
trying stop the resource. If the following conditions are  met 
TSA controlled  HA-DB2 Resoruce may become 'stuck online' due to 
a defect ( A new email notification for instance owner id is not 
properly handled) in db2V95_stop.ksh script. 
 
 
1. The instance Owner ID has new email. 
2. The following statments  are listed  in porfile file of 
instance ID 
 
  [...] 
  if [ -s "$MAIL" ] # This is at Shell startup. In normal 
  then echo "$MAILMSG" # operation, the Shell checks 
  fi # periodically. 
  [...]

Disabling mail notification in /home/db2inst1/.profile by 
commenting out above statement.

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 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 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
 

This APAR is first fixed on the DB2 v9.7 Fixpack1

Disabling mail notification in /home/db2inst1/.profile by 
commenting out above statement.

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

21.09.2009
15.01.2010
15.01.2010

9.7.