|
Problem IC82615
|
Status: Closed |
Many DB2 filesystems on single AIX volume group may be "Failed/S tuck/Pending Offline" state after failover in shared-disk HA env |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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
------------------------------------- |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 FP7 or subsequent fix pack. *
**************************************************************** |
| Local Fix: |
NA |
| available fix packs: |
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
|
| Solution |
Problem First Fixed in DB2 Version 9.7 Fix Pack 7 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.04.2012
19.02.2013
19.02.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
