|
Problem IT21927
|
Status: Closed |
BLOCK DROPPING OF CF DURING ROLLING UPGRADE |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
In a pureScale environment it is possible to drop a CF in the
middle of Rolling Upgrade (that is, Rolling Upgrade has started
but not completed and members are at different fix pack levels).
Once that occurs a CF cannot be added back as the following
SQLCODE is returned:
SQL1648N The SQL statement or command cannot be processed
because of the state of a DB2 member in a DB2 pureScale
environment. Member = "129". Reason code = "10". SQLSTATE=57061
Further, rolling upgrade cannot be cancelled as two CF's are
required:
Minimum 2 CFs are required to perform online fixpack updates
DBI20135E The online fix pack update has halted because the
secondary CF is not in PEER state.
Thus during Rolling Upgrade the dropping of a CF is now blocked. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher *
**************************************************************** |
| Local Fix: |
Complete the rolling upgrade before dropping a CF |
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Db2 11.1 Mod 3 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.08.2017
19.03.2018
19.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
