suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT16082 Status: Closed

DB2 LOAD LEAVES FILE DESCRIPTOR OPEN WHEN TEMPORARY FILES ARE GREATER THAN
128GB

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DB2 LOAD leaves file descriptor open when LOAD temporary files
are greater than 128GB. This means that the disk space is not
freed up in the LOAD temporary disk path and then subsequent
LOADs may fail due to lack of disk space.
This will only occurring when loading data into Column Organized
tables.

There is a limit of 128GB for the temporary files. If the
temporary files are less than 128GB then the files are cleared
up successfully. If they are above this size then the file
descriptor will not be closed successfully and the disk space
will not be freed until the instance is restarted.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL DB2 LUW LOAD user with COLUMN ORGANIZED tables.          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Restart the instance to free up the disk space.              *
* Upgrade to the Db2 11.1 level that contains the fix.         *
****************************************************************
Local Fix:
Restart the instance to free up the disk space.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT27675 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.07.2016
04.01.2019
09.01.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)