|
Problem IC96395
|
Status: Closed |
SQLOGETFSATTRIB() FAILS TO REPORT THE CORRECT FREE DISK SIZE OF A DISK VOLUME THAT IS ON A JUNCTION POINT. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 V10.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V10.1 FP3 *
**************************************************************** |
| Local Fix: |
Avoid using Junction Point |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in V10.1 FP3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.09.2013
18.10.2013
18.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
