Re: Strange error when initialising (long)

"Logan, David (DBA - Adelaide)" <David.Logan@hp.com> wrote: Hi Folks, I am trying to install IIUG.IDS.10.00.FC5I1.HPIA64.tar and am receiving the following error after setting everything and running oninit -ivy. informix@i64aus01:(data)> oninit -ivy Checking group membership to determine server run mode...succeeded Reading configuration file '/informix/etc/onconfig'...succeeded Creating /INFORMIXTMP/.infxdirs...succeeded Creating infos file "/informix/etc/.infos.brian"...succeeded Linking conf file "/informix/etc/.conf.brian"...succeeded Writing to infos file...succeeded Checking config parameters...succeeded Allocating and attaching to shared memory...succeeded Creating resident pool 2194 kbytes...succeeded Allocating 10016 kbytes for buffer pool of 2K page size...succeeded Initializing rhead structure...succeeded Initializing ASF...succeeded Initializing Dictionary Cache and SPL Routine Cache...succeeded Bringing up ADM VP...succeeded Creating VP classes...succeeded Onlining 0 additional cpu vps...succeeded Onlining 2 IO vps...succeeded Initialization of Encryption...succeeded Forking main_loop thread...succeeded Initializing DR structures...succeeded Forking 1 'ipcshm' listener threads...succeeded Forking 1 'soctcp' listener threads...succeeded Starting tracing...succeeded Initializing 1 flushers...succeeded oninit: Cannot open chunk '/informix/data/'. errno = 21 oninit: Fatal error in shared memory initialization informix@i64aus01:(data)> finderr 21 -21 Is a directory. An operating-system error code with the meaning shown was unexpectedly returned to the database server. A file-type operation has been directed to a directory. Some database servers store tables, indexes, and lock files as files with particular suffixes in the database directory. If a directory replaced such a file, this error might result. Look for other operating-system error messages that might give more information. This is where my root chunk should be initialised. informix@i64aus01:(data)> ls -l /informix/data/rootdbs -rw-rw---- 1 informix informix 0 Nov 14 15:39 /informix/data/rootdbs informix@i64aus01:(data)> The data directory is also informix@i64aus01:(informix)> ls -ld data drwxrwxrwx 2 informix informix 96 Nov 14 15:39 data informix@i64aus01:(informix)> I have googled and found no references to the error number and informix apart for a KAIO running out of resources in the release notes for an earlier version. The ONCONFIG is as follows : informix@i64aus01:(informix)> cat etc/onconfig #************************************************************************** # # Licensed Material - Property Of IBM # # "Restricted Materials of IBM" # # IBM Informix Dynamic Server # (c) Copyright IBM Corporation 1996, 2005 All rights reserved. # # Title: onconfig.std # Description: IBM Informix Dynamic Server Configuration Parameters # #************************************************************************** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace name ROOTPATH /informix/data # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 150000 # 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 2000 # Logical log size (Kbytes)LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) # Tablespace Tablespace Configuration in Root Dbspace TBLTBLFIRST 0 # First extent size (Kbytes) (0 = default) TBLTBLNEXT 0 # Next extent size (Kbytes) (0 = default) # Security # DBCREATE_PERMISSION: # By default any user can create a database. Uncomment DBCREATE_PERMISSON to # limit database creation to a specific user. Add a new DBCREATE_PERMISSION # line for each permitted user. #DBCREATE_PERMISSION informix # DB_LIBRARY_PATH: # When loading a (C or C++) shared object (for a UDR or UDT), IDS checks that # the user-specified path starts with one of the directory prefixes listed in # the comma-separated list of prefixes in DB_LIBRARY_PATH. The string # "$INFORMIXDIR/extend" must be included in DB_LIBRARY_PATH in order for # extensibility and IBM supplied blades to work correctly. # DB_LIBRARY_PATH $INFORMIXDIR/extend # IFX_EXTEND_ROLE: # 0 (or off) => Disable use of EXTEND role to control who can register # external routines. # 1 (or on) => Enable use of EXTEND role to control who can register # external routines. This is the default behaviour. # IFX_EXTEND_ROLE 1 # To control the usage of EXTEND role. # Diagnostics MSGPATH /informix/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 /informix/etc/alarmprogram.sh # Alarm program path ALRM_ALL_EVENTS 0 # Triggers ALARMPROGRAM for any event occur TBLSPACE_STATS 1 # Maintain tblspace statistics # System Archive Tape Device TAPEDEV /dev/null # 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/null # 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 0 # Unique id corresponding to a OnLineinstance DBSERVERNAME brian # Name of default database server DBSERVERALIASES steve # 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 formulti-processor NUMCPUVPS 1 # Number of user (cpu) vps SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps toone NOAGE 0 # Process aging AFF_SPROC 0 # Affinity start processor AFF_NPROCS 0 # Affinity numb

i guess file /informix/data/ returns a directory oninit: Cannot open chunk '/informix/data/'. errno = 21 > ROOTPATH /informix/data # Path for device containing root dbspace -----------------------------------------^^^^^^ should be a file or better a char mode raw dev or a sym link to a char mode raw dev. Superboer. way fast=http://www.clipjes.nl/clip/nederlands/n/normaal_- _oerend_hard.html Anup Nair schreef: > "Logan, David (DBA - Adelaide)" <David.Logan@hp.com> wrote: Hi Folks, > > I am trying to install IIUG.IDS.10.00.FC5I1.HPIA64.tar and am receiving the > following error after setting everything and running oninit -ivy. > > informix@i64aus01:(data)> oninit -ivy > Checking group membership to determine server run mode...succeeded > Reading configuration file '/informix/etc/onconfig'...succeeded > Creating /INFORMIXTMP/.infxdirs...succeeded > Creating infos file "/informix/etc/.infos.brian"...succeeded > Linking conf file "/informix/etc/.conf.brian"...succeeded > Writing to infos file...succeeded > Checking config parameters...succeeded > Allocating and attaching to shared memory...succeeded > Creating resident pool 2194 kbytes...succeeded > Allocating 10016 kbytes for buffer pool of 2K page size...succeeded > Initializing rhead structure...succeeded > Initializing ASF...succeeded > Initializing Dictionary Cache and SPL Routine Cache...succeeded > Bringing up ADM VP...succeeded > Creating VP classes...succeeded > Onlining 0 additional cpu vps...succeeded > Onlining 2 IO vps...succeeded > Initialization of Encryption...succeeded > Forking main_loop thread...succeeded > Initializing DR structures...succeeded > Forking 1 'ipcshm' listener threads...succeeded > Forking 1 'soctcp' listener threads...succeeded > Starting tracing...succeeded > Initializing 1 flushers...succeeded > oninit: Cannot open chunk '/informix/data/'. errno = 21 > oninit: Fatal error in shared memory initialization > > informix@i64aus01:(data)> finderr 21 > -21 Is a directory. > > An operating-system error code with the meaning shown was unexpectedly > returned to the database server. A file-type operation has been > directed to a directory. Some database servers store tables, indexes, > and lock files as files with particular suffixes in the database > directory. If a directory replaced such a file, this error might > result. Look for other operating-system error messages that might give > more information. > > This is where my root chunk should be initialised. > > informix@i64aus01:(data)> ls -l /informix/data/rootdbs > -rw-rw---- 1 informix informix 0 Nov 14 15:39 > /informix/data/rootdbs > informix@i64aus01:(data)> > > The data directory is also > > informix@i64aus01:(informix)> ls -ld data > drwxrwxrwx 2 informix informix 96 Nov 14 15:39 data > informix@i64aus01:(informix)> > > I have googled and found no references to the error number and informix > apart for a KAIO running out of resources in the release notes for an > earlier version. > > The ONCONFIG is as follows : > > informix@i64aus01:(informix)> cat etc/onconfig > #************************************************************************** > # > # Licensed Material - Property Of IBM > # > # "Restricted Materials of IBM" > # > # IBM Informix Dynamic Server > # (c) Copyright IBM Corporation 1996, 2005 All rights reserved. > # > # Title: onconfig.std > # Description: IBM Informix Dynamic Server Configuration Parameters > # > #************************************************************************** > > # Root Dbspace Configuration > > ROOTNAME rootdbs # Root dbspace name > ROOTPATH /informix/data # Path for device containing root dbspace > ROOTOFFSET 0 # Offset of root dbspace into device > (Kbytes) > ROOTSIZE 150000 # 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 2000 # Logical log size (Kbytes)> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) > > # Tablespace Tablespace Configuration in Root Dbspace > > TBLTBLFIRST 0 # First extent size (Kbytes) (0 = default) > TBLTBLNEXT 0 # Next extent size (Kbytes) (0 = default)> > # Security > # DBCREATE_PERMISSION: > # By default any user can create a database. Uncomment DBCREATE_PERMISSON to > # limit database creation to a specific user. Add a new DBCREATE_PERMISSION > # line for each permitted user. > > #DBCREATE_PERMISSION informix > > # DB_LIBRARY_PATH: > # When loading a (C or C++) shared object (for a UDR or UDT), IDS checks > that > # the user-specified path starts with one of the directory prefixes listed > in > # the comma-separated list of prefixes in DB_LIBRARY_PATH. The string > # "$INFORMIXDIR/extend" must be included in DB_LIBRARY_PATH in order for > # extensibility and IBM supplied blades to work correctly. > > # DB_LIBRARY_PATH $INFORMIXDIR/extend > > # IFX_EXTEND_ROLE: > # 0 (or off) => Disable use of EXTEND role to control who can register > # external routines. > # 1 (or on) => Enable use of EXTEND role to control who can register > # external routines. This is the default behaviour. > # > IFX_EXTEND_ROLE 1 # To control the usage of EXTEND role.> > # Diagnostics > > MSGPATH /informix/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 /informix/etc/alarmprogram.sh # Alarm program path > ALRM_ALL_EVENTS 0 # Triggers ALARMPROGRAM for any event occur > TBLSPACE_STATS 1 # Maintain tblspace statistics> > # System Archive Tape Device > > TAPEDEV /dev/null # 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/null # 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 0 # Unique id corresponding to a OnLine> instan

< Snip > Check out what ROOTPATH should be set to when using cooked space. Admin Ref should give you the answer you seek.