GSE Messages

Explanation

IBM Spatial Support for Db2 for z/OS encountered an unexpected internal error.

Explanation

IBM Spatial Support for Db2 for z/OS tried unsuccessfully to access its memory pool.

Explanation

Not enough memory was available. Possible reasons are that the supply of memory was too low, or that memory was being used by other applications.

Explanation

IBM Spatial Support for Db2 for z/OS encountered an unexpected error in a parameter passed to an internal function. The operation cannot be completed successfully.

Explanation

IBM Spatial Support for Db2 for z/OS encountered an unexpected error in an internal string operation. The operation cannot be completed successfully.

Explanation

This string lacks a closing delimiter and therefore is not terminated correctly.

Explanation

There was an attempt to raise an error identified by an invalid error-code.

Explanation

All other reason codes indicate an internal error.

Explanation

All other reason codes indicate an internal error.

Explanation

All other reason codes indicate an internal error.

Explanation

All other reason codes indicate an internal error.

Explanation

IBM Spatial Support for Db2 for z/OS was not able to connect to the database. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS was not able to disconnect from the database. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS cannot connect to a database. The command cannot be executed successfully.

Explanation

IBM Spatial Support for Db2 for z/OS tried to connect to the database database-name but was already connected to it.

Explanation

IBM Spatial Support for Db2 for z/OS could not commit the current transaction successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not roll back the current transaction. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute a SELECT statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute a VALUES statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not prepare an SQL statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not open a cursor over a result set successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not close a cursor over a result set successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not fetch a result from a cursor successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not drop the specified database object. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute an INSERT statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute an UPDATE statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute a DELETE statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute a LOCK TABLE statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute a DECLARE GLOBAL TEMPORARY TABLE statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute an EXECUTE IMMEDIATE statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not set a savepoint successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not connect to a database because the name of the database was not specified.

Explanation

IBM Spatial Support for Db2 for z/OS could not retrieve the authorization list for the current user. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not quiesce a table space successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not import data into a table successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not create a trigger successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not execute an ALTER TABLE statement successfully. Db2 returned sql-error.

Explanation

IBM Spatial Support for Db2 for z/OS could not retrieve the message for error gse-error and SQLCODE = sqlcode successfully.

Explanation

IBM Spatial Support for Db2 for z/OS encountered an error while attempting to use the Db2 service to update the system catalog.

Explanation

IBM Spatial Support for Db2 for z/OS encountered a warning condition when preparing an SQL statement. Db2 returned sql-warning. The PREPARE statement was completed successfully.

Explanation

The password used in your attempt to connect to the database is too long.

Explanation

The requested operation cannot be completed successfully because the length of the schema name exceeds the limit for schema names in Db2.

Explanation

The requested operation cannot be completed successfully because the length of the table name exceedslimit for table names in Db2.

Explanation

The requested operation cannot be completed successfully because the length of the column name exceeds the limit for column names in Db2.

Explanation

The requested operation cannot be completed successfully because the length of the index name exceeds limit for index names in Db2.

Explanation

The requested operation cannot be completed successfully because the length of the data type name exceeds limit for data type names in Db2.

Explanation

The file in a path that starts with path cannot be accessed because the length of the complete path would exceed the limit of limit bytes. As a result, the statement that you submitted cannot be executed successfully.

Explanation

The statement cannot be constructed because it would be too long.

Explanation

The requested operation cannot be completed successfully because the string, string, is too long.

Explanation

You requested this operation under a user id that does not hold the privilege or authority to perform the operation.

Explanation

The value value that you entered for argument argument-name was incorrect or misspelled.

Explanation

The requested operation cannot be completed successfully because an argument that it requires was not specified.

Explanation

A spatial reference system is already registered with the spatial column. It cannot be registered again unless it is unregistered first.

Explanation

This spatial column was not registered with a spatial reference system. Therefore, it cannot be unregistered.

Explanation

The requested operation cannot be completed successfully because the table schema-name.table-name does not exist.

Explanation

The requested operation cannot be completed successfully because schema-name.table-name.column-name does not identify an existing column.

Explanation

The requested operation cannot be completed successfully because a data type schema-name.type-name does not exist.

Explanation

The requested operation cannot be completed successfully because the database has not been enabled for spatial operations and, therefore, a IBM Spatial Support for Db2 for z/OS catalog has not been created.

Explanation

The database is already enabled for spatial operations. It cannot be enabled again.

Explanation

Either this column does not have a spatial data type, or it does not belong to a local table.

Explanation

The requested operation cannot be completed successfully because a spatial reference system with the name srs-name does not exist.

Explanation

The requested operation could not be completed successfully because a spatial reference system with the specified numeric identifier srs-id does not exist.

Explanation

A coordinate system named coordsys-name already exists. Another coordinate system with the same name cannot be created.

Explanation

The requested operation cannot be completed successfully because a coordinate system with the name coordsys-name does not exist.

Explanation

You attempted to alter the coordinate system coordsys-name, but did not specify any new values.

Explanation

A spatial reference system named srs-name already exists. Another spatial reference system with the same name cannot be created.

Explanation

The requested operation cannot be completed successfully because a spatial reference system with the name srs-name does not exist.

Explanation

The requested operation cannot be completed successfully because a spatial reference system with the numeric identifier srs-id does not exist.

Explanation

The requested operation cannot be completed successfully because a coordinate system with the numeric identifier coordsys-id does not exist.

Explanation

You attempted to alter the spatial reference system srs-name, but did not specify any new values.

Explanation

The requested operation cannot be completed successfully because IBM Spatial Support for Db2 for z/OS could not locate a function named schema-name.function-name for the geocoder.

Explanation

The SQLDA that was passed to the stored procedure is too small. It does not contain an entry for parameter parameter-name.

Explanation

The data type for parameter parameter-name that is passed to the stored procedure is not correct.

Explanation

A coordinate system named coordsys-name cannot be created because the definition given for it is invalid.

Explanation

The geocoding that you requested cannot be completed successfully because the where clause that determines which rows are to be geocoded is invalid.

Explanation

Your request to create a coordinate system could not be met because the combination of identifiers that you specified for the coordinate system (the name of the organization that defined the system and a number that this organization assigned to it) was not unique. Either these two values must be unique in combination, or they must be null.

Explanation

Your request to create a spatial reference system could not be met because the numeric identifier srs-id that you assigned to it already identifies another spatial reference system. A spatial reference system's identifier must be unique.

Explanation

Your request to create a coordinate system could not be met because the numeric identifier coordsys-id that you assigned to it already identifies another spatial coordinate system. A spatial coordinate system's identifier must be unique.

Explanation

This index already exists. It must be dropped before an index with the same name can be created.

Explanation

At least one spatial reference system exists that is based on the specified coordinate system coordsys-name. The coordinate system cannot be dropped.

Explanation

At least one spatial column exists that is associated with the specified spatial reference system srs-name. The spatial reference system cannot be dropped.

Explanation

The spatial reference system was not altered. Spatial reference systems with numeric identifiers in the range 2000000000 to 2000000317 are predefined geodetic spatial reference systems and cannot be altered.

Explanation

The spatial reference system was not altered. Spatial reference systems with numeric identifiers in the range 2000000000 to 2000000317 are predefined geodetic spatial reference systems and cannot be dropped.

Explanation

If you are importing columns that contain attribute data, you have the choice of either specifying or not specifying which attribute columns are being imported and which columns are in the target table. If you specify these values, this error occurs when the specified number of attribute columns being imported differs from the specified number of columns in the target table. If you do not specify these values, this error occurs when the actual number of columns being imported differs from the actual number of attribute columns in the target table.

Explanation

The spatial data type schema-name.type-name cannot be used during the import of spatial data because it does not exist in the database.

Explanation

A table named schema-name.table-name does not exist in the database. Also, IBM Spatial Support for Db2 for z/OS was not asked to create a table to hold the data that is to be imported. The data was not imported.

Explanation

IBM Spatial Support for Db2 for z/OS was asked to create a table named schema-name.table-name for the imported data, but a table with that name already exists in the database. No data was imported.

Explanation

The column into which you want to import data column-name does not exist in the table schema-name.table-name. No data can be imported into it.

Explanation

The import operation completed successfully but not all records from the file were imported. The exception file contains the records that could not be imported, and the messages file the contains information why those records were not imported.

Explanation

The column column-name in the table schema-name.table-name to import data into has a declared type column-type. column-type does not match the type name expected-type for the data to be imported from the file. No data can be imported.

Explanation

IBM Spatial Support for Db2 for z/OS was asked to create a table to import data into, but the table could not be created successfully. Db2 returned sql-error.

Explanation

Either no method specification was given or method is not a valid method specification. Only 'N' and 'P' are supported method specifications for importing spatial data from a file.

Explanation

An unexpected character found-char was found in the string that identifies the attribute columns to be imported from the file but expected-char was expected. The statement cannot be processed successfully.

Explanation

The column position identifier position specified in the string starting with string is not in the valid range. Only values greater than 0 (zero) and less than or equal to the number of columns in the file to be imported can be specified. The statement cannot be processed successfully.

Explanation

The name of column dbf-column-name in the dBASE file (.dbf) exceeds the limit for column names in Db2.

Explanation

The name dbf-column-name does not identify an existing attribute column in the dBASE file (.dbf). The operation cannot be completed successfully.

Explanation

The dBASE file data type dbf-data-type for the attribute column dbf-column-name in the dBASE file (.dbf) cannot be mapped to a data type in the Db2 database. The shape file cannot be imported.

Explanation

The specified column position position must be a value within the valid range. A valid value must greater than 0 (zero) and less than or equal to the dbf-column-number.

Explanation

A spatial reference system whose numeric identifier is srs-id does not exist. The data cannot be imported.

Explanation

The coordinate system definition coordsys-def used for the spatial data to be imported is too long. It could not be verified with the coordinate system that underlies the spatial reference system that is to be used for the imported data.

Explanation

The coordinate system coordsys-def does not match the coordinate system on which the spatial reference system srs-id is based. Both coordinate systems must be semantically identical.

Explanation

The spatial data covers an area that exceeds the minimum and maximum coordinates of the spatial reference system with the numeric identifier srs-id.

Explanation

The spatial column schema-name.table-name.column-name was registered with a spatial reference system srs-id2 assigned to it. This spatial reference system does not match the spatial reference system srs-id1, which is used for the spatial data to be imported into that column. The data cannot be imported.

Explanation

None of the shape data could be imported. All rows were rejected and written to the exception file.

Explanation

The specified restartCount restart-count must be a greater than or equal to 0 (zero), and less than or equal to record-count.

Explanation

The SQL statement used to import the shape data into the table does not fit into the internal buffer. A possible reason for this might be too many columns are in the file.

Explanation

IBM Spatial Support for Db2 for z/OS tried to use a single INSERT statement to import at least row-count rows, but a buffer to hold the data for these rows could not be allocated. Too much memory was required.

Explanation

The data in the shape file does not appear to have a valid spatial data type. The shape file is possibly corrupted. The data was not imported.

Explanation

The shape file contains a column whose data type is not supported by IBM Spatial Support for Db2 for z/OS. The shape file could not be imported.

Explanation

The header of the shape file shape-file is invalid. The shape file cannot be imported.

Explanation

The offset offset for the record record-number in the index file (.shx) shx-file is invalid. The offset must be greater than or equal to 50 and less than the total length of the main file (.shp) of the shape file. The offset is measured in 16 bit words.

Explanation

The length of the shape in record record-number found in the shape index file shx-file is too short. Each shape must consist of at least 4 bytes (two 16 bit words).

Explanation

IBM Spatial Support for Db2 for z/OS found an incorrect record number record-number in the shape file shp-file when expecting record number expected-number.

Explanation

The size of the shape data record-size indicated in the shape file shp-file does not match the size indicated in the shape index file index-size.

The main file of the shape file (.shp) is not consistent with the index file (.shx) and cannot be processed further.

Explanation

The data for record record-number in the dBASE file dbf-file that contains the attribute information associated with the geometries in the shape file is invalid.

Explanation

The data in shape file shape-file is corrupted. This shape file cannot be imported.

The file name shape-file indicates in which part of the shape file the error was encountered.

Explanation

The definition of the column column-name in the existing table schema-name.table-name indicates that the column may not contain nulls. The column is not included in the list of columns to be imported and Db2 would not produce the values for that column by any other means like default values, a generated column definition or any triggers.

The import operation cannot be completed successfully.

Explanation

The spatial data in the file to be imported uses a spatial reference system with different offsets and scale factors than the spatial reference system with the numeric identifier srs-id. The data cannot be imported successfully.

Explanation

Shape file file-name has an invalid file size. Shape files have a file size that is a multiple of 16-bit words. Therefore, their size is always even. The shape file might be corrupt. It cannot be used.

Explanation

A null value was passed to the function or method instead of a numeric spatial reference system identifier.

Explanation

The spatial reference system identifier srs-id that was provided to the spatial function or method does not identify an existing spatial reference system.

Explanation

A null was specified as a unit of measure. The specification for a unit of measure must be the unit itself (for example, “meter”). It cannot be a null.

Explanation

The unit unit-name that was provided to the spatial function or method does not identify an existing unit of measure.

Explanation

The conversion to the unit unit-name is not supported.

The functions ST_Area, ST_Buffer, ST_Length, and ST_Perimeter cannot accept a linear unit of measure if the given geometry is not in a projected coordinate system.

Explanation

The spatial reference system for the geometry does not have an associated linear or angular unit. The operation cannot be performed in the requested unit of measure.

Explanation

The internal data type identifier for this geometry is a null value and therefore invalid.

This error can occur if the internal representation of the geometry is corrupted, or if the geometry was not constructed by one of the supported constructor functions or methods.

Explanation

The value of the internal type identifier type-id for the geometry is not valid.

This error can occur if the internal representation of the geometry is corrupted, or if the geometry was not constructed by one of the supported constructor functions or methods.

Explanation

A mismatch of internal data type identifiers was found. IBM Spatial Support for Db2 for z/OS expected to retrieve a geometry whose internal data type identifier is type-id2, but instead retrieved a geometry whose internal data type identifier is type-id1.

This error can occur if the internal representation of the geometry is corrupted, or if the geometry was not constructed by one of the supported constructor functions or methods.

Explanation

The specified part number part-number is not valid. A null value was returned.

Explanation

The specified number ring-number for an internal ring is not valid. A null value was returned.

Explanation

The specified point number point-number is not valid. A null value was returned.

Explanation

The intersection matrix matrix specified for the ST_Relate function is not valid. The matrix must be exactly 9 characters long, and each character in the matrix must be one of the following: 'T', 'F', '0', '1', '2', or '*'.

Explanation

The linestring that is to to serve as the new exterior ring for the polygon is not a ring. To be a ring, the linestring must be both simple and closed. One or both of these two conditions is not met.

Explanation

The linestring that is to serve as a new interior ring for the polygon is not a ring. To be a ring, the linestring must be both simple and closed. At least one of these two conditions is not met.

Explanation

The geometry could not be transformed from the spatial reference system it is represented into the spatial reference system with the numeric identifier srs-id. The transform failed with reason code reason-code.

Explanation

The attempted cast operation from the data type with the internal type identifier type-id1 to the data type with the internal type identifier type-id2 is not supported. The geometry cannot be processed further.

Explanation

The geometries that are to be processed by the function or method are not represented using the same dimensions with respect to their Z coordinates and measures.

All the geometries must either contain Z coordinates or contain no Z coordinates. All the geometries must either contain measures or contain no measures.

Explanation

An internal error occurred when a spatial function or method operated on a LOB locator. The reason code reason-code was returned by a locator function.

Explanation

The representation of the geometry in Geographic Markup Language (GML), well-known text (WKT), well-known binary (WKB), or the shape representation would be too long. From append-length bytes, only written-length bytes could be appended to the encoding. A representation of the geometry cannot be created.

Explanation

The representation of the geometry in well-known binary (WKB) representation or the shape representation is only length bytes long. It needs to have at least 4 bytes for the shape representation, exactly 5 bytes for the well-known binary representation for empty geometries, and at least 9 bytes for the well-known binary representation for non-empty geometries. The binary representation must also be long enough to contain all of the geometry points.

Explanation

The internal representation of the geometry is too short. It could not be processed further.

This error can occur if the internal representation of the geometry is corrupted, or if the geometry was not constructed by one of the supported constructor functions or methods.

Explanation

The geometry value is inconsistent and cannot be processed any further.

Explanation

An internal parameter of the geometry indicates that the geometry data contains indicated-number points. But the actual geometry data contains data-number points. Because of this inconsistency, the geometry will not be used further in the processing.

This error can occur if the internal representation of the geometry is corrupted, or if the geometry was not constructed by one of the supported constructor functions or methods.

Explanation

It is invalid to specify an X coordinate, Y coordinate, Z coordinate, or measure for an empty point.

If the point is constructed by the constructor function ST_Point, the point's X and Y coordinates must both be null. Furthermore, no Z coordinate or measure should be specified unless it is a null value.

If the mutators ST_X, ST_Y, ST_Z, or ST_M are used to modify an empty point, the point's X and Y coordinates must both be null. No Z coordinate or measure should be specified unless it is null.

Explanation

If a new point is constructed, both the X and Y coordinates must be specified. Both coordinates must be either null or not null.

If both coordinate values are null, the resulting point will be empty. In that case, no Z coordinate or measure should be specified unless it is null.

Explanation

The byte order in the binary representation of the geometry must be either 0 (zero) or 1 (one), but it is byte-order.

In the well-known binary representation, a byte order of 0 (zero) indicates big endian format, and a byte order of 1 (one) indicates little endian format.

Explanation

The geometry has an invalid number of points num-points. This number must be greater than or equal to 0 (zero).

Explanation

The extent of the geometry in one of the dimensions is invalid. The minimum coordinate min-coord must be less than or equal to the maximum coordinate max-coord for all dimensions of the geometry.

Explanation

A mismatch between internal identifiers was encountered for the computation of a spatial aggregate.

Explanation

A binary representation that is passed as input to this spatial function or method has to represent a geometry whose data type identifier is type-id2. But the representation that was actually passed to the function or method represents a geometry whose data type identifier is type-id1. No geometry could be constructed.

Explanation

A text representation that is passed as input to this spatial function or method has to represent a geometry whose data type identifier is type-id2. But the representation that was actually passed to the function represents a geometry whose data type identifier is type-id1. No geometry could be constructed.

Explanation

The curve was not changed because the specified point to be appended to the curve was empty.

Explanation

The resulting geometry could not be represented accurately in the spatial reference system. One of the scale factors is too small and does not allow for a high enough precision to represent each point that defines the resulting geometry.

For example, consider a linestring with a well-known text representation of 'linestring m ( 10 10 8, 10 11 12 )' represented in a spatial reference system that includes a scale factor of 1 (one) for X coordinates and a scale factor of 1 (one) also for Y coordinates. If the function ST_MeasureBetween is applied to that linestring, and the upper and lower bounds for the measures are 9 and 10, respectively, the resulting linestring, represented in its well-known text representation, would have to be 'linestring m ( 10 10.25 9, 10 10.50 10 )'. However, the scale factor of 1 (one) for the Y coordinates prevents the representation of fractions. The coordinates 10.25 and 10.50 cannot be represented without rounding that would produce an incorrect result. Such coordinates will be removed from the geometry.

Explanation

A character char was expected in the Geography Markup Language of the geometry, but the text string was found instead at position position. The GML representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

The tag given-tag was found in the Geography Markup Language of the geometry at position position, but a tag expected-tag was expected. The GML representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

Unexpected text text was found in the Geography Markup Language of the geometry at position position. A number representing a coordinate was expected instead. The GML representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

An unknown type type was specified in the Geography Markup Language of the geometry. The GML supports points, linestrings, polygons, multipoints, multilinestrings, and multipolygons. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

The GML representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

An attempt was made to read number-bytes bytes from the locator, starting at the offset offset. This exceeds the total length of the data length that is referenced by the locator. The data might be truncated.

For binary representations of a geometry, the binary representation might indicate an invalid binary encoding. The encoded geometry has fewer points than the header indicates.

Explanation

The number of parts number-parts indicated in the binary representation of the geometry is invalid. The number of parts must be larger than 0 (zero) and match the actual number of parts supplied in the encoding.

Explanation

The number of rings number-rings indicated in the binary representation of the polygon or multipolygon is invalid. The number of rings must be larger than 0 (zero) and match the actual number of parts supplied in the encoding.

Explanation

An invalid offset part-offset for a part in the shape representation of the geometry was encountered. A part offset must be larger than or equal to 0 (zero), and each part offset must be larger than the preceding one. The shape representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

The shape representation of the geometry contains an invalid type identifier type-id. The shape data is possibly corrupted. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

The shape encoding contains shape-length bytes, which is too long. To encode a geometry of the specified type type, only expected-length bytes are required. The shape data is possibly corrupted. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

A character char was expected in the well-known text representation of the geometry, but the text string was found instead. The well-known text representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

An unexpected text text was found in the well-known text representation of the geometry. A number representing a coordinate was expected instead. The well-known text representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

An unexpected opening or closing parenthesis was found in the well-known text representation of the geometry at text. The well-known text representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

The end of the well-known text representation was reached unexpectedly. A parenthesis parenthesis was expected. The well-known text representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

The well-known text representation of the geometry contains an unknown type name of type. The well-known text representation is not valid. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

Explanation

The well-known binary representation of the geometry contains an invalid type identifier type-id. The data is possibly corrupted. IBM Spatial Support for Db2 for z/OS cannot construct the geometry successfully.

The type identifiers of separate parts in a geometry type (multipoint, multilinestring, or multipolygon) must have the same indicators for the Z and M coordinates as the geometry type itself.

Explanation

The function ST_GetIndexParms can be used to retrieve the values used for the parameters specified when the index was created.

Explanation

The function ST_GetIndexParms can be used to retrieve the values used for the parameters specified when the index was created.

Explanation

The geometry to be indexed using a Z-Order index is not a point. The Z-Order index supports only points, and the index entry cannot be generated.

Explanation

An invalid parameter was specified when the quad tree index was created. The parameter is identified by its position grid-size-number.

The function ST_GetIndexParms can be used to retrieve the values used for the parameters specified when the index was created.

Explanation

An internal error with code error-code was encountered when a geometry was processed.

Explanation

Not enough memory was available for the spatial function or method that you invoked.

Explanation

An invalid type of geometry was passed to the function or method that you invoked.

Explanation

The number of parts indicated in the binary or text representation of the geometry is greater than the actual number of parts supplied. Either the number of parts indicated is too high or not all the parts were supplied.

Explanation

The wrong type of geometry was passed to the function or method that you invoked. For example, a linestring might have been passed to a function or method that takes only polygons as input.

Explanation

The geometry contains too much detail to be converted to its well-known text representation. The well-known text representation exceeds the maximum allowable length (2 gigabytes).

Explanation

An invalid parameter was encountered.

Explanation

The parameters provided for the function or method have produced an invalid geometry; for example, an invalid shape representation. An invalid geometry is one that violates a geometry property.

Explanation

The function or method expected two geometries of a certain type and did not receive them. For example, the ST_AddPoint function expects two geometries, one a representation and the other a point.

Explanation

The function or method cannot process the geometry passed to it because one or more properties of the geometry violate the geometry's integrity.

Explanation

The construction of a geometry has exceeded the 1-megabyte storage limit; the geometry has too many points.

Explanation

The geometry returned by the ST_Difference, ST_Intersection, ST_SymDifference, or ST_Union function is too small to be represented accurately in the current spatial reference system.

For example, this can happen if the internal computation constructs a very thin polygon, but the scale factor of the spatial reference system is so low that the geometry would collapse to a linestring if it were to be represented in this spatial reference system. It would lose its property as a polygon.

Explanation

The ST_Buffer function has created a buffer around the provided geometry that is outside the range of the coordinates to which the spatial reference system applies.

Refer to the IBM Spatial Support for Db2 for z/OS catalog view DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS to determine the minimum and maximum absolute values for each of the dimensions. These values must not be exceeded by the calculated buffer.

Explanation

A scale factor for any of the four dimensions (X, Y, Z, and M) must be greater than or equal to 1 (one).

Explanation

A coordinate cannot be represented in the spatial reference system because, in at least one dimension, it exceeds the possible minimum or maximum absolute value within the system's range of values.

Refer to the IBM Spatial Support for Db2 for z/OS catalog view DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS to determine the minimum and maximum absolute values for each of the dimensions.

Explanation

There are one or more errors in the text representation of the definition of the coordinate system on which the geometry's spatial reference system is based. The representation cannot be converted into a valid projection.

Explanation

An error occurred during an attempt to project a geometry to another spatial reference system.

Explanation

The rings of a polygon overlap. By definition, the inner and outer rings of a polygon must not overlap. They can intersect only at a tangent, which means the rings can only touch but not cross each other.

Explanation

Note that if the geometry to be constructed is empty, these rules do not apply.

Explanation

The inner and outer rings that define the polygon must be closed. A ring is closed if the start and end points are identical in the X and Y dimensions. If the polygon has Z coordinates, then the start and end points must also be identical to the Z coordinates. Note that this rule does not apply to measures, which can be different for the start and end points.

Explanation

The exterior ring of the polygon is not valid.

The exterior ring of a polygon must enclose all interior rings of the polygon. All interior rings have to be completely inside the area that is defined by the outer ring and must not cross the exterior ring.

Explanation

The specified polygon lacks an interior that covers an area that is not the empty set in the X and Y dimensions.

A geometry is a polygon only if its coordinates span two dimensions in the 2-dimensional space defined by the X and Y coordinates.

Explanation

The exterior rings of distinct polygons in a multipolygon overlap. Distinct polygons in a multipolygon must not overlap, and the boundaries must touch only at a finite number of points. That means the polygons must not share line segments.

The scale factors of the spatial reference system that is used to represent the geometry influences the precision that applies to the coordinates. Rounding operations performed when the geometry is converted to the representation in the spatial reference system might cause a loss in precision and, subsequently, this error.

Explanation

A ring of a polygon cannot intersect itself. The start and end points on each ring of the polygon must be reached twice when traversing the ring. All other points must only be reached once. This holds true also for the line segments that define the rings of the polygon.

The scale factors of the spatial reference system that is used to represent the geometry influences the precision that applies to the coordinates. Rounding operations performed when the geometry is converted to the representation in the spatial reference system might cause a loss in precision and, subsequently, this error.

Explanation

The number of parts indicated in the binary or text representation of the geometry is not equal to the actual number of parts supplied. Either the number is too low or too many parts were supplied to the function or method.

Explanation

The two spatial reference systems are not compatible. They cannot be transformed into or compared with one another. The operation cannot be completed successfully.

Explanation

The number of bytes in the specified binary representation of the geometry is too small.

Explanation

An invalid internal geometry type was encountered. The geometry is not valid and will not be processed any further.

Explanation

The byte order in the binary representation of the geometry has an invalid value. The byte order must be 0 (zero) or 1 (one).

In the well-known binary representation, a byte order of 0 (zero) indicates big endianess, and a byte order of 1 (one) indicates little endianess.

Explanation

An empty geometry was passed to the ST_AsBinary function, even though it is not allowed as input.

Explanation

The specified point is intended to be appended to the curve, but it is not valid.

Explanation

The specified point is intended to be changed or removed, but it does not exist in the curve.

Explanation

No valid index was specified. The index schema parameter, the index name parameter, or both, are null. The index parameter values cannot be derived.

Explanation

The specified name of the index for which you want parameter information retrieved does not exist or does not identify a spatial index. This name is schema-name.index-name.

Explanation

The parameter number number is not valid for the specified spatial index.

Explanation

The specified column does not exist in the table. At least one of the following - table schema, table name, or column name - is a null value. The index parameter for an index on a column cannot be derived.

Explanation

The required parameter was not found.

Explanation

An environment handle could not be allocated using the Call Level Interface (CLI). The operation cannot be completed successfully.

Explanation

An unexpected error cli-error with native error code = native-error-code occurred while IBM Spatial Support for Db2 for z/OS was allocating a connection handle.

Explanation

An unexpected error cli-error with native error code = native-error-code occurred while IBM Spatial Support for Db2 for z/OS was connecting to the database.

Explanation

An unexpected error cli-error with native error code = native-error-code occurred while IBM Spatial Support for Db2 for z/OS was allocating a statement handle.

Explanation

An unexpected error cli-error with native error code = native-error-code occurred while IBM Spatial Support for Db2 for z/OS was preparing an SQL statement.

Explanation

An unexpected error cli-error with native error code = native-error-code occurred while IBM Spatial Support for Db2 for z/OS was binding parameters to an SQL statement.

Explanation

An unexpected error cli-error with native error code = native-error-code occurred while IBM Spatial Support for Db2 for z/OS was executing an SQL statement.

Explanation

An unexpected error cli-error with native error code = native-error-code occurred while IBM Spatial Support for Db2 for z/OS was ending a transaction.

Explanation

The specified option, option, is invalid.

Explanation

IBM Spatial Support for Db2 for z/OS encountered an unexpected internal error with the text error-text.

Explanation

An internal failure occurred while IBM Spatial Support for Db2 for z/OS was retrieving an error message.