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

TIMING HOLE DURING COMPLETION OF BACKUP USING DEDUP_DEVICE MAY CAUSE HANG
OR TRAP IN SQLUBCHECKCOMPLETION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During the completion of a backup using the dedup_device option 
of the backup command, the backup may hang or produce a trap in 
sqlubCheckCompletion 
 
The hang condition can be validated by seeing no progress in 
either 'db2pd -utilities'  or 'db2 list utilities show detail', 
and the Completed Work value will be close to the estimated work 
value. 
 
If a trap occurs, the stack trace in the trap file will include 
 
 
0x090000000215E110 ossHexDumpLine + 0x110 
0x090000000215E6F4 ossHexDumpToBuffer + 0x374 
0x090000000C3C78FC pdHexDump + 0x40 
0x090000000C3C7850 pdFormatArg + 0x25C 
0x090000000C3C72C8 
@133@formatPDType__FP13PDLogFacilityUlUiT2T3T2Pv + 0x194 
0x090000000C3C7044 
@133@pdTypeFormatOrDump__FP13PDLogFacilityR10PD_CONTEXTPcUlUiT4b 
T7T5T4Pv + 0x1BC 
 
0x090000000C3C441C @133@pdLogInternal__FUlUiT1T2N41PvT1bPPc + 
00x9B4 
 
0x090000000C308A54 pdLogInternal__FUlUiT1T2N41PvT1bPPc@glue44A + 
0xC0 
0x090000000C308948 pdLog + 0xD4 
0x09000000088F36AC sqlubCheckCompletion__FP12SQLU_BAGT_CB + 
0x2D4
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all backups using dedup_device                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 4                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.01.2011
09.05.2011
09.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList