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

INCORRECT ERROR LEVEL MESSAGE IS WRITTEN IN DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Incorrect Error level message for sqlplGetLockWaitInfo function
is written in db2diag.log.  It should be logged as
informational.
It just indications data has changed during snapshot monitoring.
It can be safely ignored.

2019-09-05-00.20.54.416404+540 E2188E594            LEVEL: Error
PID     : 56736                TID : 70349831991648 PROC :
db2sysc 0
INSTANCE: i1h102               NODE : 000           DB   :
APPHDL  : 0-10842              APPID: *N0.i1h102.191012073522
AUTHID  : I1H102               HOSTNAME: j4h00303
EDUID   : 43971                EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, lock manager, sqlplGetLockWaitInfo, probe:519
DATA #1 : 
DEBUG: catch error in
sqlplGetLockWaitInfo()agtCB_waiter->dpsAgentCB =
0x00003ffc1c100940 while dpsAgentCB = 0x0000000000000000
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.09.2019
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)