home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC94634 Status: Geschlossen

THERE MIGHT BE A DOUBLE FREE OR LIST CORRUPTION IN THE SQLRLC_CSM_DEFUNCT()
FUNCTION

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The db2diag.log messages suggest that a db2agent process was 
trying to free a piece of memory that was freed during the 
execution of a stored procedure, which generated a Signal #11. 
 
The following are some example db2diag.log entries that might be 
produced if this problem occurs: 
 
2013-07-03-03.45.59.085998-240 I12279328E502   LEVEL: Severe 
PID     : 18886          TID : 46931736783168  PROC : db2sysc 0 
INSTANCE: db2inst1       NODE : 000            DB   : SAMPLE 
APPHDL  : 0-6894         APPID: 12.213.148.54.2064.130703071242 
AUTHID  : db2inst1       HOSTNAME: db2inst1_host 
EDUID   : 1063           EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:30 
DATA #1 : String, 12 bytes 
Double free. 
 
2013-07-03-03.45.59.277703-240 I12279831E603   LEVEL: Error 
PID     : 18886          TID : 46931736783168  PROC : db2sysc 0 
INSTANCE: db2inst1       NODE : 000            DB   : SAMPLE 
APPHDL  : 0-6894         APPID: 12.213.148.54.2065.130703071242 
AUTHID  : db2inst1       HOSTNAME: db2inst1_host 
EDUID   : 1063           EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, base sys utilities, sqleagnt_sigsegvh, 
probe:1 
MESSAGE : Error in agent servicing application with coor_node: 
DATA #1 : Hexdump, 2 bytes 
0x00002AAF2540F952 : 0000 
 
The following is an example of a trap file stack that might be 
produced if this problem occurs: 
 
<StackTrace> 
-----FUNC-ADDR---- 
ossDumpStackTraceV98 
OSSTrapFile::dumpEx 
sqlo_trce 
sqloEDUCodeTrapHandler 
__pthread_mutex_cond_lock 
sqloCrashOnCriticalMemoryValidationFailure 
sqlofmblkEx 
sqlrlc_csm_defunct 
sqlrlc_csm_processing 
sqlrlc_check_available_memory 
sqlrlc_auth_find_insert 
sqlrlc_rtn_get_auths 
sqlrlc_rtn_request_auths 
sqlrlgra 
sqlrlgad 
sqlrlFindProcedure 
sqlnq_resolve_procedure 
sqlnq_procedure_tresolve 
sqlnq_call_stmt 
sqlnp_smactn 
sqlnp_parser 
sqlnp_main 
sqlnn_cmpl 
sqlnn_cmpl 
sqlra_compile_var 
sqlra_find_var 
sqlra_get_var 
sqlrr_prepare 
sqljs_ddm_prpsqlstt 
sqljsParseRdbAccessed 
sqljsParse 
sqljsParseUowid 
sqljsWriteUowid 
sqljsParseCntqry 
sqljsDrdaAsDriver 
sqeAgent::RunEDU 
sqzEDUObj::EDUDriver 
sqlzRunEDU 
sqloEDUEntry 
pthread_create@@GLIBC_2.2.5 
clone
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.3.                             * 
****************************************************************
Local-Fix:
There is currently no local fix for this issue.
verfügbare FixPacks:
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

Lösung
The problem is first fixed in DB2 version 10.1.0.3.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC94890 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.08.2013
27.09.2013
27.09.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.11 FixList
10.1.0.3 FixList
10.1.0.3 FixList