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

REORG TABLE USING THE LONGLOBDATA OPTION MAY RETURN "SQL2216N SQL
ERROR "-289"

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
REORG TABLE using the LONGLOBDATA option may exhaust all 
available data pages in the table's tablespace. The symptoms 
will also include a "SQL2216N  SQL error -289" and a message in 
db2diag.log which would like follows: 
 
2010-11-09-17.38.38.660474+060 E257310E1114        LEVEL: Error 
PID     : 13003                TID  : 140143897863936PROC : 
db2sysc 0 
INSTANCE: db2inst2             NODE : 000          DB   : 
TC_REORG 
APPHDL  : 0-17276              APPID: 
*LOCAL.db2inst2.101109163712 
AUTHID  : DB2INST2 
EDUID   : 215                  EDUNAME: db2agent (MYDB) 0 
FUNCTION: DB2 UDB, buffer pool services, sqlbAllocateExtent, 
probe:840 
 
MESSAGE : ADM6044E  The DMS table space "TBSPCE1" (ID "3") is 
full.  If this is 
          an autoresize or automatic storage DMS tablespace, the 
maximum table 
          space size may have been reached or the existing 
containers or 
          storage paths cannot grow any more. Additional space 
can be added to 
          the table space by either adding new containers or 
extending existing 
          ones using the ALTER TABLESPACE SQL statement. If this 
is an 
          autoresize or automatic storage DMS table space, 
additional space can 
          be added by adding containers to an autoresize table 
space or by 
          adding new storage paths to an automatic storage 
database.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all using LOB data                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see error description above                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* this issue will be addressed in a future release.            * 
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.01.2011
07.02.2011
07.02.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)