Re: Informix migrated to Solaris box
Posted in 1998
Topics: Storage & Space Management, Error Codes & Troubleshooting, Connectivity: ESQL/C, 4GL & Embedded SQL, Server Administration, Transactions, Locking & Isolation, Logging & Checkpoints, Networking & sqlhosts Configuration, Licensing & Editions, Platform-Specific Issues
Hello, Robert
Unfortunately, the program didn't show up error code or message on screen.
so, operator can not report any error message to identify the problem. I will
try to add it on program for examination. I want to say is, same program, same
case, Why I can not duplicated the problem? We never encounter such problem
on SCO open server (One CPU license) , Now I have multiprocessor Solaris box,
Should I made some change on the configuration file ? I copy the configuration
from SCO, so I suspect it cause by configuration setting (likes SPINCNT, resident
buffer... I don't know, because I didn't receive Informix administration training).
I have 25 SCO user license. now I have more than 30 users concureent running the
Informix program on solaris box. Attached the configuration file as below, I hope
you can give me some advice:
#**************************************************************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: tbconfig.std
# Sccsid: @(#)tbconfig.std 8.4 6/11/91 16:19:05
# Description: INFORMIX-OnLine Configuration Parameters
#
#**************************************************************************
# Root Dbspace Configuration
ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/online_root # Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 2097000 # 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 20000 # Physical log file size (Kbytes)# Logical Log Configuration
LOGFILES 32 # Number of logical log files
LOGSIZE 2000 # Logical log size (Kbytes)# Message Files
MSGPATH /u/inf_5.07/log/online.log # System message log file path
CONSOLE /dev/null # System console message path# System Archive Tape Device
TAPEDEV /dev/null # Tape device path
TAPEBLK 16 # Tape block size (Kbytes)
TAPESIZE 10240 # 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 (Bytes)
LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)# System Configuration
SERVERNUM 0 # Unique id corresponding to an OnLine instance
DBSERVERNAME PTISF # Unique name of this OnLine instance
RESIDENT 0 # Forced residency flag (Yes = 1, No = 0)# Shared Memory Parameters
USERS 256 # Maximum number of concurrent users (processes)
TRANSACTIONS 256 # Maximum number of concurrent transactions
LOCKS 5120 # Maximum number of locks
BUFFERS 1024 # Maximum number of shared buffersTBLSPACES 1000 # Maximum number of open tblspaces
CHUNKS 8 # Maximum number of chunks
DBSPACES 8 # Maximum number of dbspaces
PHYSBUFF 32 # Physical log buffer size (Kbytes)
LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 32 # Maximum number of logical log files
CLEANERS 1 # Number of buffer cleaner processes
SHMBASE 0x10000000 # Shared memory base address
CKPTINTVL 300 # Check point interval (in sec)DYNSHMSZ 0 # Dynamic shared memory size (Kbytes)
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 300 # Transaction timeout for I-STAR (in sec)SPINCNT 0 # No. of times process tries for latch
STAGEBLOB # INFORMIX-OnLine/Optical staging area
DEADLOCK_TIMEOUT 420 #max time to wait for lock in distrib env.# System Page Size
BUFFSIZE 2048 # Page size (do not change!)
# new parameters for ROGUE
GTRID_CMP_SZ 32 # Number of bytes to use in GTRID comparision
----------------------------------- End of attached file-----------------------------------------------
Robert Read '''g''峹 <350D51DD.7D3E5DB3@pacbell.net>...
>What is the error message?
>
>W. J. Hsu wrote:
>
>> Hello, out there
>>
>> We encounter some problem on our system software. It happened after
>> we migrated the informix from SCO open server to Ultra solaris box.
>> The application which developped by 4GL RDS compiler. It happened
>> occasionally that fail on query data from some tables. we can not
>> duplicated such problem. Each time, when operator report problem, we
>> try to debug the root cause by Informix 4GL debugger, we always
>> retrieve right data. The problem happened about twice per week. Should
>> I change Informix configuration (tbconfig)? I appreciated if someone
>> can help or any input. Let me try to explained the two system as below:
>>
>> SCO openserver Compaq 2500 (only one cpu license on SCO UNIX)
>> 256 MB memory
>> Informix online 5.07
>> RDS 4.16
>> ISQL 5.07
>> ID 4.16
>>
>> Ultra-2 Solaris (Two CPU)
>> 256 MB memory
>> Informix online 5.10
>> RDS 4.16
>> ISQL 5.10
>> ID 4.16
>
>
>