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

DB2 SNAPSHOT BACKUP WILL NOT RESPOND TO INTERRUPT SIGNALS DURING A FENCED
VENDOR CALL TO THE SNAPSHOT VENDOR API.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
During a DB2 snapshot backup, the DB2 snapshot backup process or 
the CLI interface running the backup will not responded to 
interrupts, during calls to the snapshot backup fenced vendor 
API.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During a DB2 snapshot backup, the DB2 snapshot backup        * 
* process or the CLI interface running the backup will not     * 
* responded to interrupts, during calls to the snapshot backup * 
* fenced vendor API.                                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP11                                     * 
****************************************************************
Local Fix:
Users can manual kill the fenced vendor library to terminate the 
snapshot backup. DB2 backup will exit cleanly reporting a 
failure in the vendor library.
Solution
Upgrade to DB2 v9.7 FP11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.06.2014
13.10.2015
13.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList