|
Problem IC88603
|
Status: Closed |
ADMIN_MOVE_TABLE() FAILS WITH SQL2103N, RC=17 WHEN LOB INLINE_LENGTH DIFFERS BETWEEN SOURCE AND TARGET OBJECT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| available fix packs: |
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
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.11.2012
09.04.2013
09.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
