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

In v10.1 Fixpack 6, the HADR Standby db diagpath can be flooded by
"sqlpshrEdu, probe:3100" messages

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Starting in v10.1 Fixpack 6, the Standby database db2diag.log
can be flooded with informational messages from function
"sqlpshrEdu, probe:3100", like so:

2017-05-15-10.15.18.746734+000 I379625383A504  LEVEL: Info
PID         : [pid]             TID : [tid]            PROC :
db2sysc 0
INSTANCE: [inst]            NODE : [node]     DB   : [name]
APPHDL  : [applhdl]        APPID: [appid]
AUTHID  : [authid]          HOSTNAME: [hostname]
EDUID    : [eduid]           EDUNAME: db2shred ([dbname]) 0
FUNCTION: DB2 UDB, recovery manager, sqlpshrEdu, probe:3100
DATA #1 : 
Stream 0: LFR scan out flags: 800, pages: 16


The problem is most prevalent in either of these situations:
- if a shared archive path is configured for Primary and Standby
  log archive method, and the Standby database is in 'Remote
  Catchup Pending' state reading log data.
- if the HADR log spooling feature is enabled, and the Standby
  database is reading spooled log data.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* diagpath can be flooded                                      *
* by "sqlpshrEdu, probe:3100" messages                         *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* apply a special build inclusive of this                      *
* APAR fix.                                                    *
****************************************************************
Local Fix:
Contact DB2 Support and apply a special build inclusive of this
APAR fix.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.05.2017
08.09.2017
08.09.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)