|
Problem IT02864
|
Status: Closed |
HA FILESYSTEM IS AUTOMATICALLY REMOUNTED BY TSA WHILE THE DB2 INSTANCE IS STOPPED |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
On an AIX system, where the DB2 instance has been configured for
high availability via the db2haicu utility. If a highly
available file system is unmounted while the DB2 instance is
stopped, TSA will automatically remount the file system.
In order to determine if a file system is highly available, the
following two commands can be executed:
export CT_MANAGEMENT_SCOPE=2
lsrsrc -s "StartCommand like '%/hafs01/db2inst1/NODE0000' &&
ResourceType=1" IBM.Application
where '/hafs01/db2inst1/NODE0000' is the mount path of the file
system in question. If the lsrsrc command returns a result, then
the file system is highly available.
In order to prevent this automatic unmount from happening, the
file system must be unmounted and then its underlying volume
group must be varied off. Once maintenance operations are
completed for the file system, then the volume group can be
varied back on and the file system can then be remounted. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 HA Shared Disk users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.5 FP5 *
**************************************************************** |
| Local Fix: |
N/A |
| Solution |
Fixed in DB2 V10.5 FP5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.06.2014
13.03.2015
13.03.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
