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

DURING CRASH RECOVERY PROCESS, IF DB2STOP FORCE IS ISSUED, THEN CRASH
RECOVERY WILL MARK DB BAD (ONLY HAPPEN IN SINGLE NODE)

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Problem: 
During crash recovery process, if db2stop force is issued, then 
crash recovery will mark db bad. 
==> there is already a fix for this issue already in 
wsdbu00329559 where instead of the marking db bad, db2 will do a 
softer exit and printing: 
 SQL6030N 
 START or STOP DATABASE MANAGER failed. Reason code ... 
 
However, further testing shows that the fix above is incomplete. 
The fix only works for multiple node, NOT single node. 
 
This defect is opened to complete the fix for single node.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During crash recovery process, if db2stop force is issued,   * 
* then                                                         * 
* crash recovery will mark the database as bad.                * 
*                                                              * 
*                                                              * 
* The fix for this APAR will avoid the database to be marked   * 
* as bad.  Instead, DB2 will do a softer exit and print the    * 
* following:                                                   * 
*                                                              * 
*  SQL6030N                                                    * 
*                                                              * 
*  START or STOP DATABASE MANAGER failed. Reason code ...      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 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 Version 9.7 Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
20.09.2010
28.04.2011
28.04.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList