DB2 - Problem description
Problem IC88602 | Status: Closed |
ADMIN_MOVE_TABLE can fail with SQL0010N or a SQL0104N syntax error due to the length of comments. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
If there are multiple comments attached to a table and its columns, and these comments exceed 1kB in size, OTM cannot be used to move the table. ADMIN_MOVE_TABLE fails with a sytax error, since the COMMENT ON statement that copies the remarks gets truncated. The error will be seen if the length of the command to set the comments exceeds 1kb: COMMENT ON "SCHEMA"."TABLE" ("COL1" IS 'This is the comment for col1', "COL2" IS 'This is the comment on col2', ... etc. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of ADMIN_MOVE_TABLE on tables with many comments. * **************************************************************** * PROBLEM DESCRIPTION: * * If there are multiple comments attached to a table and its * * columns, and these comments exceed 1kB in size, * * OTM cannot be used to move the table. ADMIN_MOVE_TABLE * * fails * * with a sytax error, since the COMMENT ON * * statement that copies the remarks gets truncated. * * * * The error will be seen if the length of the command to set * * the * * comments exceeds 1kb: * * * * COMMENT ON "SCHEMA"."TABLE" ("COL1" IS 'This is the comment * * for * * col1', "COL2" IS 'This is the comment on col2', ... etc. * **************************************************************** * RECOMMENDATION: * * Upgrade to v10.1 FP2 to avoid this issue * **************************************************************** | |
Local Fix: | |
Shorten the length of comments on the table/columns. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to v10.1 FP2 to avoid this issue | |
Workaround | |
Remove the comments on the table (or at least enough to get under 1kb in size) | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.11.2012 28.01.2013 28.01.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 |