RE: Will not initialize new instance.

It does this even after we boot. I can also run onmode -ky to release what shared memory it tried to allocate but we still get this error when we try to initialize. > -----Original Message----- > From: Madison Pruet [SMTP:mpruet@informix.com] > Sent: Sunday, February 20, 2000 6:38 PM > To: informix-list@iiug.org > Subject: Re: Will not initialize new instance. > > Bob, > > First you need to clear out any evidence of prior sessions. If you can > reboot, > that's the > easiest way to do that. Otherwise you need to run ps -ef | grep oninit > and kill > off any existing > oninits (assuming that there is only one on the machine). Then you need > to run > ipcs to get all > of the shared memory segments. You then need to remove all old informix > shared > memory > segments. Again - the easiest way would be to reboot. > > The point that you are refering to would have occured during the attempt > to > obtain shared memory > segments. > > "Lofstrand, Bob" wrote: > > > IDS 7.30.UC2X2 > > Dell Poweredge 4200 w/ 196meg > > SCO Openserver 3.2.5.0.5 > > > > When initializing a new instance oninit -iv stops at: > > Initializing rhead structure... > > > > onstat - from another session show: > > *** WARNING: Informix Dynamic Server is no longer running. *** > > > > *** WARNING: Informix Dynamic Server is no longer running. *** > > > > Informix Dynamic Server Version 7.30.UC2X2 -- Initialization -- Up > 00:03:59 > > -- 69632 Kbytes > > > > *** WARNING: Informix Dynamic Server is no longer running. *** > > > > The last few lines of the log file show: > > 14:25:15 shmget: [EEXIST][17]: key 52564801: shared memory already> exists > > 14:25:15 mt_shm_init: can't create resident segment > > > > 14:25:25 shmget: [EEXIST][17]: key 52564801: shared memory already> exists > > 14:25:25 mt_shm_init: can't create resident segment > > > > 15:32:15 shmget: [EEXIST][17]: key 52564801: shared memory already> exists > > 15:32:15 mt_shm_init: can't create resident segment> > > > The disks seem OK, the hardware has been checked and we are using a > > configuration that works fine at 85 other stores. > > > > Any ideas? I am completely stumped. > > > > ---------------------- > > Robert K. Lofstrand 806.351.2300 x3650 > > Informix Database Specialist lofstrr@hastings-ent.com > > Hastings Entertainment Inc. http://www.gohastings.com > > > > onconfig follows: > > > > # Root Dbspace Configuration > > > > ROOTNAME root # Root dbspace name > > ROOTPATH /u/inflinks/store/root_1> > # Path for device containing root > dbspace > > ROOTOFFSET 0 # Offset of root dbspace into device > > (Kbytes) > > ROOTSIZE 2048000 # Size of root dbspace (Kbytes)> > > > # Disk Mirroring Configuration Parameters > > > > MIRROR 0 # Mirroring flag (Yes = 1, No = 0) > > MIRRORPATH> > # Path for device containing mirrored > root > > MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> > > > # Physical Log Configuration > > > > PHYSDBS root # Location (dbspace) of physical log > > PHYSFILE 50000 # Physical log file size (Kbytes)> > > > # Logical Log Configuration > > > > LOGFILES 20 # Number of logical log files > > LOGSIZE 10000 # Logical log size (Kbytes)> > > > # Diagnostics > > > > MSGPATH /usr/informix/local/logs/log.store > > # System message log file path > > CONSOLE /usr/informix/local/logs/log.store # System console > message > > path > > ALARMPROGRAM /usr/informix/etc/log_full.sh # Alarm program path > > SYSALARMPROGRAM /usr/informix/etc/evidence.sh # System Alarm program > path > > TBLSPACE_STATS 0> > > > # System Archive Tape Device > > > > #TAPEDEV /dev/null > > #TAPEDEV /dev/rStp0 > > TAPEDEV /u/informix7/local/dbarc/dbmaster > > TAPEBLK 16 # Tape block size (Kbytes) > > TAPESIZE 4000000 # Maximum amount of data to put on tape > > (Kbytes)> > > > # Log Archive Tape Device > > > > LTAPEDEV /dev/null # Log tape device path > > LTAPEBLK 16 # Log tape block size (Kbytes) > > LTAPESIZE 10240 # Max amount of data to put on log tape > > (Kbytes)> > > > # Optical > > > > STAGEBLOB # Informix Dynamic Server/Optical > staging > > area > > > > # System Configuration > > > > SERVERNUM 0 # Unique id corresponding to a Dynamic> > Server instance > > DBSERVERNAME hst9999 # Name of default database server > > DBSERVERALIASES hst9999_eth # List of alternate dbservernames > > NETTYPE ipcshm,1,50,CPU # Configure poll thread(s) for nettype > > NETTYPE tlitcp,1,50,NET # 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 1 # If non-zero, limit number of cpu vps> to > > one > > > > NOAGE 1 # Process aging > > AFF_SPROC 0 # Affinity start processor > > AFF_NPROCS 0 # Affinity number of processors> > > > # Shared Memory Parameters > > > > LOCKS 500000 # Maximum number of locks > > BUFFERS 12000 # Maximum number of shared buffers > > NUMAIOVPS 3 # Number of IO vps > > PHYSBUFF 48 # Physical log buffer size (Kbytes) > > LOGBUFF 48 # Logical log buffer size (Kbytes)> > LOGSMAX 40 # Maximum number of logical log files > > CLEANERS 2 # Number of buffer cleaner processes > > SHMBASE 0x0 # Shared memory base address > > SHMVIRTSIZE 16384 # initial virtual shared memory segment> size > > SHMADD 8192 # Size of new shared memory segments > > (Kbytes) > > SHMTOTAL 0 # Total shared memory (Kbytes). > 0=>unlimited > > CKPTINTVL 900 # Check point interval (in sec) > > LRUS 7 # Number of LRU queues > > LRU_MAX_DIRTY 3 # LRU percent dirty begin cleaning limit > > LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit > > LTXHWM 45 # Long transaction high water mark> > percentage > > LTXEHWM 50 # Long transaction high water mark > > (exclusive) > > TXTIMEOUT 0x12c # Transaction timeout (in sec) > > STACKSIZE 32 # Stack size (Kbytes)@@NL