home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC65463 Status: Closed

DB2 TSA MOUNT START/STOP SCRIPT EXIT WITH ERROR DUE TO
INACCESSIBLE /ETC/FSTAB

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If the DB2 TSA mount stop and start scripts encounter an error 
when accessing /etc/fstab, the scripts return a 2 (offline) 
inappropriately. 
 
/etc/fstab contains appropriate entry for the filesystem 
/dev/vgdb2NODE0000/lvdb2NODE0000 /db2fs/bculinux/NODE0000 ext3 
noauto,acl,user_xattr 1 0 
 
The following message is found in the GblResRM Trace_summary 
output 
07/29/09 14:52:26.568735 T(4140616608) _GBD Monitor detect 
OpState change for resource 
Name=db2mnt-db2fs_bculinux_NODE0000-rs OldOpState=1 NewOpState=2 
Handle=0x6028 0xffff 0xccbd0e75 0xc5a5a084 0x10e591c0 0x3dc34d28 
 
As a result of the 2 return code, TSA stops the resource group 
that includes DB2 resources.  DB2 is taken offline.
Problem Summary:
DB2 TSA MOUNT START/STOP SCRIPT EXIT WITH ERROR DUE TO 
INACCESSIBLE /ETC/FSTAB
Local Fix:
In /usr/sbin/rsct/sapolicies/db2/mountV97_start.ksh, comment 
the "exit 2" for the /etc/fstab clause. 
Example below: 
   blockDevice=$(cat /etc/fstab | awk '{print $1 " " $2}' | 
grep " ${MP}$" | awk '{print $1}') 
   if [[ -z $blockDevice ]]; then 
      logger -i -p err -t $myname "Mount point $MP not defined 
at this host" 
#      exit 2 
   fi 
 
In /usr/sbin/rsct/sapolicies/db2/mountV97_stop.ksh, comment the 
"exit $mounted" for the /etc/fstab clause 
   blockDevice=$(cat /etc/fstab | awk '{print $1 " " $2}' | 
grep " ${MP}$" | awk '{print $1}') 
   if [[ -z $blockDevice ]]; then 
      logger -i -p err -t $myname "Mount point $MP not defined 
at this host" 
      isMounted 
#      exit $mounted 
   fi
available fix packs:
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 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 9a 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

Solution
Scripts modified in fixpack 2 to avoid the incorrect return code
Workaround
In /usr/sbin/rsct/sapolicies/db2/mountV97_start.ksh, comment 
the "exit 2" for the /etc/fstab clause. 
Example below: 
  blockDevice=$(cat /etc/fstab | awk '{print $1 " " $2}' | 
grep " ${MP}$" | awk '{print $1}') 
  if [[ -z $blockDevice ]]; then 
      logger -i -p err -t $myname "Mount point $MP not defined 
at this host" 
#      exit 2 
  fi 
 
In /usr/sbin/rsct/sapolicies/db2/mountV97_stop.ksh, comment the 
"exit $mounted" for the /etc/fstab clause 
  blockDevice=$(cat /etc/fstab | awk '{print $1 " " $2}' | 
grep " ${MP}$" | awk '{print $1}') 
  if [[ -z $blockDevice ]]; then 
      logger -i -p err -t $myname "Mount point $MP not defined 
at this host" 
      isMounted 
#      exit $mounted 
  fi
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.01.2010
02.09.2010
02.09.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList