shmget: [EEXIST][17]: key 52584801: shared memory already exists
Posted in 2004
Topics: Storage & Space Management, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration
Hi!
Guys please help!!!
I've tried everything with this shared memory segment(rebooted), but
nothing helped.
still doesn't want to do oninit -iv
here is some tips...
online.log
Tue Nov 30 15:20:02 2004
15:20:02 Event alarms enabled. ALARMPROG =
'/iif94/etc/alarmprogram.sh'
15:20:02 Booting Language <c> from module <>
15:20:02 Loading Module <CNULL>
15:20:02 Booting Language <builtin> from module <>
15:20:02 Loading Module <BUILTINNULL>
15:20:16 IBM Informix Dynamic Server Started.
15:20:16 shmget: [EEXIST][17]: key 52564801: shared memory alreadyexists
15:20:16 mt_shm_init: can't create resident segment
08:39:34 IBM Informix Dynamic Server Started.
08:39:34 shmget: [EEXIST][17]: key 52584801: shared memory alreadyexists
08:39:34 mt_shm_init: can't create resident segment
08:39:40 IBM Informix Dynamic Server Started.
08:39:40 shmget: [EEXIST][17]: key 52584801: shared memory alreadyexists
08:39:40 mt_shm_init: can't create resident segment
and onconfig file
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace nameROOTPATH /work/chunks/tester94/root_chunk # Path for device
containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 30000 # Size of root dbspace (Kbytes)
# Disk Mirroring Configuration Parameters
MIRROR 1 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH # Path for device containing mirroredroot
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)
# Physical Log Configuration
PHYSDBS rootdbs # Location (dbspace) of physical log
PHYSFILE 2000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 6 # Number of logical log files
LOGSIZE 2000 # Logical log size (Kbytes)
# Diagnostics
MSGPATH /iif94/online.log # System message log file path
CONSOLE /dev/console # System console message path
# To automatically backup logical logs, edit alarmprogram.sh and set
# BACKUPLOGS=Y
ALARMPROGRAM /iif94/etc/alarmprogram.sh # Alarm program path
TBLSPACE_STATS 1 # Maintain tblspace statistics
# System Archive Tape Device
TAPEDEV /dev/nul # Tape device path
TAPEBLK 32 # Tape block size (Kbytes)
TAPESIZE 10240 # Maximum amount of data to put on
tape (Kbytes)
# Log Archive Tape Device
LTAPEDEV /dev/nul # Log tape device path
LTAPEBLK 32 # Log tape block size (Kbytes)
LTAPESIZE 10240 # Max amount of data to put on log
tape (Kbytes)
# Optical
STAGEBLOB # Informix Dynamic Server staging area
# System Configuration
SERVERNUM 2 # Unique id corresponding to a OnLineinstance
DBSERVERNAME tester94 # Name of default database server
DBSERVERALIASES # List of alternate dbservernames
NETTYPE # Configure poll thread(s) for nettype
DEADLOCK_TIMEOUT 60 # Max time to wait of lock indistributed env.
RESIDENT 0 # Forced residency flag (Yes = 1, No =
0)
MULTIPROCESSOR 0 # 0 for single-processor, 1 formulti-processor
NUMCPUVPS 1 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vpsto one
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
LOCKS 2000 # Maximum number of locks
BUFFERS 5000 # Maximum number of shared buffers
NUMAIOVPS # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)
CLEANERS 1 # Number of buffer cleaner processes
SHMBASE 0x44000000L # Shared memory base address#SHMBASE 0x10000000L # Changed by Sergey Shumilov on
30/11/2004 to see if 9.4
# will be initialized because the
address
# of other versions is the same...
this one is different.
# or to change it to 0x20000000L at a
later time
# and see what happens.
SHMVIRTSIZE 81920 # initial virtual shared memorysegment size
SHMADD 8192 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes).
0=>unlimited
CKPTINTVL 300 # Check point interval (in sec)
LRUS 8 # Number of LRU queues
LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaninglimit
LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit
TXTIMEOUT 300 # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)
# Dynamic Logging
# DYNAMIC_LOGS:
# 2 : server automatically add a new logical log when necessary.
(ON)
# 1 : notify DBA to add new logical logs when necessary. (ON)
# 0 : cannot add logical log on the fly. (OFF)
#
# When dynamic logging is on, we can have higher values for
LTXHWM/LTXEHWM,
# because the server can add new logical logs during long transaction
rollback.
# However, to limit the number of new logical logs being added,
LTXHWM/LTXEHWM
# can be set to smaller values.
#
# If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller
values
# to avoid long transaction rollback hanging the server due to lack of
logical
# log space, i.e. 50/60 or lower.
DYNAMIC_LOGS 2
LTXHWM 70
LTXEHWM 80
if you need more info, please email me and I will send all the
information you need.
Thank you in advance
Sergey
Sergey wrote:
> Hi!
> Guys please help!!!
> [snip]
> 15:20:16 shmget: [EEXIST][17]: key 52564801: shared memory already
> [snip]> SERVERNUM 2 # Unique id corresponding to a OnLine
A couple of things I check when I see this:
1) Do "ipcs". If there are no other IDS instances up then you probably
should not see anything owned by informix (well I don't on our
machines.) If there are entries, and they have a KEY of 0x52564801, then
you could remove them with "ipcrm".
2) Are you sure there are no other instances running with SERVERNUM of
2. If you are doing an "oninit -iy", did you perhaps nick the onconfig
from another instance as a template? ;-)
Hope this helps,
Donny
Donny wrote:
> Sergey wrote:
>
>> Hi!
>> Guys please help!!!
>> [snip]
>> 15:20:16 shmget: [EEXIST][17]: key 52564801: shared memory already
>> [snip]>> SERVERNUM 2 # Unique id corresponding to a OnLine>
>
> A couple of things I check when I see this:
>
> 1) Do "ipcs". If there are no other IDS instances up then you probably
> should not see anything owned by informix (well I don't on our
> machines.) If there are entries, and they have a KEY of 0x52564801, then
> you could remove them with "ipcrm".
>
> 2) Are you sure there are no other instances running with SERVERNUM of
> 2. If you are doing an "oninit -iy", did you perhaps nick the onconfig
> from another instance as a template? ;-)
>
> Hope this helps,
> Donny
Provide the output from ipcs -m
or (rocket science this one)
Try changing the SERVERNUM to 251 :O