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 IC99706 Status: Closed

DB2HAICU FAILS TO CREATE A MOUNT RESOURCE FOR AN EXT4 BASED MOUNT POINT

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The db2haicu utility fails to create a mount resource for a 
mount point that is on a file system of type "ext4". The 
following error is returned by db2haicu when attempting to 
create a resource for an ext4 based mount point: 
 
"Either db2cluster could not resolve mount point '/xxxxxx', or 
mount point '/xxxxxx' is on a file system that is not eligible 
to be added to the cluster". 
 
This APAR addresses the support of mount points based on ext4 
file systems by the db2haicu utility.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL USERS of DB2 LUW V10.5                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW V10.5 FP3 or later.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in DB2 LUW V10.5 FixPack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.02.2014
22.12.2014
22.12.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList