home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC97547 Status: Closed

ADMIN_MOVE_TABLE DOES NOT PROVIDE CORRESPONDING LOAD OPTION "TEMPFILES
PATH"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fixpack 4.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in Version 101. Fixpack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.11.2013
16.06.2014
16.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList