Hi,
please see my earlier e-mail (following below) on
the same subject but with onpload/HPL. (I was on
vacation and read my e-mails newest first
when I come back ... :)
Difference in your case is to use environment variable
INFORMIXSHMBASE for client application (instead of
PLOAD_SHMBASE) for onpload (HPL). Also, client
applications do not use the IFX_XFER_SHMBASE
environment variable as this is something specific to
HPL and backup/restore clients (like ontape and onbar).
The basic concept remains the same.
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
Notes: Martin Fuerderer/Germany/IBM@IBMDE
IBM Deutschland GmbH
Chairman of the Supervisory Board: Hans Ulrich Märki
Board of Management: Martin Jetter (Chairman), Rudolf Bauer, Christian
Diedrich, Christoph Grandpierre, Matthias Hartmann, Andreas Kerstan
Corporate Seat: Stuttgart, Germany; Reg.-Gericht: Amtsgericht Stuttgart,
HRB-Nr.: 14 562 WEEE-Reg.-Nr. DE 99369940
----- Forwarded by Martin Fuerderer/Germany/IBM on 12.04.2007 13:25 -----
Martin Fuerderer/Germany/IBM
12.04.2007 11:30
To
Floyd Wellershaus <fwellers@yahoo.com>
cc
informix-list@iiug.org, informix-list-bounces@iiug.org
Subject
Re: help with hp loader errors
Hi,
when a process attaches to shared memory (SHM), then the SHM
segment gets mapped into the processes memory space at some
address. Our processes (oninit, onpload, etc.) usually want to have
SHM segments mapped to their memory space so that several SHM
segments form a contiguous area in the processes memory space.
If some memory area in a processes memory space is already in
use by some other memory object (other SHM segment, shared
libraries, memory heap, memory stack, ...), then the mapping to
the desired address fails, i.e. the system call to do the attach and
mapping fails. This is what happens when a message is given like
"... could not attach ... shared memory segment ...".
onpload processes (created by HPL) are a bit complicated,
because they not only attach to SHM from the server, but they
also have their own SHM segments. Apart from that they may use
some extra memory in the heap and stack memory structures,
especially when run with some (externally implemented) conversion
routines.
By default onpload will try to map the servers SHM segments to
the servers SHMBASE address (as defined in the onconfig file).
Also, by default the onpload will want to map its own SHM segments
to some other address (that I don't know now - it is platform
dependent anyway).
If there is a problem like you see, then you can try to use the
IFX_XFER_SHMBASE environment variable for onpload to
define a different address where onpload will want to map the
servers SHM segments (instead of using the onconfig's SHMBASE).
Also, PLOAD_SHMBASE can be used to define a different address
for onpload where to map its own SHM segments. I think this was
added in some newer version (9.4 or 10.0?: I'm not sure) and I think
it also is an environment variable.
Using these parameters you can avoid that the mapping of SHM
segments into onploads memory space clashes with other
SHM segments or other memory objects already there. It can be
a bit tricky and may require some attempts to figure out useful
values. I guess from your info that you are on a 64-bit platform,
so memory space of processes should be big enough to find
some unused area. :)
You can try to figure out the memory space layout of a running
process. On Linux this is in a pseudo file (for each process)
named /proc/<pid>/maps (where <pid> is the process ID. User
root can look into this file and thus see the memory layout to
figure out where used and unused areas exist in the memory
space of this process.
I do not recommend changing the SHMBASE onconfig file
parameter. This is used by the server (for mapping the servers
own SHM segments into its own memory space). As long as the
server (i.e. the oninit processes) runs fine with a particular
setting of this parameter (and usually this is the value from
the onconfig.std file), I would not change this. (Only when
the server runs into trouble is the time to start fiddling
around with this parameter.)
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland GmbH
Chairman of the Supervisory Board: Hans Ulrich Märki
Board of Management: Martin Jetter (Chairman), Rudolf Bauer, Christian
Diedrich, Christoph Grandpierre, Matthias Hartmann, Andreas Kerstan
Corporate Seat: Stuttgart, Germany; Reg.-Gericht: Amtsgericht Stuttgart,
HRB-Nr.: 14 562 WEEE-Reg.-Nr. DE 99369940
"OMER KHAN" <oskhan@i2cinc.com>
Sent by: ids-bounces@iiug.org
06.04.2007 09:13
Please respond to
ids@iiug.org
To
ids@iiug.org
cc
Subject
Problem Connecting Database (Sahred Memory service [8776]
Hello All,
I have facing a very interesting problem, in which, when i try to connect
to
the database using dbaccess, it sometimes connects and sometimes give the
following error:
--------------------------------------------------------------------- -
25588: The appl process cannot connect to Dynamic Server ids_tsi5.
Invalid argument
------------------------------------------------------------------- ---
Although, It is a very common error that we mostly get when the database
is
not running(offline) but in my case i have verifed that database is
working
fine as well and to my surprise, while statying in the same dbaccess
interface, when i tried to connect it to using the 'ids_net_tsi5'
services, it
connected successfully.
----Entries from sqlhost File------------------------
ids_tsi5 onipcshm etp1 sqlturbo_tsi5
ids_net_tsi5 olsoctcp etp1 sql_net_tsi5
------------------------------------------------------
B ut this problem also occures rerely using 'ids_net_tsi5' service as
well.
Now i need to know the root cause of this error, so that i could rectify
it as
soon as possible. Our 4GL routine uses the shared memory service to
connect to
the database and due to this problem we are facing alot of issues.
Please check all the info provided and do suggest me any concrete
solutiuon to
rectify this issue. Do let me know in case of any additional information
is
required.
Thanks in advance for anticipation.
---------------
Regards,
Omer Saeed Khan
----------------
Here are the additional Informations:
Informix Version:
IDS 9.40.UC3
OS:
Red Hat Enterprise Linux AS release 4 (Nahant)(Linux version 2.6.9-5.ELsmp
(gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)))
Hardware:
Linux etp1 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005 i686 i686 i386
GNU/Linux
Processor:
Intel(R) Xeon(TM) CPU 2.80GHz (This is a 4 processor machine)
RAM: 3 GB
This is the onconfig File Setting:
onstat -c
IBM Informix Dynamic Server Version 9.40.UC3 -- On-Line -- Up 2 days
10:35:59
-- 222636 Kbytes
Configuration File: /u/informix/etc/onconfig_tsi5
#*********************************************
*****************************
#
# INFORMIX SOFTWARE, INC.
#
# Title: onconfig.std
# Description: Informix Dynamic Server Configuration Parameters
#
#***********************************************************
***************
# Root Dbspace Configuration
ROOTNAME rootdbs5 # Root dbspace name
ROOTPATH /u/ids_space/rootdbs5
# Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 512000 # 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 rootdbs5 # Location (dbspace) of physical log
PHYSFILE 4000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 60 # Number of logical log files
LOGSIZE 1000 # Logical log size (Kbytes)
# Diagnostics
MSGPATH /u/informix/online.log5 # System message log file path
CONSOLE /dev/console # System console message path
ALARMPROGRAM /u/informix/etc/log_full.sh6 # Alarm program path
SYSALARMPROGRAM /u/informix/etc/evidence.sh # System Alarm program path
TBLSPACE_STATS 1
# System Archive Tape Device
TAPEDEV /u/informix/onconfig_tsi5.level.0.fifo # Tape device path
TAPEBLK 128 # Tape block size (Kbytes)
TAPESIZE 20480000 # Maximum amount of data to put on tape (Kbytes)
# Log Archive Tape Device
LTAPEDEV /y/ABS_backups/informix/logical/ids_tsi5.log # Tape device path
LTAPEBLK 128 # Log tape block size (Kbytes)
LTAPESIZE 2048000 # Max amount of data to put on log tape (Kbytes)
# Optical
STAGEBLOB # Informix Dynamic Server/Optical staging area
# System Configuration
SERVERNUM 1 # Unique id corresponding to a Dynamic Server instance
DBSERVERNAME ids_tsi5 # Name of default database server
DBSERVERALIASES ids_net_tsi5 # List of alternate dbservernames
NETTYPE ipcshm,4,50,CPU # Configure poll thread(s) for nettype
NETTYPE soctcp,4,50,NET # 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 for multi-processor
NUMCPUVPS 4 # Number of user (cpu) vps
SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one
NUMAIOVPS 8 # Number of IO vps
NOAGE 1 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 4 # Affinity number of processors
# Shared Memory Parameters
LOCKS 2000000 # Maximum number of locks
BUFFERS 5000 # Maximum number of shared buffers
PHYSBUFF 64 # Physical log buffer size (Kbytes)
LOGBUFF 64 # Logical log buffer size (Kbytes)
CLEANERS 8 # Number of buffer cleaner processes
SHMBASE 0x10000000 # Shared memory base address
SHMVIRTSIZE 32000 # initial virtual shared memory segment size
SHMADD 8192 # Size of new shared memory segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
#SHMTOTAL 256000 # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL 300 # 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
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 - Dynamic Server no longer supports this configuration
parameter.
# To determine the page size used by Dynamic Server 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
DRINTERVAL 30 # DR max time between DR buffer flushes (in sec)
DRTIMEOUT 30 # DR network timeout (in sec)
DRLOSTFOUND /u/informix/etc/dr.lostfound.tsi5 # 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)
# Backup/Restore variables
BAR_ACT_LOG /tmp/bar_act.log5
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31
# Informix Storage Manager variables
ISM_DATA_POOL ISMData # If the data pool name is changed, be sure to
# update $INFORMIXDIR/bin/onbar. Change to
# ism_catalog -create_bootstrap -pool <new name>
ISM_LOG_POOL ISMLogs
# Read Ahead Variables
RA_PAGES 2 # Number of pages to attempt to read ahead
RA_THRESHOLD # Number of pages left before next group
# DBSPACETEMP:
# Dynamic Server equivalent of DBTEMP for SE. This is the list of dbspaces
# that the Dynamic Server SQL Engine will use to create temp tables etc.
# If specified it must be a colon separated list of dbspaces that exist
# when the Dynamic Server 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 tempdbs5 # 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 Dynamic Server 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 Dynamic Server)
DUMPCNT 1 # Number of shared memory or gcore dumps for
# a single user's session
FILLFACTOR 90 # Fill factor for building indexes
# method for Dynamic Server 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
# 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
OPTCOMPIND 0 # To hint the optimizer
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
# Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
OPT_GOAL -1
# Optimizer DIRECTIVES ON (1/Default) or OFF (0)
DIRECTIVES 1
# Status of restartable restore
RESTARTABLE_RESTORE off
CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max)
#TAPEDEV /dev/null # Tape device path
DYNAMIC_LOGS 0
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 0 # Dynamic log addition disabled by default
BAR_DEBUG_LOG /tmp/bar_dbug.log # ON-Bar Debug Log - not in /tmp please
BAR_PROGRESS_FREQ 0
SBSPACENAME # Default smartblob space name - this is where blobs
SYSSBSPACENAME # Default smartblob space for use by the Informix
BLOCKTIMEOUT 3600 # Default timeout for system block
ALLOW_NEWLINE 0 # embedded newlines(Yes = 1, No = 0 or anything but 1)
JVPJAVAHOME # JRE installation root directory
JVPHOME # Krakatoa installation directory
JVPPROPFILE .jvpprops # JVP property file
JDKVERSION # JDK version supported by this server
JVPJAVALIB
JVPJAVAVM libjava.so
JVPCLASSPATH
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
