DB2 FOR LUW / DB2FORLUW / 970 - DB2

Each TRUNCATE command causes DB2 to write the following messages 
to the diagnostic log file: 
 
2010-06-23-15.16.32.958800+120                        LEVEL: 
Warning 
PID     : 15538                TID  : 47960297564480PROC : 
db2sysc 0 
INSTANCE: db2e72               NODE : 000          DB   : E72 
 
APPHDL  : 0-2091               APPID: 
AUTHID  : DB2E72 
 
EDUID   : 40                   EDUNAME: db2agent (E72) 0 
 
FUNCTION: DB2 UDB, data management, sqldBeginIndexCreate, 
probe:1 
MESSAGE : ADM5540W  Rebuilding "1" indexes on table "SCHEMA 
.TABLE". 
 
 
2010-06-23-15.16.32.959233+120                       LEVEL: 
Warning 
PID     : 15538                TID  : 47960297564480PROC : 
db2sysc 0 
INSTANCE: db2e72               NODE : 000          DB   : E72 
 
APPHDL  : 0-2091               APPID: 
AUTHID  : DB2E72 
 
EDUID   : 40                   EDUNAME: db2agent (E72) 0 
 
FUNCTION: DB2 UDB, data management, sqldIndexCreate, probe:1 
 
MESSAGE : ADM5541W  Rebuilding index with IID "1" in object with 
ID 
"161" and 
 
          table space ID "6" on table "SCHEMA  .TABLE". 
 
 
 
2010-06-23-15.16.32.981259+120                       LEVEL: 
Warning 
PID     : 15538                TID  : 47960297564480PROC : 
db2sysc 0 
INSTANCE: db2e72               NODE : 000          DB   : E72 
 
APPHDL  : 0-2091               APPID: 
AUTHID  : DB2E72 
 
EDUID   : 40                   EDUNAME: db2agent (E72) 0 
 
FUNCTION: DB2 UDB, data management, sqldEndIndexCreate, probe:1 
 
MESSAGE : ADM5542W  Indexes on table "SCHEMA  .TABLE" are 
successfully 
rebuilt. 
 
 
Execution of many TRUNCATE commands might quickly swamp entire 
log file, making further maintainability harder. Since the table 
is empty after TRUNCATE TABLE, the index recreate should be 
extremely fast so the user does not need to be warned about the 
index recreate making the system sub-optimal.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users are affected.                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Each TRUNCATE command causes a warning message in the DB2    * 
* diagnostics log file. Execution of many TRUNCATE commands    * 
* might quickly swamp entire log file, making further          * 
* maintainability harder. Since the table is empty after       * 
* TRUNCATE TABLE, the index recreate should be extremely fast  * 
* so it is not needed to produce warnings about the index      * 
* recreate making the system sub-optimal.                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 FP4.                              * 
****************************************************************

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Warning messages produced by TRUNCATE will be changed to 
informational ones and will appear only when the diagnostic 
level set to 4.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC73197 
Nachfolger : 

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

06.09.2010
28.04.2011
28.04.2011

9.7.FP4