Re: informix mirroring

In article <6aq168$eh6@bgtnsc01.worldnet.att.net>, Philip J. Mutino <pjmbhc@postoffice.worldnet.att.net> writes >------ ONSTAT -A ------- > >INFORMIX-OnLine Version 7.20.UC3 -- On-Line -- Up 8 days 21:44:07 -- 70536 >Kbytes > >Message Log File: /usr/informix/online.log >06:50:57 Checkpoint Completed: duration was 0 seconds. >06:55:57 Checkpoint Completed: duration was 0 seconds. Checkpoints seem ok. With LRU MIN/MAX at 50/60 it appears disk writes are not a problem. > >Configuration File: /usr/informix/etc/g30 >#************************************************************************** ># ># INFORMIX SOFTWARE, INC. ># ># Title: onconfig.std ># Description: INFORMIX-OnLine Configuration Parameters ># >#************************************************************************** > ># Root Dbspace Configuration > >ROOTNAME rootdbs # Root dbspace name >ROOTPATH /dev/rlv00 # Path for device containing root dbspace >ROOTOFFSET 4 # Offset of root dbspace into device (Kbytes) >ROOTSIZE 380000 # Size of root dbspace (Kbytes)> ># Disk Mirroring Configuration Parameters > >MIRROR 1 # Mirroring flag (Yes = 1, No = 0) >MIRRORPATH /dev/rlv04 # Path for device containing mirrored root >MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> ># Physical Log Configuration > >PHYSDBS rootdbs # Location (dbspace) of physical log >PHYSFILE 7000 # Physical log file size (Kbytes)> ># Logical Log Configuration > >LOGFILES 6 # Number of logical log files >LOGSIZE 2000 # Logical log size (Kbytes)> ># Diagnostics > >MSGPATH /usr/informix/online.log # System message log file path >CONSOLE /dev/null # System console message path Change to /usr/informix/cons.log Please! Some error messages do actually get sent here!! >ALARMPROGRAM /usr/informix/log_full.sh # Alarm program path > ># System Archive Tape Device > >TAPEDEV /dev/rmt0 # Tape device path >TAPEBLK 1024 # Tape block size (Kbytes) Big... >TAPESIZE 4500000 # Maximum amount of data to put on tape (Kbytes)> ># Log Archive Tape Device > >LTAPEDEV /dev/null # Log tape device path >LTAPEBLK 16 # Log tape block size (Kbytes) ...Small... >LTAPESIZE 5000000 # Max amount of data to put on log tape (Kbytes) ..Big again. Try increasing LTAPEBLK to say 256K. > ># Optical > >STAGEBLOB # INFORMIX-OnLine/Optical staging area > ># System Configuration > >SERVERNUM 0 # Unique id corresponding to a OnLine instance >DBSERVERNAME g30_online # Name of default database server >DBSERVERALIASES # List of alternate dbservernames >NETTYPE ipcshm,1,200,CPU # 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) Try setting to 1. We don't want online buffers getting paged out. > >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 > >NOAGE 0 # Process aging Try setting to 1, we don't want online processes to get aged. Although looking at the amount of cpu used by the CPU VPs below I doubt they are getting aged! >AFF_SPROC 0 # Affinity start processor >AFF_NPROCS 0 # Affinity number of processors> Try setting these, AFF_SPROC=1 AFF_NPROCS=2 ># Shared Memory Parameters > >LOCKS 10000 # Maximum number of locks >BUFFERS 800 # Maximum number of shared buffers These seems low even with 4K buffers, how much memory does the machine have? >NUMAIOVPS 1 # Number of IO vps You are using KAIO so 1 is ok. >PHYSBUFF 64 # Physical log buffer size (Kbytes) Physical logging pages/io = 15.x x hence try setting this to 16. >LOGBUFF 64 # Logical log buffer size (Kbytes) Logical logging pages/io = 1.xx hence try setting this to 2. From this I assume you can using unbuffered logging. This means that the physical and logging log buffers get flushed every time a user issues a commit work. Hence the pages/io are not likely to increase much and reducing the buffer sizes will help. PS These pages/io ALWAYS seem to be 15.xx and 1.xx with unbuffered logging. Has anyone seen different?? I certainly have not... >LOGSMAX 7 # Maximum number of logical log files >CLEANERS 12 # Number of buffer cleaner processes One per chunk. But how many physical disks do you have? You are not trying to page clean >1 chunk on the same disk at a time are you. That would cause a lot of disk seeks... >SHMBASE 0x30000000 # Shared memory base address >SHMVIRTSIZE 8000 # initial virtual shared memory segment size You have >1 virtual shared memory segment. Since you have 8*8Mb of them Try increaseing this to 64000 and bouncing Online. >SHMADD 8192 # Size of new shared memory segments (Kbytes) >SHMTOTAL 156000 # Total shared memory (Kbytes). 0=>unlimited >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 >LTXHWM 50 # Long transaction high water mark percentage >LTXEHWM 60 # Long transaction high water mark (exclusive) >TXTIMEOUT 0x12c # Transaction timeout (in sec) >STACKSIZE 64 # Stack size (Kbytes)> ># System Page Size ># BUFFSIZE - OnLine no longer supports this configuration parameter. ># To determine the page size used by OnLine 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 ># 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 /usr/informix/etc/dr