RE: shmget: [EEXIST][17]: key 52584801: shared memory already exists

Hi Sergey. Make sure your configration parameter. . Kernel Parameters The values of the kernel parameters that were used for testing this product are given below. These values might need to be tuned depending on the application and availability of system resources. They can either be dynamically changed in the /proc file system or are defined in the kernel sources and can be changed by rebuilding the kernel. SHMMAX: 33554432 SHMMIN: 1 SHMMNI: 128 SHMSEG: 128 SHMALL: 4194304 SEMMNI: 128 SEMMSL: 250 SEMMNS: 32000 SEMOPM: 32 Change kernel parameter, use sysctl -w. OR Edit /proc/sys/kernel/shm... /proc/sys/kernel/sem Probably you use 2 of SERVERNUM, change SERVERNUM to other. Then oninit -iv.(Dangaer , initialize your database!) Regards. -- Tsutomu Ogiwara from Tokyo Japan. ICQ#:168106592 >From: sshumilov@yahoo.com (Sergey) >Reply-To: sshumilov@yahoo.com (Sergey) >To: informix-list@iiug.org >Subject: shmget: [EEXIST][17]: key 52584801: shared memory already exists >Date: 1 Dec 2004 23:20:46 -0800 > >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 already>exists >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 already>exists >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 already>exists >08:39:40 mt_shm_init: can't create resident segment> > > >and onconfig file > > ># Root Dbspace Configuration > >ROOTNAME rootdbs # Root dbspace name>ROOTPATH /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 mirrored>root >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 OnLine>instance >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 in>distributed env. >RESIDENT 0 # Forced residency flag (Yes = 1, No = >0) > >MULTIPROCESSOR 0 # 0 for single-processor, 1 for>multi-processor >NUMCPUVPS 1 # Number of user (cpu) vps >SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps>to 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 memory>segment 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 cleaning>limit >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