DB2 FOR LUW / DB2FORLUW / A50 - DB2

Automatic reorg will return following errors in the db2diag.log: 
 
2013-06-26-01.00.01.149619+120 I3779E669           LEVEL: Error 
PID     : 4132                 TID  : 139923044009728PROC : 
db2acd 0 
INSTANCE: db2v977              NODE : 000 
FUNCTION: DB2 UDB, Automatic Table Maintenance, 
db2AutoReorgExec, probe:190 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 2220   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : db2Reorg 
 sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
2013-06-26-01.00.01.149779+120 I4449E342           LEVEL: Event 
PID     : 4132                 TID  : 139923044009728PROC : 
db2acd 0 
INSTANCE: db2v977              NODE : 000 
FUNCTION: DB2 UDB, Automatic Table Maintenance, 
db2AutoReorgExec, probe:10 
STOP    : Automatic reorg has completed with errors on table 
SAMPLE  ."DB2V977 "."TESTTAB" 
 
 
To hit the above errors following conditions need to be met: 
 
- table is a compressed table (CREATE TABLE ... COMPRESS YES) 
- automatic reorg policy uses option dictionaryOption="Rebuild" 
- table data has been deleted 
 
With the above conditions being true the table will be marked 
for a reorg. DB2 automatic reorg will attempt to reorganize the 
table and starts a REORG. 
Due to table being empty the REORG will fail to build a new 
compression dictionary and return warning SQL2220. The table 
reorganization as such will be successful only the dictionary 
rebuilt could not be performed. 
 
Automatic reorg does treat the warning as error and prints the 
db2diag.log messages.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to 10.5.0.3                                           * 
****************************************************************

You should execute a manual runstats against such a table to 
reflect the current state after the messages are seen in the 
db2diag.log. This will ensure the table is no longer in need for 
reorg and prevent it from being considered in the next automatic 
reorg window.

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
 

Problem Fixed In 10.5.0.3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

27.08.2013
28.02.2014
28.02.2014