Re: ErrorCode = -27002

Prasad Dont know about 9.x but if the engine is in quiescent mode (in 7.x) I can make it online by this command: onmode -my. Of course you may want to check why the engine goes into quiescent mode whrn you bring it up. Check the online log (onstat -m) for possible answers. HTH Sujit Prasad Bandaru <pbandaru@agency.com> on 06/14/99 11:58:45 AM Please respond to Prasad Bandaru <pbandaru@agency.com> To: informix-list@iiug.org cc: (bcc: Sujit Pal) Subject: ErrorCode = -27002 To All Informix experts, I am not a DBA. But apparently I had to manage this Informix9.1.3 for my project that I am working right now. I am trying to connect to the DB but, I am getting the error code -27002 ([VENDORLIB] Vendor Library Error: No connections are allowed in OnLine quiescent mode.) when I try to connect to the database. I tried to shut down by using onmode -yuk.But it does not work. Is there any way to get my DB into non - quiescent mode. Or How do I fix my problem. Please Help, I appreciate any help, Thanks, Prasad

Hi, Thanks for the reply. I tried onmode -my. the server waits there for ever doing nothing. I am not sure what's happening. Here's my onconfig file. ========================================================= INFORMIX-Universal Server Version 9.13.UC3 -- Fast Recovery (CKPT REQ) -- Up 4 days 01:35:40 -- 29384 Kbytes Blocked:CKPT Configuration File: /usr/informix/etc/onconfig.att2 #************************************************************************** # # INFORMIX SOFTWARE, INC. # # Title: onconfig.std # Description: INFORMIX-Universal Server Configuration Parameters # This is the config file for the second instance on the prod server. #************************************************************************** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace nameROOTPATH /usr/informix/data/rootdbs #Path for device containing root dbspace ROOTOFFSET 2 # Offset of root dbspace into device (Kbytes) ROOTSIZE 50000 # 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 1000 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 6 # Number of logical log files LOGSIZE 500 # Logical log size (Kbytes) # Diagnostics MSGPATH /usr/informix/online2.log # System message log file path CONSOLE /dev/console # System console message path ALARMPROGRAM /usr/informix/etc/log_full.sh # Alarm program path # System Archive Tape Device TAPEDEV /tmp/backup2 # Tape device path TAPEBLK 16 # Tape block size (Kbytes) TAPESIZE 102400000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /tmp/backup_logs2 # Log tape device path LTAPEBLK 16 # Log tape block size (Kbytes) LTAPESIZE 1024000 # Max amount of data to put on log tape (Kbytes) # Optical STAGEBLOB # INFORMIX-OnLine/Universal Server staging area # System Configuration SERVERNUM 2 # Unique id corresponding to a OnLine instance DBSERVERNAME attpba913_2 # Name of default database server DBSERVERALIASES attpba913_tcp_2 # List of alternate dbservernames NETTYPE ipcshm,1,15,CPU # Configure poll thread(s) for nettype NETTYPE tlitcp,1,15,NET # 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) MULTIPROCESSOR 0 # 0 for single-processor, 1 for multi-processor NUMCPUVPS 1 # 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 2000 # Maximum number of locks BUFFERS 10000 # Maximum number of shared buffers NUMAIOVPS 2 # Number of IO vps PHYSBUFF 32 # Physical log buffer size (Kbytes) LOGBUFF 32 # Logical log buffer size (Kbytes)LOGSMAX 6 # Maximum number of logical log files CLEANERS 1 # Number of buffer cleaner processes SHMBASE 0xa000000L # Shared memory base address SHMVIRTSIZE 8000 # initial virtual shared memory segment size SHMADD 8192 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # 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 32 # 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.lostfound # DR lost+found file path # Backup/Restore variables BAR_ACT_LOG /tmp/bar_act.log BAR_MAX_BACKUP 0 BAR_RETRY 1 BAR_NB_XPORT_COUNT 10 BAR_XFER_BUF_SIZE 31 # Read Ahead Variables RA_PAGES # Number of pages to attempt to read ahead RA_THRESHOLD # Number of pages left before next group # DBSPACETEMP: # OnLine equivalent of DBTEMP for SE. This is the list of dbspaces # that the OnLine SQL Engine will use to create temp tables etc. # If specified it must be a colon separated list of dbspaces that exist # when the OnLine system is brought online. If not specified, or if # all dbspaces specified are invalid, various ad hoc queries will create # temporary files in /tmp instead. DBSPACETEMP # Default temp dbspaces # DUMP*: # The following parameters control the type of diagnostics information which # is preserved when an unanticipated error condition (assertion failure) occurs # during OnLine operations. # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No. DUMPDIR /tmp # Preserve diagnostics in this directory DUMPSHMEM 1 # Dump a copy of shared memory DUMPGCORE 0 # Dump a core image using 'gcore' DUMPCORE 0 # Dump a core image (Warning:this aborts OnLine) DUMPCNT 1 # Number of shared memory or gcore dumps for # a single user's session FILLFACTOR 90

Prasad Bandaru wrote: > > Hi, > > Thanks for the reply. I tried onmode -my. the server waits there for ever doing > nothing. I am not sure what's happening. > > Here's my onconfig file. > ========================================================= > > INFORMIX-Universal Server Version 9.13.UC3 -- Fast Recovery (CKPT REQ) -- Up > 4 days 01:35:40 -- 29384 Kbytes > Blocked:CKPT The header here is the answer to why the server seems to be hung, it is! It is in fast recovery, ie trying to start up and recover from the last, abnormal, shutdown, and is stuck because it cannot complete the checkpoint. This is usually caused by the logical logs filling. I see that you only have the original 6 log files configured and you have the logfiles marked to be backed up to a disk file with the alarm handler set up to backup the logfiles using onbar. Have you set up onbar? If not the log backups are failing and your logs are surely full. You need more logfiles. Run onstat -l and look at the status of the logfile. Since you have LBU_PRESERVE set you should see that all but the last logfile are full and that last one is emmpty. If so, set LBU_PRESERVE to 0 and try to restart the engine that last logfile should give you the headroom you need to complete the startup. Once the engine is online backup the logical logs immediately to free the logfiles for reuse. You can also try to set LTAPEDEV to /dev/null when you restart the engine so that it immediately frees up all of the existing logs, that MAY work. You can then use onmonitor to change it back to the file in /tmp. If not call tech support. This may also be caused by a missing log record. Several logical log record types are actually multiple records in the log. It is possible that the first of a multiple record set was forced to disk by a logical log buffer flush caused by the completion of another transaction or by the log buffer filling up while the balance of the entry had not yet been written to the buffer. Then the engine crashed before the subsequent buffer could be flushed to disk. This leaves a condition that the engine cannot recover from. If this is the case there should be a message in the Informix message log to the effect that a logical log record was not found. In this case Tech support will have to log in and zero out the partial transaction log record so that the fast recovery can get past it and complete when you bring the engine back online. This is harmless since the transaction had not completed when the engine/server crashed originally so it will be rolled back by the physical log slapdown that begins fast recovery. Art S. Kagel