RE: ontape problems
Posted in 2000
I'm also experienced the same problem before. According to Informix Tech
Support, this is cause by the archive bug. You might consider to upgrade the
version to 7.31 in order to elimate this bug.
Jason
-----Original Message-----
From: Murray Wood [mailto:murray@quanta.co.nz]
Sent: Tuesday, September 26, 2000 5:53 AM
To:
Subject: RE: ontape problems
This looks like the ontape issue after large numbers of pages are updates.
It is a consequence of only having a 4 byte page number (which is updated
when each page is updated). The duration of the archive is intermittently
long and some checkpoints are long because the page number of "old" pages
are updated during the archive.
Informix Tech Support have full details. You will have to live with it
until 9.30 (we hope).
MW
-----Original Message-----
From: owner-informix-list@iiug.iiug.org
[mailto:owner-informix-list@iiug.iiug.org]On Behalf Of Byrd Farmer
Sent: Tuesday, September 26, 2000 1:25 AM
To: informix-list@iiug.org
Subject: ontape problems
I have an issue with on-tape. I am using version 7.24UC3 on Solaris 2.6.
For the last several months, we have had issues with on-tape taking an
excessive amount of time to write to tape when doing a level 0. Checkpoints
are taking in excess of 300 seconds apiece, even when we have the database
in quescient mode. The level 1 backups we do during the week are quick,
roughly an hour and a half, but the level 0 is taking 10-20 hours. It is
never consistent. Sometimes we can get a level 0 to run in 6-8 hours when
checkpoints are running 1-3 seconds, but then the next couple of weeks they
will run 20 hours with checkpoints running 200-300 seconds each. Is this
normal when the database is in quesient mode? We have moved checkpoints to
15 minute duration, to have the engine run longer before being held by the
checkpoints. Even with checkpoints running 5 minutes, it still will have a
300 second checkpoint. Any suggestions? Here is the onconfig file to look
at.....
#**************************************************************************
#
# Title: onconfig.cf
# Purpose: INFORMIX-OnLine Configuration Parameters
#
#**************************************************************************
#=====================================================================
# Root Dbspace Configuration
#=====================================================================
ROOTNAME rootdbsROOTPATH /usr/informix/chunks/rootdbs
ROOTOFFSET 0 # Offset into device (Kbytes)
ROOTSIZE 1000000 # Size of root dbspace (Kbytes)
#=====================================================================
# Disk Mirroring Configuration Parameters
#=====================================================================
MIRROR 0 # Yes = 1, No = 0
MIRRORPATH #
MIRROROFFSET 0 # Offset into mirrored device (Kbytes)
#=====================================================================
# Physical Log Configuration
#=====================================================================
PHYSFILE 1000000 # Physical log file size (Kbytes)PHYSDBS dbs_plog # Dbspace location of physical log
#PHYSDBS rootdbs # Dbspace location of physical log
#=====================================================================
# Logical Log Configuration
#=====================================================================
LOGFILES 10 # Number of logical log files
LOGSIZE 40000 # Logical log size (Kbytes)
#=====================================================================
# Diagnostics
#=====================================================================
MSGPATH /usr/informix/online.log
CONSOLE /dev/console
ALARMPROGRAM /export/home/informix/dba/eventalarm.ksh
#=====================================================================
# System Archive Tape Device
#=====================================================================
#TAPEDEV /dev/null # Tape device path
TAPEDEV /dev/rmt/1u # Tape device path
TAPEBLK 2048 # Tape block size (Kbytes)
TAPESIZE 59999992 # Maximum data on tape (Kbytes)
#=====================================================================
# Log Archive Tape Device
#=====================================================================
LTAPEDEV /dev/null
#LTAPEDEV /export/home/informix/llog
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 999999998 # Maximum data on tape (Kbytes)
#=====================================================================
# Optical
#=====================================================================
STAGEBLOB # OnLine/Optical staging area
#=====================================================================
# System Configuration
#=====================================================================
SERVERNUM 1 # Unique id corresponding to a OnLineinstance
DBSERVERNAME pcotcp # Name of default database server
DBSERVERALIASES pcoshm # List of alternate dbservernames
NETTYPE ipcshm,1,20,NET # Configure poll thread(s) for nettype
NETTYPE tlitcp,2,20,CPU # Configure poll thread(s) for nettype
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed
env.
RESIDENT 1 # Forced residency flag (Yes = 1, No = 0)
MULTIPROCESSOR 1 # 0 for single-processor, 1 formulti-processor
NUMCPUVPS 7 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # Set to 1 for 1/2 processor machines
NOAGE 0 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
#=====================================================================
# Shared Memory Parameters
#=====================================================================
LOCKS 400000 # Maximum number of locks
BUFFERS 600000 # Maximum number of shared buffers
NUMAIOVPS 4 # Number of IO vps
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 24 # Maximum number of logical log files
CLEANERS 125 # Number of buffer cleaner processes
SHMBASE 0xa000000 # Shared memory base address
SHMVIRTSIZE 1200000 # initial virtual shared memory segmentkbytes
SHMADD 32768 # Size of new shared memory segments
(Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL 900 # Check point interval (in sec)
LRUS 85 # Number of LRU queues
LRU_MAX_DIRTY 40 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 10 # LRU percent dirty end cleaning limit