Welcome
Data warehousing
In addition to designing and implementing Informix® dimensional databases, you can use tools to create data warehouse applications and optimize your data warehouse queries.
Informix® Warehouse Accelerator
Data marts and AQTs
For efficient query processing, the accelerator server must have its own copy of the data. The data is stored in logical collections of related data, or data marts. A data mart specifies the collection of tables that are loaded into an accelerator and the relationships, or references, between these tables.
Update a data mart
You can refresh the data in a data mart by re-creating the data mart or by dropping and loading the data in a partition or in a fact or dimension table. You can refresh the data in a data mart. You can update the data mart definition when you change the warehouse schema.
Refreshing all the data in a data mart
You can refresh all the data in a data mart while queries are being accelerated by creating a new data mart based on your existing data mart definition. You do not need to suspend query acceleration in order to drop and re-create the original data mart.

HCL Informix® V15.0 documentation
Welcome to the documentation for HCL Informix® 15.0 and related client tools and products.
Product overview
HCL Informix® is a fast and scalable database server that manages traditional relational, object-relational, and dimensional databases. Its small footprint and self-managing capabilities are suited to embedded data-management solutions.
Installing
These topics describe how to install HCL Informix® database servers, client products, and DataBlade® modules.
Administering
In addition to administering the database server, you can tune performance, replicate data, and archive data.
Migrating and upgrading
You can upgrade to the 15.0 release of HCL Informix® or migrate from other database servers to Informix. Upgrading is an in-place migration method that uses your existing hardware and operating system software. Some changes to the Informix database server can affect upgrading from a previous release.
Client APIs and tools
You can use the HCL Informix® implementation of client APIs to develop applications for Informix database servers.
Embedding Informix®
When you embed HCL Informix®, you can use enterprise-class high-availability and high performance with embeddability features such as easy programmability, a small disk and memory footprint, and silent deployment.
Extending Informix®
Beyond standard relational database objects, HCL Informix® can be extended to handle specialized data types, access methods, routines, and other objects. Informix includes many built-in extensions that are fully integrated in the database server. Informix also provides DataBlade® modules, which are packages of extended database objects for a particular purpose and that are installed separately from the database server. Alternatively, you can create your own user-defined objects for Informix.
Data warehousing
In addition to designing and implementing Informix® dimensional databases, you can use tools to create data warehouse applications and optimize your data warehouse queries.
- Dimensional databases
  These topics provide information to help you design, implement, and manage dimensional databases, and describes the tools that you can use to create data warehouses and optimize your data warehouse queries.
- Informix® Warehouse Accelerator
  - Overview of Informix® Warehouse Accelerator
    Informix® Warehouse Accelerator is a product that you use to improve the performance of your warehouse queries.
  - Installation
    You can install Informix® Warehouse Accelerator on the same computer as the Informix database server, on a separate computer, or on a cluster (including a high-availability cluster).
  - Configuration
    You must configure the accelerator server to work with the Informix® database server.
  - Create an accelerator
    You create an accelerator by connecting the Informix® database server to the accelerator server.
  - Data marts and AQTs
    For efficient query processing, the accelerator server must have its own copy of the data. The data is stored in logical collections of related data, or data marts. A data mart specifies the collection of tables that are loaded into an accelerator and the relationships, or references, between these tables.
    - Accelerated query tables
      Accelerated query tables, or AQTs, store information about data marts that the database server uses to determine which queries can be processed by Informix® Warehouse Accelerator.
    - Data marts
      Typically, data marts contain a subset of the tables in your database. The data marts can also contain a subset of the columns within a table. This configuration is advantageous when you are using the TCP/IP loopback optimization between Informix® and IWA, because it provides a seamless experience for the customer.
    - Create a data mart
      After you configure the accelerator server and set up the connection between an accelerator and the database server, you need to create the data marts.
    - Deploy and load the data mart
      To deploy a data mart, you specify the accelerator that will contain the data mart definition file. When you load a data mart, the related data is unloaded from the Informix® tables and transferred to the accelerator server.
    - Update a data mart
      You can refresh the data in a data mart by re-creating the data mart or by dropping and loading the data in a partition or in a fact or dimension table. You can refresh the data in a data mart. You can update the data mart definition when you change the warehouse schema.
      - Refreshing all the data in a data mart
        You can refresh all the data in a data mart while queries are being accelerated by creating a new data mart based on your existing data mart definition. You do not need to suspend query acceleration in order to drop and re-create the original data mart.
      - Refreshing data mart data at the partition level
        Use the dropPartMart() and loadPartMart() functions to refresh the data in a specific partition in a fragmented table instead of refreshing all the data in the data mart. If your database table is fragmented, your data mart table follows the same fragmentation scheme. Refreshing data by partition is faster than refreshing an entire data mart.
      - Refreshing data mart data in a table
        You can use the dropPartMart() and loadPartMart() functions to refresh the data in a table instead of refreshing all the data in the data mart. The table must be a non-fragmented table. If your database table is not fragmented, your data mart table is also not fragmented. Refreshing the data in a table is faster than refreshing an entire data mart.
    - Managing a data mart
      You might need to drop or re-create a data mart, for example, if the schema of the underlying tables is changed, or if you create a new data mart and need to remove an old data mart.
    - Drop a data mart
      You can drop a data mart if you no longer need the data mart or if you need to update the data in a data mart.
  - Data marts and AQTs
    For efficient query processing, the accelerator server must have its own copy of the data. The data is stored in logical collections of related data, or data marts. A data mart specifies the collection of tables that are loaded into an accelerator and the relationships, or references, between these tables.
  - Turning on query acceleration
    Before queries can be routed to the accelerator server for processing, you must set the use_dwa session environment variable.
  - SQL administration routines
    You can use the Informix® Warehouse Accelerator functions and procedures from the command line or in an application to automate administration tasks.
  - Reversion requirements for an Informix® warehouse server and Informix® Warehouse Accelerator
    If you revert the HCL Informix® server to an earlier version, you must drop all of the data marts. If you created data mart definitions by using workload analysis, you must drop all of the tables that were created by the probe2Mart() procedure.
  - Troubleshooting
  - Sample warehouse schema
    The Informix® Warehouse Accelerator examples use this sample warehouse schema.
  - Sysmaster interface (SMI) pseudo tables for query probing data
    The SMI tables provide a way to access probing data in a relational form, which is most convenient for further processing.
  - Supported locales
    Informix® Warehouse Accelerator supports a subset of the locales that HCL Informix supports.
Designing databases
The first step in creating a relational database is to construct a data model, which is a precise, complete definition of the data you want to store. After you prepare your data model, you must implement it as a database and tables. To implement your data model, you first select a data type for each column and then you create a database and tables and populate the tables with data. You can also implement fragmentation strategies and control access to your data.
JSON compatibility
You can use the popular JSON-oriented query language created by MongoDB to interact with data stored in HCL Informix®.
Security
You can secure your Informix® database server and the data that is stored in your Informix databases. You can encrypt data, secure connections, control user privileges and access, and audit data security.
SQL programming
You can use the HCL Informix® implementation of the SQL language to develop applications for Informix database servers.
Troubleshooting HCL Informix®
Several troubleshooting techniques, tools, and resources are available for resolving problems that you encounter in your HCL Informix® database server environment.

Refreshing all the data in a data mart

You can refresh all the data in a data mart while queries are being accelerated by creating a new data mart based on your existing data mart definition. You do not need to suspend query acceleration in order to drop and re-create the original data mart.

About this task

To refresh the data-mart data, create a new data mart. As soon as the new data mart is loaded, the database server uses the new data mart for matching new queries to AQTs. New candidate queries that are sent to the accelerator server will use the new data mart.

Drop the original data mart and deploy and load the new data mart. The new and old data marts must have the same data mart definition, but different names.

If you have enough memory, you can create the new data mart and then drop the original data mart. During the load phase, you need approximately twice as much memory as the original data mart uses. Otherwise, drop the original data mart and then recreate it. Make sure you save the data mart definition file with a different file name before you drop the original data mart.

In this example, datamart_1 has been loaded and sent to the accelerator server for processing. The data for datamart_1 has changed. You want any new queries that are sent to the database server to use the new data.

Procedure

Create a data mart that has the same definition as datamart_1, but name the data mart datamart_2.
Load datamart_2. When the data loading for datamart_2 completes, the accelerator server uses datamart_2 with the refreshed data for incoming queries.
Disable datamart_1.
Optional: Drop datamart_1. When multiple data marts use the same tables, the Informix® database server uses the latest data mart to accelerate the queries.