home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC91694 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 Fix Pack 9                    * 
****************************************************************
Local Fix:
No local fix available
available fix packs:
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

Solution
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95513 IC97828 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.04.2013
23.12.2013
23.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList