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

DB2 DATABASE SERVER RUNS OUT OF ENTRIES IN RESYNC LIST

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In a distributed unit of work (DUOW) environment, transactions 
which have been prepared but not yet committed are kept in a 
linked resync list. This list is used to recover from 
transaction commit or rollback failures due to network, 
hardware, or software failures. The resync list is stored in the 
resync heap with a fixed size, which is in the shared memory of 
the server. 
 
If there are a lot of outstanding DUOW transactions, DB2 
database server can run out of entries in Resync List during 
user activities or during crash recovery with the following 
message in db2diag.log: 
 
2011-09-23-15.08.39.785187-420 E1503306A441       LEVEL: Severe 
 
PID     : 758298               TID  : 110442      PROC : db2sysc 
0 
 
INSTANCE: test                NODE : 000         DB   : SAMPLE 
 
APPHDL  : 0-40210              APPID: 
 
USPCCW01.INA400.C86AD450D8A8 
 
AUTHID  : user 
 
EDUID   : 110442               EDUNAME: db2agent (SAMPLE) 0 
 
FUNCTION: DB2 UDB, base sys utilities, sqleAddEntryToResync, 
 
probe:20 
 
MESSAGE : Out of ResyncEntries! 
 
 
 
In case that crash recovery hits this symptom, crash recovery 
fails. In other cases, if APAR IC79235 has not been fixed yet, 
DB2 database server traps afterward, otherwise user's sql fails.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2                       * 
****************************************************************
Local Fix:
Increase NUMDB in DBM CFG, restart DB2 database server and 
restart database.
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
First fixed in Version 10.1 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.11.2012
31.12.2012
31.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList