DB2 - Problembeschreibung
Problem IC70638 | Status: Geschlossen |
DB2 TRIES TO DELETE OLD BACKUPS AND LOGS MULTIPLE TIMES WHEN DOI NG BACKUP TO TSM AND AUTO_DEL_REC_OBJ IS ON AND USING MULTIPLE S | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
DB2 tries to delete old backups and logs multiple times when doing backup to TSM and AUTO_DEL_REC_OBJ is ON and using multiple session in backup command. Recreation of the problem can be done as below: db2 create db AUTODEL db2 update db cfg for AUTODEL using REC_HIS_RETENTN 0 NUM_DB_BACKUPS 2 AUTO_DEL_REC_OBJ ON db2 terminate db2 backup db AUTODEL USE TSM OPEN 2 SESSIONS db2 backup db AUTODEL USE TSM OPEN 2 SESSIONS rm ~/sqllib/db2dump/db2diag.log db2 backup db AUTODEL USE TSM OPEN 2 SESSIONS In db2diag.log, user will see: 2010-08-11-17.02.37.710729-240 E4426E453 LEVEL: Info PID : 4433 TID : 47484961286464PROC : db2sysc INSTANCE: XXXXXX NODE : 000 DB : AUTODEL APPHDL : 0-36 APPID: *100811210235 AUTHID : XXXXXX EDUID : 136 EDUNAME: db2agent (AUTODEL) FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1600 MESSAGE : Starting an offline db backup. 2010-08-11-17.02.43.884073-240 E4880E521 LEVEL: Info PID : 4433 TID : 47484961286464PROC : db2sysc INSTANCE: XXXXXX NODE : 000 DB : AUTODEL APPHDL : 0-36 APPID: *100811210235 AUTHID : XXXXXXX EDUID : 136 EDUNAME: db2agent (AUTODEL) FUNCTION: DB2 UDB, database utilities, sqluhPruneHistoryDeleteFile, probe:1112 MESSAGE : ADM8504I Successfully deleted the backup image with timestamp< "20100811170152". 2010-08-11-17.02.44.108856-240 E5402E464 LEVEL: Error PID : 9205 TID : 47099491015392PROC : db2vend (DB2 Prune Agent - 136 ( INSTANCE: XXXXXX NODE : 000 FUNCTION: DB2 UDB, database utilities, sqluvDoQueryAndDelete, probe:2762 DATA #1 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes Vendor RC=0x00000006=6 -- see DB2 API Guide for meaning. MESSAGE : Could not find any objects to delete. DATA #2 : signed integer, 8 bytes 0 2010-08-11-17.02.44.109812-240 E5867E521 LEVEL: Info PID : 4433 TID : 47484961286464PROC : db2sysc INSTANCE: XXXXXXX NODE : 000 DB : AUTODEL APPHDL : 0-36 APPID: *100811210235 AUTHID : XXXXXXX EDUID : 136 EDUNAME: db2agent (AUTODEL) FUNCTION: DB2 UDB, database utilities, sqluhPruneHistoryDeleteFile, probe:1112 MESSAGE : ADM8504I Successfully deleted the backup image with timestamp< "20100811170152". 2010-08-11-17.02.45.266974-240 E6389E426 LEVEL: Info PID : 4433 TID : 47484961286464PROC : db2sysc INSTANCE: XXXXXXX NODE : 000 DB : AUTODEL APPHDL : 0-36 APPID: *100811210235 AUTHID : XXXXXXX EDUID : 136 EDUNAME: db2agent (AUTODEL) FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:905 MESSAGE : Backup complete. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 tries to delete old backups and logs multiple times * * when doing backup to TSM and AUTO_DEL_REC_OBJ is on and * * using multiple session. * **************************************************************** * RECOMMENDATION: * * First Fixed in DB2 V9.7 Fixpack 4. * **************************************************************** | |
Local-Fix: | |
Do not use Multiple OPEN Session in backup command. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
DB2 tries to delete old backups and logs multiple times when doing backup to TSM and AUTO_DEL_REC_OBJ is ON and using multiple session in backup command. Recreation of the problem can be done as below: db2 create db AUTODEL db2 update db cfg for AUTODEL using REC_HIS_RETENTN 0 NUM_DB_BACKUPS 2 AUTO_DEL_REC_OBJ ON db2 terminate db2 backup db AUTODEL USE TSM OPEN 2 SESSIONS db2 backup db AUTODEL USE TSM OPEN 2 SESSIONS rm ~/sqllib/db2dump/db2diag.log db2 backup db AUTODEL USE TSM OPEN 2 SESSIONS In db2diag.log, user will see: 2010-08-11-17.02.37.710729-240 E4426E453 LEVEL: Info PID : 4433 TID : 47484961286464PROC : db2sysc INSTANCE: XXXXXX NODE : 000 DB : AUTODEL APPHDL : 0-36 APPID: *100811210235 AUTHID : XXXXXX EDUID : 136 EDUNAME: db2agent (AUTODEL) FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1600 MESSAGE : Starting an offline db backup. 2010-08-11-17.02.43.884073-240 E4880E521 LEVEL: Info PID : 4433 TID : 47484961286464PROC : db2sysc INSTANCE: XXXXXX NODE : 000 DB : AUTODEL APPHDL : 0-36 APPID: *100811210235 AUTHID : XXXXXXX EDUID : 136 EDUNAME: db2agent (AUTODEL) FUNCTION: DB2 UDB, database utilities, sqluhPruneHistoryDeleteFile, probe:1112 MESSAGE : ADM8504I Successfully deleted the backup image with timestamp< "20100811170152". 2010-08-11-17.02.44.108856-240 E5402E464 LEVEL: Error PID : 9205 TID : 47099491015392PROC : db2vend (DB2 Prune Agent - 136 ( INSTANCE: XXXXXX NODE : 000 FUNCTION: DB2 UDB, database utilities, sqluvDoQueryAndDelete, probe:2762 DATA #1 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes Vendor RC=0x00000006=6 -- see DB2 API Guide for meaning. MESSAGE : Could not find any objects to delete. DATA #2 : signed integer, 8 bytes 0 2010-08-11-17.02.44.109812-240 E5867E521 LEVEL: Info PID : 4433 TID : 47484961286464PROC : db2sysc INSTANCE: XXXXXXX NODE : 000 DB : AUTODEL APPHDL : 0-36 APPID: *100811210235 AUTHID : XXXXXXX EDUID : 136 EDUNAME: db2agent (AUTODEL) FUNCTION: DB2 UDB, database utilities, sqluhPruneHistoryDeleteFile, probe:1112 MESSAGE : ADM8504I Successfully deleted the backup image with timestamp< "20100811170152". 2010-08-11-17.02.45.266974-240 E6389E426 LEVEL: Info PID : 4433 TID : 47484961286464PROC : db2sysc INSTANCE: XXXXXXX NODE : 000 DB : AUTODEL APPHDL : 0-36 APPID: *100811210235 AUTHID : XXXXXXX EDUID : 136 EDUNAME: db2agent (AUTODEL) FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:905 MESSAGE : Backup complete. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC71170 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 18.08.2010 14.07.2011 14.07.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.2.05, 9.7.FP4 | |
Problem behoben lt. FixList in der Version | |
9.7.0.4 |