Config for new live system

I'm implementing a brand new system for a brand new Informix customer soon. It's an on-line gambling system so it will be up for months on end. It's to be IDS 7.31FC6 on a Sun SureFire v440 with 2 processors and 4GBytes of RAM, running Solaris 9. The Informix database will be the only thing running, and will be replicated via HDR to an identically-configured server. The database server is expected only to grow to 50Gbytes. The SureFire v440 has 4 x 36GBytes disks, and a StorEdge arrears, to be presented as JBOD, has an additional 8 x 36Gbyte disks. I'm planning to use two of the internal disks as a RAID-1 mirror boot, and use Solaris Volume Manager to present the remaining 10 as a 5 x 36 = 180 Gbyte logical volume, also protected with RAID-1. It'll be up for months on end so I need to get the initial config correct. I'd be grateful for any comments on the above layout or the proposed onconfig below. btw, we'll be backing up data and logs with onbar/ISM. thanks Neil #************************************************************************** # # INFORMIX SOFTWARE, INC. # # Title: onconfig.std # Description: Informix Dynamic Server Configuration Parameters # #************************************************************************** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace nameROOTPATH /opt/informix/dbspaces1/rootdbs # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 51200 # 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 physdbs # Location (dbspace) of physical log PHYSFILE 102294 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 40 # Number of logical log files LOGSIZE 1024 # Logical log size (Kbytes) # Diagnostics MSGPATH /opt/informix/online_1.log # System message log file path CONSOLE /opt/informix/console_1.log # System console message path ALARMPROGRAM /opt/informix/7.31/etc/log_full.sh # Alarm program path SYSALARMPROGRAM /opt/informix/7.31/etc/evidence.sh # System Alarm program path TBLSPACE_STATS 1 # System Archive Tape Device TAPEDEV /opt/informix/dbspaces1/tapedev TAPEBLK 16 # Tape block size (Kbytes) TAPESIZE 2048000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /opt/informix/dbspaces1/ltapedev # 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/Optical staging area # System Configuration SERVERNUM 1 # Unique id corresponding to a DynamicServer instance DBSERVERNAME fafdb1_tcp # Name of default database server DBSERVERALIASES fafdb1_shm # List of alternate dbservernames NETTYPE tlitcp,2,100,NET DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env. RESIDENT 0 # Forced residency flag (Yes = 1, No = 0) MULTIPROCESSOR 1 # 0 for single-processor, 1 formulti-processor NUMCPUVPS 2 # Number of user (cpu) vps SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps toone NOAGE 1 # Process aging AFF_SPROC 0 # Affinity start processor AFF_NPROCS 0 # Affinity number of processors # Shared Memory Parameters LOCKS 50000 # Maximum number of locks BUFFERS 1024000 # Maximum number of shared buffers NUMAIOVPS 2 # Number of IO vps PHYSBUFF 32 # Physical log buffer size (Kbytes) LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 60 # Maximum number of logical log files CLEANERS 29 # Number of buffer cleaner processes SHMBASE 0x10a000000 # Shared memory base address SHMVIRTSIZE 768000 # initial virtual shared memory segment size SHMADD 81920 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 300 # Check point interval (in sec) LRUS 32 # Number of LRU queues LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit 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 0x12c # Transaction timeout (in sec) STACKSIZE 64 # Stack size (Kbytes) # System Page Size # BUFFSIZE - Dynamic Server no longer supports this configuration parameter. # To determine the page size used by Dynamic Server 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 # Default number of offline workerthreads ON_RECVRY_THREADS 1 # Default number of online worker threads # Data Replication Variables # DRAUTO: 0 manual, 1 retain type, 2 reverse type DRAUTO 0 # DR automatic switchover DRINTERVAL 30 # DR max time between DR buffer flushes (in sec) DRTIMEOUT 30 # DR network timeout (in sec) DRLOSTFOUND /opt/informix/7.31/etc/dr.lostfound # DR lost+found filepath # CDR Variables CDR_LOGBUFFERS 2048 # size of log reading buffer pool (Kbytes) CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional) CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds) CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue (Kbytes)CDR_LOGDELTA 30 # % of log space allowed in queue memory CDR_NUMCONNECT 16 # Expected connections per server CDR_NIFRETRY 300 # Connection retry (seconds) CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max) # Backup/Restore variables BAR_ACT_LOG /opt/informix/bar_act_1.log # ON-Bar Log file - not in /tmp please BAR_DEBUG_LOG /opt/informix/bar_dbug_1.log # ON-Bar

