db2start fails with SQL10003 due to attaching the FMP memory set
to an invalid address on the Solaris 10 / Sparc T4 processor
combination with 2GB page size support. Solaris 10 update 4
(kernel patch 147440-04) enables 2GB pages by default.
The problem is due to an inconsistency in the way DB2 rounds up
shared segment sizes and then calculates the attach addresses of
"fixed address" segments. With 2GB page sizes available, DB2
tries to attach a shared memory segment at an address that is in
use by a previously attached segment. This is independent of
the actual backing page size used, it only matters what the
largest page size is determined to be available on the system
from the Solaris getpagesizes API.
expected db2diag.log messages:
2012-02-18-13.04.43.276604-360 I8210A728 LEVEL: Severe
PID : 17832 TID : 2 PROC : db2sysc
INSTANCE: db2inst2 NODE : 000
EDUID : 2 EDUNAME: db2sysc
FUNCTION: DB2 UDB, routine_infrastructure, sqlerInitFmpHeap,
probe:60
MESSAGE : Failed to create the memory segment used for
communication with
fenced routines. If re-starting db2, ensure no db2fmp
processes were
on the instance prior to start. Otherwise, you can
adjust this value
through DB2_FMP_COMM_HEAPSZ db2set value, or by
decreasing your
ASLHEAPSZ setting.
DATA #1 : Hexdump, 8 bytes
0xFFFFFFFF603FCDB8 : 0000 0000 015E 8480
.....^..
...
2012-02-18-13.04.43.278198-360 I9653A320 LEVEL: Severe
PID : 17832 TID : 2 PROC : db2sysc
INSTANCE: db2inst2 NODE : 000
EDUID : 2 EDUNAME: db2sysc
FUNCTION: DB2 UDB, oper system services, sqloWatchDogSetup,
probe:60
MESSAGE : ZRC=0xFFFFD8ED=-10003
...
2012-02-18-13.04.43.288489-360 I10469A906 LEVEL: Error
PID : 17827 TID : 2 PROC : db2wdog
0
INSTANCE: db2inst2 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:10
MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
memory addr"
DIA8561C A invalid memory block was encountered.
DATA #1 : Pointer, 8 bytes
0x0000000000000000 |
