|
Problem IC76506
|
Status: Closed |
ENSURE DB2IUPDT RUNS FIXTOPOLOGY WHENEVER 'DB2START ADD MEMBER' RETURNS A NON-SUCCESS RETURN CODE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
When db2start add member fails it does not completely clean up
the state of the instance. This APAR is opened to ensure that
the cluster is completely cleaned up and returned to a working
state after a failed attempt to add a new member. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Any users doing an add member request *
****************************************************************
* PROBLEM DESCRIPTION: *
* If an add member command fails, not all of the instance *
* cleanup is done. *
****************************************************************
* RECOMMENDATION: *
* Update to V9.8 Fixpack 4 or above *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
The problem was first fixed in V9.8 Fixpack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.05.2011
03.08.2011
03.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