\

I suppose I won't be much of a help but I'll try... > ROOTOFFSET 0 # Offset of root dbspace into device We had problems on Solaris 9 with zero offset. We set iz to 100 K and problems dissapeared. I think it has to do something with OS writing some info in first few KB of each disk it uses. > LOGFILES 40 # Number of logical log files > LOGSIZE 1024 # Logical log size (Kbytes) This may be insufficient. Depends on how busy system is. We have only about 1GB of data on the whole instance but a lot of transactions on it. We use following params: LOGFILES 256 LOGSIZE 2000 On a busy day we get one log filled up each 10 minutes. We use onbar/Legato and continuos log backup via log_full.sh. > MULTIPROCESSOR 1 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 2 # Number of user (cpu) vps > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to> one I think I read somewhere if you have a 2-processor machine it should be configured as a single CPU machine. The article said it has to do something with internal locking which is not so efficient if it's only 2-processor machine. Based on that this should look like: MULTIPROCESSOR 0 # 0 for single-processor, 1 formulti-processor NUMCPUVPS 1 # Number of user (cpu) vps SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps to Of course, I would like to hear comments on this from someone else because I'm not so sure about all this. It sounds like Informix can't really take advantage of other processor in a 2-procs machine. > SHMVIRTSIZE 768000 # initial virtual shared memory segmentsize > SHMADD 81920 # Size of new shared memory segments If SHMVIRTSIZE should not be sufficient then SHMADD would be added quite often, wouldn't it? Why have too much segments? I'd set SHMADD to SHMVIRTSIZE / 2 since your server is dedicated only to Informix. > BAR_MAX_BACKUP 0 There is a formula in the manual for this param but didn't use it. I set it to number of dbspaces (excluding rootdbs and temporary dbspace(s)) to have each dbspace backed up in parallel to maximaze throughput to backup server. Mind you, I'm not much of an Informix guru so take these advices with care. Hope they help. Bye.

"Davorin Kremenjas" <davorin.kremenjas@inet.hr> wrote in message news:cie5jj$8lk$1@bagan.srce.hr... > I suppose I won't be much of a help but I'll try... > > > ROOTOFFSET 0 # Offset of root dbspace into device> > We had problems on Solaris 9 with zero offset. We set iz to 100 K and > problems dissapeared. > I think it has to do something with OS writing some info in first few KB of > each disk it uses. I think this won't be a problem with Solaris LVM. > > > LOGFILES 40 # Number of logical log files > > LOGSIZE 1024 # Logical log size (Kbytes)> > This may be insufficient. Depends on how busy system is. We have only about > 1GB of data on the whole instance but a lot of transactions on it. We use > following params: I've actually configured 2Gbytes of 50k logs in a separate dbspace, which isn't reflected here. > > MULTIPROCESSOR 1 # 0 for single-processor, 1 for> > multi-processor > > NUMCPUVPS 2 # Number of user (cpu) vps > > SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vpsto > > one > > I think I read somewhere if you have a 2-processor machine it should be > configured as a single CPU machine. The article said it has to do something > with internal locking which is not so efficient if it's only 2-processor > machine. Based on that this should look like: > MULTIPROCESSOR 0 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 1 # Number of user (cpu) vps > SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps to> > Of course, I would like to hear comments on this from someone else because Me too! Thanks very much: lots of Food for Thought.