A severe diagnostic message with the function
"sqloMemDetachFromSegments" may be logged to the db2diag.log
unnecessarily by the db2rocm process when using the DB2
pureScale feature. The error is related to a harmless expected
condition and will be removed.
db2diag.log example:
2011-11-29-19.43.55.384847+540 I2751121A1425 LEVEL:
Severe (OS)
PID : 21758068 TID : 1 PROC :
db2rocm 2 [db2inst]
INSTANCE: db2inst NODE : 002
HOSTNAME: host1
EDUID : 1 EDUNAME: db2rocm 2 [db2inst1]
FUNCTION: DB2 UDB, SQO Memory Management,
sqloMemDetachFromSegments, probe:100
MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
memory addr"
DIA8561C A invalid memory block was encountered.
CALLED : OS, -, shmdt
OSERR : EINVAL (22) "Invalid argument"
DATA #1 : unsigned integer, 8 bytes
0
DATA #2 : unsigned integer, 8 bytes
1
DATA #3 : Pointer, 8 bytes
0x0a00040000000000
CALLSTCK:
[0] 0x090000000566BF20 pdLogSysRC@glue45B + 0x11C
[1] 0x0900000005431320
@84@sqloMemDetachFromSegments__FPCvCUlCb + 0xA0
[2] 0x090000000566DA98
sqloMemDetachFromSegments__FPCvCUlCb@glue52A + 0x78
[3] 0x09000000054328AC
@84@sqloMemDetachFromSharedMemory__FCP12SQLO_MEM_SETCbT2 + 0xA4
[4] 0x090000000B3C3348 sqlodshr + 0x148
[5] 0x00000001000093E4
sqlhaDbmsDetach__FPA85_lP18SQLHA_SHMEM_HANDLE + 0x1E4
[6] 0x000000010000DFC0
sqlhaMonitorPartition__FsUlP23SQLO_PGRP_FILE_CONTENTS + 0x1C0
[7] 0x000000010000FA44
sqlhaMonitorPartitionAndLog__FsUlP23SQLO_PGRP_FILE_CONTENTS26_sq
lhaExpectedMonitorState + 0x284
[8] 0x0000000100007828 rocmDB2Monitor + 0x48
[9] 0x0000000100002C64 main + 0x1284
[10] 0x0000000100000320 __start + 0x98
2011-11-29-19.43.55.819036+540 I2752547A1763 LEVEL: Error
PID : 21758068 TID : 1 PROC :
db2rocm 2 [db2inst1]
INSTANCE: db2inst1 NODE : 002
HOSTNAME: host1
EDUID : 1 EDUNAME: db2rocm 2 [db2inst1]
FUNCTION: DB2 UDB, SQO Memory Management,
sqloMemDetachFromSharedMemory, probe:220
MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
memory addr"
DIA8561C A invalid memory block was encountered.
DATA #1 : Memory set handle, PD_TYPE_OSS_MEM_SET_HDL, 48 bytes
0x0FFFFFFFFFFFD798 : 0780 0000 0000 0000 0780 0000 0000 0000
................
0x0FFFFFFFFFFFD7A8 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0FFFFFFFFFFFD7B8 : 0000 0000 0A2E 0000 0180 001A 0000 0002
................
DATA #2 : Chunk group, PD_TYPE_CHUNK_GROUP, 64 bytes
0x0780000000001E48 : 0000 0000 0000 0000 0780 0000 0000 1E08
................
0x0780000000001E58 : 0A00 0400 0000 0000 07F0 001E 0000 0000
................
0x0780000000001E68 : 0080 2044 0000 0007 0000 0007 0000 0001
.. D............
0x0780000000001E78 : 0780 0000 0000 0000 0780 0000 0000 02C0
................
CALLSTCK:
[0] 0x090000000B063170 pdLog@glue663 + 0xD4
[1] 0x09000000054328E0
@84@sqloMemDetachFromSharedMemory__FCP12SQLO_MEM_SETCbT2 + 0xD8
[2] 0x090000000B3C3348 sqlodshr + 0x148
[3] 0x00000001000093E4
sqlhaDbmsDetach__FPA85_lP18SQLHA_SHMEM_HANDLE + 0x1E4
[4] 0x000000010000DFC0
sqlhaMonitorPartition__FsUlP23SQLO_PGRP_FILE_CONTENTS + 0x1C0
[5] 0x000000010000FA44
sqlhaMonitorPartitionAndLog__FsUlP23SQLO_PGRP_FILE_CONTENTS26_sq
lhaExpectedMonitorState + 0x284
[6] 0x0000000100007828 rocmDB2Monitor + 0x48
[7] 0x0000000100002C64 main + 0x1284
[8] 0x0000000100000320 __start + 0x98 |
