DB2 - Problembeschreibung
Problem IT25336 | Status: Geschlossen |
INFORMATIONAL: IF COLUMNAR TABLES ARE PRESENT THEN UPGRADE FROM10.5FP10 to 11.1 MIGHT REQUIRE A SPECIAL BUILD | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
This APAR is opened to inform customers with Columnar organized tables in the database of the following: If columnar organized table has at least one character or graphic data type column, then , once 10.5 FP10 is installed, upgrade to 11.1 has to be done to one of the following levels: - upgrade to 11.1 GA or 11.1 Mod 1 Fix Pack 1 - wait for 11.1 Mod 3 Fix Pack 3 iFix002 or 11.1 Mod 4 Fix Pack 4 to be released and upgrade to these fixpaks. If above is not done, db2ckupgrade will fail with SQL10007N Message "5556" could not be retrieved. Reason code: "4" when upgrading from v10.5fp10 to v11.1 To check if you have tables that could cause this issue in your database , please, run this query : "SELECT DISTINCT T.TBSPACEID, T.TABLEID, T.TABSCHEMA, T.TABNAME from SYSCAT.TABLES T JOIN SYSCAT.COLUMNS C on T.TABSCHEMA = C.TABSCHEMA and T.TABNAME = C.TABNAME WHERE T.TABLEORG='C' and SUBSTR(T.PROPERTY,21,1)!='Y' and (C.TYPENAME='CHARACTER' or C.TYPENAME='GRAPHIC') ORDER BY TBSPACEID DESC" | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * N/A * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Real APAR with the fix is IT25322, firstly fixed in Db2 11.1 * * Fixpack 3 Mod 2. * **************************************************************** | |
Local-Fix: | |
No workaround. | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Kommentar | |
cancelled | |
Bug-Verfolgung | |
Vorgänger : IT25322 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 12.06.2018 16.09.2018 16.09.2018 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |