Informix ONCONFIG Parameters

Every ONCONFIG parameter from a real, current Informix Dynamic Server onconfig.std, one line each with a link to IBM's own documentation for the full detail. Descriptions below are a short summary in our own words — follow the link for the complete, authoritative reference, including the full list of acceptable values.

232 parameters.

ROOTNAME: The name of the root dbspace, which contains reserved pages and internal tracking tables. IBM documentation →
ROOTPATH: The path for the device containing the root chunk. IBM documentation →
ROOTOFFSET: The starting offset, in KB, of the primary root chunk. An offset is required for some raw devices. IBM documentation →
ROOTSIZE: The size of the root chunk, in KB. The value of 300000 allows for a default user space of about 180 MB and the default system space requirements. IBM documentation →
MIRRORPATH: The path for the device containing the root chunk's mirror (optional). IBM documentation →
MIRROROFFSET: The starting offset, in KB, of the root chunk's mirror. IBM documentation →
PHYSFILE: The size, in KB, of the physical log on disk. If RTO_SERVER_RESTART is enabled, the suggested formula for the size of PHSYFILE (up to about 1 GB) is: PHYSFILE = Size of BUFFERS * 1.1. IBM documentation →
PLOG_OVERFLOW_PATH: The directory for extra physical log data if the physical log overflows during recovery or long transaction rollback. IBM documentation →
PHYSBUFF: The size of the physical log buffer, in KB. IBM documentation →
LOGFILES: The number of logical log files. IBM documentation →
LOGSIZE: The size of each logical log, in KB. IBM documentation →
DYNAMIC_LOGS: The type of dynamic log allocation. IBM documentation →
LOGBUFF: The size of the logical log buffer, in KB. IBM documentation →
LTXHWM: The percentage of the logical logs that can be filled before a transaction is determined to be a long transaction and is rolled back. IBM documentation →
LTXEHWM: The percentage of the logical logs filled before the server suspends all other transactions so a long-transaction rollback has exclusive use of the logs. IBM documentation →
MSGPATH: The path of the server message log file. IBM documentation →
MSG_DATE: Customize the date or time preceding each message written to MSGPATH. MSG_DATE values result in these formats. IBM documentation →
CONSOLE: The path of the server console message file. IBM documentation →
TBLTBLFIRST: The first extent size, in KB, for the tblspace tblspace. Must be in multiples of the page size. IBM documentation →
TBLTBLNEXT: The next extent size, in KB, for the tblspace tblspace. Must be in multiples of the page size. IBM documentation →
TBLSPACE_STATS: Enables (1) or disables (0) the server to maintain tblspace statistics. IBM documentation →
DBSPACETEMP: The list of dbspaces used to store temporary tables and other objects. Specify a colon separated list of dbspaces that exist when the server is started. IBM documentation →
SBSPACETEMP: The list of sbspaces used to store temporary tables for smart large objects. If no sbspace is specified, temporary files are created in a standard sbspace. IBM documentation →
SBSPACENAME: The default sbspace name where smart large objects are stored if no sbspace is specified during smart large object creation. Some DataBlade modules store smart large objects in this location. IBM documentation →
SYSSBSPACENAME: The default sbspace for system statistics collection. Otherwise, the server stores statistics in the sysdistrib system catalog table. IBM documentation →
ONDBSPACEDOWN: Specifies how the server behaves when it encounters a dbspace that is offline. IBM documentation →
SERVERNUM: The unique ID for the server instance. Acceptable values are 0 through 255, inclusive. IBM documentation →
DBSERVERNAME: The name of the default database server. IBM documentation →
DBSERVERALIASES: The list of up to 32 alternative dbservernames, separated by commas. IBM documentation →
FULL_DISK_INIT: Specifies if oninit -i can run. IBM documentation →
NETTYPE: The configuration of poll threads for a specific protocol. IBM documentation →
LISTEN_TIMEOUT: The number of seconds that the server waits for a connection. IBM documentation →
MAX_INCOMPLETE_CONNECTIONS: The maximum number of incomplete connections before the server logs a Denial of Service (DoS) error. IBM documentation →
FASTPOLL: Enables (1) or disables (0) fast polling of your network, if your operating system supports it. IBM documentation →
NUMFDSERVERS: The maximum number of poll threads to handle. IBM documentation →
NS_CACHE: The number of seconds for Informix name service cache (host, service, user, group, sqlhosts) expiration time. A value of 0 disables the cache. IBM documentation →
NET_IO_TIMEOUT_ALARM: Controls notifications about blocked network write operations. <num1>[,<num2>[,<num3>]] <num1> - Network categories where the timeout applies. IBM documentation →
DRDA_COMMBUFFSIZE: Specifies size of the DRDA communications buffer. IBM documentation →
MULTIPROCESSOR: Specifies whether the computer has multiple CPUs. IBM documentation →
VPCLASS: Configures a class of virtual processors (cpu, aio, jvp, and so on) — the number to start, an optional maximum, and CPU affinity. IBM documentation →
VP_MEMORY_CACHE_KB: Specifies the amount of private memory blocks of your CPU VP, in KB, that the database server can access and whether the memory changes dynamically (default). IBM documentation →
SINGLE_CPU_VP: Optimizes performance if the server runs with only one CPU VP. IBM documentation →
AUTO_TUNE: The default value for the other AUTO_* auto-tuning parameters (AUTO_AIOVPS, AUTO_CKPTS, AUTO_REPREPARE, AUTO_STAT_MODE, AUTO_READAHEAD, AUTO_LRU_TUNING) when they aren't set individually. IBM documentation →
AUTO_READAHEAD: Controls automatic read-ahead mode and tuning — the modern replacement for the old RA_PAGES/RA_THRESHOLD pair. Defaults from AUTO_TUNE when not set. IBM documentation →
CLEANERS: The number of page cleaner threads. IBM documentation →
DIRECT_IO: A set of hex flags controlling direct I/O, concurrent I/O, and special I/O for TEMP dbspaces. IBM documentation →
LOCKS: The initial number of locks when the server starts. Dynamic locking can add extra locks if needed. IBM documentation →
DEF_TABLE_LOCKMODE: The default table lock mode for new tables. Acceptable values are ROW and PAGE (default). IBM documentation →
RESIDENT: Controls whether shared memory is resident. IBM documentation →
SHMBASE: The shared memory base address; do not change. IBM documentation →
SHMVIRTSIZE: The initial size, in KB, of the virtual segment of shared memory. IBM documentation →
SHMADD: The size, in KB, of additional virtual shared memory segments. IBM documentation →
EXTSHMADD: The size, in KB, of each extension shared memory segment. IBM documentation →
SHMTOTAL: The maximum amount of shared memory for the server, in KB. A 0 indicates no specific limit. IBM documentation →
SHMVIRT_ALLOCSEG: Controls when the server adds a memory segment and the alarm level if the memory segment cannot be added. For the first field, acceptable values are: . IBM documentation →
SHMNOACCESS: A list of up to 10 memory address ranges that the server cannot use to attach shared memory. Each address range is the start and end memory address in hex format, separated by a hyphen. IBM documentation →
CKPTINTVL: Specifies how often, in seconds, the server checks if a checkpoint is needed. 0 indicates that the server does not check for checkpoints. Ignored if RTO_SERVER_RESTART is set. IBM documentation →
RTO_SERVER_RESTART: Specifies, in seconds, the Recovery Time Objective for the server restart after a server failure. Acceptable values are 0 (off) and any number from 60-1800, inclusive. IBM documentation →
BLOCKTIMEOUT: Specifies the amount of time, in seconds, for a system block. IBM documentation →
CONVERSION_GUARD: To turn on conversion guard feature. - 0 - Off, - 1 - On, Abort conversion on Conversion Guard error, - 2 - On, Continue conversion; ignore Conversion Guard error. IBM documentation →
RESTORE_POINT_DIR: The directory, which stores the Conversion Guard - feature generated files. IBM documentation →
TXTIMEOUT: The distributed transaction timeout, in seconds. IBM documentation →
DEADLOCK_TIMEOUT: The maximum time, in seconds, to wait for a lock in a distributed transaction. IBM documentation →
HETERO_COMMIT: Enables (1) or disables (0) heterogeneous commits for a distributed transaction involving an EGM gateway. IBM documentation →
TAPEDEV: The tape device path for backups. To use standard I/O instead of a device, set to STDIO. IBM documentation →
TAPEBLK: The tape block size, in KB, for backups. IBM documentation →
TAPESIZE: The maximum amount of data to put on one backup tape. Acceptable values are 0 (unlimited) or any positive integral multiple of TAPEBLK. IBM documentation →
LTAPEDEV: The tape device path for logical logs. IBM documentation →
LTAPEBLK: The tape block size, in KB, for backing up logical logs. IBM documentation →
LTAPESIZE: The maximum amount of data to put on one logical log tape. Acceptable values are 0 (unlimited) or any positive integral multiple of LTAPEBLK. IBM documentation →
BAR_ACT_LOG: The ON-Bar activity log file location. Do not use the /tmp directory. IBM documentation →
BAR_DEBUG_LOG: The ON-Bar debug log file location. Do not use the /tmp directory. IBM documentation →
BAR_DEBUG: The debug level for ON-Bar. Acceptable values are 0 (off) through 9 (high). IBM documentation →
BAR_MAX_BACKUP: The number of backup or restore processes used in a backup or restore. Acceptable values are 0 (unlimited) or any positive integer. IBM documentation →
BAR_MAX_RESTORE: The number of restore processes used in a restore. Acceptable values are 0 (unlimited) or any positive integer. IBM documentation →
BAR_RETRY: Specifies the number of time to retry a backup or restore operation before reporting a failure. IBM documentation →
BAR_NB_XPORT_COUNT: Specifies the number of data buffers that each onbar_d process uses to communicate with the database server. IBM documentation →
BAR_XFER_BUF_SIZE: The size, in pages, of each data buffer. Acceptable values are 1 through 15 for 4 KB pages and 1 through 31 for 2 KB pages. IBM documentation →
RESTARTABLE_RESTORE: Enables ON-Bar to continue a backup after a failure. Acceptable values are OFF or ON. IBM documentation →
BAR_PROGRESS_FREQ: Specifies, in minutes, how often progress messages are placed in the ON-Bar activity log. IBM documentation →
BAR_BSALIB_PATH: The shared library for ON-Bar and the storage manager. The default value is $INFORMIXDIR/lib/ibsad001 (with a platform-specific file extension). IBM documentation →
BACKUP_FILTER: Specifies the pathname of a filter program to transform data during a backup, plus any program options. IBM documentation →
RESTORE_FILTER: Specifies the pathname of a filter program to transform data during a restore, plus any program options. IBM documentation →
BAR_PERFORMANCE: Specifies the type of performance statistics to report to the ON-Bar activity log for backup and restore operations. IBM documentation →
BAR_CKPTSEC_TIMEOUT: Time in seconds to wait for an archive checkpoint to complete in the secondary server. IBM documentation →
BAR_SEC_ALLOW_BACKUP: Allows to perform backups in secondary servers. IBM documentation →
BAR_HISTORY: Specifies whether the sysutils database maintains a backup history when you use onsmsync to expire old backups. IBM documentation →
PSM_DBS_POOL: The Pool where to place dbspace data. The default is "DBSPOOL". IBM documentation →
PSM_LOG_POOL: The Pool where to place log data. The default is "LOGPOOL". IBM documentation →
DD_HASHSIZE: The number of data dictionary pools. Set to any positive integer; a prime number is recommended. IBM documentation →
DD_HASHMAX: The number of entries per pool. Set to any positive integer. IBM documentation →
DS_HASHSIZE: The number of data distribution pools. Set to any positive integer; a prime number is recommended. IBM documentation →
DS_POOLSIZE: The maximum number of entries in the data distribution cache. Set to any positive integer. IBM documentation →
PC_HASHSIZE: The number of UDR pools. Set to any positive integer; a prime number is recommended. IBM documentation →
PC_POOLSIZE: The maximum number of entries in the UDR cache. Set to any positive integer. IBM documentation →
PRELOAD_DLL_FILE: Specifies a C UDR shared library path name to load when the server starts. Each shared library file needs a separate PRELOAD_DLL_FILE entry. IBM documentation →
STMT_CACHE: Controls SQL statement caching. IBM documentation →
STMT_CACHE_HITS: The number of times an SQL statement must be executed before becoming fully cached. 0 indicates that all statements are fully cached the first time. IBM documentation →
STMT_CACHE_SIZE: The size, in KB, of the SQL statement cache. IBM documentation →
STMT_CACHE_NOLIMIT: Controls additional memory consumption. IBM documentation →
STMT_CACHE_NUMPOOL: The number of pools for the SQL statement cache. IBM documentation →
STMT_CACHE_QUERY_PLAN: Stores query plan for each SQL statement. IBM documentation →
USEOSTIME: The precision of SQL statement timing. Accepted values are 0 (precision to seconds) and 1 (precision to subseconds). IBM documentation →
STACKSIZE: The size, in KB, for a session stack. IBM documentation →
ALLOW_NEWLINE: Controls whether embedded new line characters in string literals are allowed in SQL statements. Acceptable values are 1 (allowed) and any number other than 1 (not allowed). IBM documentation →
USELASTCOMMITTED: Controls the committed read isolation level. IBM documentation →
FILLFACTOR: The percentage of index page fullness. IBM documentation →
MAX_FILL_DATA_PAGES: Enables (1) or disables (0) filling data pages that have variable length rows as full as possible. IBM documentation →
BTSCANNER: Specifies the configuration settings for all btscanner threads. IBM documentation →
ONLIDX_MAXMEM: The amount of memory, in KB, allocated for the pre-image pool and updator log pool for each partition. IBM documentation →
MAX_PDQPRIORITY: The maximum amount of resources, as a percentage, that PDQ can allocate to any one decision support query. IBM documentation →
DS_MAX_QUERIES: The maximum number of concurrent decision support queries. IBM documentation →
DS_TOTAL_MEMORY: The maximum amount, in KB, of decision support query memory. IBM documentation →
DS_MAX_SCANS: The maximum number of concurrent decision support scans. IBM documentation →
DS_NONPDQ_QUERY_MEM: The amount of non-PDQ query memory, in KB. Acceptable values are 128 to 25% of DS_TOTAL_MEMORY. IBM documentation →
DATASKIP: Specifies whether to skip dbspaces when processing a query. IBM documentation →
OPTCOMPIND: Controls how the optimizer determines the best query path. IBM documentation →
DIRECTIVES: Specifies whether optimizer directives are enabled (1) or disabled (0). Default is 1. IBM documentation →
EXT_DIRECTIVES: Controls the use of external SQL directives. IBM documentation →
OPT_GOAL: Controls how the optimizer should optimize for fastest retrieval. IBM documentation →
IFX_FOLDVIEW: Enables (1) or disables (0) folding views that have multiple tables or a UNION ALL clause. Disabled by default. IBM documentation →
IFX_FLATSUBQ: Enables (1) or disables (0) flattenning subqueries. Enabled by default. IBM documentation →
STATCHANGE: In automatic mode, rebuild statistics only for table, fragment or index changed by STATCHANGE percentage since last statistics run. IBM documentation →
USTLOW_SAMPLE: Enables (1) or disables (0) the use of sampling during update statistics low operations that gather index statistics for large indexes. IBM documentation →
BATCHEDREAD_TABLE: Turn on/off xps api for table scans. IBM documentation →
BATCHEDREAD_INDEX: Turn on/off xps api for index scans. IBM documentation →
EXPLAIN_STAT: Enables (1) or disables (0) including the Query Statistics section in the EXPLAIN output file. IBM documentation →
IFX_EXTEND_ROLE: Controls whether administrators can use the EXTEND role to specify which users can register external routines. IBM documentation →
SECURITY_LOCALCONNECTION: Specifies whether the server performs security checking for local connections. IBM documentation →
UNSECURE_ONSTAT: Controls whether non-DBSA users are allowed to run all onstat commands. IBM documentation →
ADMIN_USER_MODE_WITH_DBSA: Controls who can connect to the server in administration mode. IBM documentation →
ADMIN_MODE_USERS: Specifies the user names, separated by commas, who can connect to the server in administration mode, in addition to the user informix. IBM documentation →
SSL_KEYSTORE_LABEL: The label, up to 512 characters, of the server certificate used in Secure Sockets Layer (SSL) protocol communications. IBM documentation →
TLS_VERSION: Specifies which TLS levels will be allowed. Default is 1.2. IBM documentation →
PLCY_POOLSIZE: The maximum number of entries in each hash bucket of the LBAC security information cache. IBM documentation →
PLCY_HASHSIZE: The number of hash buckets in the LBAC security information cache. IBM documentation →
USRC_POOLSIZE: The maximum number of entries in each hash bucket of the LBAC credential memory cache. IBM documentation →
USRC_HASHSIZE: The number of hash buckets in the LBAC credential memory cache. IBM documentation →
SQL_LOGICAL_CHAR: Enable/Disable the expansion of size specification for built-in character data types. IBM documentation →
SEQ_CACHE_SIZE: Maximum number of sequence objects that can have preallocated values in sequence cache. IBM documentation →
ENCRYPT_HDR: Enables (1) or disables (0) encryption for HDR. IBM documentation →
ENCRYPT_SMX: Controls the level of encryption for RSS and SDS servers. IBM documentation →
ENCRYPT_CDR: Controls the level of encryption for ER. IBM documentation →
ENCRYPT_CIPHERS: A list of encryption ciphers and modes, separated by commas. Default is all. IBM documentation →
ENCRYPT_MAC: Controls the level of message authentication code (MAC). Acceptable values are off, high, medium, and low. IBM documentation →
ENCRYPT_MACFILE: The paths of the MAC key files, separated by commas. Use the builtin keyword to specify the built-in key. IBM documentation →
ENCRYPT_SWITCH: Defines the frequencies, in minutes, at which ciphers and keys are renegotiated. IBM documentation →
CDR_EVALTHREADS: The number of evaluator threads per CPU VP and the number of additional threads, separated by a comma. IBM documentation →
CDR_DSLOCKWAIT: The number of seconds the Datasync waits for database locks. IBM documentation →
CDR_QUEUEMEM: The maximum amount of memory, in KB, for the send and receive queues. IBM documentation →
CDR_NIFCOMPRESS: Controls the network interface compression level. IBM documentation →
CDR_SERIAL: Specifies the incremental size and the starting value of replicated serial columns. IBM documentation →
CDR_DBSPACE: The dbspace name for the syscdr database. IBM documentation →
CDR_QHDR_DBSPACE: The name of the transaction record dbspace. Default is the root dbspace. IBM documentation →
CDR_QDATA_SBSPACE: The names of sbspaces for spooled transaction data, separated by commas. IBM documentation →
CDR_SUPPRESS_ATSRISWARN: The Datasync error and warning code numbers to be suppressed in ATS and RIS files. IBM documentation →
CDR_DELAY_PURGE_DTC: Specifies the time at which delete table purge can be delayed. IBM documentation →
CDR_LOG_LAG_ACTION: Specifies the action when ER log processing lags behind the current log. Separate multiple actions with a plus sign (+). IBM documentation →
CDR_LOG_STAGING_MAXSIZE: Maximum size, in KB (default), MB, GB, or TB, that ER can use to stage log files in the directory specified by the LOG_STAGING_DIR configuration parameter. ER temporarily stops staging log files, at a log file boundary, when the staging directory reaches this value. IBM documentation →
CDR_MAX_DYNAMIC_LOGS: The maximum number of dynamic log requests that ER can make within one server session. IBM documentation →
DRAUTO: Controls automatic failover for HDR systems. If the connection manager is providing failover, then the only value which should be used is '3'. IBM documentation →
DRINTERVAL: The maximum interval, in seconds, between HDR buffer flushes. Valid for HDR only. IBM documentation →
HDR_TXN_SCOPE: Defines transactional synchronization in the HDR primary when DRINTERVAL is turned off The default is NEAR_SYNC. IBM documentation →
DRTIMEOUT: The time, in seconds, before a network timeout occurs. Valid for HDR only. IBM documentation →
DRLOSTFOUND: The path of the HDR lost-and-found file. Valid of HDR only. IBM documentation →
DRIDXAUTO: Enables (1) or disables (0) automatic index repair for an HDR pair. Default is 0. IBM documentation →
HA_ALIAS: The server alias for a high-availability cluster. Must be the same as a value of DBSERVERNAME or DBSERVERALIASES that uses a network-based connection type. IBM documentation →
HA_FOC_ORDER: The cluster failover rules. Values are MANUAL or some order of SDS,HDR,RSS. IBM documentation →
LOG_INDEX_BUILDS: Enable (1) or disable (0) index page logging. Required for RSS. IBM documentation →
SDS_ENABLE: Enables (1) or disables (0) an SDS server. Set this value on an SDS server after setting up the primary. IBM documentation →
SDS_TIMEOUT: The time, in seconds, that the primary waits for an acknowledgement from an SDS server while performing page flushing before marking the SDS server as down. Valid for SDS only. IBM documentation →
SDS_TEMPDBS: The temporary dbspace used by an SDS server. IBM documentation →
SDS_ALTERNATE: Define an alternate means of communicating between the primary and SDS node. This is used if the normal network communication between the primary and secondary becomes unavailable. IBM documentation →
SDS_FLOW_CONTROL: Defines the point at which SDS flow control will be activated. Values defined as being SDS_FLOW_CONTROL <start>,<end> where start is the point at which flow control is activated and end is the point at which it deactivated. IBM documentation →
SDS_PAGING: The paths of two buffer paging files, Separated by a comma. Valid for SDS only. IBM documentation →
SDS_LOGCHECK: The time, in seconds, that the SDS server waits to detect if the primary server is generating log activity before allowing failover to the secondary server. IBM documentation →
UPDATABLE_SECONDARY: Controls whether secondary servers can accept update, insert, and delete operations from clients. If enabled, specifies the number of connection threads between the secondary and primary servers for transmitting updates from the secondary. IBM documentation →
FAILOVER_CALLBACK: Specifies the path and program name called when a secondary server transitions to a standard or primary server. Valid for HDR, SDS, and RSS. IBM documentation →
TEMPTAB_NOLOG: Controls the default logging mode for temporary tables that are explicitly created with the CREATE TEMP TABLE or SELECT INTO TEMP statements. Secondary servers must not have logged temporary tables. IBM documentation →
DELAY_APPLY: On an RS secondary server, specifies an amount of time to delay application of received logical logs. ###[unit] using one of the following units: D - Days H - Hours M - Minutes S - Seconds (default unit). IBM documentation →
STOP_APPLY: On an RS secondary server, stops, or specifies a time to stop the application of logical logs. 1 Stop application. IBM documentation →
LOG_STAGING_DIR: Specifies a directory in which to stage log files. IBM documentation →
RSS_FLOW_CONTROL: Defines the point at which RSS flow control will be activated. Values defined as being RSS_FLOW_CONTROL <start>,<end> where start is the point at which flow control is activated and end is the point at which it deactivated. IBM documentation →
FAILOVER_TX_TIMEOUT: Specifies the timeout for a failover to take before transaction survival is abandonded. IBM documentation →
ENABLE_SNAPSHOT_COPY: Specifies whether we can clone this instance Directly to another machine using the Snapshot Clone facility. 1 - Enable snapshot copies 0 - Disable snapshot copies. IBM documentation →
SMX_NUMPIPES: Defines the number of network pipes to be used by RSS. This value is used to set the level of network threading for SMX, which can increase the transfer rates on slower network connections. IBM documentation →
SMX_COMPRESS: Controls the network interface compression level. IBM documentation →
SMX_PING_INTERVAL: Specifies the maximum number of seconds to wait before closing a network connection to an unresponsive peer server. IBM documentation →
SMX_PING_RETRY: Specifies the number of times to repeat SMX_PING_INTERVAL before closing a connection. Can be any positive numeric value. IBM documentation →
CLUSTER_TXN_SCOPE: Defines the scope of the awareness of a transaction executing on a cluster. This defines the scope of that transaction's updates as part of the commit. IBM documentation →
SEC_NONBLOCKING_CKPT: Enable non-blocking checkpoint at HDR / RSS 1 - Enable non-blocking checkpoints, continue log replay while flushing modified buffers to disk during checkpoint operation. 0 - (Default) Disable non-blocking checkpoints. IBM documentation →
SEC_APPLY_POLLTIME: In micro seconds, how long apply thread should poll for new work before yielding. Recommended value for smaller systems (between 1 to 8 CPUVPs). IBM documentation →
SEC_LOGREC_MAXBUFS: Configure number of 16K buffers to be used for replaying log records. If set to zero, default value. IBM documentation →
SEC_DR_BUFS: Configure number of DR buffers to be used for replicating log records to secondary server. Buffer size is same as LOGBUFF config value. IBM documentation →
ON_RECVRY_THREADS: The number of logical recovery threads that run in parallel during a warm restore. IBM documentation →
OFF_RECVRY_THREADS: The number of logical recovery threads used in a cold restore. Also, the number of threads used during fast recovery. IBM documentation →
DUMPDIR: The location Assertion Failure (AF) diagnostic files. IBM documentation →
DUMPSHMEM: Controls shared memory dumps. IBM documentation →
DUMPGCORE: Enables (1) or disables (0) whether the server dumps a core using gcore. IBM documentation →
DUMPCORE: Enables (1) or disables (0) whether the server dumps a core after an AF. IBM documentation →
DUMPCNT: An integer representing the maximum number of shared memory dumps or core files for a single thread, or, for managed shared memory dumps, the extended format: thrdlimit=<#>,instlimit=<#>,insttime=<#>,interval=<#> where all parameters are optional and have these meanings: - thrdlimit = max number of shared memory dumps per thread - instlimit = max number of shared memory dumps for the instance in the time period defined by insttime. The default value value of 0 implies no limit. IBM documentation →
ALARMPROGRAM: Specifies the alarm program to display event alarms. To enable automatic logical log backup, edit alarmprogram.sh and set BACKUPLOGS=Y. IBM documentation →
ALRM_ALL_EVENTS: Controls whether the alarm program runs for every event. IBM documentation →
STORAGE_FULL_ALARM: <time interval in seconds>,<alarm severity> specifies in what interval: - a message will be printed to the online.log file - an alarm will be raised when - a dbspace becomes full (ISAM error -131) - a partition runs out of pages or extents (ISAM error -136) time interval = 0 : OFF severity = 0 : no alarm, only message. IBM documentation →
SYSALARMPROGRAM: Specifies the system alarm program triggered when an AF occurs. IBM documentation →
RAS_PLOG_SPEED: Technical Support diagnostic parameter. Do not change; automatically updated. IBM documentation →
RAS_LLOG_SPEED: Technical Support diagnostic parameter. Do not change; automatically updated. IBM documentation →
EILSEQ_COMPAT_MODE: Controls whether when processing characters, the server checks if the characters are valid for the locale and returns error -202 if they are not. IBM documentation →
QSTATS: Enables (1) or disables (0) the collection of queue statistics that can be viewed with onstat -g qst. IBM documentation →
WSTATS: Enables (1) or disables (0) the collection of wait statistics that can be viewed with onstat -g wst. IBM documentation →
USERMAPPING: Control access to the server for users without operating system accounts. IBM documentation →
SP_AUTOEXPAND: When set to 1, the server will automatically expand spaces that are low on or out of free pages. Set this param to 0 to disable automatic chunk extensions and chunk additions. IBM documentation →
SP_THRESHOLD: Minimum amount of free space in a DBspace, BLOBspace, or Smart BLOBspace before the space will automatically be expanded. Value is a decimal, and can be an absolute number of kilobytes or a percentage of the total size in the DBspace. IBM documentation →
SP_WAITTIME: Access to the storage pool is serialized. When one thread is accessing the storage pool, SP_WAITIME is the number of seconds another thread will wait before giving up on its own access. IBM documentation →
AUTOLOCATE: When creating a database, table, or index, a Dbspace may be specified for the object's location. If no space is specified, and AUTOLOCATE is set to an integer between 1 and 32, the server will locate these objects for optimal performance and space utilization. IBM documentation →
DEFAULTESCCHAR: The default escape character. If not defined, '\' is used as escape character. IBM documentation →
MQSERVER: Specifies the location of the WebSphere MQ server and the communication method to be used. IBM documentation →
MQCHLLIB: Specifies the path to the directory containing the client channel definition table. IBM documentation →
MQCHLTAB: Specifies the name of the client channel definition table. IBM documentation →
REMOTE_SERVER_CFG: Specifies the name of a file that lists the remote hosts that are trusted by the computer on which the database server resides. The file specified must be located in $INFORMIXDIR/etc. IBM documentation →
REMOTE_USERS_CFG: Specifies the name of a file that lists names of trusted users that exist on remote hosts. The file specified must be located in $INFORMIXDIR/etc. IBM documentation →
S6_USE_REMOTE_SERVER_CFG: Specifies that the server will use the value for REMOTE_SERVER_CFG rather than $INFORMIXDIR/etc/hosts.equiv when using secured ER/HDR connections (i.e. s=6). IBM documentation →
LOW_MEMORY_RESERVE: the amount of memory reserved for critical operations like rollback. If these operations fail then it crashes the Server. IBM documentation →
INFORMIXCONTIME: Specifies for how many seconds the CONNECT statement continues each attempt to establish a connection to a database server before returning an error. IBM documentation →
INFORMIXCONRETRY: Specifies the maximum number of additional connection attempts that should be made to each database server by the client during the time limit specified by INFORMIXCONRETRY. IBM documentation →
JVPJAVAHOME: Absolute path to the JRE. Defaults to $INFORMIXDIR/extend/krakatoa/jre Seldom needs to be changed. IBM documentation →
JVPJAVALIB: The JVPJAVALIB configuration parameter specifies the path from $JVPJAVAHOME to the location of the JVM libraries. Normally, the platform-dependent defaults are correct. IBM documentation →
JVPJAVAVM: The JVPJAVAVM configuration parameter lists the Java Virtual Machine (JVM) libraries that the database server loads. The names in this list exclude the lib prefix and .so suffix. IBM documentation →
JVPPROPFILE: The Java VP property file. IBM documentation →
JVPARGS: Configures the Java VM. To display JNI calls, use JVPARGS -verbose:jni. IBM documentation →
JVPCLASSPATH: The Java classpath to use. Must include krakatoa.jar. IBM documentation →
BUFFERPOOL: Specifies the default buffers and LRU queue settings for each page-size buffer pool. Consolidates the older BUFFERS/LRUS/LRU_MIN_DIRTY/LRU_MAX_DIRTY parameters into one entry. IBM documentation →

Deprecated parameters

These parameters no longer exist in current Informix releases. Each entry below points to the parameter that replaced it.

BUFFERS (deprecated): Replaced by BUFFERPOOL.
LRUS (deprecated): Replaced by BUFFERPOOL.
LRU_MAX_DIRTY (deprecated): Replaced by BUFFERPOOL.
LRU_MIN_DIRTY (deprecated): Replaced by BUFFERPOOL.
NUMCPUVPS (deprecated): Replaced by VPCLASS cpu.
NOAGE (deprecated): Replaced by VPCLASS cpu.
AFF_SPROC (deprecated): Replaced by VPCLASS cpu.
AFF_NPROCS (deprecated): Replaced by VPCLASS cpu.
NUMAIOVPS (deprecated): Replaced by VPCLASS aio.
RA_PAGES (deprecated): Replaced by AUTO_READAHEAD.
RA_THRESHOLD (deprecated): Replaced by AUTO_READAHEAD.