Technical Blog Post
Abstract
Many 'sqlpshrScanClose, probe:90444' db2diag.log message on v11.1m3fp3 and v11.1m3if1
Body
Symptom
If you are using v11.1m3fp3 and v11.1m3if1, you might have lots of the following error message in your db2diag.log
2019-04-07-15.17.39.594893+480 I24726862E574 LEVEL: Error
PID : 6975 TID : 47284876207872 PROC : db2sysc 0
INSTANCE: xxxxxxx NODE : 000 DB : XX
APPHDL : 0-37450 APPID: xxx.xxx.xxx.xxx.xxxxx.xxxxxxxxxxx
AUTHID : xxxxxx HOSTNAME: xxxxx
EDUID : 250 EDUNAME: db2agent (XX) 0
FUNCTION: DB2 UDB, recovery manager, sqlpshrScanClose, probe:90444
DATA #1 : Boolean, 1 bytes
false
DATA #2 : Pointer, 8 bytes
0x00002affcedfb020
DATA #3 : Pointer, 8 bytes
0x00002affcde645a0
Cause
This is the false error message so you can ignore this message.
Resolution
This issue is fixed in v111m3if2 and v11.1m4fp4 code base internally.
Therefore you can upgrade to those if you don't want to see this message in db2diag.log.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
UID
ibm13285849