|
Problem IC72714
|
Status: Closed |
CRASH RECOVERY WILL NOT BE TERMINATED ANY MORE IF THE FIRST CLIENT CONNECTION IS GONE |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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.
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 Summary: |
****************************************************************
* 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.5 and Fixpack 8 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 Version 9.5 and Fixpack 8 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.11.2010
30.06.2011
30.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
