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

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
Upgrade to DB2 v9.7 FP11
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.06.2014
13.10.2015
13.10.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP11
Problem behoben lt. FixList in der Version
9.7.0.11 FixList