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

DB2 DUMP FILE SIZE IS GETTING BIGGER WHEN REPEATING SAME WARNINGMESSAGE IN
LOG RETRIEVING

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When log retrieving warning message repeats with hitting max
retrieveArray size,
DUMP information is appended to a dump file and it's getting
bigger.
Ever increasing of dump file size can trigger the relevant file
system full condition.

Following is the db2diag.log pattern with generating dump
information.

...

EDUID   : XXXX                EDUNAME: db2lfr.0 (DBNAME) 0
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveStartUse, probe:190
DATA #1 : 
WARNING: No room for retrieved log number 13365 in
retrieveArray. Index 18446744073709551615 entryCount 264
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)

...

PID:29521 TID:140728323794688 NODE:000 Title: SQLP_DBCB
Dump File:/aaa/db2dump/29521.25550.000.dump.bin

...

2015-12-14-23.01.48.329366+480 I10454441E190      LEVEL: Warning
PID:29521 TID:140728323794688 NODE:000 Title: SQLP_LFPB
Dump File:/aaa/db2dump/29521.25550.000.dump.bin
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher               *
****************************************************************
Local Fix:
1. Delete the dump file under the risk of file system full
2. To reset retrieveCount, deactivate and activate the database.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT17870 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.10.2017
24.10.2017
24.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)