|
Problem IT17909
|
Status: Closed |
DB2 COMMANDS AND CONNECTION ATTEMPT HANG WHEN CF SCA STRUCTURE MEMORY IS FULL |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
DB2 commands and connection attempt can be hung when CF SCA
structure memory is full.
An agent calling SAL_WriteAndRegister went into sleep without
finishing the call completely.
This may impact to other agents to wait for latches that this
agent holds.
db2diag log pattern :
EDUID : XXXXX EDUNAME: db2agent (DBNAME_CA0) 0
FUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for
CF,
SAL_GBP_HANDLE::SAL_WriteAndRegister, probe:25126
MESSAGE :
ZRC=0x852700A1=-2061041503=SQLE_SAL_CACHE_STOCLASS_FULL
"CF CA_CACHE_WAR_STOCLASS_FULL or
CA_CACHE_WARM_STOCLASS_FULL error."
DATA #1 : String, 43 bytes
Giving up retries due to out of SCA memory.
Relevant stack pattern :
_p_nsleep
nsleep
nanosleep
ossSleep
sqlorest
SAL_WriteAndRegister
sqleSCAWrite
sqlpWriteXaTranToSCA
.... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.11.2016
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
