Re: getting IDS 2000 running on RH 6.2
Posted in 2000
From: Matthew Denny <mdenny@cs.berkeley.edu>
>
>Thanks for your help. When I run "onmode -ky", I get:
>
>onmode: Cannot attach to shared memory. errno = 43
>12:27:08 mt_shm_remove: WARNING: may not have removed all/correct>segments
>
>The output from ipcs -m looks like after I reboot before run oninit:
>
>
>------ Shared Memory Segments --------
>key shmid owner perms bytes nattch status
>
>
>and it looks like this after I ran "oninit -i" and it failed
>
>------ Shared Memory Segments --------
>key shmid owner perms bytes nattch status
>
>0x52564801 385 root 660 2764800 1 dest
>0x52564802 386 root 660 8192000 1 dest
>0x52564803 387 root 666 663552 1 dest
I'm confused. This looks like an instance of OnLine is running? Have you got
another version of IDS on this box? If so, I'd say your onconfig SERVERNUM
is the same in both of them, which is wrong.
>This seems OK, since the ipcs -m output from the good install
>looks like this after a reboot before oninit is ran
>
>
>------ Shared Memory Segments --------
>key shmid owner perms bytes nattch status
>
>0x00000000 0 informix 600 46084 2 dest
>
>
>and it looks like this after oninit is ran (just oninit of course, not
>
>oninit -i)>
>------ Shared Memory Segments --------
>key shmid owner perms bytes nattch status
>
>0x00000000 0 informix 600 46084 2 dest
>0x52564801 26753 root 660 2764800 11
>0x52564802 26754 root 660 8192000 11
>0x52564803 26755 root 666 663552 11
>
>from what I can tell, the
>
>0x00000000 0 informix 600 46084 2 dest
>
>is from the ONWeb daemon that I have running on the successful install
>
>in a
>
>What did I do wrong here? The Onconfig files for these two installs
>are exactly the same except for path info. Any help would be geratly
>appreciated.
>Obnoxio The Clown writes:
> > From: Matthew Denny <mdenny@cs.berkeley.edu>
> > >
> > >I am currently trying to get IDS 2000 running on a RedHat 6.2 Linux
> > >box. I have taken the following steps
> > >
> > >- created an sqlhosts file in $INFORMIXDIR/etc/sqlhosts to have 1
> > >connection for the localhost with shared memory IPC communication
> > >- created an onconfig file in $INFORMIXDIR/etc/ using onconfig.std as
>a
> > >template, with the following changes
> > > - set the ROOTPATH to a file that is owned by user and group
> > >informix with 644 permission (created as steps indicate in docs)
> > > - changed path names where appropos.
> > > - set DBSERVERNAME to the value of INFORMIXSERVER env var
> > > - changed J/Foundation stuff to use my box's JDK
> > >- set INFORMIXDIR, PATH, and INFORMIXSERVER appropriately
> > >
> > >However, when I call "oninit -i" (or any variant of this), I get
> > >"oninit: Fatal error in shared memory creation"
> > >
> > >The online.log file shows the following details:
> > >23:22:36 shmget: [EEXIST][17]: key 52564801: shared memory already>exists
> > >23:22:36 mt_shm_init: can't create resident segment> > >
> > >I basically get this same error no matter what command I run. Does
> > >anyone know what might be causing this? I've set up IDS 2000
> > >on a RedHat box before, so I know that either I must be missing
>something
> > >small,
> > >or there's some sort of hardware conflict. Any help would be geratly
> > >appreciated.
> >
> > It looks like you either have another instance of 7.3 or 5 (ha! Ha!) or
> > IDS.2000 on the box, or it hasn't cleared down another attempt to
>initialise
> > correctly.
> >
> > If you have got another instance up on the box, make sure to change
>your
> > SERVERNUM in the new instance.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > If you haven't, try running onmode -ky a couple of times, if that
>doesn't
> > help, post the output from ipcs -m.
> >
> > >if it helps, I have the following configuration:
> > >
> > >env. vars:
> > >
> > >PATH=/opt/informix/bin:. . .
> > >INFORMIXDIR=/opt/informix
> > >INFORMIXSERVER=idsserver> > >
> > >Also, here are teh contents of my onconfig file, located at
> > >/opt/informix/etc/onconfig (Apoogies for the line break problems due
> > >to cut and paste)
> > >
> >
> >#**************************************************************************
> > >#
> > ># INFORMIX SOFTWARE, INC.
> > >#
> > ># Title: onconfig.std
> > ># Description: Informix Dynamic Server 2000 Configuration Parameters
> > >#
> >
> >#**************************************************************************
> > >
> > ># Root Dbspace Configuration
> > >
> > >ROOTNAME rootdbs # Root dbspace name> > >ROOTPATH /opt/informix/data/idsserver # 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 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 rootdbs # Location (dbspace) of physical log
> > >PHYSFILE 2000 # Physical log file size (Kbytes)> > >
> > ># Logical Log Configuration
> > >
> > >LOGFILES 6 # Number of logical log files
> > >LOGSIZE 1500 # Logical log size (Kbytes)> > >
> > ># Diagnostics
> > >
> > >MSGPATH /opt/informix/online.log # System message log file
> > >path
> > >CONSOLE /dev/console # System console message path
> > >ALARMPROGRAM /opt/informix/etc/log_full.sh # Alarm program path
> > >TBLSPACE_STATS 1 # Maintain tblspace statistics> > >
> > ># System Archive Tape Device
> > >
> > >TAPEDEV /dev/tapedev # Tape device path
> > >TAPEBLK 16 # Tape block size (Kbytes)
> > >TAPESIZE 10240 # Maximum amount of data to put on
> > >tape (Kbytes)> > >
> > ># Log Archive Tape Device
> > >
> > >LTAPEDEV /dev/tapedev # 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 2000 staging
> > >area
> > >
> > ># System Configuration
> > >
> > >SERVERNUM 0 # Unique id corresponding to a OnLine> > >instance
> > >DBSERVERNAME idsserver # 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.@@N