| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC69019 | Status: Closed |
OTM FAILED WITH SQL2032N DUE TO LEADING WHITE SPACES IN THE 'LOAD_MSGPATH' OPTION | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 | |
| Problem description: | |
The leading white spaces between the 'COPY_USE_LOAD,' and
'LOAD_MSGPATH' option should be removed when parsing the load
message path, or it will cause the SQL2032N error.
For example, moving the table with the following command will
fail:
db2 "call
sysproc.admin_move_table('TEST','TAB1','','COPY_USE_LOAD,
LOAD_MSGPATH \"/home/test/msgpath\"','MOVE'"
But the command runs successfully without the white spaces:
db2 "call
sysproc.admin_move_table('TEST','TAB1','','COPY_USE_LOAD,LOAD_MS
GPATH
\"/home/test/msgpath\"','MOVE'" | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of ADMIN_MOVE_TABLE * **************************************************************** * PROBLEM DESCRIPTION: * * See error description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.8 Fix Pack 4 * **************************************************************** | |
| Local Fix: | |
Removing the leading spaces in the 'LOAD_MSGPATH' option. | |
| available fix packs: | |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux | |
| Solution | |
Problem fixed in DB2 Version 9.8 Fix Pack 4 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.06.2010 29.07.2011 29.07.2011 |
| Problem solved at the following versions (IBM BugInfos) | |
9.8.FP4 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.8.0.4 |
|