IDS Forum

RE: How can I use 32Gb of ram in IDS 9.4

Posted By: Wyza, Jonathon
Date: Wednesday, 12 May 2010, at 10:45 p.m.

In Response To: How can I use 32Gb of ram in IDS 9.4 (BRETT SIMPSON)

are you running 32-bit IDS or 64-bit IDS?

Jonathon Wyza
CX & CBORD System Administrator
CX Programmer/Analyst
Administrative Computing
Bethel College
(574)-257-3381
AIM: Iamwyza
jonathon.wyza@bethelcollege.edu
==============================
SLES 10x32 SP2 & IDS 10.00.UC9

“Mostly, when you see programmers, they aren’t doing anything. One of the attractive things about programmers is that you cannot tell whether or not they are working simply by looking at them. Very often they’re sitting there seemingly drinking coffee and gossiping, or just staring into space. What the programmer is trying to do is get a handle on all the individual and unrelated ideas that are scampering around in his head.”
– Charles M. Strauss

________________________________________
From: ids-bounces@iiug.org [ids-bounces@iiug.org] on behalf of BRETT SIMPSON [brett.simpson@actrol.com.au]
Sent: Wednesday, May 12, 2010 10:24 PM
To: ids@iiug.org
Subject: How can I use 32Gb of ram in IDS 9.4 [20124]

I have IDS9.4 on Suze 8.2 on a IBM 445 with 8 CPU and 32 Gb of ram

How Can I use more of the Ram ?

I have tried playing around with buffers but if I go past 280000 the instance
dosn't come on like and complains :

Segment locked: addr=0x44000000, size=1450098688
shmat: [ENOMEM][12]: out of available data space, check system memory
parameters (e.g. MAXMEM)

My onconfig is :

IBM Informix Dynamic Server Version 9.40.UC7 -- On-Line -- Up 02:37:54 --
2026892 Kbytes

Configuration File: /app/informix/etc/onconfig.actrol
#**************************************************************************
#
# IBM Corporation
#
# Title: onconfig.actrol
# Description: IBM Informix Dynamic Server Configuration Parameters
#
#**************************************************************************

# Root Dbspace Configuration

ROOTNAME rootdbs # Root dbspace name
ROOTPATH /database/chunk01 # Path for device containing root dbspace
ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes)
ROOTSIZE 2097152 # 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
PHYSDBS physlogdbs # Location (dbspace) of physical log
# PHYSFILE 200000 # Physical log file size (Kbytes)
PHYSFILE 10000000 # Physical log file size (Kbytes)

# Logical Log Configuration

LOGFILES 2500 # Number of logical log files
LOGSIZE 10000 # Logical log size (Kbytes)

# Diagnostics

MSGPATH /database/online.log # System message log file path
CONSOLE /dev/null # System console message path

# To automatically backup logical logs, edit alarmprogram.sh and set
# BACKUPLOGS=Y
ALARMPROGRAM /app/informix/etc/alarmprogram.sh # Alarm program path
TBLSPACE_STATS 1 # Maintain tblspace statistics

# System Archive Tape Device

TAPEDEV /dev/nst0 # Tape device path
# TAPEDEV /dev/null # Tape device path
TAPEBLK 128 # Tape block size (Kbytes)
TAPESIZE 21470000 # Maximum amount of data to put on tape (Kbytes)

# Log Archive Tape Device

LTAPEDEV /dev/zero # Log tape device path
#LTAPEDEV /dev/null # Log tape device path
LTAPEBLK 128 # Log tape block size (Kbytes)
LTAPESIZE 214700000 # Max amount of data to put on log tape (Kbytes)

# Optical

STAGEBLOB # Informix Dynamic Server staging area

# System Configuration

SERVERNUM 0 # Unique id corresponding to a OnLine instance
DBSERVERNAME sage # Name of default database server
# DBSERVERALIASES sage_tcp,sage_ext,sage_stream # List of alternate
dbservernames
DBSERVERALIASES sage_tcp,sage_ext # List of alternate dbservernames
NETTYPE ipcshm,1,800,CPU # Configure poll thread(s) for nettype
# NETTYPE ipcshm,1,400,CPU # Configure poll thread(s) for nettype
NETTYPE soctcp,1,600,NET # Configure poll thread(s) for nettype
NETTYPE soctcp,1,600,NET # Configure poll thread(s) for nettype
# NETTYPE soctcp,1,400,NET # Configure poll thread(s) for nettype
# NETTYPE soctcp,1,400,NET # Configure poll thread(s) for nettype
# NETTYPE ipcstr,1,400,CPU # 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

