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

MESSAGE PDRECOVERY, PROBE:10 AND PROBE:20 IS LOGGED WITH EACH DIAGEVEL

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Command "db2pd -d  -recovery" always logs the following
db2diag.log messages, no matter about the DIAGLEVEL:

2019-10-24-10.37.06.839695-240 I2420A313            LEVEL: Event
PID     : 20251218             TID : 1              PROC : db2pd
INSTANCE: vspr                 NODE : 000
HOSTNAME: hostname
EDUID   : 1
FUNCTION: DB2 UDB, RAS/PD component, pdRecovery, probe:10
START   : db2pd -recovery started

2019-10-24-10.37.06.841166-240 I2734A314            LEVEL: Event
PID     : 20251218             TID : 1              PROC : db2pd
INSTANCE: vspr                 NODE : 000
HOSTNAME: hostname
EDUID   : 1
FUNCTION: DB2 UDB, RAS/PD component, pdRecovery, probe:20
STOP    : db2pd -recovery finished
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5 m3 fp0 or later                          *
****************************************************************
Local Fix:
Use the -nolog command option like

"db2pd -nolog -db  -recovery"
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.11.2019
24.04.2020
24.04.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)