More recent Linux distributions have newer defaults(4GB) on
virtual memory (and other) resource limits, it is 80% of
RAM+swap. This makes the password checking daemons to fail to
attach shared memory particularly when FCM over allocates shared
memory.
db2start command would fail with the following symptom.
05/02/2011 06:30:33 0 0 SQL1042C An unexpected system
error occurred.
05/02/2011 06:30:33 1 0 SQL1042C An unexpected system
error occurred.
SQL1032N No start database manager command was issued.
SQLSTATE=57019
diag.log would contain something like below,
2011-05-02-06.29.33.729607-240 E13553E825 LEVEL:
Error
PID : 8547 TID : 140736813065984PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 12 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager,
sqlkf_init_allocate_shared, probe:121
DATA #1 : <preformatted>
Allocated FCM shared memory.
Required size: 226922980 bytes
Total shared memory needed: 226922980 bytes
Total shared memory needed for FCM control structures:
64111072
bytes
Total shared memory needed for FCM buffers: 85639168
bytes
Total shared memory needed for FCM channels: 19931136
bytes
Total shared memory needed for FCM sessions: 9527296
bytes
Current FCM resources configuration (for 2 logical and 2
failover
partitions):
buffers: 17900
channels: 10740
sessions (internal): 1790
2011-05-02-06.29.33.729801-240 I14379E344 LEVEL:
Error
PID : 8547 TID : 140736813065984PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000
EDUID : 12 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, fast comm manager,
sqlkf_init_allocate_shared, probe:122
DATA #1 : Codepath, 8 bytes
14:16:22:24
2011-05-02-06.29.33.759528-240 I14724E874 LEVEL:
Severe (OS)
PID : 8542 TID : 140736813065984PROC :
db2wdog 0
[db2inst1]
INSTANCE: db2inst1 NODE : 000
EDUID : 2 EDUNAME: db2wdog 0 [db2inst1]
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:180
MESSAGE : ZRC=0x850F00C4=-2062614332=SQLO_ADDR_CONFLICT
"An address space conflict was detected attaching to
shared
memory."
CALLED : OS, -, shmat OSERR: ENOMEM
(12)
DATA #1 : Memory set handle, PD_TYPE_OSS_MEM_SET_HDL, 48 bytes
0x00007FFFD7BFD750 : 0000 0020 0200 0000 0000 0020 0200
0000 ... ....... ....
0x00007FFFD7BFD760 : 0000 0000 0000 0000 0000 0000 0000
0000 ................
0x00007FFFD7BFD770 : 0000 F90F 0000 0000 0480 0600 0B00
0000 ................
DATA #2 : Pointer, 8 bytes
0x0000000220000000
2011-05-02-06.29.34.563621-240 I15599E854 LEVEL:
Severe (OS)
PID : 8548 TID : 140736813065984PROC :
db2ckpwd 0
INSTANCE: db2inst1 NODE : 000
EDUID : 1 EDUNAME: db2ckpwd 0
FUNCTION: DB2 UDB, SQO Memory Management, sqlocshr, probe:180
MESSAGE : ZRC=0x850F00C4=-2062614332=SQLO_ADDR_CONFLICT
"An address space conflict was detected attaching to
shared
memory."
CALLED : OS, -, shmat OSERR: ENOMEM
(12)
DATA #1 : Memory set handle, PD_TYPE_OSS_MEM_SET_HDL, 48 bytes
0x0000000200011F20 : 0000 0020 0200 0000 0000 0020 0200
0000 ... ....... ....
0x0000000200011F30 : 0000 0000 0000 0000 0000 0000 0000
0000 ................
0x0000000200011F40 : 0000 F90F 0000 0000 0480 0600 0B00
0000 ................
DATA #2 : Pointer, 8 bytes
0x0000000220000000 |
