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

DB2 MAY TRAP IN FUNCTION SQLRA_DBMON_STMT_RELEASE DURING HADR TAKE OVER.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DB2 may trap in function sqlra_dbmon_stmt_release during hadr 
take over. 
 
 
The trap file will contain the following callstack: 
sqlra_dbmon_stmt_release 
termFastWriterQueueMgr 
termFastWriterManager 
hdrTakeover2Secondary 
hdrTransition 
hdrPDoTakeover 
hdrEdu 
hdrEduEntry 
sqloEDUEntry
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platform                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade DB2 V101 FP1                                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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
DB2 V101 FP1 will contain the fix.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
14.11.2012
14.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList