Jump to main content
Product Documentation
Customer Support
HCL OneDB V 1.0.1.0
What's new in
HCL OneDB™
1.0.1.0
Getting Started
Installing
Administering
Security
Client APIs and tools
SQL programming
JSON compatibility
Extending
HCL OneDB™
Designing databases
Embedding
HCL OneDB™
Release information
Search
Home
Extending
HCL OneDB™
Beyond standard relational database objects,
HCL OneDB™
can be extended to handle specialized data types, access methods, routines, and other objects.
HCL OneDB™
includes many built-in extensions that are fully integrated in the database server.
HCL OneDB™
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
HCL OneDB™
.
HCL OneDB™
extensions and
DataBlade®
modules
These topics describe how to use built-in database extensions and separately installed
DataBlade®
modules.
Spatial Data User's Guide
The
HCL OneDB™ Spatial Data User's Guide
contains information to assist you in using the
HCL® OneDB®
spatial extension. The
HCL® OneDB®
spatial extension adds custom data types and supporting routines to the server.
Appendixes
Error messages
Error messages and their explanations
USE37
The geometry boundary is self-intersecting in %FUNCTION%.
Extending
HCL OneDB™
Beyond standard relational database objects,
HCL OneDB™
can be extended to handle specialized data types, access methods, routines, and other objects.
HCL OneDB™
includes many built-in extensions that are fully integrated in the database server.
HCL OneDB™
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
HCL OneDB™
.
HCL OneDB™
extensions and
DataBlade®
modules
These topics describe how to use built-in database extensions and separately installed
DataBlade®
modules.
Database Extensions User's Guide
The
HCL OneDB™
Database Extensions User's Guide
explains how to use the database extensions that come with
HCL OneDB™
: Large Object Locator, MQ messaging, binary data types, basic text search, node data type,
HCL OneDB™
web feature service for Geospatial Data,
and SQL packages.
Performing XML Publishing
The
HCL OneDB™
XML User's Guide
includes information about using built-in functions for XML publishing with
HCL® OneDB®
.
Excalibur Text Search
DataBlade®
Module User's Guide
These topics describe the module and how to access and use its components.
Spatial Data User's Guide
The
HCL OneDB™ Spatial Data User's Guide
contains information to assist you in using the
HCL® OneDB®
spatial extension. The
HCL® OneDB®
spatial extension adds custom data types and supporting routines to the server.
Introducing the IBM Informix Spatial DataBlade Module
Spatial data types
HCL® OneDB®
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.
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
DataBlade®
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
DataBlade®
.
-674
Routine (%FUNCTION%) cannot be resolved.
Spatiotemporal Search for Moving Objects User's Guide
The
HCL OneDB™ Spatiotemporal Search for Moving Objects User's Guide
describes how to program applications to search data from moving objects in
HCL OneDB™
databases using the spatiotemporal search extension.
TimeSeries Data User's Guide
The
HCL OneDB™ TimeSeries Data User's Guide
contains information to assist you in using the TimeSeries extension with
HCL OneDB™
.
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
HCL OneDB™
databases.
USE37
The geometry boundary is self-intersecting in %FUNCTION%.