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

MESSAGE: "POSSIBLE MEMORY CORRUPTION" IN DB2DIAG.LOG WHEN USING
ADMIN_MOVE_TABLE()

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When using ADMIN_MOVE_TABLE() with  the following call: 
 
CALL SYSPROC.ADMIN_MOVE_TABLE('DB2ADMIN', 'TAB1','ACCOUNTING', 
'ACCOUNTING', 'ACCOUNTING','', '', '', '', 'KEEP, COPY_USE_LOAD 
COPY YES LOAD /usr/lib/libnsrdb2.so',  'MOVE') ; 
 
message: "Possible memory corruption detected" might show in 
db2diag.log: 
 
2013-03-22-13.44.45.262951+060 I2897E558           LEVEL: 
Warning 
LOADID: 340.2013-03-22-13.44.44.541534.0 (20;4) 
 
Starting LOAD phase at 22.03.2013 13:44:45.257677. Table 
DB2ADMIN.TAB1 
 
LOADID: 340.2013-03-22-13.44.44.541534.0 (20;4) 
 
Completed LOAD phase at 22.03.2013 13:44:46.771029. 
 
Completed BUILD phase at 22.03.2013 13:44:47.854045. 
 
2013-03-22-13.44.49.324395+060 I5050E1652          LEVEL: Severe 
 
PID     : 1194                 TID  : 46912557509984PROC : 
db2fmp ( 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
 
APPID   : 10.6.18.45.61945.130315082929 
 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, 
probe:10 
 
MESSAGE : Possible memory corruption detected. 
 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
 
0x820F0002 
 
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 
bytes 
0x00002aaab48ee128 
 
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
 
0x00002AAAB48EE110 : 0000 0000 0000 0000 4F00 0000 0100 0000 
 
........O....... 
 
0x00002AAAB48EE120 : 28E1 8EB4 AA2A 0000 
(....*.. 
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
 
0x00002AAAB48EE128 : 0000 0000 2F75 7372 2F6C 6962 2F6C 6962 
 
..../usr/lib/lib 
 
0x00002AAAB48EE138 : 6E73 7264 6232 2E73 6F00 0000 0000 0000 
 
nsrdb2.so....... 
 
0x00002AAAB48EE148 : 0000 0000 0000 0000 0000 0000 0000 0000 
 
................ 
 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
 
2013-03-22-13.44.49.423660+060 I6703E431           LEVEL: Severe 
 
PID     : 1194                 TID  : 46912557509984PROC : 
db2fmp ( 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
 
APPID   : 10.6.18.45.61945.130315082929 
 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, 
probe:50 
 
MESSAGE : Invalid memory block, unable to find associated pool. 
 
DATA #1 : Pointer, 8 bytes 
 
0x0000000000000000
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 10.5 Fix Pack 3                   * 
****************************************************************
Local-Fix:
No local fix available
verfügbare FixPacks:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 10.5 Fix Pack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.08.2013
27.02.2014
27.02.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.3 FixList
10.5.0.3 FixList