DB2 - Problem description
Problem IT21413 | Status: Closed |
BLOCK DROPPING OF CF DURING ROLLING UPGRADE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - 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: * * any pureScale users that drop CF's * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to v10.5 fix pack 9 * **************************************************************** | |
Local Fix: | |
Complete the rolling upgrade before dropping a CF | |
Solution | |
This problem is first fixed in v10.5 fix pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.07.2017 27.09.2017 27.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |