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.
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.
Appendixes
Error messages
Error messages and their explanations
USE27
Unknown or unsupported geometry data structure version (%VERSION%) found in %FUNCTION%.

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.
    - Getting started with spatial data
      The HCL® Informix® spatial solution embeds a geographic information system (GIS) within the HCL Informix database server. The HCL Informix spatial data types integrate spatial and non-spatial data, providing a seamless point of access using SQL (Structured Query Language).
    - Spatial data types
      HCL® Informix® spatial data types are divided into two categories: the base geometry subclasses and the homogeneous collection subclasses.
    - Data exchange formats
      You can use several different GIS data exchange formats for spatial data.
    - R-tree indexes
      An index organizes access to data so that entries can be found quickly, without searching every row. The R-tree access method enables you to index multidimensional objects.
    - Run parallel queries
      Running queries in parallel distributes the work for one aspect of a query among several processors and can dramatically improve performance.
    - Estimate your spatial data
      The total amount of space you need for spatial data is equal to the size of spatial tables plus the size of the spatial indexes.
    - Spatial functions
      Use specific spatial data type functions to perform operations on spatial data.
    - Spatial Java™ API
      The spatial Java™ API enables Java applications to access geometry features that are stored in databases that contain spatial data. The spatial Java API provides classes to work with spatial objects from Java client-side programs. The client-side objects are called value objects. Spatial value objects can also be created and examined by Java methods that parallel some of the spatial data functions.
    - Appendixes
      - Load and unload shapefile data
        Use the infoshp, loadshp, and unloadshp utilities for working with spatial data contained in ESRI shapefiles.
      - OGC well-known text representation of spatial reference systems
        These topics explain how to represent a spatial reference system using a text string and provides information about supported units of measure, spheroids, datums, prime meridians, and projections.
      - OGC well-known text representation of geometry
      - OGC well-known binary representation of geometry
      - ESRI shape representation
      - Error messages
        Error messages and their explanations
        USE01
        Unable to establish a connection in %FUNCTION%.
        7USE02
        Function %FUNCTION% is unable to allocate memory.
        USE03
        Invalid geometry in %FUNCTION%.
        USE04
        Function %FUNCTION% not applicable to type %TYPE%.
        USE05
        This function is not yet implemented.
        USE06
        Unknown ESRI shape library error (%ERRCODE%) in %FUNCTION%.
        USE07
        Internal SAPI error. %SAPIFUNC% returned %RETVAL%. Failure in %FUNCNAME%.
        USE08
        Nearest-neighbor queries require an index scan.
        USE09
        Unknown or unsupported shape file type (%TYPE%) found in %FUNCTION%.
        USE10
        Unknown or unsupported OpenGIS WKB type (%TYPE%) found in %FUNCTION%.
        USE11
        Invalid SRID %SRID% or NULL in %FUNCTION%.
        USE12
        Unknown or unsupported geometry type (%TYPE%) found in %FUNCTION%.
        USE13
        Spatial not installed correctly: the spatial_references table does not exist.
        USE14
        Unknown spatial reference identifier %SRID%.
        USE15
        Invalid coordinate reference system object in function %FUNCTION%.
        USE16
        Unable to get the geometry data pointer from the server in %FUNCTION%.
        USE17
        Geometry verification failed.
        USE18
        Buffer operation failed.
        USE19
        Coordinates out of bounds in %FUNCTION%.
        USE20
        Invalid parameter in function %FUNCTION%.
        USE21
        Geometry integrity error in function %FUNCTION%.
        USE22
        Too many points in feature.
        USE23
        Spatial reference conflict, %SRID1% vs %SRID2%.
        USE24
        Incompatible geometries in function %FUNCTION%.
        USE25
        Subscript %SUBSCRIPT% out of range in function %FUNCTION%.
        USE26
        Subtype mismatch: received subtype=%TYPE1%, expected subtype=%TYPE2%.
        USE27
        Unknown or unsupported geometry data structure version (%VERSION%) found in %FUNCTION%.
        USE28
        Invalid text in %FUNCTION%.
        USE29
        Unexpected system error in %FUNCTION%.
        USE30
        Overlapping polygon rings in %FUNCTION%.
        USE31
        Too few points for geometry type in %FUNCTION%.
        USE32
        Polygon does not close in %FUNCTION%.
        USE33
        Interior ring not enclosed by exterior ring in %FUNCTION%.
        USE34
        Polygon has no area in %FUNCTION%.
        USE35
        Polygon ring contains a spike in %FUNCTION%.
        USE36
        Multipolygon exterior rings overlap in %FUNCTION%.
        USE37
        The geometry boundary is self-intersecting in %FUNCTION%.
        USE38
        The geometry has too many parts in %FUNCTION%.
        USE39
        Mismatched text string parentheses in %FUNCTION%.
        USE40
        Unknown or unsupported ESRI entity type (%TYPE%) found in %FUNCTION%.
        USE41
        The projection string for your SRID is invalid in %FUNCTION%.
        USE42
        Nearest-neighbor queries are not supported by the current version of the server.
        USE43
        %PARAM1% value must be less than %PARAM2% value.
        USE44
        Unknown OGIS WKB byte-order byte encountered in %FUNCTION%.
        USE45
        OGIS WKB geometry collection type is not supported.
        USE46
        USE47
        Cannot create SE_Metadata lohandle file %NAME%. Check directory permissions.
        USE48
        SE_Metadata lohandle file %FILE% not found, unreadable, or corrupt. Execute function SE_MetadataInit to reinitialize.
        USE49
        SE_MetadataTable is a read only table.
        USE50
        Vertex not found in %FUNCTION%.
        USE51
        SE_Metadata smart blob is corrupt or unreadable.
        USE52
        SE_Metadata memory cache is locked.
        USE53
        Spatial datablade assert failure. File = %FILE%, line = %LINE%.
        USE54
        You must create a default sbspace before you can register the Spatial .
        -674
        Routine (%FUNCTION%) cannot be resolved.
  - 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.
  - 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.

USE27

Unknown or unsupported geometry data structure version (%VERSION%) found in %FUNCTION%.

Future versions of the Spatial may not be able to interpret geometries stored using this version of the module. Similarly, this version of the Spatial may not be able to interpret geometries stored using a future version.

If an upgrade mechanism is provided with a new version of this module, use it on your data as described in the release notes. If an upgrade mechanism is not provided, you must unload your data with the old module version and reload it with the new version.