To view the Information Center in a specific language:
Go the the Informix 12.10 Information Center at http://pic.dhe.ibm.com/infocenter/informix/v121/index.jsp?
By default, the information is in English.
Append ?lang=xx to the URL, where xx equals one of the following language codes:
Language = Code
Brazilian Portuguese = pt-BR
Chinese Simplified = zh-CN
Chinese Traditional = zh-TW
Czech = cs
French = fr-FR
German = de
Hungarian = hu
Italian = it
Japanese = ja
Korean = ko
Polish = pl
Russian = ru
Slovak = sk
Spanish = es
For example, use the following URL to view the information that is available in German:
Refresh your browser.
Note that not every topic or publication is available in every language. To see which publications are available in specific languages go to:
Check out some new ideas for OAT and talk to us about how you use Informix and Informix documentation at the IIUG conference in San Diego. Alison Eckholm, the Informix usability expert, and I, the OAT information developer, are hosting a usability sandbox at the conference on April 23, 24, and 25. You can participate in any of these sandbox sessions:
- Take a sneak peek at future possibilities in IBM® OpenAdmin Tool (OAT) for Informix®. Participate and provide feedback in an interactive, small-group session.
- Help optimize the OAT experience by participating in a hands-on activity. Provide feedback on your key tasks and how you would customize OAT.
- Preview enhancements to the Informix Warehouse Accelerator. Check out some of the features being considered and influence the development of this important tool.
- Help us improve the Informix experience. Tell us how you use Informix, how you use the product documentation, and what other kinds of information you need to do your job.
Whether you attend IIUG or not, you can participate in our survey on Informix administration. We want to understand how you find information about Informix when you need it. You can help by completing the survey, whether you use the command line, OAT, or other administrative tools. Your answers will remain anonymous and confidential. To participate, go to the IBM Informix Administration Survey on the IBM website: https://www-950.ibm.com/survey/oid/wsb.dll/s/ag456
Ever wonder what to do when you got a severity 4 event alarm? For IBM® Informix® 11.50.xC9, we added descriptions, server states, and user actions for severity 4 and 5 event alarms to the Administrator's Reference.
Look for the descriptions of the severity 4 and 5 event alarms here
. (You'll have to scroll down a bit to get to the first severity 4 alarm description.) You can see all severity 5 alarms here
. Event alarms specific to Enterprise Replication are here
With IBM® Informix® 12.10.xC5, you can search time series data for matches to a specific pattern of values. For example, after you identify a pattern of abnormal electricity usage that indicates an outage, you can search for matches to that pattern to find other outages. A pattern is a sequence of numeric values in a field within the TimeSeries subtype. You can specify a search pattern as a time range in a specific time series or as a list of numeric values. A match is a sequence of values from a target time series that conform to the search criteria.
When you run a pattern matching search, you specify the method to evaluate possible matches and the margin of error between the search pattern and matching values.
The following information is returned for each resulting match:
The primary key value for the time series instance.
The begin point of the match.
The end point of the match.
The score of the match, as a double precision number 0.0-1.0 that represents the percentage of values in the matching sequence that are an exact match to the corresponding values in the search pattern.
You can create a pattern matching search index on a time series instance to improve query performance.
Read more: Pattern matching searches.
Attend the Using Pattern Matching Analytics in IoT and TimeSeries data Webinar on April 20: https://events.na.collabserv.com/register.php.
Modified on by IngeHalilovic
The IBM® Informix® team has added the following features to version 12.10.xC6, which is available today:
- Backup and restore
- JSON compatibility
- High availability
- Application development
- Time series data
See the full list of new features with links for more information.
The Informix® 11.70 information center
has been updated with 11.70.xC3 information!
The new features
in IBM® Informix 11.70.xC3 are:
- Automatic read-ahead operations
- Configuring the server response to low memory
- Reserving memory for critical activities
- Connection Manager enhancements
- Enhancements to the OpenAdmin Tool
- Managing message logs in embedded and enterprise environments
- Built-in SQL compatibility functions for string manipulation and trigonometric support
- Client SDK includes the DB-Access utility
- High availability clusters and Enterprise
- Automatically connecting to a grid
- Code set conversion for Enterprise Replication
- Enhancements to the Informix Replication plug-in for OAT
- Non-root installations support shared-memory and stream-pipe connections
- Retaining numbers for audit log files
- Restrict operating system properties for mapped users
- Time Series data
- Simplified handling of time series data
- Informix TimeSeries plug-in for OAT
Follow this link
to see a short description of the features and links to more detailed information.
IBM® Informix® 11.70.xC4 contains the following new functionality in the following categories.
- Enhancements to the OpenAdmin Tool (OAT) for Informix
- Enhancements to the Informix Replication Plug-in for OAT
- Informix Health Advisor Plug-in for OAT
- Dynamically change additional configuration parameters
- Compare date and interval values
- Plan responses to high severity event alarms
- Data sampling for update statistics operations
- SQL administration API command arguments for creating sbspaces
- Monitor client program database usage
- Progress of compression operations
High availability and Enterprise Replication
- Easier setup of faster consistency checking
- Handle Connection Manager event alarms
- Easier startup of Connection Manager
- Prevent failover if the primary server is active
- Configure secure connections for replication servers
- Global Security Kit (GSKit) support
- Use a file to authenticate server connections in a secured network environment
Time Series data
- IBM Informix TimeSeries Plug-in for Data Studio
- Delete a range of elements and free empty pages from a time series
- Aggregate time series data across multiple rows
- Install Informix Warehouse Accelerator on a cluster system
- Refresh data mart data during query acceleration
- User informix can run the ondwa commands
- Support for new functions is implemented
- New options for monitoring AQTs
For IBM® Informix® 12.10.xC5, we rewrote the database server installation information. Previously, we had two installation guides: one for UNIX, Linux, and Mac OS X, and one for Windows platforms. For 12.10.xC5, we combined the two guides into one guide and while we are at it, we condensed the information and corrected out-of-date information.
Take a look at the new Installation Guide!
Here's a teaser: the new Preparing for installation topic:
Preparing for installation
Before you install Informix database server products, you must prepare your system and plan for choices that you must make during the installation process.
Preparing for installation includes reviewing system requirements, planning how to upgrade, deciding on the installation owner and the installation directory, reviewing installation options, and gathering information if you want to create a database server during installation. It also includes preinstallation tasks such as obtaining the software and reviewing the machine notes.
To prepare for installation:
Obtain the software. You can download the product package from Passport Advantage: http://www.ibm.com/software/howtobuy/passportadvantage.
Review the Informix components that can be installed with the database server. You can install all of them or some of them.
Ensure that your computer meets the system requirements.
Choose a user account with which to install the product. The user account becomes the installation owner.
UNIX, Linux, Mac OS X: Decide between a non-root owner and an owner with root or administrative privileges.
If you plan to install as an administrative user, decide on a password for user informix.
Choose an installation directory. If the database server is already installed, decide on the upgrade path.
Decide between a typical or custom installation.
Choose a typical installation in the following cases:
To install all database server components, IBM® Informix Client Software Development Kit, and the IBM Informix JDBC Driver.
To create a configured database during installation with connectivity for JSON applications and multiple storage spaces for data.
Choose a custom installation if you want to have any of the following options:
To install a subset of database server components.
To choose which client products to install.
In root-based installation, to set up event auditing for the security policies of your organization.
To create a configured database server during installation with one storage space for data.
To prepare a response file for a non-interactive installation.
Depending on your operating system, you can choose other types of installations that have similar options to a custom installation. UNIX, Linux, Mac OS X: You can choose the Legacy installation to prepare a script-based installation. Linux: You can choose the RPM installation to generate an RPM package.
Decide whether to create a configured database server during installation.
If you do not create a configured database server during installation, you must configure the database server and initialize disk space after installation is complete.
If you create a database server during installation, you must supply some information:
Specify information to configure the database server, such as the number of expected users.
Windows: For a typical setup, specify a password for user ifxjson. This user administers the JSON wire listener.
Log files are created during the installation process. You can use the log files to troubleshoot installation errors.
After you install the database server, you can create the demonstration databases that are included with the database server. Many examples in the documentation and in the $INFORMIXDIR/demo (UNIX, Linux, Mac OS X) or the %INFORMIXDIR%\demo (Windows) directory are based on the demonstration databases. You can use the demonstration databases to explore database server features. You can create the demonstration databases at any time after installation by running the dbaccessdemo command. See Demonstration databases.
Modified on by IngeHalilovic
Informix 12.10.xC4 has some very exciting new features for JSON compatibility:
Support for CORS requests in the REST API (12.10.xC4W1)
You can now set up cross-origin resource sharing (CORS) with the REST API. To do so, set the following optional parameters that were added to the jsonListener.properties file:
Informix now supports the following MongoDB 2.4 features:
Cursor support so that you can query large volumes of data.
Text search of string content in collections and tables.
Geospatial indexes and queries.
Pipeline aggregation operators.
The array update modifiers: $each, $slice, $sort.
You can perform the following new tasks that extend MongoDB functionality in your JSON application:
Import and export data directly with the wire listener by using the Informix JSON commands exportCollection and importCollection.
Configure a strategy for calculating the size of your database by using the Informix extension to the MongoDB listDatabases command: sizeStrategy option or command.listDatabases.sizeStrategy property.
You can customize the behavior of the wire listener by setting new properties. For example, you can control logging, caching, timeout, memory pools, and the maximum size of documents.
Access Informix from REST API clients
You can now directly connect applications or devices that communicate through the REST API to Informix. You create connections by configuring the wire listener for the REST API. With the REST API, you can use MongoDB and SQL queries against JSON and BSON document collections, traditional relational tables, and time series data. The REST API uses MongoDB syntax and returns JSON documents.
Create a time series with the REST API or the MongoDB API
If you have applications that handle time series data, you can now create and manage a time series with the REST API or the MongoDB API. Previously, you created a time series by running SQL statements. For example, you can program sensor devices that do not have client drivers to load time series data directly into the database with HTTP commands from the REST API.
You create time series objects by adding definitions to time series collections. You interact with time series data through a virtual table.
See the IBM Informix JSON Compatibility Guide.
IBM® Informix® shard cluster architecture is very flexible:
- Shard servers can run on different hardware and operating systems.
- Shard servers can run different version of Informix. For example, you can upgrade Informix on shard servers individually.
- Shard servers can have high-availability secondary servers from which users can query the sharded table.
As of Informix 12.10.xC6, you can now run SELECT statements in sharded queries in parallel instead of serially on each shard. Parallel sharded queries return results faster, but also have the following benefits:
- Reduced memory consumption: Table consistency is enforced on the shard servers, which eliminates the processing of data dictionary information among the shard servers.
- Reduced network traffic: Client connections are multiplexed over a common pipe instead of being created individual connections between each client and every shard server. Client connections are authenticated on only one shard server instead of on every shard server. Network traffic to check table consistency is eliminated.
To enable parallel sharded queries, set the new SHARD_ID configuration parameter in the onconfig file to a unique value on each shard server in the shard cluster. Also set the new sharding.parallel.query.enable=true and sharding.enable=true parameters in the wire listener configuration file for each shard server. You can customize how shared memory is allocated for parallel sharded queries on each shard server by setting the new SHARD_MEM configuration parameter. You can reduce latency between shard servers by increasing the number of pipes for SMX connections with the new SMX_NUMPIPES configuration parameter.
See documentation about JSON sharding.
Also see this cool demo of parallel sharding: https://ibm.biz/BdHaru
Modified on by IngeHalilovic
With IBM® Informix® 12.10.xC5, you have a lot more control over session resources. Besides setting session environment variables to control the current session, you can set configuration parameters to limit all sessions and prevent blocked transactions.
You can specify to end sessions that exceed a specified amount of shared memory or temporary storage space:
- Set the SESSION_LIMIT_MEMORY configuration parameter to the maximum amount of shared memory that can be allocated for a session.
- Set the SESSION_LIMIT_TEMPSPACE configuration parameter to the maximum amount of temporary storage space that can be allocated for a session.
You can specify to roll back transactions that are too large or take too long:
- Set the SESSION_LIMIT_LOGSPACE configuration parameter to the maximum amount of log space that a transaction can fill.
- Set the SESSION_LIMIT_TXN_TIME configuration parameter to the maximum number of seconds that a transaction can run.
Starting in 12.10.xC4, you can set the SESSION_LIMIT_LOCKS configuration parameter (and the IFX_SESSION_LIMIT_LOCKS environment option) to limit the number of locks.
Session limits do not apply to a user who holds administrative privileges, such as user informix or a DBSA user.
Transactions and sessions that exceed a set limit are terminated by the session_mgr thread. The session_mgr thread starts when the database server starts, and remains inactive until a session limit is exceeded.
Monitor sessions with the onstat -g ses command.
An Informix customer suggested that we create a quick reference card for the SQL administration API, so we created one for 11.50.xC8.
This quick reference card
shows SQL administration API task()
function arguments sorted by functional category with examples of
syntax. Version numbers indicate in which version of Informix each argument was
This is the last blog entry for the year: Happy New Year!
Did you know that you can monitor and analyze the state and performance of your Informix® database server, and send automatic email alerts, by using the Health Advisor plug-in for the OpenAdmin Tool (OAT)?
At the next Informix Chat with the Lab, my colleague Erika Von Bargen, IBM Software Engineer and OAT programmer par excellence, will present a deep dive into the Health Advisor plug-in. She will cover how the plug-in works and how to use it in OAT. She will also explain how you can add your own health checks and alarms.
Come and join us for the chat. You can register at:
The Health Advisor plug-in was first available with OAT 2.74, which was released with Informix 11.70.xC4. The Health Advisor plug-in works with Informix 11.50 and later. For more information about the Health Advisor plug-in, see Informix Health Advisor Plug-in for OAT.
We've updated the SQL administration API quick reference card
with 11.70.xC4 content. This is the same version that was available in hard copy at IIUG.
In IBM© Informix© 12.10.xC4, we added the ability to run text searches on JSON documents that are stored in Informix databases. You have three different ways of indexing and searching JSON documents:
MongoDB API command: Run the ensureIndex command and specify text as the type of index, and then query with the MongoDB $text query operator. This method is appropriate if you don't want to change your existing MongoDB application, but provides limited options for indexing and querying.
Informix extension to the MongoDB API: Run the createTextIndex command through the MongoDB API and then query with the Informix $ifxtext query operator. The createTextIndex command takes the same parameters as creating a basic text search index through SQL statements. This method is appropriate if you want to use MongoDB commands and also take advantage of the flexibility and power of Informix basic text search indexing and querying.
Informix SQL statement: Create a basic text search index with JSON index parameters through SQL statements and query with the bts_contains() search predicate. This method is appropriate if you want to query JSON documents through SQL.
When you create a basic text search index on JSON documents, you can control the following aspects of the index:
Whether to index the documents as field name-value pairs so that you can search for text by field. Enable the all_json_names index parameter to index all field names. Set the json_names index parameters to index specific field names. You have the following choices to further refine how field name-value pairs are indexed:
Whether to include JSON or BSON object paths in field name-value pairs so that you can search based on the field hierarchy in the document. Enable the json_path_processing index parameter to index paths.
Whether to index the position of values in arrays so that you can search specific positions in arrays. Enable the json_array_processing index parameter to index the position of arrays.
Whether to index as both field name-value pairs and unstructured text so that you have the flexibility to search a specific field or all fields. Enable the include_contents index parameter to include an unstructured index of field names and values.
Whether an unstructured index contains only values and no field names so that you do not receive field names in search results. Enable the only_json_values index parameter to limit the unstructured index to values.
Whether to ignore format errors for JSON or BSON documents. Enable the ignore_json_format_errors index parameter to ignore incorrectly formatted documents.
For more information, see:
The createTextIndex command
JSON index parameters