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

ADMIN_MOVE_TABLE DOES NOT PROVIDE CORRESPONDING LOAD OPTION "TEMPFILES
PATH"

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Current usage of ADMIN_MOVE_TABLE does not provide corresponding 
TEMPFILES PATH option which is used in load utility and 
admin_cmd load procedure. 
 
ex) 
$ db2 "call 
admin_move_table('AMT','ORDER','TS1','TS1','TS1','','','','','CO 
PY_USE_LOAD MESSAGES ON SERVER TEMPFILES PATH /tmp','COPY')" 
SQL0104N  An unexpected token "TEMPFILES" was found following 
"NO".  Expected 
tokens may include:  "COPY".  SQLSTATE=42601 
 
This restricts users to specify path where load temporary files 
are saved.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fixpack 4.                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First fixed in Version 10.5 Fixpack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.11.2013
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList