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 IC84321 Status: Geschlossen

DB2 ABEND WITH SIG11 FOR A SELECT WITH XML QUERIES

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
DB2 Abnormal Termination with Sig#11 may result from Xml queries 
with similar program error stack. 
 
The trap happens during XML Aggregation exit. 
 
select xmlelement(name "table", xmlattributes('xxx' as "name"), 
xmlconcat(xmlelement(name "types", xmlattributes('INT' as 
"ACCOUNT_ID", 'VARCHAR' as "SOR_IND",'VARCHAR' as "NICKNAME")), 
xmlagg(xmlrow(A.ACCOUNT_ID, TRIM(A.SOR_IND) AS SOR_IND, a.cust 
as cust, '' as "NICKNAME")))), xmlelement(name "table", 
xmlattributes('xxx' as "name"), mlconcat(xmlelement(name 
"types", xmlattributes('INT' as "ACCOUNT_ID", 'VARCHAR' as 
"SOR_IND", 'VARCHAR' as "NICKNAME")), 
xmlagg(xmlrow(A.ACCOUNT_ID, TRIM(A.SOR_IND) AS SOR_IND, a.cust 
as cust, '' as "NICKNAME")))), xmlelement(name "table", 
xmlattributes('xxx' as "name"), xmlconcat(xmlelement(name 
"types", xmlattributes('INT' as "ACCOUNT_ID", 'VARCHAR' as 
SOR_IND", 'VARCHAR' as "NICKNAME")), xmlagg(xmlrow(A.ACCOUNT_ID, 
TRIM(A.SOR_IND) AS SOR_IND, a.cust as cust, '' as 
"NICKNAME")))), xmlelement(name "table", xmlattributes('xxx' as 
"name"), xmlconcat(xmlelement(name "types", xmlattributes('INT' 
as "ACCOUNT_ID", 'VARCHAR' as "SOR_IND", 'VARCHAR' as 
"NICKNAME")), xmlagg(xmlrow(A.ACCOUNT_ID, TRIM(A.SOR_IND) AS 
SOR_IND, a.cust as cust, '' as "NICKNAME")))), xmlelement(name 
"table", xmlattributes('xxx' as "name"), 
xmlconcat(xmlelement(name "types", xmlat 
tributes('INT' as "ACCOUNT_ID", 'VARCHAR' as "SOR_IND", 
'VARCHAR' as "NICKNAME")), xmlagg(xmlrow(A.ACCOUNT_ID, 
TRIM(A.SOR_IND) AS SOR_IND, a.cust as cust, '' as "NICKNAME")))) 
from ty A 
 
-------Frame------ ------Function + Offset------ 
0x09000000068932C4 sqloCrashOnCriticalMemoryValidationFailure + 
0x34 
0x090000000689BCB0 
sqloCrashOnCriticalMemoryValidationFailure@glue6E8 + 0x78 
0x0900000009BB7B44 sqlofmblkEx + 0x4C 
0x09000000081EF008 
writeReferenceNode__19XmlrnSequenceWriterFUcR8XMLS_XIDT1UlT4T 
1PUcT1 + 0x1E0 
0x0900000006102FB4 
addItemSubtree__13XmlrnSequenceFP17xmlDataDescriptor + 0xB4C 
0x09000000066E2108 sqlriXAgg__FP8sqlrr_cb + 0x79C 
0x0900000009D1F504 sqlriagg__FP8sqlrr_cb + 0x1B8 
0x0900000009D2DB84 sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 
0x28 
0x0900000009E83844 
sqlrr_process_fetch_request__FP14db2UCinterface + 0x184 
0x0900000009CE2F10 
sqlrr_fetch__FP14db2UCinterfaceP15db2UCCursorInfo + 0x518 
0x0900000009CE292C 
sqljs_ddm_cntqry__FP14db2UCinterfaceP13sqljDDMObject + 0xAE4 
0x0900000009CEE308 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db 
2UCinterface + 0x148 
0x0900000009CEE71C 
.sqljsParse.fdpr.clone.77__FP13sqljsDrdaAsCbP14db2UCinterface 
P8sqeAgentb + 0x240
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW ALL                                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10 FP1 and newer release.                        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Upgrade to V10 FP1 and newer release.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
28.01.2013
28.01.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList