Additional configuration parameters and environment variables:
Name | Description | Link |
---|---|---|
BAR_MAX_RESTORE Configuration Parameter | The maximum number of parallel restore processes that are allowed during an ON-Bar restore operation. | BAR_MAX_RESTORE configuration parameter |
IFXGUARD Configuration Parameter | Enables auditing with IBM® Security Guardium® and sets the actions of the database server if the IBM Security Guardium server does not respond in the timeout period. | IFXGUARD configuration parameter |
SHARD_ID Configuration Parameter | Sets the unique ID for a shard server in a shard cluster. | SHARD_ID configuration parameter |
SHARD_MEM Configuration Parameter | Specifies how to allocate shared memory for sharded queries on a shard server. | SHARD_MEM configuration parameter |
SMX_NUMPIPES Configuration Parameter | The SMX_NUMPIPES configuration parameter sets the number of pipes for server multiplexer group (SMX) connections. | SMX_NUMPIPES configuration parameter |
TENANT_LIMIT_CONNECTIONS Configuration Parameter | The TENANT_LIMIT_CONNECTIONS configuration parameter specifies the maximum number of connections to a tenant database. | TENANT_LIMIT_CONNECTIONS configuration parameter |
TENANT_LIMIT_MEMORY Configuration Parameter | The TENANT_LIMIT_MEMORY configuration parameter specifies the maximum amount of shared memory for all sessions that are connected to the tenant database. | |
IFX_SOC_KEEPALIVE Environment variable | New environment variable for Informix JDBC Driver version 4.10.JC6. When set to true, sets the TCP property SO_KEEPALIVE on the socket for open connections. |
This is via the new TENANT_LIMIT_CONNECTIONS/TENANT_LIMIT_MEMORY Configuration Parameter or tenant_limit_memory/tenant_limit_connections passed to the admin() or task() function.
Memory can be 100MB to 2TB, connections can be 1-65536.
When the memory limit is exceeded, the session that is using the most shared memory is terminated
Restore tenant databases to a point in time, run onbar -r -t time with the new -T tenant_database option
See onbar -r syntax: Restoring data
See the new BAR_MAX_RESTORE configuration parameter above.
You can now run SELECT statements in sharded queries in parallel instead of serially on each shard.
Informix now supports the following MongoDB commands:
You can authenticate MongoDB clients with the MongoDB 3.0 SCRAM-SHA-1 authentication method
You upgrade to MongoDB 3.0 by setting the new mongo.api.version parameter to 3.0 in the wire listener configuration file.
New parameters to customize the wire listener.
Name | Description | Link |
---|---|---|
mongo.api.version | Version of MongoDB API compatibility | mongo.api.version |
command.blacklist | Disable commands | The wire listener configuration file |
db.authentication | Optional parameter specifies the user authentication method. | The wire listener configuration file |
listener.admin.ipAddress | Optional parameter specifies the IP address for the administrative host. Must be a loopback IP address. The default value is 127.0.0.1. | The wire listener configuration file |
listener.authentication.timeout | Optional parameter specifies the number of milliseconds that the wire listener waits for a client connection to authenticate, default 0=forever | The wire listener configuration file |
listener.http.headers | Optional parameter specifies the information to include in the HTTP headers of responses, as a JSON document, default is no headers. | The wire listener configuration file |
listener.memoryMonitor.enable | Optional parameter enables the wire listener memory monitor.When memory usage for the wire listener is high, the memory monitor attempts to reduce resources, such as removing cached JDBC prepared statements, removing idle JDBC connections from the connection pools, and reducing the maximum size of responses. | The wire listener configuration file |
listener.memoryMonitor.allPoint | Optional parameter specifies the maximum percentage of heap usage before the memory monitor reduces resources. The default value is 80. | The wire listener configuration file |
listener.memoryMonitor.diagnosticPoint | Optional parameter specifies the percentage of heap usage before diagnostic information about memory usage is logged. The default value is 99. | The wire listener configuration file |
listener.memoryMonitor.zeroPoint | Optional parameter specifies the percentage of heap usage before the memory manager reduces resource usage to the lowest possible levels. The default value is 95. | The wire listener configuration file |
listener.pool.admin.enable | Optional parameter enables a separate thread pool for connections from the administrative IP address, which is set by the listener.admin.ipAddress parameter, default is false. | The wire listener configuration file |
listener.socket.accept.timeout | Optional parameter specifies the number of milliseconds that a server socket waits for an accept() function,default is 1024. | The wire listener configuration file |
listener.socket.read.timeout | Optional parameter specifies the number of milliseconds to block when calling a read() function on the socket input stream.default is 1024. A value of 0 might prevent the wire listener from shutting down because the threads that poll the socket might never unblock. | The wire listener configuration file |
pool.lenient.return.enable | Optional parameter suppresses some checks on a connection that is being returned that might throw exceptions, default false | The wire listener configuration file |
pool.lenient.dispose.enable | Optional parameter suppresses some checks on a connection that is being disposed of that might throw exceptions, default false | The wire listener configuration file |
Clients can be configured to authenticate wiith PAM, this allows Informix auditing and fine grained access control
See Configuring database server authentication with PAM (UNIX, Linux)
You can start the wire listener for the REST API or the MongoDB API by using the start command.
See Starting the wire listener
You can now reduce latency between high-availability servers by increasing the number of pipes that are used for the server multiplexer group (SMX) connections between servers.
See the new SMX_NUMPIPES configuration parameter above
When the LOG_INDEX_BUILD configuration parameter is enabled, the transfer of newly-created detached indexes to HDR or remote stand-alone secondary servers use light scans when possible.
See the new SMX_NUMPIPES configuration parameter above
The ifxclone utility has a new parameter --createchunkfile option to automatically create the cooked chunks and mirror chunks on the target server that exist on the source server.
You can now reoptimize previously prepared query plans. Set the new withReoptimization argument of the IfmxPreparedStatement.executeQuery method to true.
You can now reoptimize previously prepared query plans. Set the new withReoptimization argument of the IfmxPreparedStatement.executeQuery method to true.
See the IFX_SOC_KEEPALIVE environment variable above
Some SQL statements produce significantly different query plans depending on the values of the placeholders that are passed to the database server when the statements are run.
Statement caching can be disabled using the new AVOID_STMT_CACHE optimizer directive.
You can now assign a priority to each of your databases in the Auto Update Statistics (AUS) maintenance system, default medium priority.
You can also disable AUS for a database.
Add a row to the ph_threshold in the sysadmin database, name "AUS_DATABASE_HIGH","AUS_DATABASE_LOW" or "AUS_DATABASE_DISABLE" and value the name of the database
See Prioritizing databases in AUS
You can now audit the user actions for your Informix database server with IBM Security Guardium®, version 10.0
There is an ifxguard configuration file, default $INFORMIXDIR/etc/ifxguard.$INFORMIXSERVER
There is also an ifxguard utility to start, stop, and configure auditing.
Also see the IFXGUARD Configuration Parameter above.
See Auditing with IBM Security Guardium (UNIX, Linux)
You can now see the time series reference count in the metadata section of the output of the TSInfo function.
The time series reference count is the number rows in time series tables that reference the same time series data in a container.
This is done via the TSInfo function - field refCount
See TSInfo function
When calling the TSCreateContainer procedure, the dbspace_name parameter can be left NULL
The container is created in the same dbspace as the time series table, or, if the table is in a tenant database, the dbspace for the tenant database catalogs.
See TSContainerCreate procedure
The ondwa tasks command to monitor Informix Warehouse Accelerator queries now displays client session information for running queries and basic information about queued queries.
The client session information includes the session ID and the server number to which the client is connected.