dbschema shows locked table
Posted in 1997
We have a HP K220 with one processor. HPUX Version 10.20
We are using mirroring, and striping the drives.
We are using a single raw device
Informix Online 7.14.UD2
RDS 6.03.UC2
C4GL 6.03.UC2
Installed HP-UX patches as suggested by Informix.
PHKL_9910 system hand due to LVM
PHKL_9724 select () system call
PHKL_9274 high %sys and switch
PHKL_8377 vmtrace and malloc()
PHKL_8204 Fix for system hand during panic
PHKL_10670 SCSI diskc cumulative patch
PHKL_10459 SystemV semaphores, semop(2)
PHKL_10422 HSC SCSI tape
PHKL_10289 Buffer cache
This is a new install with a sparsly populated database.
(usually less than 1000 rows)
The tables that lock have approxoimately 400+ rows and 2500+ rows
Occasionally we are running into an unusually locking problem, where the
4GL program will freeze up. No error responses on the 4gl program.
The DBA must use onmode -z to kill the users processes.
However in the meantime, no one else can do a dbschema on
the table in question.
There error received from the dbschema command
-252 Cannot get system information for table
-113 The file is locked
However, I can get schema information from isql using table/columns
isoloation is dirty read
row level locking on all tables
oncheck showed as being Ok
there are NO lock tables occuring in the code
We are using transaction logging in unbuffered mode
At the end of this document is the onconfig.
On onmode -u shows:
Userthreads
address flags sessid user tty wait tout locks nreads nwrites
c5c6d010 ---P--D 0 root - 0 0 0 22 14
c5c6d444 ---P--F 0 root - 0 0 0 0 0
c5c6d878 ---P--F 0 root - 0 0 0 0 0
c5c6dcac ---P--F 0 root - 0 0 0 0 0
c5c6e0e0 ---P--F 0 root - 0 0 0 0 0
c5c6e514 ---P--F 0 root - 0 0 0 0 0
c5c6e948 ---P--F 0 root - 0 0 0 0 0
c5c6ed7c ---P--B 24 root - 0 0 0 0 0
c5c6f1b0 ---P--D 0 root - 0 0 0 0 0
c5c6fa18 Y--P--- 74 root ttyp2 c5e82278 0 3 0 6
c5c6fe4c Y--P--- 75 root ttyp2 c5f5a5f8 0 1 0 6
c5c70280 --BP--- 76 root ttyp2 0 0 29 0 11
c5c70ae8 Y--P--- 58 carolv ttyp7 c60622d8 0 1 31 33
13 active, 128 total, 22 maximum concurrent
We have to onmode -z the sessid 76 and 74 in order to use the tables again.
Has anyone run into anything like this?
Any suggestions?
Arggg, we are supposed to go live in a week, this of course reduces our
concurrent usage ability... :-(
--
Rick Tucker
rickt@wybbs.mi.org
razer99@aol.com
-- I try to take one day at a time..., but lately several days
have attacked me at once. --
#**************************************************************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.foursite
# Description: INFORMIX-OnLine Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/online/infx-ldsk1 # Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 2000000 # 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 rootdbs # Location (dbspace) of physical log
PHYSFILE 100000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 50 # Number of logical log files
LOGSIZE 10000 # Logical log size (Kbytes)
# Diagnostics
MSGPATH /usr/informix/foursite.log # System message log file path
CONSOLE /dev/console # System console message path
ALARMPROGRAM # Alarm program path
# System Archive Tape Device
TAPEDEV /dev/rmt/0m # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 4000000 # Maximum amount of data to put on tape (Kbytes)
# Log Archive Tape Device
LTAPEDEV /dev/rmt/0m # Log tape device path
LTAPEBLK 16 # Log tape block size (Kbytes)
LTAPESIZE 10000000 # Max amount of data to put on log tape (Kbytes)
# Optical
STAGEBLOB # INFORMIX-OnLine/Optical staging area
# System Configuration
SERVERNUM 0 # Unique id corresponding to a OnLine instance
DBSERVERNAME foursite # Name of default database server
DBSERVERALIASES foursite_tcp # List of alternate dbservernames
NETTYPE soctcp,1,100,CPU
NETTYPE ipcshm,5,200,NET
DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env.
RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)
MULTIPROCESSOR 0 # 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
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors
# Shared Memory Parameters
LOCKS 50000 # Maximum number of locks
BUFFERS 33000 # Maximum number of shared buffers
NUMAIOVPS 4 # Number of IO vps
PHYSBUFF 100 # Physical log buffer size (Kbytes)
LOGBUFF 100 # Logical log buffer size (Kbytes)LOGSMAX 153 # Maximum number of logical log files
CLEANERS 6 # Number of buffer cleaner processes
SHMBASE 0x0 # Shared memory base address
SHMVIRTSIZE 50000 # initial virtual shared memory segment size
SHMADD 8192 # Size of new shared memory segments (Kbytes)
SHMTOTAL 150000 # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL 600 # Check point interval (in sec)
LRUS 6 # Number of LRU queues
LRU_MAX_DIRTY 40 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 25 # 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 32 # Stack size (Kbytes)
# System Page Size
# BUFFSIZE - OnLine no longer support