|
Problem IC97880
|
Status: Closed |
CONTAINER RESIZE BEYOND 16 TB DOES NOT FAIL AND CAUSES UNEXPECTED RESULTS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
JFS2 has a MAX_FILESIZE limitation of 16 TB
When DB2 re-sizes a container to a size beyond 16 TB, the action
succeeds without giving and error but the container only grows
till the JFS2 limit.
This causes unexpected results when trying to access the
container again. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* V10.5 FP2 and below *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix *
* Pack 4) *
**************************************************************** |
| 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 |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.11.2013
08.09.2014
17.10.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
|
 |
