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

DB2ROCM CONSTANTLY CREATES DUMP FILES WHEN THE MEMBER IS STOPPED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
db2dump folder is flooded with SQLHA.events.bin dumps. The
following is repeatedly logged in db2diag.log:
 LEVEL: Event
PID     : 1234567             TID : 1              PROC :
db2rocm 1 [db2inst1]
INSTANCE: db2inst1             NODE : 001
HOSTNAME: host1
EDUID   : 1                    EDUNAME: db2rocm 1 [db2inst1]
FUNCTION: DB2 UDB, high avail services,
sqlhaEventRecorder::HaErDumpEvents, probe:314
DATA #1 : String, 56 bytes
binary event file successfully dumped ( path, recorder )
DATA #2 : String, 108 bytes
/home/db2inst1/sqllib/db2dump/DIAG0001//2017-01-01-01.01.01.1234
567.DB2ROCM.1234567.SQLHA.events.bin
DATA #3 : String, 7 bytes
DB2ROCM
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 10.5 Fix Pack 10 or higher                    *
****************************************************************
Local Fix:
Starting db2 instance then stop to prevent these dump files from
being generated
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT24355 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.07.2017
19.07.2018
19.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)