NOAGE 1 # Process aging
AFF_SPROC 0 # Affinity start processor
AFF_NPROCS 0 # Affinity number of processors

# Shared Memory Parameters

#LOCKS 2000000 # Maximum number of locks
LOCKS 2500000 # Maximum number of locks
BUFFERS 280000 # Maximum number of shared buffers
#BUFFERS 1120000 # Maximum number of shared buffers
#BUFFERS 560000 # Maximum number of shared buffers
NUMAIOVPS 10 # Number of IO vps
PHYSBUFF 256 # Physical log buffer size (Kbytes)
LOGBUFF 256 # Logical log buffer size (Kbytes)
CLEANERS 3 # Number of buffer cleaner processes
SHMBASE 0x44000000 # Shared memory base address
#SHMBASE 0x10000000 # Shared memory base address
SHMVIRTSIZE 1200000 # initial virtual shared memory segment size
SHMADD 200000 # Size of new shared memory segments (Kbytes)
SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited
CKPTINTVL 900 # Check point interval (in sec)
LRUS 200 # Number of LRU queues
LRU_MAX_DIRTY 5.500000 # LRU percent dirty begin cleaning limit
LRU_MIN_DIRTY 3.500000 # LRU percent dirty end cleaning limit
TXTIMEOUT 0x12c # Transaction timeout (in sec)
STACKSIZE 32 # Stack size (Kbytes)

# 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
#LTXHWM 92
LTXEHWM 80
#LTXEHWM 98

# 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 /app/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 /app/informix/bar_act.log # ON-Bar Log file - not in /tmp please
BAR_DEBUG_LOG /app/informix/bar_dbug.log

BAR_MAX_BACKUP 1
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31
RESTARTABLE_RESTORE on
BAR_PROGRESS_FREQ 5
#BAR_BSALIB_PATH /usr/lib/ibsad001.so
BAR_DEBUG 0
BAR_HISTORY 0

# Informix Storage Manager variables
ISM_DATA_POOL ISMData
ISM_LOG_POOL ISMDiskLogs

# Read Ahead Variables
RA_PAGES 64 # Number of pages to attempt to read ahead
RA_THRESHOLD 16 # 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 tempdbs,tempdbs2,tempdbs3 # 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 /work/data/informix/dump # 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 100 # 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
# 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 0 # To hint the optimizer

DIRECTIVES 1 # Optimizer DIRECTIVES ON (1/Default) or OFF (0)

ONDBSPACEDOWN 0 # 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 /app/informix/etc/evidence.sh # System Alarm program path

# Optimization goal: -1 = ALL_ROWS(Default), 0 = FIRST_ROWS
OPT_GOAL 0

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 /lib/i386/

# The JRE libraries to use for the Java VM

JVPJAVAVM hpi:server:verify: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/jdbc_g.jar
JVPCLASSPATH
/usr/informix/extend/krakatoa/krakatoa.jar:/usr/informix/extend/krakatoa/jdbc.jar

# Default locking mode to row for newly created tables.
DEF_TABLE_LOCKMODE ROW

Any Ideas of how I can use more of the ram ?

thanks

*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.

Messages In This Thread

• How can I use 32Gb of ram in IDS 9.4
  BRETT SIMPSON -- Wednesday, 12 May 2010, at 10:24 p.m.
  • RE: How can I use 32Gb of ram in IDS 9.4
    Knox, Ernest -- Wednesday, 12 May 2010, at 10:43 p.m.
  • RE: How can I use 32Gb of ram in IDS 9.4
    Wyza, Jonathon -- Wednesday, 12 May 2010, at 10:45 p.m.
    • RE: How can I use 32Gb of ram in IDS 9.4
      Knox, Ernest -- Wednesday, 12 May 2010, at 10:47 p.m.
      • RE: How can I use 32Gb of ram in IDS 9.4
        Joerg Volz -- Thursday, 13 May 2010, at 6:02 a.m.
  • Re: How can I use 32Gb of ram in IDS 9.4
    Art Kagel -- Thursday, 13 May 2010, at 11:31 a.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.