Updated Informix Linux install/configuration FAQ?

I need to verify that our driver works against Informix on Linux - which pretty much requires a working copy of Informix on Linux. The downloads from Intraware are in RPM format. The documentation from Intraware assumes otherwise. Is there an updated FAQ somewhere else? - the one from iiug.org is dated somewhere in 1998. Trying to follow the instructions as simple as possible, I did the following: System is P2, 256MB RAM, Redhat 6.1 made user/group informix/informix and user dba rpm -i the rpms for ids-....rpm set Informix variables (INFORMIXDIR, INFORMIXSERVER, PATH) edit sqlhosts.demo, sqlhosts run installserver (using the eval key) run dbaccessdemo7 (which spews out errors about sqlexec) This file /opt/informix/lib/sqlexec was never in the distribution. ----------------------- Alex Lee Chili!Soft Technical Support

Alex Lee wrote: > I need to verify that our driver works against Informix on Linux - which > pretty much requires a working copy of Informix on Linux. > > The downloads from Intraware are in RPM format. The documentation from > Intraware assumes otherwise. > > Is there an updated FAQ somewhere else? - the one from iiug.org is dated > somewhere in 1998. > > Trying to follow the instructions as simple as possible, I did the > following: > > System is P2, 256MB RAM, Redhat 6.1 > > made user/group informix/informix and user dba > rpm -i the rpms for ids-....rpm > set Informix variables (INFORMIXDIR, INFORMIXSERVER, PATH) > edit sqlhosts.demo, sqlhosts > run installserver (using the eval key) OK to this point. You need to have the engine online and running to create a database which is the first thing that dbaccessdemo7 will try to do. In the $INFORMIXDIR/etc directory find a file onconfig.std, this is a basic sample Informix IDS configuration file. Copy this to $INFORMIXDIR/etc/onconfig.$INFORMIXSERVER (a typical naming convention) and export ONCONFIG=onconfig.$INFORMIXSERVER Now edit $INFORMIXDIR/etc/$ONCONFIG and set the following parameters from their sample values: ROOTPATH <path to the file that will become the root dbspace for IDS> ROOTSIZE <20000 is bare minimum, increase it for sort & temp table space> MSGPATH <the online.log file should live in $INFORMIXDIR> ALARMPROGRAM <blank it out or get my utils3_ak package or write your own script. log_full.sh needs onbar.> SYSALARMPROGRAM <fix the path to $INFORMIXDIR/etc/evidence.sh> TBLSPACE_STATS 0 <too slow with stats on> TAPEDEV <your backup device/file> TAPESIZE <size of your backup device/file FYI file backups less than 2GB> LTAPEDEV <your logical log backup device/file or /dev/null to trash logs> LTAPESIZE <size of log backup device/file> SERVERNUM <pick a number from 1-255 I HATE zero though it's legal> DBSERVERNAME <$INFORMIXSERVER>DBSERVERALIAS <comma list of aliases for different interfaces-tcp/spx/pip> NETTYPE <leave it to default for now, but read the admin guide for latter > BUFFERS <200 is NOT enough. Each is 2K so how much RAM can you spare for the buffer cache?> CLEANERS 8 <should be >= LRUS> That's enough to get you started, read the Admin Guide when you have time and lurk here for tuning tips. Now create the ROOTPATH file with touch and set it to owner: informix, group: informix, chmod 660. Same for the TAPEDEV and LTAPEDEV if they point to files. If you only need local connections use shared memory. In the file $INFORMIXDIR/etc/sqlhosts add the line: <value of $INFORMIXSERVER> onipcshm <value of uname -n> sqlexec If you have DBSERVERALIASES set you will need a line for each alias defining its interface type (see the admin guide) and a servicename different from the other lines for this server in the fourth field. Enter each service with a port number in /etc/services. Now you are ready to start the engine: oninit -ivy # YOU WILL NEVER AGAIN USE THE -i FLAG! # Normal startup is: oninit -v or just oninit Now you can use onmonitor or the onspaces utility to add disk chunks (read files) for databases and THEN run the dbaccessdemo7 to create the demo database. It is a good idea to run that script with -dbspace <dbspacename> naming the data dbspace you created so the database is not created in the rootdb dbspace and -log so the database will have logging so you can play with transactions. Art S. Kagel > > run dbaccessdemo7 (which spews out errors about sqlexec) > > This file /opt/informix/lib/sqlexec was never in the distribution. > > ----------------------- > Alex Lee > Chili!Soft Technical Support