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 IC69019 Status: Geschlossen

OTM FAILED WITH SQL2032N DUE TO LEADING WHITE SPACES IN THE
'LOAD_MSGPATH' OPTION

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Lösung
Problem fixed in DB2 Version 9.8 Fix Pack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.06.2010
29.07.2011
29.07.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP4
Problem behoben lt. FixList in der Version
9.8.0.4 FixList