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 IT01476 Status: Closed

AUTOMATIC BACKUP DOES NOT DELETE OLD BACKUP IMAGE IN DB2 V10

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
The automatic backup is supposes to leave the most recent backup 
and delete all the rest. But it is not deleting the old backups 
in DB2v10. This problem didn't exist in DB2v9. 
 
When automatic backup is enabled and backup directory is set, 
DB2 will search in the designated backup directory for old 
backup files and remove them. DB2 identifies the backup files by 
it's name pattern. 
 
This defect is caused by the backup image name change from v9 
(<DBALIAS>.0.<INST_NAME>.NODEnnnn.CATNnnnn.##############.###) 
to v10 (<DBALIAS>.0.<INST_NAME>.DBPARTnnn.##############.###). 
This change caused the problem that DB2 fails to recognize these 
files as backup files, and thus fails to delete them.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 Fix Pack 4 (aka. DB2 Cancun)     * 
****************************************************************
Local Fix:
Solution
The APAR is fixed in DB2 version 10.5 Fix Pack 4 (aka. DB2 
Cancun)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.05.2014
13.10.2014
13.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 FixList