Comment on my config

Before you go into production you should have a plan for backup and restore (just in case). So you must choose between onbar and ontape. Ontape is the simplest and you only have to configure the TAPExxx and LTAPExxx parameters in the onconfig file. Onbar must use a storage manager - either ISM that comes with IDS or a standard SM like Tivoli Storage Manager. Remember that you must backup both data and transaction record (logical log files) with the same backup application. Bjorn De Waele wrote: > Hello, > > > here is our newbie again :) > I've been reading a lot lately, I searched the internet and browsed the > newsgroups to gather all my info. > I would like to thank especially Art Kagel, Neil Truby, Jonathan Leffler and > in fact so many other people here ! Cause you guys helped me through it ! > You're all a lot more clear then IBM docs ;) > > I'm playing around with our new servers. We made an import off the existing > data. > Our server is a HP proliant with 4 processors, 3 physical disks (one with > data for the moment, thinking of placing the most accessed data on the > second physical disk), 2 gig of Ram. Running on Win2003 with version 9.4 > We have in our current environment 8 chunks which I want to reduce to 1 > chunk if we go live (after last import). If we go live, I'll import, drop > stats, run update stat medium and run update stats high for the indexes. > I can't give you yet much statistics from onstat cause we're testing it > right now. > > This is my onconfig.... I really hope you can help me out if I overlooked > some things ! Pretty much is clearing up in my head but there's still so > much fuzzy for me:) > > Thanks a lot, Bjorn > > > #************************************************************************** > # > # INFORMIX SOFTWARE, INC. > # > # Title: onconfig.std > # Description: Informix Dynamic Server Configuration Parameters > # > #************************************************************************** > > # Root Dbspace Configuration > > ROOTNAME rootdbs # Root dbspace name > ROOTPATH E:\\data\\rootdbs.000 # Path for device containing root dbspace > ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) > ROOTSIZE 100000 # 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 plogdbs # Location (dbspace) of physical log > PHYSFILE 40000 # Physical log file size (Kbytes)> > # Logical Log Configuration > > LOGFILES 178 # Number of logical log files > LOGSIZE 2000 # Logical log size (Kbytes)> LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) > > # Diagnostics > > MSGPATH C:\\Informix\\ol_ouden.log # System message log file path > CONSOLE C:\\Informix\\conol_ouden.log # System console message path > > # To automatically backup logical logs, edit alarmprogram.bat and set > # BACKUPLOGS=Y > ALARMPROGRAM C:\\Informix\\etc\\alarmprogram.bat # Alarm program path > TBLSPACE_STATS 1 # Maintain tblspace statistics> > > # System Diagnostic Script. > # SYSALARMPROGRAM - Full path of the system diagnostic script (e.g. > # c:\\informix\\etc\\evidence.bat.) Set this parameter > # if you want a different Diagnostic Script than > # {INFORMIXDIR}\\etc\\evidence.bat, which is default. > > # System Archive Tape Device > > #TAPEDEV \\\\.\\TAPE0 # Tape device path > TAPEDEV D:\\BACKUP > TAPEBLK 16 # Tape block size (Kbytes) > TAPESIZE 200000000 # Maximum amount of data to put on tape (Kbytes)> > # Log Archive Tape Device > > LTAPEDEV NUL # 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 > OPTICAL_LIB_PATH # Location of Optical Subsystem driver DLL > > # System Configuration > > SERVERNUM 0 # Unique id corresponding to a server instance > DBSERVERNAME ol_ouden # Name of default Dynamic Server > DBSERVERALIASES # List of alternate dbservernames > NETTYPE onsoctcp,1,,NET # Override sqlhosts nettype parameters > 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 for> multi-processor > NUMCPUVPS 6 # 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 200000 # Maximum number of locks > BUFFERS 200000 # Maximum number of shared buffers > NUMAIOVPS 12 # Number of IO vps #Initieel leeg > PHYSBUFF 64 # Physical log buffer size (Kbytes) #Initieel 32 > LOGBUFF 64 # Logical log buffer size (Kbytes) #Initieel 32 > CLEANERS 8 #1 # Number of buffer cleaner processes ->> normaal 1 per chunk > SHMBASE 0xC000000L # Shared memory base address > SHMVIRTSIZE 300000 # 54975 #8192 # initial virtual shared memory> segment size > SHMADD 20000 # Size of new shared memory segments > (Kbytes) > SHMTOTAL 1500000 # Total shared memory (Kbytes). > 0=>unlimited # initieel 0 > CKPTINTVL 300 # Check point interval (in sec) > LRUS 8 # Number of LRU queues > LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit > LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit > TXTIMEOUT 0x66c # Transaction timeout (in sec) > STACKSIZE 64 # 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 > rollback. > # However, to limit the number of new logical logs being added, > LTXHWM/LTXEHWM > # can be set to smaller values. > # > # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller values > # to avoid long transaction rollback hanging the server due to lack of > logical > # log space, i.e. 50/60 or lower. > > DYNAMIC_LOGS 2 > LTXHWM 40 > LTXEHWM 50> > # 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 thread

Hello, here is our newbie again :) I've been reading a lot lately, I searched the internet and browsed the newsgroups to gather all my info. I would like to thank especially Art Kagel, Neil Truby, Jonathan Leffler and in fact so many other people here ! Cause you guys helped me through it ! You're all a lot more clear then IBM docs ;) I'm playing around with our new servers. We made an import off the existing data. Our server is a HP proliant with 4 processors, 3 physical disks (one with data for the moment, thinking of placing the most accessed data on the second physical disk), 2 gig of Ram. Running on Win2003 with version 9.4 We have in our current environment 8 chunks which I want to reduce to 1 chunk if we go live (after last import). If we go live, I'll import, drop stats, run update stat medium and run update stats high for the indexes. I can't give you yet much statistics from onstat cause we're testing it right now. This is my onconfig.... I really hope you can help me out if I overlooked some things ! Pretty much is clearing up in my head but there's still so much fuzzy for me:) Thanks a lot, Bjorn #************************************************************************** # # INFORMIX SOFTWARE, INC. # # Title: onconfig.std # Description: Informix Dynamic Server Configuration Parameters # #************************************************************************** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace name ROOTPATH E:\\data\\rootdbs.000 # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 100000 # 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 plogdbs # Location (dbspace) of physical log PHYSFILE 40000 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 178 # Number of logical log files LOGSIZE 2000 # Logical log size (Kbytes)LOG_BACKUP_MODE MANUAL # Logical log backup mode (MANUAL, CONT) # Diagnostics MSGPATH C:\\Informix\\ol_ouden.log # System message log file path CONSOLE C:\\Informix\\conol_ouden.log # System console message path # To automatically backup logical logs, edit alarmprogram.bat and set # BACKUPLOGS=Y ALARMPROGRAM C:\\Informix\\etc\\alarmprogram.bat # Alarm program path TBLSPACE_STATS 1 # Maintain tblspace statistics # System Diagnostic Script. # SYSALARMPROGRAM - Full path of the system diagnostic script (e.g. # c:\\informix\\etc\\evidence.bat.) Set this parameter # if you want a different Diagnostic Script than # {INFORMIXDIR}\\etc\\evidence.bat, which is default. # System Archive Tape Device #TAPEDEV \\\\.\\TAPE0 # Tape device path TAPEDEV D:\\BACKUP TAPEBLK 16 # Tape block size (Kbytes) TAPESIZE 200000000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV NUL # 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 OPTICAL_LIB_PATH # Location of Optical Subsystem driver DLL # System Configuration SERVERNUM 0 # Unique id corresponding to a server instance DBSERVERNAME ol_ouden # Name of default Dynamic Server DBSERVERALIASES # List of alternate dbservernames NETTYPE onsoctcp,1,,NET # Override sqlhosts nettype parameters 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 6 # 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 number of processors # Shared Memory Parameters LOCKS 200000 # Maximum number of locks BUFFERS 200000 # Maximum number of shared buffers NUMAIOVPS 12 # Number of IO vps #Initieel leeg PHYSBUFF 64 # Physical log buffer size (Kbytes) #Initieel 32 LOGBUFF 64 # Logical log buffer size (Kbytes) #Initieel 32 CLEANERS 8 #1 # Number of buffer cleaner processes ->normaal 1 per chunk SHMBASE 0xC000000L # Shared memory base address SHMVIRTSIZE 300000 # 54975 #8192 # initial virtual shared memorysegment size SHMADD 20000 # Size of new shared memory segments (Kbytes) SHMTOTAL 1500000 # Total shared memory (Kbytes). 0=>unlimited # initieel 0 CKPTINTVL 300 # Check point interval (in sec) LRUS 8 # Number of LRU queues LRU_MAX_DIRTY 60 # LRU percent dirty begin cleaning limit LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit TXTIMEOUT 0x66c # Transaction timeout (in sec) STACKSIZE 64 # 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 rollback. # However, to limit the number of new logical logs being added, LTXHWM/LTXEHWM # can be set to smaller values. # # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller values # to avoid long transaction rollback hanging the server due to lack of logical # log space, i.e. 50/60 or lower. DYNAMIC_LOGS 2 LTXHWM 40 LTXEHWM 50 # 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 worker threads ON_RECVRY_THREADS 1 # Default number of online worker threads # Data Replication Variables DRINTERVAL 30 # DR max time between DR buffer flushes (in sec) DRTIMEOUT 30 # DR network timeout (in sec) DRLOSTFOUND \\tmp # DR lost+found file path # CDR Variables CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional) CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds) CDR_QUEUEMEM 4096 # Maximum memory for any CDR queue (Kbytes) CDR_QHDR_DBSPACE # CDR queue dbspace (default same as catalog) CDR_QDATA_SBSPACE # CDR queue smart blob space CDR_QDATA_SBFLAGS 2 # Log/no-log (default no log) CDR_NIFC