Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC99706 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
First fixed in DB2 LUW V10.5 FixPack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.02.2014
22.12.2014
22.12.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList