home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC89712 Status: Closed

FENCED WRAPPER GETS HANG SPORADICALLY AFTER -1131 ERROR

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Fenced wrapper may get hang sporadically after a -1131 error in 
db2diag.log. For this problem, only the specific query hang and 
anything else ran fine on the server at the same time. 
 
You will see following error messages from db2diag.log: 
 
2012-09-29-02.44.53.139002-240 I1951E322           LEVEL: Severe 
PID     : 19415                TID  : 139708008859408PROC : 
db2fmp ( 
INSTANCE: db2inst1              NODE : 000 
APPID   : 9.26.121.169.48208.120929064451 
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFedFmpListener, 
probe:20 
RETCODE : ZRC=0xFFFFFB95=-1131 
 
2012-09-29-02.44.53.139333-240 I2274E454           LEVEL: 
Warning 
PID     : 19415                TID  : 139708008859408PROC : 
db2fmp ( 
INSTANCE: db2inst1              NODE : 000 
APPID   : 9.26.121.169.48208.120929064451 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
logging func, probe:0 
MESSAGE : Thread of db2fmp terminated with nonzero rc 
DATA #1 : Hexdump, 4 bytes 
0x00007F104E3D7E84 : 95FB FFFF 
.... 
 
2012-09-29-02.44.53.170265-240 I2729E373           LEVEL: Error 
PID     : 19415                TID  : 139708008859408PROC : 
db2fmp ( 
INSTANCE: db2inst1              NODE : 000 
FUNCTION: DB2 UDB, drda wrapper, 
FencedDRDA_Server::get_diagnostic, probe:10 
MESSAGE : DiagRec han_type 
DATA #1 : Hexdump, 2 bytes 
0x00007F104E3D7158 : 0300 
.. 
 
The problem was introduced in v97 fix pack 5 by APAR IC76273, so 
you should not have this problem in v97 fix pack 4 or earlier.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The users are running DRDA wrapper when ASLHEAPSZ is set to  * 
* a value less than 17.                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 and Fix Pack 3.                  * 
****************************************************************
Local Fix:
Set ASLHEAPSZ to a value no less than 17 and recycle db2 server.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 Version 10.1 and Fix Pack 3.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC96601 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.01.2013
03.10.2013
03.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList