DB2 - Problem description
Problem IC78332 | Status: Closed |
DEDUP OPERATIONS ATTEMPT TO RUN DEDUP MEDIA CONTROLLER TERMINATION LOGIC DURING BACKUP COMPLETION PHASE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The Assertion noticed internally will not actually occur in a customer S build. In the S build case, we will possibly send a targeted end message to the last BM with unpredictable results depending on possible timings. The issue is during the final phase of a backup. If there is a large delay in the amount of time it takes DB2 to open a session to write too, as compared to the amount of time it takes for the process reading the necessary log files and metadata files to write that information to buffer, then logic meant to protect against an end being sent to the writer at the time of the media writer's initialization, does not apply. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users using DB2 and the dedup keyword for backups * **************************************************************** * PROBLEM DESCRIPTION: * * This problem was caught via an Assert in internal testing. * * Possible customer results are somewhat unpredictable based * * on timing, but may include the termination of the media * * writer, resulting in an incomplete backup. * **************************************************************** * RECOMMENDATION: * * move up to a fixpac with this fix. * **************************************************************** | |
Local Fix: | |
It's relatively unlikely for the BM to finish entirely before the MC has time to initiate a session, but there is no real practical local fix if this should occur. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
in v97 this problem will be fixed in fp5 | |
Workaround | |
special build. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.08.2011 17.01.2012 17.01.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |