Jump to main content
HCL Logo 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
  1. Home
  2. 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™.
  3. HCL OneDB™ extensions and DataBlade® modulesThese topics describe how to use built-in database extensions and separately installed DataBlade® modules.
  4. Spatial Data User's GuideThe 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.
  5. Appendixes
  6. Error messages
  7. Error messages and their explanations
  8. USE41The projection string for your SRID is invalid 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® modulesThese topics describe how to use built-in database extensions and separately installed DataBlade® modules.
      • Database Extensions User's GuideThe 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 PublishingThe 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 GuideThese topics describe the module and how to access and use its components.
      • Spatial Data User's GuideThe 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 typesHCL® OneDB® spatial data types are divided into two categories: the base geometry subclasses and the homogeneous collection subclasses.
        • Data exchange formatsYou can use several different GIS data exchange formats for spatial data.
        • R-tree indexesAn 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 queriesRunning queries in parallel distributes the work for one aspect of a query among several processors and can dramatically improve performance.
        • Estimate your spatial dataThe 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 functionsUse specific spatial data type functions to perform operations on spatial data.
        • Appendixes
          • Load and unload shapefile dataUse the infoshp, loadshp, and unloadshp utilities for working with spatial data contained in ESRI shapefiles.
          • OGC well-known text representation of spatial reference systemsThese 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
              • USE01Unable to establish a connection in %FUNCTION%.
              • 7USE02Function %FUNCTION% is unable to allocate memory.
              • USE03Invalid geometry in %FUNCTION%.
              • USE04Function %FUNCTION% not applicable to type %TYPE%.
              • USE05This function is not yet implemented.
              • USE06Unknown ESRI shape library error (%ERRCODE%) in %FUNCTION%.
              • USE07Internal SAPI error. %SAPIFUNC% returned %RETVAL%. Failure in %FUNCNAME%.
              • USE08Nearest-neighbor queries require an index scan.
              • USE09Unknown or unsupported shape file type (%TYPE%) found in %FUNCTION%.
              • USE10Unknown or unsupported OpenGIS WKB type (%TYPE%) found in %FUNCTION%.
              • USE11Invalid SRID %SRID% or NULL in %FUNCTION%.
              • USE12Unknown or unsupported geometry type (%TYPE%) found in %FUNCTION%.
              • USE13Spatial DataBlade® not installed correctly: the spatial_references table does not exist.
              • USE14Unknown spatial reference identifier %SRID%.
              • USE15Invalid coordinate reference system object in function %FUNCTION%.
              • USE16Unable to get the geometry data pointer from the server in %FUNCTION%.
              • USE17Geometry verification failed.
              • USE18Buffer operation failed.
              • USE19Coordinates out of bounds in %FUNCTION%.
              • USE20Invalid parameter in function %FUNCTION%.
              • USE21Geometry integrity error in function %FUNCTION%.
              • USE22Too many points in feature.
              • USE23Spatial reference conflict, %SRID1% vs %SRID2%.
              • USE24Incompatible geometries in function %FUNCTION%.
              • USE25Subscript %SUBSCRIPT% out of range in function %FUNCTION%.
              • USE26Subtype mismatch: received subtype=%TYPE1%, expected subtype=%TYPE2%.
              • USE27Unknown or unsupported geometry data structure version (%VERSION%) found in %FUNCTION%.
              • USE28Invalid text in %FUNCTION%.
              • USE29Unexpected system error in %FUNCTION%.
              • USE30Overlapping polygon rings in %FUNCTION%.
              • USE31Too few points for geometry type in %FUNCTION%.
              • USE32Polygon does not close in %FUNCTION%.
              • USE33Interior ring not enclosed by exterior ring in %FUNCTION%.
              • USE34Polygon has no area in %FUNCTION%.
              • USE35Polygon ring contains a spike in %FUNCTION%.
              • USE36Multipolygon exterior rings overlap in %FUNCTION%.
              • USE37The geometry boundary is self-intersecting in %FUNCTION%.
              • USE38The geometry has too many parts in %FUNCTION%.
              • USE39Mismatched text string parentheses in %FUNCTION%.
              • USE40Unknown or unsupported ESRI entity type (%TYPE%) found in %FUNCTION%.
              • USE41The projection string for your SRID is invalid in %FUNCTION%.
              • USE42Nearest-neighbor queries are not supported by the current version of the server.
              • USE43%PARAM1% value must be less than %PARAM2% value.
              • USE44Unknown OGIS WKB byte-order byte encountered in %FUNCTION%.
              • USE45OGIS WKB geometry collection type is not supported.
              • USE46
              • USE47Cannot create SE_Metadata lohandle file %NAME%. Check directory permissions.
              • USE48SE_Metadata lohandle file %FILE% not found, unreadable, or corrupt. Execute function SE_MetadataInit to reinitialize.
              • USE49SE_MetadataTable is a read only table.
              • USE50Vertex not found in %FUNCTION%.
              • USE51SE_Metadata smart blob is corrupt or unreadable.
              • USE52SE_Metadata memory cache is locked.
              • USE53Spatial datablade assert failure. File = %FILE%, line = %LINE%.
              • USE54You must create a default sbspace before you can register the Spatial DataBlade®.
              • -674Routine (%FUNCTION%) cannot be resolved.
      • Spatiotemporal Search for Moving Objects User's GuideThe 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 GuideThe HCL OneDB™ TimeSeries Data User's Guide contains information to assist you in using the TimeSeries extension with HCL OneDB™.
    • Creating extensionsYou 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.

USE41

The projection string for your SRID is invalid in %FUNCTION%.

The projection string stored in the spatial_references table was determined to be invalid.

Compare the projection string with the valid projection strings listed in OGC well-known text representation of spatial reference systems.

  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences