DB2 - Problembeschreibung
| Problem IC96419 | Status: Geschlossen |
SQLOGETFSATTRIB() FAILS TO REPORT THE CORRECT FREE DISK SIZE OF A DISK VOLUME THAT IS ON A JUNCTION POINT. | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problembeschreibung: | |
On windows function sqloGetFSAttrib() fails to report the
correct free disk size of a disk volume that is on a
Junction Point.
Tablespace RollForward fails with Tablespace container full
error even when enough space is available
db2diag.log
----------------
MESSAGE : ADM6017E The table space "xxx" is full. Detected on
container "H:\XXX\XXXXX" (ID "0"). The
underlying file system is full or the maximum allowed
space usage for
the file system has been reached. It is also possible
that there are
user limits in place with respect to maximum file size
and these
limits have been reached.
FUNCTION: DB2 UDB, buffer pool services, sqlbSMSDirectWrite,
probe:99
MESSAGE : container page this was encountered on =
DATA #1 : unsigned integer, 8 bytes
389869
FUNCTION: DB2 UDB, buffer pool services, sqlbCheckAllocation,
probe:0
MESSAGE : ZRC=0x85020021=-2063466463=SQLB_END_OF_CONTAINER
"DMS Container space full" | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 V10.5 FP2 and below * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to 10.5.0.3 * **************************************************************** | |
| Local-Fix: | |
Avoid using Junction Point | |
| verfügbare FixPacks: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Lösung | |
Problem Fixed In 10.5.0.3 | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.09.2013 04.03.2014 04.03.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.5.0.3 |
|
| 10.5.0.3 |
|