DB2 FOR LUW / DB2FORLUW / 950 - DB2

In using a shared disk configuration on AIX, with DB2 and TSA, 
if you have one volume group consisting of multiple file 
systems, after failover, some resource groups could be in a 
"Pending Offline" state. 
 
For Example, you have a VG called "db2vg1" with mulitple DB2 
filesystems, for logs, tablespaces etc, like the following: 
 
/db2/db2inst1 <-- DB2 instance home 
/db2/db2inst1/log_dir  <-- DB2 log directories 
/db2/db2inst1/temp1  <-- DB2 temporary space 
/db2/db2inst1/data1  <-- DB2 data space 
/db2/db2inst1/data2  <-- DB2 data space 
/db2/db2inst1/db2dump  <-- DB2 diagnostic data 
 
After a failover operation, the lssam output (shown below), may 
indicate several DB2 mount 
resources are in "Pending Offline", eventually reaching a Failed 
Offline" or "Stuck Online" state. 
 
------lssam output snippet------ 
**Pending offline** IBM.ResourceGroup:db2_db2inst1_0-rg 
Request=Lock 
Binding=Sacrificial Control=SuspendedPropagated Nominal=Online 
|- Offline IBM.Application:db2_db2inst1_0-rs Binding=Sacrificial 
Control=SuspendedPropagated 
  |- Offline IBM.Application:db2_db2inst1_0-rs:hostname01 
  '- Offline IBM.Application:db2_db2inst1_0-rs:hostname02 
>><< 
Binding=Sacrificial Control=SuspendedPropagated 
  |- Offline IBM.Application:db2inst1-db2_db2inst1-rs:hostname01 
  '- Online IBM.Application:db2inst1-db2_db2inst1-rs:hostname02 
|- **Pending offline** 
IBM.Application:db2inst1-db2inst1_log_dir-rs 
Binding=Sacrificial Control=SuspendedPropagated 
  |- Offline 
IBM.Application:db2inst1-db2inst1_log_dir-rs:hostname01 
  '- **Pending offline** 
IBM.Application:db2inst1-db2inst1_log_dir-rs:hostname02 
-------------------------------------

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 users on AIX platforms                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.5 FP10 or subsequent fix pack.              * 
****************************************************************

NA

Problem First Fixed in DB2 Version 9.5 Fix Pack 10

not known / see Local fix

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

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

02.04.2012
19.02.2013
19.02.2013

9.5.FP10