DB2 - Problem description
Problem IC71331 | Status: Closed |
DURING CRASH RECOVERY PROCESS, IF DB2STOP FORCE IS ISSUED, THEN CRASH RECOVERY WILL MARK DB BAD (ONLY HAPPEN IN SINGLE NODE) | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.09.2010 28.04.2011 28.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |