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

CRASH IN SQLRAGSN WHEN PRINTING PROBE 1400

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
DB2 can crash with the following stack: 
 
0        ossHexDumpLine 
1        ossHexDumpToBuffer 
2        pdHexDump 
3        pdFormatArg 
4        pdInvokeFmtFnc 
5        formatPDType 
6        pdTypeFormatOrDump 
7        pdLogInternal 
8        pdLog 
9        sqlragsn 
10       sqlrr_sql_request_pre 
11       sqlrr_prepare 
12       sqljs_ddm_prpsqlstt 
13       sqljsParseRdbAccessed 
14       sqljsParse 
15       sqljsSqlam 
16       sqljsDriveRequests 
17       sqljsDrdaAsInnerDriver 
18       sqljsDrdaAsDriver 
19       sqeAgent::RunEDU 
20       sqlzRunEDU 
21       sqloEDUEntry 
 
The last message before the crash in the db2diag.log is on 
sqlragsn, probe 1350 
 
FUNCTION: DB2 UDB, access plan manager, sqlragsn, probe:1350 
MESSAGE : cannot prepare a non-dynamic section for section 14. 
DATA #1 : Hexdump, 8 bytes 
0xFFFFFFFF643B3E58 : 4E55 4C4C 4944 2020 
NULLID 
 
There is no message in the db2diag.log after this with sqlragsn, 
probe 1400 for the same EDUID. 
 
If we did not crash we would have after the message above: 
 
FUNCTION: DB2 UDB, access plan manager, sqlragsn, probe:1400 
MESSAGE : cannot prepare a non-dynamic section for section 14. 
DATA #1 : Hexdump, 128 bytes 
0xFFFFFFFF611AFFBC : 5351 4C55 4648 3133 2020 2020 2020 2020 
SQLUFH13 
0xFFFFFFFF611AFFCC : 2020 4141 4141 4159 4758 000E FFFF FFFF 
 AAAAAYGX...... 
 
Note the Hexdump might vary. 
 
We will only hit this crash as a result of hitting -804 
(SQL0804N), reason code 100.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* We are hitting a memory boundary with the package name that  * 
* we are trying to print.                                      * 
*                                                              * 
* Signal #11 (SIGSEGV): si_addr is 0xFFFFFFFF63B00000, si_code * 
* is 0x00000001 (SEGV_MAPERR:Address not mapped to object.)    * 
*                                                              * 
* The trap file will show for the address that we are failing  * 
* on that it is a memory boundary:                             * 
* <ProcessObjects>                                             * 
* 0xffffffff63a00000-0xffffffff63b00000      1024K rw--  [     * 
* anon ]                                                       * 
*                                                              * 
* This is a rare condition. The problem is due to not passing  * 
* the package name length to the function sqlragsn and using a * 
* standard size to print the package name.                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.5 and Fix Pack 6                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 Version 9.5 and Fix Pack 6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC75455 IC75503 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
31.03.2011
27.06.2011
27.06.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version
9.5.0.8 FixList