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 IC95514 Status: Closed

SQL0108N returned when using ADMIN_CMD procedure to do table reorg with
temp tablespace option being specified

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Running the ADMIN_CMD procedure  for  table reorg with temp 
tablespace option 
The reorg  may failed with error : 
 
SQL0108N  The name "NM", T_00."XV3DT", T_" has the wrong number 
of qualifiers.  SQLSTATE=01H52 
 
This issue seen when running reorg using DBACOCKPIT  with temp 
tablespace flag on
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL DB2 VERSION 10.5 USERS                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* UPGRADE TO DB2 V10.5 FIXPACK 3                               * 
****************************************************************
Local Fix:
Run reorg without temp tablespace option.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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

Solution
Problem Fixed In DB2 V10.5 FIXPACK 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
28.04.2014
28.04.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList