home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC99671 Status: Closed

DB2 DOES NOT REMOVE OLD LOGS DURING UPGRADE IN V10

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Upgrading database to DB2 V10 and above from DB2 V9.7 or V9.5 
may fail if there is not enough space on the file system to 
accommodate all the active logs files. Previously in the older 
releases active log files were under SQLOGDIR. However, it has 
changed in V10 to LOGSTREAM0000. This results in all the old log 
files getting copied and moved to the new directory, causing 
double the amount of space required. On top of this, a new set 
up log chain is created in LOGSTREAM0000. 
 
The deletion only happens after it gets copied over, thus an 
upgrade could fail if the log files cannot be accommodated.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 fixpack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.02.2014
24.04.2014
24.04.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList