Re: IDS 9.40 on SLES 8 install problem
Posted in 2003
Topics: Installation, Setup & Upgrades, Storage & Space Management, Stored Procedures & SPL, Connectivity: ODBC / JDBC / .NET, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration, Java & JDBC Development, Internationalization & Character Sets, Versions, Editions & End-of-Life
I installed the same version yesterday on Suse 9.0 Pro
on Xeon cpu (IBM e-server) without any problems.
I had to get an older version of Java (1.3) from Sun
for JDBC to install. Using raw devices, not flat files.
I think that's the only difference.
I have not made any changes to default system configuration either.
I know this is not really helpful!
Michael
Dragi Bonzi Raos wrote:
> Hi!
>
> I am trying to run Informix IDS 9.40UC2E1 on SuSE SLES 8 (single-proc
> P4). Installation
> goes OK, but when oninit is supposed to initialize the root dbspace
> chunk, it quietly dies (failing to remove SHM segments and semaphores).
>
> This is what oninit -iv says before it dies:
>
>
> This action will initialize IBM Informix Dynamic Server;
> any existing IBM Informix Dynamic Server databases will NOT be
> accessible -
> Do you wish to continue (y/n)?
> Checking group membership to determine server run modesucceeded
> Reading configuration file '/home/informix/etc/onconfig'...succeeded
> Creating /INFORMIXTMP/.infxdirs ... succeeded
> Creating infos file "/home/informix/etc/.infos.Informix" ...
> "/home/informix/etc/.conf.Informix" ... succeeded
> Writing to infos file ... succeeded
> Checking config parameters...succeeded
> Allocating and attaching to shared memory...succeeded
> Creating resident pool 1382 kbytes...succeeded
> Creating buffer pool 10002 kbytes...succeeded
> Initializing rhead structure...succeeded
> Initializing ASF ...succeeded
> Initializing Dictionary Cache and SPL Routine Cache...succeeded
> Bringing up ADM VP...
> <<<<<<
>
> The log contains only this:
>
>
> 17:23:23 Event alarms enabled. ALARMPROG =
> '/home/informix/etc/alarmprogram.sh'
> 17:23:23 Booting Language <c> from module <>
> 17:23:23 Loading Module <CNULL>
> 17:23:23 Booting Language <builtin> from module <>
> 17:23:23 Loading Module <BUILTINNULL>
> <<<<<<>
> Locale is left on en_US. onconfig (pretty much vanilla) is attached.
>
> Can anybody shed any light on this? Is it me, Informix or SuSE?
>
> I tried to attach onconfig, but the news server kept complaining, so I
> am including it below.
>
>
> Regards,
>
> Dragi Raos
>
>
>
>
> onconfig:
>
> #***********************************************************************
> ***
> #
> # INFORMIX SOFTWARE, INC.
> #
> # Title: onconfig.std
> # Description: Informix Dynamic Server Configuration Parameters
> #
> #***********************************************************************
> ***
>
> # Root Dbspace Configuration
>
> ROOTNAME rootdbs # Root dbspace name
> ROOTPATH /home/informix/data/chunk # Flat file, long enough,> owned by informix, 660
> # Path for device containing root
> dbspace
> ROOTOFFSET 0 # Offset of root dbspace into device
> (Kbytes)
> ROOTSIZE 128000 # 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)>
> # Diagnostics
>
> MSGPATH /home/informix/online.log # System message log file path
> # CONSOLE /dev/console # System console message path
> CONSOLE /home/informix/console.log # System console message
> path
>
> # To automatically backup logical logs, edit alarmprogram.sh and set
> # BACKUPLOGS=Y
> ALARMPROGRAM /home/informix/etc/alarmprogram.sh # Alarm program path
> TBLSPACE_STATS 1 # Maintain tblspace statistics>
> # System Archive Tape Device
>
> TAPEDEV /dev/st0 # 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/st0 # 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 1 # Unique id corresponding to a OnLine> instance
> DBSERVERNAME Informix # Name of default database server
> DBSERVERALIASES # List of alternate dbservernames
> 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 0x10000000L # Shared memory base address> # SHMBASE 0x44000000 # Shared memory base address
> SHMVIRTSIZE 8000 # 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.000000 # LRU percent dirty begin cleaning limit
> LRU_MIN_DIRTY 50.000000 # LRU percent dirty end cleaning limit
> TXTIMEOUT 0x12c # 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
> rollba
Well, it at least means that the combination should work... I tried with raw devices first, then swithched to an ordinary file thinking that I might be doing something wrong with /dev/raw binding. Next step, IIUG as per Sean's advice. This is very frustrating - Informix installation and configuration was always a breeze, from the days before Turbo (well, except for the first versions of Turbo, maybe :-)... Anyway, thanks! Dragi "Michael Krzepkowski" <NOmichaelkSPAM@sqlcanada.com> wrote in message news:3FE8C612.2080108@sqlcanada.com... > I installed the same version yesterday on Suse 9.0 Pro > on Xeon cpu (IBM e-server) without any problems. > I had to get an older version of Java (1.3) from Sun > for JDBC to install. Using raw devices, not flat files. > I think that's the only difference. > I have not made any changes to default system configuration either. > > I know this is not really helpful! > > Michael