DB2 - Problem description
Problem IC70386 | Status: Closed |
CRASH RECOVERY WILL NOT BE TERMINATED ANY MORE IF THE FIRST CLIENT CONNECTION IS GONE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * 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.8 and Fixpack 0 * **************************************************************** | |
Local Fix: | |
Solution | |
Problem was first fixed in DB2 Version 9.8 and Fixpack 0 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.08.2010 28.02.2011 28.02.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.8. | |
Problem solved according to the fixlist(s) of the following version(s) |