|
Problem IT19905
|
Status: Closed |
BACKGROUND DAEMONS MIGHT NOT START JUST AFTER TAKEOVER HADR DUE TO TIMING HOLE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Background daemons like db2wlmd, db2taskd might not start just
after takeover HADR.
There might be small timing hole to allow new connection before
all the internal takeover state has been cleared.
Users can see the following error if such connection takes
metrics before starting db2wlmd.
2016-01-27-12.15.32.062250+540 I99673A647 LEVEL: Error
PID : 35651692 TID : 6486 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-41260 APPID:
*LOCAL.db2inst1.160127031615
AUTHID : db2inst1 HOSTNAME: irita
EDUID : 6486 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, WLM,
sqlrwWlmStatsCollectionServices::requestWlmStatsCo, probe:20
RETCODE : ZRC=0x870000CD=-2030042931=SQLZ_RC_UNEXPECTED_SYSERR
"Unexpected System Error"
DATA #1 : String, 66 bytes
WLW stats collector not started. Unable to force stats
collection.
This APAR will change the return code from SYSTEM ERROR to
SQL1632W. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
Please ignore the error. Background agents will be started by
subsequent connection. |
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.03.2017
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
