If a user connects to the server using shared memory or TCP/IP has nothing
to do with how much shared memory is allocated for the threads running from
that users session. Shared memory connection vs. TCP/IP is simply the
method of communication between the server and client.

If you want to verify the type of connection:

If the client app is running on the same machine, get the process id of the
client. Run:
onstat -g ses | grep PID - the process id of the client
The session id is the first column in the onstat -g ses output. Then run:
onstat -g ntu | grep SESSION_ID - the session id found above
The connection type is the second field. The run:
onstat -g ses SESSION_ID - the session id found above
This will give you pretty much all the info you need for that users session.

Check out this site for info on the onstat -g output:

http://www.oninit.com/database/redir...init.com/onsta
t/index.html

Regards,
Bill Dare

> -----Original Message-----
> From: sharad [SMTP:sha_pawar@hotmail.com]
> Sent: Friday, August 01, 2003 5:41 AM
> To: informix-list@iiug.org
> Subject: Re: Informix 9.40 crash after stress test.
>
> Hi Bill,
>
> Thanks for your suggetion . I had made changes as per suggetion so
> rerunning
> stress test. but I had one question about I had set connection protocol is
> soctcp ,I want to verify is now really using this protocol or not. if not
> how to get use this protocol. and why it is using the this much shared
> memory ?
>
> Parameter in onconfig file :
> NETTYPE soctcp,4,150,NET
>
> sqlhosts:
> fpt_server onsoctcp 9.182.25.49 INF
>
> $INFORMIXSERVER fpt_server
> - sharad
>
>
>
> "Bill Dare" <dareb@jevic.com> wrote in message
> news:bgbf6v$p1o$1@terabinaries.xmission.com...
> >
> > The user controls whether he connects using a TCP/IP connection vs. a
> SHM
> > connection by setting the INFORMIXSERVER environment variable or
> explicitly
> > selecting a server in his SQL. You can see how a user is connected
> using
> > "onstat -g ses".
> >
> > But that's not your problem here.
> >
> > Your getting errno 24 because your server is allocating too many shared
> > memory segments.
> > #define EMFILE 24 /* Too many open files */
> >
> > With these settings:
> >
> > SHMVIRTSIZE 87500 # initial virtual shared memory segment size
> >
> > SHMADD 16384 # Size of new shared memory segments (Kbytes)
> >
> > SHMTOTAL 419430 # Total shared memory (Kbytes). 0=>unlimited
> >
> > you have the possibility of allocating (419430 - 87500) / 16384 = 20
> shared
> > memory segments. Obviously more than the OS is configured to allow.
> Fix
> > this particular problem by making SHMADD large enough or SHMTOTAL small
> > enough so that you do not exceed SHMSEG. Or set SHMSEG in the kernel to
> > allow the number you are allocating.
> >
> > Of course you still have a problem with a user trying to use to much
> virtual
> > memory. At least your server will not crash.
> >
> > Regards,
> > Bill Dare
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: sharad [SMTP:sha_pawar@hotmail.com]
> > > Sent: Thursday, July 31, 2003 8:00 AM
> > > To: informix-list@iiug.org
> > > Subject: Informix 9.40 crash after stress test.
> > >
> > > Hi ,
> > >
> > > I had install informix 9.40 UC2 on AIX 5.2.
> > > did anybody has idea how to check informix server is using tcp
> connection
> > > and not shared memory connection.How to check memory leak in informix
> > > server
> > > ?
> > >
> > > Here is some portion of online.log file .
> > > ================================================== =============
> > > 16:28:31 shmat: [EMFILE][24]: out of shared memory segments, check
> system
> > > SHMSEG
> > >
> > > 16:28:31 shmdt: errno = 22
> > > 16:28:31 out of virtual shared memory
> > >
> > > 16:28:31 shmat: [EMFILE][24]: out of shared memory segments, check
> system
> > > SHMSEG
> > >
> > > 16:28:31 shmdt: errno = 22
> > > 16:28:31 out of virtual shared memory
> > >
> > > 16:28:31 Assert Failed: No Exception Handler
> > > 16:28:31 IBM Informix Dynamic Server Version 9.40.UC2
> > > 16:28:31 Who: Session(16, informix@adolphus, 5002, 40215d00)
> > > Thread(40, sqlexec, 401e5e68, 1)
> > > File: mtex.c Line: 431
> > > 16:28:31 Results: Exception Caught. Type: MT_EX_OS, Context: mem
> > > 16:28:31 Action: Please notify IBM Informix Technical Support.
> > > 16:28:31 stack trace for pid 32182 written to /tmp/af.410fd5e
> > > 16:28:31 See Also: /tmp/af.410fd5e, shmem.410fd5e.0
> > > 16:29:06 mtex.c, line 431, thread 40, proc id 32182, No Exception
> > > Handler.
> > > 16:29:08 The Master Daemon Died
> > > 16:29:08 PANIC: Attempting to bring system down
> > > ================================================== =============
> > > onconfig :file
> > > shared memory not initialized for INFORMIXSERVER 'fpt_server'
> > >
> > > Configuration File: /dbms/informix/etc/onconfig.file
> > >
> > >
> #************************************************* ************************
> > > *
> > >
> > > #
> > >
> > > # INFORMIX SOFTWARE, INC.
> > >
> > > #
> > >
> > > # Title: onconfig.std
> > >
> > > # Description: Informix Dynamic Server Configuration Parameters
> > >
> > > #
> > >
> > >
> #************************************************* ************************
> > > *
> > >
> > > # Root Dbspace Configuration
> > >
> > > ROOTNAME rootdbs # Root dbspace name
> > >
> > > ROOTPATH /dbms/informix/data/fpt_data
> > >
> > > ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
> > >
> > > ROOTSIZE 200000 # 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 2000 # Physical log file size (Kbytes)
> > >
> > > # Logical Log Configuration
> > >
> > > LOGFILES 6 # Number of logical log files
> > >
> > > LOGSIZE 2000 # Logical log size (Kbytes)
> > >
> > > # Diagnostics
> > >
> > > MSGPATH /dbms/informix/online.log # System message log file path
> > >
> > > CONSOLE /dev/console # System console message path
> > >
> > > # To automatically backup logical logs, edit alarmprogram.sh and set
> > >
> > > # BACKUPLOGS=Y
> > >
> > > ALARMPROGRAM /dbms/informix/etc/no_log.sh # Alarm program path
> > >
> > > TBLSPACE_STATS 1 # Maintain tblspace statistics
> > >
> > > # System Archive Tape Device
> > >
> > > TAPEDEV /dev/tapedev # Tape device path
> > >
> > > TAPEBLK 32 # 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 32 # Log tape block size (Kbytes)
> > >
> > > LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)
> > >
> > > # Optical
> > >
> > > STAGEBLOB # Informix Dynamic Server staging area
> > >
> > > # System Configuration
> > >
> > > SERVERNUM 1 # Unique id corresponding to a OnLine instance
> > >
> > > DBSERVERNAME fpt_server # Name of default database server
> > >
> > > DBSERVERALIASES # List of alternate dbservernames
> > >
> > > NETTYPE soctcp,4,150,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 20000 # Maximum number of shared buffers
> > >
> > > NUMAIOVPS # Number of IO vps
> > >
> > > PHYSBUFF 32 # Physical log buffer size (Kbytes)
> > >
> > > LOGBUFF 32 # Logical log buffer size (Kbytes)
> > >
> > > CLEANERS 1 # Number of buffer cleaner processes
> > >
> > > SHMBASE 0x30000000 # Shared memory base address
> > >
> > > SHMVIRTSIZE 87500 # initial virtual shared memory segment size
> > >
> > > SHMADD 16384 # Size of new shared memory segments (Kbytes)
> > >
> > > SHMTOTAL 419430 # Total shared memory (Kbytes). 0=>unlimited
> > >
> > > CKPTINTVL 150 # Check point interval (in sec)
> > >
> > > LRUS 8 # Number of LRU queues
> > >
> > > LRU_MAX_DIRTY 60.000000 # LRU percent dirty begin cleaning limit
> > >
> > > LRU_MIN_DIRTY 50.000000 # LRU percent dirty end cleaning limit
> > >
> > > TXTIMEOUT 0x12c # Transaction timeout (in sec)
> > >
> > > STACKSIZE 64
> > >
> > > # Dynamic Logging
> > >
> > > # DYNAMIC_LOGS:
> > >
> > > # 2 : server automatically add a new logical log when necessary. (ON)
> > >
> > > # 1 : notify DBA to add new logical logs when necessary. (ON)
> > >
> > > # 0 : cannot add logical log on the fly. (OFF)
> > >
> > > #
> > >
> > > # When dynamic logging is on, we can have higher values for
> > > LTXHWM/LTXEHWM,
> > >
> > > # because the server can add new logical logs during long transaction
> > > rollback.
> > >
> > > # However, to limit the number of new logical logs being added,
> > > LTXHWM/LTXEHWM
> > >
> > > # can be set to smaller values.
> > >
> > > #
> > >
> > > # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to smaller
> > > values
> > >
> > > # to avoid long transaction rollback hanging the server due to lack of
> > > logical
> > >
> > > # log space, i.e. 50/60 or lower.
> > >
> > > DYNAMIC_LOGS 2
> > >
> > > LTXHWM 70
> > >
> > > LTXEHWM 80
> > >
> > > # 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
> > >
> > > 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
> > >
> > > # CDR Variables
> > >
> > > CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
> > >
> > > CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
> > >
> > > CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue
> (Kbytes)
> > >
> > > CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max)
> > >
> > > CDR_SERIAL 0,0 # Serial Column Sequence
> > >
> > > CDR_DBSPACE # dbspace for syscdr database
> > >
> > > CDR_QHDR_DBSPACE # CDR queue dbspace (default same as catalog)
> > >
> > > CDR_QDATA_SBSPACE # List of CDR queue smart blob spaces
> > >
> > > # CDR_MAX_DYNAMIC_LOGS
> > >
> > > # -1 => unlimited
> > >
> > > # 0 => disable dynamic log addition
> > >
> > > # >0 => limit the no. of dynamic log additions with the specified
> value.
> > >
> > > # Max dynamic log requests that CDR can make within one server
> session.
> > >
> > > CDR_MAX_DYNAMIC_LOGS 0 # Dynamic log addition disabled by default
> > >
> > > # Backup/Restore variables
> > >
> > > BAR_ACT_LOG /usr/informix/bar_act.log # ON-Bar Log file - not in /tmp
> > > please
> > >
> > > BAR_DEBUG_LOG /usr/informix/bar_dbug.log
> > >
> > > # ON-Bar Debug Log - not in /tmp please
> > >
> > > BAR_MAX_BACKUP 0
> > >
> > > BAR_RETRY 1
> > >
> > > BAR_NB_XPORT_COUNT 10
> > >
> > > BAR_XFER_BUF_SIZE 31
> > >
> > > RESTARTABLE_RESTORE on
> > >
> > > BAR_PROGRESS_FREQ 0
> > >
> > > # Informix Storage Manager variables
> > >
> > > ISM_DATA_POOL ISMData
> > >
> > > ISM_LOG_POOL ISMLogs
> > >
> > > # 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 # Fill factor for building indexes
> > >
> > > # method for OnLine to use when determining current time
> > >
> > > USEOSTIME 0 # 0: use internal time(fast), 1: get time from OS(slow)
> > >
> > > # Parallel Database Queries (pdq)
> > >
> > > MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority
> > >
> > > DS_MAX_QUERIES # Maximum number of decision support queries
> > >
> > > DS_TOTAL_MEMORY # Decision support memory (Kbytes)
> > >
> > > DS_MAX_SCANS 1048576 # Maximum number of decision support scans
> > >
> > > DATASKIP off # List of dbspaces to skip
> > >
> > > # OPTCOMPIND
> > >
> > > # 0 => Nested loop joins will be preferred (where
> > >
> > > # possible) over sortmerge joins and hash joins.
> > >
> > > # 1 => If the transaction isolation mode is not
> > >
> > > # "repeatable read", optimizer behaves as in (2)
> > >
> > > # below. Otherwise it behaves as in (0) above.
> > >
> > > # 2 => Use costs regardless of the transaction isolation
> > >
> > > # mode. Nested loop joins are not necessarily
> > >
> > > # preferred. Optimizer bases its decision purely
> > >
> > > # on costs.
> > >
> > > OPTCOMPIND 2 # To hint the optimizer
> > >
> > > DIRECTIVES 1 # Optimizer DIRECTIVES ON (1/Default) or OFF (0)
> > >
> > > ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1 = ABORT, 2 =
> WAIT
> > >
> > > OPCACHEMAX 0 # Maximum optical cache size (Kbytes)
> > >
> > > # HETERO_COMMIT (Gateway participation in distributed transactions)
> > >
> > > # 1 => Heterogeneous Commit is enabled
> > >
> > > # 0 (or any other value) => Heterogeneous Commit is disabled
> > >
> > > HETERO_COMMIT 0
> > >
> > > SBSPACENAME # Default smartblob space name - this is where blobs
> > >
> > > # go if no sbspace is specified when the smartblob is
> > >
> > > # created. It is also used by some datablades as
> > >
> > > # the location to put their smartblobs.
> > >
> > > SYSSBSPACENAME # Default smartblob space for use by the Informix
> > >
> > > # Server. This is used primarily for Informix Server
> > >
> > > # system statistics collection.
> > >
> > > BLOCKTIMEOUT 3600 # Default timeout for system block
> > >
> > > SYSALARMPROGRAM /dbms/informix/etc/evidence.sh # System Alarm program
> path
> > >
> > > # Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
> > >
> > > OPT_GOAL -1
> > >
> > > ALLOW_NEWLINE 0 # embedded newlines(Yes = 1, No = 0 or anything but 1)
> > >
> > > #
> > >
> > > # The following are default settings for enabling Java in the
> database.
> > >
> > > # Replace all occurrences of /usr/informix with the value of
> $INFORMIXDIR.
> > >
> > > #VPCLASS jvp,num=1 # Number of JVPs to start with
> > >
> > > JVPJAVAHOME /usr/informix/extend/krakatoa/jre
> > >
> > > # JRE installation root directory
> > >
> > > JVPHOME /usr/informix/extend/krakatoa # Krakatoa installation
> directory
> > >
> > > JVPPROPFILE /usr/informix/extend/krakatoa/.jvpprops # JVP property
> file
> > >
> > > JDKVERSION 1.3 # JDK version supported by this server
> > >
> > > # The path to the JRE libraries relative to JVPJAVAHOME
> > >
> > > JVPJAVALIB /bin
> > >
> > > # The JRE libraries to use for the Java VM
> > >
> > > JVPJAVAVM hpi:jvm:java:net:zip:jpeg
> > >
> > > # use JVPARGS to change Java VM configuration
> > >
> > > #To display jni call
> > >
> > > #JVPARGS -verbose:jni
> > >
> > > # Classpath to use upon Java VM start-up (use _g version for
> debugging)
> > >
> > > #JVPCLASSPATH
> > >
> /usr/informix/extend/krakatoa/krakatoa_g.jar:/usr/informix/extend/krakatoa
> > > /j
> > > dbc_g.jar
> > >
> > > JVPCLASSPATH
> > >
> /usr/informix/extend/krakatoa/krakatoa.jar:/usr/informix/extend/krakatoa/j
> > > db
> > > c.jar
> > >
> > > ================================================== =============
> > >
> > >
> > >
> > sending to informix-list
>
sending to informix-list

Hi Bill,

Thanks I had checked my connection is using the soctcp that is provided
in ONCONFIG and sqlhost file.
I am just watching the shared memory segment allocation by informix.

thanks for suggetion.

- Sharad


"Bill Dare" <dareb@jevic.com> wrote in message
news:bgdqk1$91o$1@terabinaries.xmission.com...
>
> If a user connects to the server using shared memory or TCP/IP has nothing
> to do with how much shared memory is allocated for the threads running
from
> that users session. Shared memory connection vs. TCP/IP is simply the
> method of communication between the server and client.
>
> If you want to verify the type of connection:
>
> If the client app is running on the same machine, get the process id of
the
> client. Run:
> onstat -g ses | grep PID - the process id of the client
> The session id is the first column in the onstat -g ses output. Then run:
> onstat -g ntu | grep SESSION_ID - the session id found above
> The connection type is the second field. The run:
> onstat -g ses SESSION_ID - the session id found above
> This will give you pretty much all the info you need for that users
session.
>
> Check out this site for info on the onstat -g output:
>
>
http://www.oninit.com/database/redir...init.com/onsta
> t/index.html
>
> Regards,
> Bill Dare
>
> > -----Original Message-----
> > From: sharad [SMTP:sha_pawar@hotmail.com]
> > Sent: Friday, August 01, 2003 5:41 AM
> > To: informix-list@iiug.org
> > Subject: Re: Informix 9.40 crash after stress test.
> >
> > Hi Bill,
> >
> > Thanks for your suggetion . I had made changes as per suggetion so
> > rerunning
> > stress test. but I had one question about I had set connection protocol
is
> > soctcp ,I want to verify is now really using this protocol or not. if
not
> > how to get use this protocol. and why it is using the this much shared
> > memory ?
> >
> > Parameter in onconfig file :
> > NETTYPE soctcp,4,150,NET
> >
> > sqlhosts:
> > fpt_server onsoctcp 9.182.25.49 INF
> >
> > $INFORMIXSERVER fpt_server
> > - sharad
> >
> >
> >
> > "Bill Dare" <dareb@jevic.com> wrote in message
> > news:bgbf6v$p1o$1@terabinaries.xmission.com...
> > >
> > > The user controls whether he connects using a TCP/IP connection vs. a
> > SHM
> > > connection by setting the INFORMIXSERVER environment variable or
> > explicitly
> > > selecting a server in his SQL. You can see how a user is connected
> > using
> > > "onstat -g ses".
> > >
> > > But that's not your problem here.
> > >
> > > Your getting errno 24 because your server is allocating too many
shared
> > > memory segments.
> > > #define EMFILE 24 /* Too many open files */
> > >
> > > With these settings:
> > >
> > > SHMVIRTSIZE 87500 # initial virtual shared memory segment size
> > >
> > > SHMADD 16384 # Size of new shared memory segments (Kbytes)
> > >
> > > SHMTOTAL 419430 # Total shared memory (Kbytes). 0=>unlimited
> > >
> > > you have the possibility of allocating (419430 - 87500) / 16384 = 20
> > shared
> > > memory segments. Obviously more than the OS is configured to allow.
> > Fix
> > > this particular problem by making SHMADD large enough or SHMTOTAL
small
> > > enough so that you do not exceed SHMSEG. Or set SHMSEG in the kernel
to
> > > allow the number you are allocating.
> > >
> > > Of course you still have a problem with a user trying to use to much
> > virtual
> > > memory. At least your server will not crash.
> > >
> > > Regards,
> > > Bill Dare
> > >
> > >
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: sharad [SMTP:sha_pawar@hotmail.com]
> > > > Sent: Thursday, July 31, 2003 8:00 AM
> > > > To: informix-list@iiug.org
> > > > Subject: Informix 9.40 crash after stress test.
> > > >
> > > > Hi ,
> > > >
> > > > I had install informix 9.40 UC2 on AIX 5.2.
> > > > did anybody has idea how to check informix server is using tcp
> > connection
> > > > and not shared memory connection.How to check memory leak in
informix
> > > > server
> > > > ?
> > > >
> > > > Here is some portion of online.log file .
> > > > ================================================== =============
> > > > 16:28:31 shmat: [EMFILE][24]: out of shared memory segments, check
> > system
> > > > SHMSEG
> > > >
> > > > 16:28:31 shmdt: errno = 22
> > > > 16:28:31 out of virtual shared memory
> > > >
> > > > 16:28:31 shmat: [EMFILE][24]: out of shared memory segments, check
> > system
> > > > SHMSEG
> > > >
> > > > 16:28:31 shmdt: errno = 22
> > > > 16:28:31 out of virtual shared memory
> > > >
> > > > 16:28:31 Assert Failed: No Exception Handler
> > > > 16:28:31 IBM Informix Dynamic Server Version 9.40.UC2
> > > > 16:28:31 Who: Session(16, informix@adolphus, 5002, 40215d00)
> > > > Thread(40, sqlexec, 401e5e68, 1)
> > > > File: mtex.c Line: 431
> > > > 16:28:31 Results: Exception Caught. Type: MT_EX_OS, Context: mem
> > > > 16:28:31 Action: Please notify IBM Informix Technical Support.
> > > > 16:28:31 stack trace for pid 32182 written to /tmp/af.410fd5e
> > > > 16:28:31 See Also: /tmp/af.410fd5e, shmem.410fd5e.0
> > > > 16:29:06 mtex.c, line 431, thread 40, proc id 32182, No Exception
> > > > Handler.
> > > > 16:29:08 The Master Daemon Died
> > > > 16:29:08 PANIC: Attempting to bring system down
> > > > ================================================== =============
> > > > onconfig :file
> > > > shared memory not initialized for INFORMIXSERVER 'fpt_server'
> > > >
> > > > Configuration File: /dbms/informix/etc/onconfig.file
> > > >
> > > >
> >
#************************************************* ************************
> > > > *
> > > >
> > > > #
> > > >
> > > > # INFORMIX SOFTWARE, INC.
> > > >
> > > > #
> > > >
> > > > # Title: onconfig.std
> > > >
> > > > # Description: Informix Dynamic Server Configuration Parameters
> > > >
> > > > #
> > > >
> > > >
> >
#************************************************* ************************
> > > > *
> > > >
> > > > # Root Dbspace Configuration
> > > >
> > > > ROOTNAME rootdbs # Root dbspace name
> > > >
> > > > ROOTPATH /dbms/informix/data/fpt_data
> > > >
> > > > ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
> > > >
> > > > ROOTSIZE 200000 # 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 2000 # Physical log file size (Kbytes)
> > > >
> > > > # Logical Log Configuration
> > > >
> > > > LOGFILES 6 # Number of logical log files
> > > >
> > > > LOGSIZE 2000 # Logical log size (Kbytes)
> > > >
> > > > # Diagnostics
> > > >
> > > > MSGPATH /dbms/informix/online.log # System message log file path
> > > >
> > > > CONSOLE /dev/console # System console message path
> > > >
> > > > # To automatically backup logical logs, edit alarmprogram.sh and set
> > > >
> > > > # BACKUPLOGS=Y
> > > >
> > > > ALARMPROGRAM /dbms/informix/etc/no_log.sh # Alarm program path
> > > >
> > > > TBLSPACE_STATS 1 # Maintain tblspace statistics
> > > >
> > > > # System Archive Tape Device
> > > >
> > > > TAPEDEV /dev/tapedev # Tape device path
> > > >
> > > > TAPEBLK 32 # 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 32 # Log tape block size (Kbytes)
> > > >
> > > > LTAPESIZE 10240 # Max amount of data to put on log tape (Kbytes)
> > > >
> > > > # Optical
> > > >
> > > > STAGEBLOB # Informix Dynamic Server staging area
> > > >
> > > > # System Configuration
> > > >
> > > > SERVERNUM 1 # Unique id corresponding to a OnLine instance
> > > >
> > > > DBSERVERNAME fpt_server # Name of default database server
> > > >
> > > > DBSERVERALIASES # List of alternate dbservernames
> > > >
> > > > NETTYPE soctcp,4,150,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 20000 # Maximum number of shared buffers
> > > >
> > > > NUMAIOVPS # Number of IO vps
> > > >
> > > > PHYSBUFF 32 # Physical log buffer size (Kbytes)
> > > >
> > > > LOGBUFF 32 # Logical log buffer size (Kbytes)
> > > >
> > > > CLEANERS 1 # Number of buffer cleaner processes
> > > >
> > > > SHMBASE 0x30000000 # Shared memory base address
> > > >
> > > > SHMVIRTSIZE 87500 # initial virtual shared memory segment size
> > > >
> > > > SHMADD 16384 # Size of new shared memory segments (Kbytes)
> > > >
> > > > SHMTOTAL 419430 # Total shared memory (Kbytes). 0=>unlimited
> > > >
> > > > CKPTINTVL 150 # Check point interval (in sec)
> > > >
> > > > LRUS 8 # Number of LRU queues
> > > >
> > > > LRU_MAX_DIRTY 60.000000 # LRU percent dirty begin cleaning limit
> > > >
> > > > LRU_MIN_DIRTY 50.000000 # LRU percent dirty end cleaning limit
> > > >
> > > > TXTIMEOUT 0x12c # Transaction timeout (in sec)
> > > >
> > > > STACKSIZE 64
> > > >
> > > > # Dynamic Logging
> > > >
> > > > # DYNAMIC_LOGS:
> > > >
> > > > # 2 : server automatically add a new logical log when necessary.
(ON)
> > > >
> > > > # 1 : notify DBA to add new logical logs when necessary. (ON)
> > > >
> > > > # 0 : cannot add logical log on the fly. (OFF)
> > > >
> > > > #
> > > >
> > > > # When dynamic logging is on, we can have higher values for
> > > > LTXHWM/LTXEHWM,
> > > >
> > > > # because the server can add new logical logs during long
transaction
> > > > rollback.
> > > >
> > > > # However, to limit the number of new logical logs being added,
> > > > LTXHWM/LTXEHWM
> > > >
> > > > # can be set to smaller values.
> > > >
> > > > #
> > > >
> > > > # If dynamic logging is off, LTXHWM/LTXEHWM need to be set to
smaller
> > > > values
> > > >
> > > > # to avoid long transaction rollback hanging the server due to lack
of
> > > > logical
> > > >
> > > > # log space, i.e. 50/60 or lower.
> > > >
> > > > DYNAMIC_LOGS 2
> > > >
> > > > LTXHWM 70
> > > >
> > > > LTXEHWM 80
> > > >
> > > > # 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
> > > >
> > > > 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
> > > >
> > > > # CDR Variables
> > > >
> > > > CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)
> > > >
> > > > CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds)
> > > >
> > > > CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue
> > (Kbytes)
> > > >
> > > > CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max)
> > > >
> > > > CDR_SERIAL 0,0 # Serial Column Sequence
> > > >
> > > > CDR_DBSPACE # dbspace for syscdr database
> > > >
> > > > CDR_QHDR_DBSPACE # CDR queue dbspace (default same as catalog)
> > > >
> > > > CDR_QDATA_SBSPACE # List of CDR queue smart blob spaces
> > > >
> > > > # CDR_MAX_DYNAMIC_LOGS
> > > >
> > > > # -1 => unlimited
> > > >
> > > > # 0 => disable dynamic log addition
> > > >
> > > > # >0 => limit the no. of dynamic log additions with the specified
> > value.
> > > >
> > > > # Max dynamic log requests that CDR can make within one server
> > session.
> > > >
> > > > CDR_MAX_DYNAMIC_LOGS 0 # Dynamic log addition disabled by default
> > > >
> > > > # Backup/Restore variables
> > > >
> > > > BAR_ACT_LOG /usr/informix/bar_act.log # ON-Bar Log file - not in
/tmp
> > > > please
> > > >
> > > > BAR_DEBUG_LOG /usr/informix/bar_dbug.log
> > > >
> > > > # ON-Bar Debug Log - not in /tmp please
> > > >
> > > > BAR_MAX_BACKUP 0
> > > >
> > > > BAR_RETRY 1
> > > >
> > > > BAR_NB_XPORT_COUNT 10
> > > >
> > > > BAR_XFER_BUF_SIZE 31
> > > >
> > > > RESTARTABLE_RESTORE on
> > > >
> > > > BAR_PROGRESS_FREQ 0
> > > >
> > > > # Informix Storage Manager variables
> > > >
> > > > ISM_DATA_POOL ISMData
> > > >
> > > > ISM_LOG_POOL ISMLogs
> > > >
> > > > # 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 # Fill factor for building indexes
> > > >
> > > > # method for OnLine to use when determining current time
> > > >
> > > > USEOSTIME 0 # 0: use internal time(fast), 1: get time from OS(slow)
> > > >
> > > > # Parallel Database Queries (pdq)
> > > >
> > > > MAX_PDQPRIORITY 100 # Maximum allowed pdqpriority
> > > >
> > > > DS_MAX_QUERIES # Maximum number of decision support queries
> > > >
> > > > DS_TOTAL_MEMORY # Decision support memory (Kbytes)
> > > >
> > > > DS_MAX_SCANS 1048576 # Maximum number of decision support scans
> > > >
> > > > DATASKIP off # List of dbspaces to skip
> > > >
> > > > # OPTCOMPIND
> > > >
> > > > # 0 => Nested loop joins will be preferred (where
> > > >
> > > > # possible) over sortmerge joins and hash joins.
> > > >
> > > > # 1 => If the transaction isolation mode is not
> > > >
> > > > # "repeatable read", optimizer behaves as in (2)
> > > >
> > > > # below. Otherwise it behaves as in (0) above.
> > > >
> > > > # 2 => Use costs regardless of the transaction isolation
> > > >
> > > > # mode. Nested loop joins are not necessarily
> > > >
> > > > # preferred. Optimizer bases its decision purely
> > > >
> > > > # on costs.
> > > >
> > > > OPTCOMPIND 2 # To hint the optimizer
> > > >
> > > > DIRECTIVES 1 # Optimizer DIRECTIVES ON (1/Default) or OFF (0)
> > > >
> > > > ONDBSPACEDOWN 2 # Dbspace down option: 0 = CONTINUE, 1 = ABORT, 2 =
> > WAIT
> > > >
> > > > OPCACHEMAX 0 # Maximum optical cache size (Kbytes)
> > > >
> > > > # HETERO_COMMIT (Gateway participation in distributed transactions)
> > > >
> > > > # 1 => Heterogeneous Commit is enabled
> > > >
> > > > # 0 (or any other value) => Heterogeneous Commit is disabled
> > > >
> > > > HETERO_COMMIT 0
> > > >
> > > > SBSPACENAME # Default smartblob space name - this is where blobs
> > > >
> > > > # go if no sbspace is specified when the smartblob is
> > > >
> > > > # created. It is also used by some datablades as
> > > >
> > > > # the location to put their smartblobs.
> > > >
> > > > SYSSBSPACENAME # Default smartblob space for use by the Informix
> > > >
> > > > # Server. This is used primarily for Informix Server
> > > >
> > > > # system statistics collection.
> > > >
> > > > BLOCKTIMEOUT 3600 # Default timeout for system block
> > > >
> > > > SYSALARMPROGRAM /dbms/informix/etc/evidence.sh # System Alarm
program
> > path
> > > >
> > > > # Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
> > > >
> > > > OPT_GOAL -1
> > > >
> > > > ALLOW_NEWLINE 0 # embedded newlines(Yes = 1, No = 0 or anything but
1)
> > > >
> > > > #
> > > >
> > > > # The following are default settings for enabling Java in the
> > database.
> > > >
> > > > # Replace all occurrences of /usr/informix with the value of
> > $INFORMIXDIR.
> > > >
> > > > #VPCLASS jvp,num=1 # Number of JVPs to start with
> > > >
> > > > JVPJAVAHOME /usr/informix/extend/krakatoa/jre
> > > >
> > > > # JRE installation root directory
> > > >
> > > > JVPHOME /usr/informix/extend/krakatoa # Krakatoa installation
> > directory
> > > >
> > > > JVPPROPFILE /usr/informix/extend/krakatoa/.jvpprops # JVP property
> > file
> > > >
> > > > JDKVERSION 1.3 # JDK version supported by this server
> > > >
> > > > # The path to the JRE libraries relative to JVPJAVAHOME
> > > >
> > > > JVPJAVALIB /bin
> > > >
> > > > # The JRE libraries to use for the Java VM
> > > >
> > > > JVPJAVAVM hpi:jvm:java:net:zip:jpeg
> > > >
> > > > # use JVPARGS to change Java VM configuration
> > > >
> > > > #To display jni call
> > > >
> > > > #JVPARGS -verbose:jni
> > > >
> > > > # Classpath to use upon Java VM start-up (use _g version for
> > debugging)
> > > >
> > > > #JVPCLASSPATH
> > > >
> >
/usr/informix/extend/krakatoa/krakatoa_g.jar:/usr/informix/extend/krakatoa
> > > > /j
> > > > dbc_g.jar
> > > >
> > > > JVPCLASSPATH
> > > >
> >
/usr/informix/extend/krakatoa/krakatoa.jar:/usr/informix/extend/krakatoa/j
> > > > db
> > > > c.jar
> > > >
> > > > ================================================== =============
> > > >
> > > >
> > > >
> > > sending to informix-list
> >
> sending to informix-list