|
Problem IC66683
|
Status: Closed |
AFTER ALTER TABLESPACE REDUCE ON DMS TABLESPACE, "DF -K" ON THE VERITAS FS (VXFS) STILL SHOWS SPACE NOT RELEASE BACK TO OS. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
After issuing the ALTER TABLESPACE ... REDUCE command on the
DMS tablespace which resides on the Veritas Filesystem (VxFS),
the "df -k" OS command still shows disk space not release back
to the OS.
However, both the "ls -l" and "db2 list tablespace" commands
show the DMS container size has been reduced. NOTE: the issue
is only applicable to the Veritas filesystem (VxFS). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users with DMS tablespace on VxFS. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Without this APAR, customer is exposed to the issue as *
* described in the "ERROR DESCRIPTION" section. *
* *
* See "ERROR DESCRIPTION" section for more details. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to product version DB2 V9.5 fixpack 6. *
**************************************************************** |
| Local Fix: |
External Veritas setext tool can be used to release the space
but should be done with caution, and users are advise to take
a DB2 backup before making any changes. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.5, Fixpack 6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66949 IC66950
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.02.2010
30.06.2010
30.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
