DB2 - Problem description
Problem IT10696 | Status: Closed |
DB2CKUPGRADE IN PURESCALE DOES NOT FAIL IF DATABASE IS ADD MEMBER TOPOLOGY CHANGE PENDING BUT UPGRADE DOES FAIL | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
UPGRADE is not allowed when a database is add member topology change pending, sqlcode = SQL1712N. But db2ckupgrade does not validate this and it succeeds. This mis-informs the user into thinking they can upgrade only to fail later. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * pureScale * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 7. * **************************************************************** | |
Local Fix: | |
Going back to the downlevel release and ensure all databases are no longer add member topology change pending. | |
Solution | |
First fixed in DB2 Version 10.5 Fix Pack 7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.08.2015 25.01.2016 25.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |