< oninit -i >"Fatal error in Shared memory"
Posted in 1999
Topics: Installation, Setup & Upgrades, Server Administration, Platform-Specific Issues
Hi
We 're using informix on an solaris 2.6 platform, but we 're having
the following message after the < oninit -i > command
"Fatal error in Shared memory"
The shared memory settings in both the /etc/system and the
$INFORMIXDIR/etc/onconfig file seem ok.
What could be wrong? The damn thing worked 2 days ago
without any problems, I even reinstalled the whole machine from
scratch with the same result.
HELP
David.Govaert@Teleatlas.com
Dave,
One thing that this may mean is that UNIX shmget call has failed. this
has happened to me in two situations:
1. I had two instances and mistakenly let the server number for both of
them be the same (this is a configurable parameter in onconfig). I
believe that this number is used to construct the key used in shmget, so
when instance 2 starts it trys to use the same shmid as instance one,
and fails.
2. If I do an oninit, then do it again, I get this failure. Can't
initialize shared memory for an instance more than once without first
taking it off-line.
Look in the onconfig log for the specific shmget error message, then
post it here and more can be said about this problem.
Dave wrote:
> Hi
>
> We 're using informix on an solaris 2.6 platform, but we 're having
> the following message after the < oninit -i > command
> "Fatal error in Shared memory"
>
> The shared memory settings in both the /etc/system and the
> $INFORMIXDIR/etc/onconfig file seem ok.
>
> What could be wrong? The damn thing worked 2 days ago
> without any problems, I even reinstalled the whole machine from
> scratch with the same result.
>
> HELP
>
> David.Govaert@Teleatlas.com
Dave wrote:
>
> Hi
>
> We 're using informix on an solaris 2.6 platform, but we 're having
> the following message after the < oninit -i > command
> "Fatal error in Shared memory"
>
> The shared memory settings in both the /etc/system and the
> $INFORMIXDIR/etc/onconfig file seem ok.
>
> What could be wrong? The damn thing worked 2 days ago
> without any problems, I even reinstalled the whole machine from
> scratch with the same result.
>
> HELP
>
> David.Govaert@Teleatlas.com
How about your message log file ?
Possibliy it contains the reason why the system won't come up :-)
Bye
--
Stefan Weideneder
Phone: +49 89/3565478-2 ---------------
--- Fax: +49 89/3565478-3 -------------
------ mailto:/stefan@weideneder.de ---
-------- http://www.weideneder.de -----
>We 're using informix on an solaris 2.6 platform, but we 're having
>the following message after the < oninit -i > command
>"Fatal error in Shared memory"
>
>The shared memory settings in both the /etc/system and the
>$INFORMIXDIR/etc/onconfig file seem ok.
>
>What could be wrong? The damn thing worked 2 days ago
>without any problems, I even reinstalled the whole machine from
>scratch with the same result.
>
>HELP
>
>David.Govaert@Teleatlas.com
Here is some more info:
SQLHOSTS
informix> more sqlhosts
#**************************************************************************
# INFORMIX SOFTWARE, INC.
# PROPRIETARY DATA
# THIS DOCUMENT CONTAINS TRADE SECRET DATA WHICH IS THE PROPERTY
OF
# INFORMIX SOFTWARE, INC. THIS DOCUMENT IS SUBMITTED TO
RECIPIENT IN
# CONFIDENCE. INFORMATION CONTAINED HEREIN MAY NOT BE USED,
COPIED OR
# DISCLOSED IN WHOLE OR IN PART EXCEPT AS PERMITTED BY WRITTEN
AGREEMENT
# SIGNED BY AN OFFICER OF INFORMIX SOFTWARE, INC.
#
# THIS MATERIAL IS ALSO COPYRIGHTED AS AN UNPUBLISHED WORK UNDER
# SECTIONS 104 AND 408 OF TITLE 17 OF THE UNITED STATES CODE.
# UNAUTHORIZED USE, COPYING OR OTHER REPRODUCTION IS PROHIBITED
BY LAW.
# Title: sqlhosts.demo
# Sccsid: @(#)sqlhosts.demo 9.2 7/15/93 15:20:45
# Description:
# Default sqlhosts file for running demos.
#**************************************************************************
ol_besrvdb04 ontlitcp besrv-db04 ifmx2serv
informix> ls
ac_config.std boot911.sql cnv50t60.sql
log_full.sh pl_sym.out sym.out
arc_purge.sql boot911u.sql config.arc
logevent.sh plconfig.std sysmaster.sql
bldutil.sh boot912.sql evidence.sh
no_log.sh sm_versions.std sysutils.sql
boot90.sql boot912b.sql install
oncfg_ol_besrvdb04.1 smi_6to7 tctermcap
boot901.sql brand IUS-cr
onconfig smi_load termcap
boot910.sql buildsmi iusfiles
onconfig.std smi_unld xpg4_is.sql
boot910b.sql clone iusfiles.org
oper_deflt.arc sqlhosts
informix> more onconfig
#**************************************************************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.std
# Description: INFORMIX-Universal Server Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/informix/iusraw5 # Path for device containing
root dbspace
ROOTOFFSET 4 # Offset of root dbspace into device
(Kbytes)
ROOTSIZE 102396 # Size of root dbspace (Kbytes)
# Disk Mirroring Configuration Parameters
MIRROR 1 # Mirroring flag (Yes = 1, No = 0)
MIRRORPATH /dev/informix/iusraw10 # Path for device
containing mirrored root
MIRROROFFSET 327684 # Offset into mirrored device (Kbytes)
# Physical Log Configuration
PHYSDBS rootdbs # Location (dbspace) of physical log
PHYSFILE 1000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 6 # Number of logical log files
LOGSIZE 1500 # Logical log size (Kbytes)
# Diagnostics
MSGPATH /export/home/informix/online.log # System message log
file path
CONSOLE /dev/console # System console message path
ALARMPROGRAM /usr/informix/etc/log_full.sh # Alarm program path
# 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-OnLine/Universal Server
staging area
# System Configuration
SERVERNUM 1 # Unique id corresponding to a OnLineinstance
DBSERVERNAME ol_besrvdb04 # Name of default database server
DBSERVERALIASES # List of alternate dbservernames
NETTYPE tlitcp,1,50,CPU # 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)LOGSMAX 6 # Maximum number of logical log files
CLEANERS 1 # Number of buffer cleaner processes
SHMBASE 0x0A000000L # Shared memory base address
SHMVIRTSIZE 8000 # 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
LTXHWM 50 # Long transaction high water markpercentage
LTXEHWM 60 # Long transaction high water mark
(exclusive)
TXTIMEOUT 300 # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)
# System Page Size
# BUFFSIZE - OnLine no longer supports this configuration parameter.
# To determine the page size used by OnLine on your
platform
# see the last line of output from the command, 'onstat
-b'.
# Recovery Variables
# OFF_RECVRY_THREADS:
# Number of parallel worker threads during fast recovery or an offline
restore.
# ON_RECVRY_THREADS:
# Number of parallel worker threads during an online restore.
OFF_RECVRY_THREADS 10 # D
It looks like ifmx2serv is missing from /etc/services
Also you should check the permissions on the actual
device files. In solaris they live under /devices.
In article <37456c3d.190060130@news.ping.be>,
Dave <david.govaert@teleatlas.com> wrote:
>14:51:50 INFORMIX-Universal Server Version 9.14.UC6 Software Serial>Number AAC#J632153
>14:51:50 The chunk '/dev/informix/iusraw5' must have READ/WRITE>permissions for owner and group.
>
>14:51:50 The chunk '/dev/informix/iusraw10' must have READ/WRITE>permissions for owner and group.
This is probably your problem here.
>
> The chunk READ/WRITE permissions are ok (see below)
>
This does not show you the permissions on the device files, you need
to go to the file it links to, /dev/rdsk/c0t1xxxx. In solaris this
is yet another link to a file in /devices so you need to go there
too.
>
>
>informix> pwd
>/dev/informix
>informix> ls -l
>total 30
>lrwxrwxrwx 1 informix informix 18 May 20 09:38 iusraw1 ->
>/dev/rdsk/c0t1d0s0
>lrwxrwxrwx 1 informix informix 18 May 20 09:42 iusraw10 ->
>/dev/rdsk/c0t2d0s5
>lrwxrwxrwx 1 informix informix 18 May 20 09:43 iusraw11 ->
>/dev/rdsk/c0t5d0s0
>lrwxrwxrwx 1 informix informix 18 May 20 09:43 iusraw12 ->
>/dev/rdsk/c0t5d0s1
>lrwxrwxrwx 1 informix informix 18 May 20 09:43 iusraw13 ->
>/dev/rdsk/c0t5d0s3
>lrwxrwxrwx 1 informix informix 18 May 20 09:43 iusraw14 ->
>/dev/rdsk/c0t5d0s4
>lrwxrwxrwx 1 informix informix 18 May 20 09:43 iusraw15 ->
>/dev/rdsk/c0t5d0s5
>lrwxrwxrwx 1 informix informix 18 May 20 09:39 iusraw2 ->
>/dev/rdsk/c0t1d0s1
>lrwxrwxrwx 1 informix informix 18 May 20 09:39 iusraw3 ->
>/dev/rdsk/c0t1d0s3
>lrwxrwxrwx 1 informix informix 18 May 20 09:39 iusraw4 ->
>/dev/rdsk/c0t1d0s4
>lrwxrwxrwx 1 informix informix 18 May 20 09:40 iusraw5 ->
>/dev/rdsk/c0t1d0s5
>lrwxrwxrwx 1 informix informix 18 May 20 09:40 iusraw6 ->
>/dev/rdsk/c0t2d0s0
>lrwxrwxrwx 1 informix informix 18 May 20 09:41 iusraw7 ->
>/dev/rdsk/c0t2d0s1
>lrwxrwxrwx 1 informix informix 18 May 20 09:41 iusraw8 ->
>/dev/rdsk/c0t2d0s3
>lrwxrwxrwx 1 informix informix 18 May 20 09:41 iusraw9 ->
>/dev/rdsk/c0t2d0s4
>
Related threads
- onbar -c -F in Windows Informix instance
- Anyone... SQLCODE=-668, ISAM error=-1
- Not using the 100% logical log page size alloacted to informix