Welcome
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 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.
Informix® extensions and modules
These topics describe how to use built-in database extensions and separately installed modules.
TimeSeries Data User's Guide
The IBM® Informix® TimeSeries Data User's Guide contains information to assist you in using the TimeSeries extension with HCL Informix.
Data types and system tables
Specialized data types and system tables handle time series data.
TSContainerWindowTable
The TSContainerWindowTable table has one row for each rolling window container.

HCL Informix® V15.0.0 documentation
Welcome to the documentation for HCL Informix® 15.0.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 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.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 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.
- Informix® extensions and modules
  These topics describe how to use built-in database extensions and separately installed modules.
  - Database Extensions User's Guide
    The IBM® Informix® Database Extensions User's Guide explains how to use the database extensions that come with HCL Informix: Large Object Locator, MQ messaging, binary data types, basic text search, node data type, and SQL packages.
  - Performing XML Publishing
    The IBM® Informix® XML User's Guide includes information about using built-in functions for XML publishing with HCL Informix.
  - Spatial Data User's Guide
    The contains information to assist you in using the HCL® Informix® spatial extension. The HCL Informix spatial extension adds custom data types and supporting routines to the server.
  - TimeSeries Data User's Guide
    The IBM® Informix® TimeSeries Data User's Guide contains information to assist you in using the TimeSeries extension with HCL Informix.
    - Informix® TimeSeries solution
      Database administrators and applications developers use the Informix® TimeSeries solution to store and analyze time series data.
    - Data types and system tables
      Specialized data types and system tables handle time series data.
      - CalendarPattern data type
        The CalendarPattern data type defines the interval duration and the pattern of valid and invalid intervals in a calendar pattern.
      - Calendar data type
        The Calendar data type controls the times at which time series data can be stored.
      - TimeSeries data type
        The TimeSeries data type is constructed from a row data type and is a collection of row subtypes.
      - Time series return types
        When a routine returns a time series, calendar information is preserved and, if possible, threshold and container information is preserved.
      - CalendarPatterns table
        The CalendarPatterns table contains information about calendar patterns.
      - CalendarTable table
        The CalendarTable table maintains information about the time series calendars used by the database.
      - TSContainerTable table
        The TSContainerTable table has one row for each container.
      - TSContainerWindowTable
        The TSContainerWindowTable table has one row for each rolling window container.
        TSContainerUsageActiveWindowVTI Table
        The TSContainerUsageActiveWindowVTI table is a virtual table that is based on the TSContainerWindowTable table. The TSContainerUsageActiveWindowVTI table has one row for each partition in the active window of a rolling window container.
        TSContainerUsageDormantWindowVTI Table
        The TSContainerUsageDormantWindowVTI table is a virtual table that is based on the TSContainerWindowTable table. The TSContainerUsageDormantWindowVTI table has one row for each partition in the dormant window of a rolling window container.
      - TSInstanceTable table
        The TSInstanceTable table contains one row for each large time series, no matter how many times it is referenced.
    - Create and manage a time series through SQL
      Before you can load time series data into the database, you must configure database objects specific to your time series. You can manage data storage and remove data as necessary. You can run SQL statements to create and manage time series.
    - Virtual tables for time series data
      A virtual table provides a relational view of your time series data.
    - Pattern matching searches
      You can search time series data for matches to a particular 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. Pattern matching searches find matches to a pattern that you supply. Pattern matching searches do not discover patterns in time series data.
    - Advanced analytics
      Advanced analytics functions provide specialized methods of analyzing time series data for patterns or abnormalities.
    - Calendar pattern routines
      You can use calendar pattern routines to manipulate calendar patterns.
    - Calendar routines
      You can use calendar routines to manipulate calendars.
    - Time series SQL routines
    - Time series Java™ class library
      You can use the time series Java™ class library to create and manage a time series from within Java applications or applets.
    - Time series API routines
      The time series application programming interface routines allow application programmers to directly access a time series datum.
    - Appendixes
  - Spatiotemporal Search for Moving Objects User's Guide
    The describes how to program applications to search data from moving objects in HCL Informix® databases using the spatiotemporal search extension.
- Creating extensions
  You can create user-defined data types, routines, access methods, and other database objects to suit your needs. You can use application programming interfaces to write user-defined routines and applications that access data in Informix® databases.
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.
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.

TSContainerWindowTable

The TSContainerWindowTable table has one row for each rolling window container.

Two virtual tables are based on the TSContainerWindowTable table. The virtual tables contain a row for each partition:

The TSContainerUsageActiveWindowVTI contains information about the partitions in the active window.
The TSContainerUsageDormantWindowVTI contains information about the partitions in the dormant window.

Table 1. The columns in the TSContainerWindowTable table
Column name	Data type	Description
name	VARCHAR(128)	The name of the rolling window container.
windowinterval	VARCHAR(8)	The size of the interval of each partition: year, month, week, or day.
activewindowsize	INTEGER	The number of partitions in the active window.
dormantwindowsize	INTEGER	The number of partitions in the dormant window.
windowspaces	LVARCHAR(4096)	The list of dbspaces in which partitions are stored.
activewindow	TimeSeries(TSContainerWindow_r)	A row type that contains interval information for the partitions that are in the active window. To view the starting timestamp and location information about the partitions, query the TSContainerUsageActiveWindowVTI table.
dormantwindow	TimeSeries(TSContainerWindow_r)	A row type that contains interval information for the partitions that are in the dormant window. To view the starting timestamp and location information about the partitions, query the TSContainerUsageDormantWindowVTI table.
container_size	INTEGER	The first extent size of the partitions.
container_grow	INTEGER	The next extent size of the partitions.
windowcontrol	INTEGER	A flag that indicates how active partitions are handled when they are manually or automatically detached: 0 = Default. As many as necessary dormant partitions are destroyed. 1 = As many as necessary existing dormant partitions and older active partitions are destroyed. 2 = Dormant partitions are destroyed, but limited to the number specified by the windowdordestroycount value. 3 (2 + 1) = Existing dormant partitions and older active partitions are destroyed, but limited to the number specified by the windowdordestroycount value.
windowdordestroycount	INTEGER	How many partitions can be destroyed in an operation if windowcontrol is 2 or 3. 0 = Default. No dormant partitions are destroyed. A positive integer = The maximum number of partitions that can be destroyed in an operation.