home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC88603 Status: Geschlossen

ADMIN_MOVE_TABLE() FAILS WITH SQL2103N, RC=17 WHEN LOB INLINE_LENGTH
DIFFERS BETWEEN SOURCE AND TARGET OBJECT

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The implicite INLINE_LENGTH value for LOB columns has changed 
between DB2 Versions. Prior to DB2 V9.7, it is 0, starting with 
DB2 V9.7, it is set to 164. Now when a source table with an old 
INLINE_LENGTH value (0) is moved with ADMIN_MOVE_TABLE() in DB2 
V9.7, the MOVE command will fail with SQL2103N, RC=17. This APAR 
will lift this restriction and continue with the MOVE command 
without error.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2.                      * 
****************************************************************
Local-Fix:
The FORCE option with the MOVE command will avoid SQL2103N and 
move the table as expected.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.1 Fix Pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.11.2012
09.04.2013
09.04.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList