Appropriate Content: Informix Documentation Team
We asked IBM® Software Support about the questions they are frequently asked about Informix® and put the questions and answers in the v11.70 information center. Most questions are about installing, upgrading, and administering Informix.
Take a look at the FAQ in the information center and let us know what you think!
The 59 new oninit return codes introduced in Informix® 11.70 describe exactly why the server didn't start. We also document what your next move should be.
For example, oninit return code 175 says: The database server failed to initialize the root dbspace. What you should do if you get this return code is to check the root dbspace related parameters in server configuration file (onconfig) to make sure that the path for the root dbspace is valid.
The oninit return codes are documented in the Administrator's Reference.
96QY_Pat_Smith 27000196QY 807 Visits
Neelima Doguparthy, an IBM Informix software engineer, wrote a very useful developerWorks article about version 11.70.xC1 new features that have upgrade and reversion impact. The article is designed to help you smoothly upgrade to version 11.70.xC1 and efficiently use the new features. The article contains descriptions of new features that have upgrade and reversion impact, along with lists of new configuration parameters and information about the system catalog changes that were made for the new features.
You can also read about new features in the "What's new in Informix" topic in the IBM Informix 11.70 Information Center, and you can find information about reversion restrictions and lists of new configuration parameters, new environment variables, new keywords of SQL, and system catalog changes in the version 11.70 IBM Informix Migration Guide.
This entry is provided by Tom Houston, our esteemed SQL writer. He will be contributing the occasional entry about how to interpret syntax diagrams as they are used in IBM® Informix® documentation.
The Informix documentation uses syntax diagrams to summarize in a graphic format the syntax tokens -- the keywords, input values, delimiters, and other symbols -- and the order in which they can appear in a valid statement or command. Syntax diagrams that Informix user documents like Administrator's Reference and Guide to SQL:Syntax use a standard graphical notation that many IBM products currently use. Syntax diagrams are described in the Introduction chapter of PDF manuals and in the information centers.
The term syntax note refers to
Several instances of the same parenthetical digit (or digits) within the diagram can reference the same note below the diagram.
This blog entry addresses two potential ways to interpret a syntax note:
This diagram of the CONNECT statement of SQL (for the Informix 11.70 database server) includes two restrictive syntax notes and two cross-reference syntax notes:
1. See Database Environment
2. ESQL/C and DB-Access only
3. See USER Validation Clause
4. ESQL/C only
Here the cross-referencing note (1) that follows the Database Environment syntax segment matches the digit that precedes the
text of the "See Database Environment" note below the diagram, which is a link to the topic that shows the syntax of the Database
Environment syntax segment. Similarly, the cross-referencing note (3) that follows the USER Authentication Clause
syntax segment matches the digit that precedes the text of the "See USER Validation Clause " note below the diagram, which is a link to
the topic that shows the syntax of the USER Authentication Clause syntax segment.
The digit 2 delimited by parentheses (2) preceding the optional USER Authentication Clause syntax segment matches the digit that precedes the "ESQL/C and DB-Access only" syntax note text, restricting that clause to IBM Informix ESQL/C routines and to scripts of the DB-Access utility. This note implies, for example, that the database server will throw an exception if you attempt to run an SPL routine that attempts to connect to a database by using a CONNECT statement that includes this clause.
Similarly, the digit 4 delimited by parentheses (4) preceding the optional WITH CONCURRENT TRANSACTION keywords matches the digit that precedes the "ESQL/C only" syntax note text, restricting that clause to IBM Informix ESQL/C routine. In this diagram, the optional TRUSTED keyword is outside the scope.of syntax note (4), because a CONNECT statement that omits the WITH CONCURRENT TRANSACTION keywords can reach the TRUSTED keyword without following a path that syntax note (4) restricts.
In both instances, the restrictive syntax notes appear immediately above the path of the syntax tokens that the syntax note references, and to the left of those tokens. Syntax notes do not refer to the path above the digit that identifies the note. To apply the same syntax note to several independent paths in a diagram, the parenthetical digit that identifies the syntax note must be repeated for each path.
In an SPL routine, the following SQL statement fails with an error:
CONNECT TO DEFAULT WITH CONCURRENT TRANSACTION TRUSTED;
Even if a default database environment is defined for the current session, this statement fails because CONNECT statements that include the WITH CONCURRENT TRANSACTION keywords are not supported in SPL applications (unless the SPL routine invokes an ESQL/C routine to issue the CONNECT statement).
In summary, a cross-reference syntax note
A restrictive syntax note
Simplify the process of adding storage space by configuring for the automatic expansion of the space
96QY_Pat_Smith 27000196QY 756 Visits
If you upgrade to version 11.70, you can configure Informix to automatically expand an existing storage space when the space is full. You can also configure Informix to expand the space before it is full, when its free pages fall below a specified threshold. When you enable and configure automatic storage provisioning, you do not need to manually add storage space to avoid out-of-space errors. Even if you prefer to add space manually, automatic storage expansion greatly simplifies the process of adding space, because you do not need to determine where to get the space.
IngeHalilovic 060000MPB8 Tags:  configuration quick_reference informix onconfig onstat 1,281 Visits
The Quick Reference Cards for onconfig.std and onstat have been updated for Informix 11.70. These cards are designed to be printed double-sided on legal-sized paper (8.5" by 14") and folded into a four-sided pamphlet. They look best printed in color, especially the onconfig.std card, which shows version numbers in red.
IngeHalilovic 060000MPB8 Tags:  highlights 11.7 database features information_center information informix 1,483 Visits
Do you want to know exactly what's new for IBM® Informix® 11.70? Visit the new v11.70 information center.
For highlights of Informix 11.70, short descriptions of all the new features, and links to where the features are described in detail, see What's new in Informix.
Don't forget to subscribe to the RSS feed so that you'll know when we update the information center.
The v11.70 information center has the same collaboration features as the v11.50 information center. Find out how to comment on, rate, and watch topics.
The v11.70 information center works best with these browsers:
Basic text searching in Informix v11.50 became more versatile, configurable, and faster. See the What's New in Database Extensions for more information.
Process Multiple Basic Test Search Queries Simultaneously
If basic text search queries are slow because multiple users are running queries at the same time, you can add more BTS virtual processors so that queries run simultaneously, each in their own virtual processor. Previously, you could only create one BTS virtual processor and queries ran serially.
Control the Results of a Fuzzy Search with the Basic Text Search DataBlade® module
You can now specify the degree of similarity of search results in fuzzy searches when using the Basic Text Search DataBlade module. Specify a number between 0 and 1, where a higher value results in a higher degree of similarity. To limit results, specify a higher number. To maximize results, specify a lower number. The default degree of similarity is 0.5.
Map Characters for Indexing with the Basic Text Search DataBlade module
You can now map characters in your data to other characters during indexing with the Basic Text Search DataBlade module. For example, you can specify that letters with diacritical marks are indexed as the same letters without marks. You can also standardize inconsistent prefixes or delete character strings from indexed text. To use character maps, include the canonical_maps parameter when you create your bts index.
Default Boolean Operator in Basic Text Search Queries
You can now change the default Boolean
operator between search terms in Basic Text Search queries from OR to AND by
using the query_default_operator parameter when you create a bts index. The default
operator is represented by a blank space between terms. Many popular end-user
search engines use AND as the default operator between search terms, where
end-users expect the search results to contain all their search terms.
Storage for Temporary Basic Text Search Files
You can now specify that temporary files used by the Basic Text Search DataBlade module are stored in a separate sbspace from the one used to store the bts index. Separating temporary files from the bts index might improve query performance.
Track Basic Text Search Query Trends
You can now track what queries are run against your bts index by including the query_log parameter when you create a bts index. You can use query trends information to provide hints to end-users on popular queries or work on optimizing the most popular queries.
Fragment bts Indexes by Expressions
You can now fragment bts indexes by expressions into multiple sbspaces instead of a single sbspace.
Basic Text Search DataBlade module Supports High-Availability Clusters
You can now use the Basic Text Search DataBlade module to perform searches on high-availability cluster servers by creating indexes in sbspaces. Previously, the Basic Text Search DataBlade module only supported the creation of indexes in extspaces, and thus could not participate in any queries on high-availability secondary servers and in backup and restore operations.
Querying XML Attributes with the Basic Text DataBlade module
The Basic Text Search DataBlade module now supports searches on XML attributes in a document repository. The new all_xmlattrs parameter enables searches on all attributes that are contained in the XML tags or paths in a column that contains an XML document.
Support added for a user-defined stopword list
You can create a customized stopword list for frequently occurring words in your data or you can use the default stopword list.
Support added for XML-structured documents
You can use Basic Text Search XML index parameters to manipulate searches of XML data in different ways.
96QY_Pat_Smith 27000196QY 992 Visits
For Version 11.50xC6 of IBM Informix, we added a new Migration Guide chapter on high-availability cluster migration. This information helps you coordinate the migration of all servers in a high-availability cluster or, if necessary, revert all servers in a cluster to the previous version of the server. Chapter topics include information on the additional steps you must perform when preparing to migrate, migrating, and reverting clusters.
If you use high-availability clusters, refer to the information when you upgrade to a new version of Informix, PID, or fix pack, migrate or, if necessary, when you revert to the previous version.
For more information, see High-availability cluster migration.
Informix added a couple of key warehousing features in 11.50.xC5 and 11.50.xC6:
Load and Unload Data with External Tables
IDS supports external tables. You can read and write from a source that is external to the database server. External tables provide an SQL interface to data in text files managed by the operating system or to data from a FIFO device. To create external tables, use the CREATE EXTERNAL TABLE statement. Use the existing DROP TABLE statement to drop an external table.
See the Guide to SQL: Syntax.
Loading Data into a Warehouse with the MERGE Statement
Instead of using separate UPDATE and INSERT statements to load data from an OLTP database into a database warehouse environment, use the new MERGE statement, which can combine UPDATE and INSERT operations into a single SQL statement.
The MERGE statement can merge records from a table, view, or query (the source) with the records in a local table (the target). You can specify a logical condition that MERGE applies to a join of the source and target objects.
The MERGE statement supports Update and Insert triggers on the target table. Any constraints on the target table are enforced in MERGE operations.
See the Guide to SQL: Syntax.
Retrieving Data by Using Hierarchical Queries
You can now retrieve data from a table by using hierarchical queries, which maintain the relationship between the data.
The SELECT statement of Informix now supports START WITH .. CONNECT BY syntax for recursively querying a table in which a hierarchy of parent-child relationships exist. The syntax can define recursive queries that reflect the topology of the data hierarchy.
This implementation of hierarchical queries uses extensions to the ISO standard for SQL.
See the Guide to SQL: Syntax.
Informix Warehouse Feature
The Informix Warehouse Feature provides an integrated platform for the design and administration of data warehousing applications.
The core of Informix Warehouse Feature is the SQL Warehousing Tool. It includes an application development component in the Informix Warehouse Feature client and an administration component on the Informix Warehouse Feature server.
Informix Warehouse Feature client includes the Design Studio, which provides a common design environment for creating physical data models, SQL data flows and control flows. Design Studio is built on the Eclipse Workbench and automatically generates SQL that is based on visual operator flows that you model in the Design Studio. The library of SQL operators covers the in-database data operations that are typically needed to move data between database tables.