Re: logical logs

At 06:42 PM 12/11/97 EDT, you wrote: } } }Hi } }I am running Online 7.23 on HP 10.20 } }Why was logical log backed up every 2-3 minutes? Under normal circumstances, you may have had Continuous Backup on, which would backup any freed logical log as it's available for backup. In your case, I'm seeing something I never saw before, which is an output message from a script log_full.sh. What does this do? Your logs filled up pretty quickly (log 609 took nearly 3 mins to fill), and this seems to spark off your log_full.sh program. Check your cronjobs or ps -ef, to see if user informix is running it. Then confirm if log_full.sh is a readable text, UNIX script, and see if it's your culprit. Is your system such a high-throughput OLTP environment, that your 6MB logs are filled in under three mins, or is this only happening during a non-frequent data manipulation exercise, such as table defragmentation? If it's normal behaviour, then I would be glad to have my logs backed up immediately, especially with Continuous Backup. I would also look at modifying LTXHWM/LTXEHWM to something between 25/35 to 35/45 to minimize risk of a long transaction creaping up on me. }Is there any hint not to make that backup too fast? }Here is the info... } }11:07:08 Logical Log 608 Complete. }11:07:09 Process exited with return code 133: /bin/sh /bin/sh -c }/usr/informix/ }etc/log_full.sh 2 23 "Logical Log 608 Complete." "Logical Log 608 }Complete." }11:07:13 Logical Log 608 - Backup Started }11:07:19 Logical Log 608 - Backup Completed }11:08:58 Checkpoint Completed: duration was 3 seconds. } }11:09:51 Logical Log 609 Complete. }11:09:53 Process exited with return code 133: /bin/sh /bin/sh -c }/usr/informix/ }etc/log_full.sh 2 23 "Logical Log 609 Complete." "Logical Log 609 }Complete." }11:09:55 Logical Log 609 - Backup Started }11:10:02 Logical Log 609 - Backup Completed }11:12:19 Logical Log 610 Complete. }11:12:19 Process exited with return code 133: /bin/sh /bin/sh -c }/usr/informix/ }etc/log_full.sh 2 23 "Logical Log 610 Complete." "Logical Log 610 }Complete." }11:12:23 Logical Log 610 - Backup Started }11:12:30 Logical Log 610 - Backup Completed }11:14:10 Checkpoint Completed: duration was 8 seconds. } }11:14:55 Logical Log 611 Complete. }11:14:55 Logical Log 611 - Backup Started }11:14:57 Process exited with return code 133: /bin/sh /bin/sh -c }/usr/informix/ }etc/log_full.sh 2 23 "Logical Log 611 Complete." "Logical Log 611 }Complete." }11:15:02 Logical Log 611 - Backup Completed } }============================================ }onconfig info.. } }# Physical Log Configuration } }PHYSDBS phydbs # Location (dbspace) of physical log } }PHYSFILE 60000 # Physical log file size (Kbytes) } }# Logical Log Configuration } }LOGFILES 20 # Number of logical log files }LOGSIZE 6000 # Logical log size (Kbytes) } } }NETTYPE ipcshm,1,200,CPU # Override sqlhosts nettype }parameters }NETTYPE soctcp,1,75,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 4 # 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 90000 # Maximum number of locks }BUFFERS 85000 # Maximum number of shared buffers } }NUMAIOVPS 0 # Number of IO vps }PHYSBUFF 32 # Physical log buffer size (Kbytes) }LOGBUFF 32 # Logical log buffer size (Kbytes) }LOGSMAX 48 # Maximum number of logical log files }CLEANERS 4 # Number of buffer cleaner processes }SHMBASE 0x0 # Shared memory base address }SHMVIRTSIZE 400000 # initial virtual shared memory segment }size }SHMADD 32768 # Size of new shared memory segments }(Kbytes) }SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited } }CKPTINTVL 300 # Check point interval (in sec) }LRUS 4 # Number of LRU queues }LRU_MAX_DIRTY 30 # LRU percent dirty begin cleaning limit } }LRU_MIN_DIRTY 20 # LRU percent dirty end cleaning limit }LTXHWM 40 # Long transaction high water mark }percentage }LTXEHWM 50 # Long transaction high water mark }(exclusive) }TXTIMEOUT 0x12c # Transaction timeout (in sec) }STACKSIZE 32 # Stack size (Kbytes) }WSTATS 1 # Enable wait statistics } } }Thanks in advance for your response! }Thuc } } } Best regards, Nigel +-------------------------------------------------------------+ |Name : Edmund Nigel Gall Tel: (868) 636 3153 | |Title : Information Systems Specialist Fax: (868) 679 3770 | |Company: Process Plant Services Limited | |Address: Atlantic Avenue, Point Lisas Industrial Estate | | Point Lisas, Couva, Trinidad & Tobago, W.I. | +----- mailto:nigelg@ppsl.com ------ http://www.ppsl.com -----+