home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC96871 Status: Geschlossen

IN DPF ENVIRONMENT PRUNE WILL NOT DELETE IMAGE FROM DISK WHERE T HE
DATABASE PARTITION EXPRESSION $N WAS USED IN TARGET DIRECTORY

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
In DPF environment, prune will not delete backup images from 
disk where the database partition expression $N was used in 
target directory. 
Entries from history file are getting deleted. 
 
This can be reproduced with the following steps: 
1. Set the following db cfg parameters: 
 Auto deletion of recovery objects    (AUTO_DEL_REC_OBJ) = ON 
 Number of database backups to retain   (NUM_DB_BACKUPS) = 1 
 Recovery history retention (days)     (REC_HIS_RETENTN) = 1 
 
2. Use database partition expression $N to backup 
$ db2 "backup db db1 on all dbpartitionnums to 
'/home/db2inst1/backup/NODE000 \$N'" 
 
Backup is successful and images are saved to 
'/home/db2inst1/backup/NODE0001, NODE0002, NODE0003 etc. 
 
$ db2 LIST HISTORY BACKUP all for db1 
 
                    List History File for db1 
 
Number of matching file entries = 1 
 
 
 Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log 
Backup ID 
 -- --- ------------------ ---- --- ------------ ------------ 
-------------- 
  B  D  20130917115709001   F    D  S0000016.LOG S0000016.LOG 
 
---------------------------------------------------------------- 
------------ 
  Contains 3 tablespace(s): 
 
  00001 SYSCATSPACE 
  00002 USERSPACE1 
  00003 SYSTOOLSPACE 
 
---------------------------------------------------------------- 
------------ 
    Comment: DB2 BACKUP DB1 OFFLINE 
 Start Time: 20130917115709 
   End Time: 20130917115717 
     Status: A 
 
---------------------------------------------------------------- 
------------ 
  EID: 36 Location: /home/db2inst1/backup/NODE000 $N 
 
3. doing another backup, this should delete the previous backup 
image based on database parameters set previously. 
In db2diag.log, the backup images deleted messages are logged, 
however the backup images are not removed from the disk. 
 
2013-09-17-11.59.29.195079-600 E11390A510         LEVEL: Info 
PID     : 487482               TID  : 7044        PROC : db2sysc 
1 
INSTANCE: db2inst1                NODE : 001         DB   : DB1 
APPHDL  : 1-80                 APPID: *N1.db2inst1.130917215912 
AUTHID  : DB2INST1 
EDUID   : 7044                 EDUNAME: db2agntp (DB1) 1 
FUNCTION: DB2 UDB, database utilities, 
sqluhPruneHistoryDeleteFile, probe:1112 
MESSAGE : ADM8504I  Successfully deleted the backup image with 
timestamp 
          "20130917115709". 
 
The entries from history file are getting deleted correctly. 
 
If the backup command doesn't use $N in the target directory, 
then backup images are deleted correctly.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in Version 10.1 Fix Pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.10.2013
02.06.2014
02.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList