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

DB2 query might produce SQL0901N with "SECTION LENGTH MISMATCH"

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
DB2 query might produce SQL0901N with "SECTION LENGTH MISMATCH" 
 
A diaglog entry similar to this will be produced: 
 
2013-02-12-10.30.47.848780-300 I4293495E852        LEVEL: Severe 
PID     : 14237                TID  : 140737010198272PROC 
:db2sysc 0 
INSTANCE: instname             NODE : 000          DB   : dbname 
APPHDL  : 0-502                APPID:  appid 
AUTHID  : authid EDUID   : 45                   EDUNAME: 
db2agent 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 23 
 sqlerrmc: Section length mismatch 
 sqlerrp : SQLRA01B 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3)0x00000000 
           (4) 0x00000000      (5) 0xFFFFFEA2      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
Stack Trace will show these functions: 
 
<StackTrace> 
sqlra_cache_fill_sec 
sqlra_find_sect 
sqlra_get_section 
sqlrr_sql_request_pre 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2FORLUW Version 9.7                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 query might produce SQL0901N with "SECTION LENGTH        * 
* MISMATCH"                                                    * 
*                                                              * 
* A diaglog entry similar to this will be produced:            * 
*                                                              * 
* 2013-02-12-10.30.47.848780-300 I4293495E852        LEVEL:    * 
* Severe                                                       * 
* PID     : 14237                TID  : 140737010198272PROC    * 
* :db2sysc 0                                                   * 
* INSTANCE: instname             NODE : 000          DB   :    * 
* dbname                                                       * 
* APPHDL  : 0-502                APPID:  appid                 * 
* AUTHID  : authid EDUID   : 45                   EDUNAME:     * 
* db2agent                                                     * 
* FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,      * 
* probe:300                                                    * 
* DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes                * 
*  sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901            * 
* sqlerrml: 23                                                 * 
*  sqlerrmc: Section length mismatch                           * 
*  sqlerrp : SQLRA01B                                          * 
*  sqlerrd : (1) 0x00000000      (2) 0x00000000                * 
* (3)0x00000000                                                * 
*            (4) 0x00000000      (5) 0xFFFFFEA2      (6)       * 
* 0x00000000                                                   * 
*  sqlwarn : (1)      (2)      (3)      (4)        (5)         * 
* (6)                                                          * 
*            (7)      (8)      (9)      (10)        (11)       * 
*  sqlstate:                                                   * 
*                                                              * 
* Stack Trace will show these functions:                       * 
*                                                              * 
* <StackTrace>                                                 * 
* sqlra_cache_fill_sec                                         * 
* sqlra_find_sect                                              * 
* sqlra_get_section                                            * 
* sqlrr_sql_request_pre                                        * 
* </StackTrace>                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP9                                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.02.2013
16.12.2013
16.12.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP9
Problem behoben lt. FixList in der Version
9.7.0.9 FixList
9.7.0.9 FixList