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

CRASH RECOVERY WILL NOT BE TERMINATED ANY MORE IF THE FIRST CLIENT
CONNECTION IS GONE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Normally during a crash recovery, if the first client connection 
is gone, then the crash recovery will be terminated. 
This APAR fix will let the crash recovery complete, even when 
the first client connection is gone. 
The idea here is that recovery, if driven implicitly, has 
nothing to do with the client connection - the client just so 
happens to be the first to run into a database that needs 
restart processing. 
The bottom line is that the database requires recovery and that 
should be completed as soon as possible.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* CRASH RECOVERY WILL NOT BE TERMINATED ANY MORE IF THE FIRST  * 
* CLIENT CONNECTION IS GONE                                    * 
* Normally during a crash recovery, if the first client        * 
* connection                                                   * 
* is gone, then the crash recovery will be terminated.         * 
*                                                              * 
* This APAR fix will let the crash recovery complete, even     * 
* when                                                         * 
* the first client connection is gone.                         * 
*                                                              * 
* The idea here is that recovery, if driven implicitly, has    * 
*                                                              * 
* nothing to do with the client connection - the client just   * 
* so                                                           * 
* happens to be the first to run into a database that needs    * 
*                                                              * 
* restart processing.                                          * 
*                                                              * 
* The bottom line is that the database requires recovery and   * 
* that                                                         * 
* should be completed as soon as possible.                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 and Fixpack 4                     * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in DB2 Version 9.7 and Fixpack 4
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC70386 IC72714 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.06.2010
28.04.2011
28.04.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.4 FixList