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
------------------------------------- |
