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

Memory corruption causes instance trap in SQLYT_TRF_DEALLOC, SQLOFMBLKEX

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Memory corruption causes instance trap in sqlyt_trf_dealloc, 
sqlofmblkEx 
 
Sample call stack : 
DB2SYS64!sqloCrashOnCriticalMemoryValidationFailure+0x23 
DB2SYS64!sqlofmblkEx+0x558 
DB2STRUC!sqlyt_trf_dealloc+0x86 
DB2ENGN!sqlra_describe_static+0xc62 
DB2ENGN!sqlraDescribeOutput+0x25e 
DB2ENGN!sqlrr_sqldd+0xc7 
DB2ENGN!sqlrr_process_open_request+0x2b6 
DB2ENGN!sqlrr_open+0x197 
DB2APP64!csmOpen+0x8f
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Please see error description.                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10 Fixpak 2                                  * 
****************************************************************
Local Fix:
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
Problem first fix in v10 fixpak 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.07.2012
28.01.2013
28.01.2013
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