|
Problem IT10696
|
Status: Geschlossen |
DB2CKUPGRADE IN PURESCALE DOES NOT FAIL IF DATABASE IS ADD MEMBER TOPOLOGY CHANGE PENDING BUT UPGRADE DOES FAIL |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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. |
| Lösung |
First fixed in DB2 Version 10.5 Fix Pack 7. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.08.2015
25.01.2016
25.01.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.5.0.7
|
 |
