DB2 - Problem description
Problem IC86001 | Status: Closed |
ADM5530W MESSAGES LOGGED INTO THE DB2DIAG.LOG MULTIPLE TIMES FOR A RANGE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If a range partiton table is altered, to be "NOT LOGGED INITIALLY", and then data is loaded into it, at EACH commit, DB2 will dump the following messages in the db2diag.log: 2012-08-08-18.39.27.377776+060 E1935718340A657 LEVEL: Warning PID : 13893634 TID : 40714 PROC : db2sysc 1 INSTANCE: db2inst1 NODE : 001 DB : SAMPLE APPHDL : 0-20981 APPID: *N0.linfi01.120808133640 AUTHID : DB2INST1 EDUID : 40714 EDUNAME: db2agnta (SAMPLE) 1 FUNCTION: DB2 UDB, data management, sqldEndNoLogList, probe:1 MESSAGE : ADM5530W The COMMIT processing of table "DB2INST1. .TAB_RANGE" that used NOT LOGGED INITIALLY has been initiated. It is recommended that you take a backup of this table's table space(s). If the range partition table is in a dpf setup, these messages are logged, ( number of database partition ) x ( number of range partion ) times. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users on V97fp7 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V97fp8 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
Fixed in V97Fp8 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.08.2012 02.04.2013 02.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |
![]() |