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

TIMING ISSUE ON THE CF LEADS TO FODC MEMBER WHEN A MEMBER TRIES TO CLEAN A
CONNECTION TO THE CF

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
A member can purge a connection , send a connection kill to the 
CF and then query the connection kill to check if it's done. 
Due to some timing issue on the CF the CF can create a new 
connection with the same ID as the one we query and 
then keep returning CA_MGMNT_QUERY_CMD_BLOCKED as if the kill 
did not complete. This leads to FODC of member after 6 minutes. 
 
577160 2016-06-15-20.09.23.747081+540 E27785817A3919 
LEVEL: Error 
   577161 PID     : 42533856             TID : 437569 
PROC : db2sysc 1 
   577162 INSTANCE: db2instance       NODE : 001           DB 
: DB 
a> 577163 APPHDL  : 1-39527              APPID: 
42.1.231.28.51232.160603090718 
   577164 AUTHID  : auth                   HOSTNAME: hostname 
   577165 EDUID   : 437569               EDUNAME: db2agent (DB) 
1 
   577166 FUNCTION: DB2 UDB, Shared Data Structure Abstraction 
Layer for CF, 
SAL_MANAGEMENT_PORT_HANDLE::SAL_ManagementQueryKillConnection, 
probe:12464 
   577167 MESSAGE : ECF=0x94C6004D=-1798963123 
   577168 DATA #1 : CF RC, PD_TYPE_SD_CF_RC, 4 bytes 
   577169 2147876941 
   577170 DATA #2 : CF Response Structure, 
PD_TYPE_SD_CFRESPONSE, 424 bytes 
   577171 API Response Code = 2147876941 
   577172 Model Code = 6 
   577173 Response Code = 128 
   577174 Exception Code = 0 
   577175 SID = 0 
   577176 API ID = 160 
   577177 Line Number = 0 
   577178 Description = API Function: 160 (PsWorkerPurge), 
   577179 Structure ID (SID): 0 (Unknown Name), 
   577180 Model Code: 6 (Management), Command Code: 196 (0xc4) 
(***Undefined***) 
   577181 Return Code: Severity = 0x8 (Error), Component = 6 
(svr_mgmnt [Management]), Error = 77 (0x4d) 
   577182 Error Name = CA_MGMNT_QUERY_CMD_BLOCKED 
   577183 API Return Code: 0x8006004d, 
   577184 CA Response Code: 128 (***Undefined***) 
   577185 Status Conditions: 
   577186     5: Incorrect facility state 
   577187     6: Allocation incomplete 
   577188    17: ***Undefined*** 
   577189    20: Fencing failure 
   577190    21: ***Undefined*** 
   577191    23: Facility damage 
   577192 DATA #3 : management port state for connection to a 
single physical CF, PD_TYPE_SAL_MANAGEMENT_PORT_HANDLE, 88 bytes 
   577193 m_mgmntPortToken  = 0x111EA12D0 
   577194 m_mgmntPortNumber = 56000 
   577195 m_caNodeNum       = 129 
   577196 m_szHostname      = eccfap02 
   577197 m_ErrorFromOpenIfFailed = 0x0 
   577198 CALLSTCK: (Static functions may not be resolved 
correctly, as they are resolved to the nearest symbol) 
   577199   [0] 0x090000003A785160 
sqleSingleCaPurgeConnection__21SQLE_SINGLE_CA_HANDLEFCPP18SQLE_C 
A_CONN_ENTRY + 0x294 
   577200   [1] 0x090000003A78327C 
sqleSingleCaPurgeConnection__21SQLE_SINGLE_CA_HANDLEFCPP18SQLE_C 
A_CONN_ENTRY + 0x564 
   577201   [2] 0x090000003A786060 
SAL_ReplaceOrPurgeConnections__17SAL_CA_CONNECTIONFRCUi + 0xB8
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fix Pack 8                               * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 10.5 Fix Pack 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.07.2016
13.03.2017
13.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)