GSE3000-3999

GSE3000N

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

Specify a numeric spatial reference system identifier for an existing spatial reference system. When using Spatial Extender, refer to the DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, otherwise the SYSCAT.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, for the defined spatial reference systems.

msgcode: -3000

sqlstate: 38SU0

GSE3001N

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

Specify an existing numeric spatial reference system identifier or create a spatial reference system that is identified by srs-id. To check for existing reference systems, refer to the DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS catalog view when using Spatial Extender, otherwise use the SYSCAT.ST_SPATIAL_REFERENCE_SYSTEMS catalog view.

msgcode: -3001

sqlstate: 38SU1

GSE3002N

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.

Either omit the unit of measure when calling the spatial function or method, or specify an existing unit of measure. When using Spatial Extender, consult the spatial catalog view DB2GSE.ST_UNITS_OF_MEASURE for supported units, use catalog view SYSCAT.ST_UNITS_OF_MEASURE.

msgcode: -3002

sqlstate: 38SU2

GSE3003N

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

Either omit the unit of measure when calling the spatial function or method, or specify an existing unit of measure. When using Spatial Extender, consult the spatial catalog view DB2GSE.ST_UNITS_OF_MEASURE for supported units, use catalog view SYSCAT.ST_UNITS_OF_MEASURE.

msgcode: -3003

sqlstate: 38SU3

GSE3004N

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.

msgcode: -3004

sqlstate: 38SU4

GSE3005N

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.

Either represent the geometry in a correct spatial reference system, which does have an associated linear or angular unit of measure, or omit the unit parameter when you request the operation.

msgcode: -3005

sqlstate: 38SU5

GSE3006N

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.

Construct the geometry again by using one of the supported constructor functions or methods.

msgcode: -3006

sqlstate: 38SU6

GSE3007N

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.

Construct the geometry again by using one of the supported constructor functions or methods.

msgcode: -3007

sqlstate: 38SU7

GSE3008N

A mismatch of internal data type identifiers was found. The spatial operation 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.

Construct the geometry again by using one of the supported constructor functions or methods.

msgcode: -3008

sqlstate: 38SU8

GSE3009W

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

If the geometry is not empty, then specify a valid part number, which should be greater than 0 (zero) and less then or equal to the maximum number of parts in the geometry collection.

You can use the ST_NumGeometries function to determine the number of parts of the geometry collection.

If the geometry is empty, the method should not be applied.

msgcode: +3009

sqlstate: 01HS0

GSE3010W

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

If the polygon value is not empty, then specify a valid ring number, which should be greater than or equal to 1 (one) and less than or equal to the maximum number of interior rings in the polygon.

If the polygon is empty, the function or method should not be applied. You can use the function ST_NumInteriorRings to determine the number of interior rings of the polygon.

msgcode: +3010

sqlstate: 01HS1

GSE3011W

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

If the curve value is not empty, then specify a valid point number, which should be greater than 0 (zero) and less than or equal to the maximum number of points in the curve. If the curve is empty, the function or method should not be applied.

You can use the ST_NumPoints function to determine the number of points used to define the curve.

msgcode: +3011

sqlstate: 01HS2

GSE3012N

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 '*'.

Specify a valid intersection matrix.

msgcode: -3012

sqlstate: 38SU9

GSE3013N

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.

Specify a simple and closed linestring for the new exterior ring of the polygon.

msgcode: -3013

sqlstate: 38SUA

GSE3014N

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.

Specify a simple and closed linestring for the new interior ring of the polygon.

msgcode: -3014

sqlstate: 38SUB

GSE3015N

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.

Represent the geometry in a spatial reference system that can be transformed into the spatial reference system identified by srs-id, or specify a different spatial reference system identifier to transform the geometry into.

msgcode: -3015

sqlstate: 38SUC

GSE3016N

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.

Specify a supported cast operation. For more information, refer to the IBM DB2 SQL Reference for the supported cast functions.

msgcode: -3016

sqlstate: 38SUD

GSE3017E

The conversion to LineString is only supported for MultiPoint geometries.

Make sure to use a MultiPoint geometry as input for the conversion.

msgcode: -3017

sqlstate: 38SUE

GSE3018E

The KML document cannot be converted into a geometry object due to the following reason:

1

No geometry type found.

2

Missing coordinates.

3

Invalid KML format.

4

Missing end-tag.

5

Measures are not supported.

6

Invalid coordinate format.

7

Multi-Geometries can only contain the same geometry type.

8

Document not marked as multi-geometry, but includes multiple geometries.

Review the KML document and fix the format.

msgcode: -3018

sqlstate: 38SUF

GSE3019E

The geometry cannot be exported to KML due to the following reason:

1

The additional attribute must be tagged with one of the following options: extrude, tessellate, or altitudeMode.

2

Cannot write points into the KML output.

3

Failure to read the points defining the geometry.

4

The number of points in a part of the geometry is too large.

5

Invalid selection for KML header printout.

1

Review the syntax of the additional attribute.

2,3

Verify that the geometry is valid and retry. If the failure persists, contact IBM Support.

4

Use a smaller precision for the output (default is 16).

5

Use 0 to skip or 1 to print the KML header.

msgcode: -3019

sqlstate: 38SUG

GSE3020N

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.

Provide geometries to the function or method that are represented using the same dimensions with respect to their Z coordinates and measures.

msgcode: -3020

sqlstate: 38SUH

GSE3021N

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.

Refer to the DB2 Application Development Guide to determine the meaning of reason-code returned from the LOB locator operation and correct the problem. If the problem persists, contact IBM Software Support.

msgcode: -3021

sqlstate: 38SUI

GSE3022N

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.

Simplify the geometry by omitting points that are not essential for the geometry. You can use the ST_Generalize function for this procedure. Alternatively, break down the geometry into several smaller geometries.

msgcode: -3022

sqlstate: 38SUJ

GSE3023N

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.

Provide a valid well-known binary representation or shape representation to the function or method.

msgcode: -3023

sqlstate: 38SUK

GSE3024N

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.

Construct the geometry again using one of the supported constructor functions or methods.

msgcode: -3024

sqlstate: 38SUL

GSE3025N

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

Recreate the geometry from a valid binary or text representation.

msgcode: -3025

sqlstate: 38SUM

GSE3026N

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.

Recreate the geometry using the functions or methods supported by the spatial feature.

msgcode: -3026

sqlstate: 38SUN

GSE3027N

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.

Use mutators ST_X, ST_Y, ST_Z, or ST_M to modify points that are not empty, or construct the point by specifying both X and Y coordinates with values that are not null.

msgcode: -3027

sqlstate: 38SUO

GSE3028N

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.

Specify null values for both the X and Y coordinates, or specify values that are not null for both coordinates.

msgcode: -3028

sqlstate: 38SUP

GSE3029N

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.

Correct the byte order in the binary representation so that it is either 0 (zero) or 1 (one).

msgcode: -3029

sqlstate: 38SUQ

GSE3030N

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

Construct the geometry by using the functions or methods supported by the spatial feature.

msgcode: -3030

sqlstate: 38SUR

GSE3031N

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.

Construct the geometry by using the functions or methods supported by the spatial feature.

msgcode: -3031

sqlstate: 38SUS

GSE3032N

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

Make sure that you use the aggregate function in a way that is supported by the spatial feature.

msgcode: -3032

sqlstate: 38SUT

GSE3033N

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.

Either call the correct function or method which constructs geometries of type type-id2 or correct the binary representation to represent a geometry of type-id1.

msgcode: -3033

sqlstate: 38SUU

GSE3034N

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.

Either call the correct function which constructs geometries of type type-id1 or correct the text representation to represent a geometry of type-id2.

msgcode: -3034

sqlstate: 38SUV

GSE3035W

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

Append a point that is not empty to the curve.

msgcode: +3035

sqlstate: 01HS3

GSE3036W

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.

Represent the geometry in a spatial reference system that uses larger scale factors. Alternatively, choose different parameters that influence the resulting geometry.

msgcode: +3036

sqlstate: 01HS4

GSE3037N

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. The spatial operation cannot construct the geometry successfully.

Correct the GML representation and construct the geometry again.

msgcode: -3037

sqlstate: 38SUW

GSE3038N

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. The spatial operation cannot construct the geometry successfully.

Correct the GML representation and construct the geometry again.

msgcode: -3038

sqlstate: 38SUX

GSE3039N

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. The spatial operation cannot construct the geometry successfully.

Correct the GML representation and construct the geometry again.

msgcode: -3039

sqlstate: 38SUY

GSE3040N

An unknown type type was specified in the Geography Markup Language of the geometry. The GML supports points, linestrings, polygons, multipoints, multilinestrings, and multipolygons. The spatial operation cannot construct the geometry successfully.

Correct the GML representation and construct the geometry again.

msgcode: -3040

sqlstate: 38SUZ

GSE3041N

The GML representation is not valid. The spatial operation cannot construct the geometry successfully.

Correct the GML representation and construct the geometry again.

msgcode: -3041

sqlstate: 38SV0

GSE3042N

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.

Verify and correct the representation of the geometry. Make sure that the binary or textual representation does not get truncated before it is passed to the spatial function.

msgcode: -3042

sqlstate: 38SV1

GSE3043N

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.

Specify the correct number of parts or supply all parts for the geometry.

msgcode: -3043

sqlstate: 38SV2

GSE3044N

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.

Specify the correct number of rings or supply all rings for the geometry.

msgcode: -3044

sqlstate: 38SV3

GSE3045N

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 preceeding one. The shape representation is not valid. The spatial operation cannot construct the geometry successfully.

Correct the shape representation and construct the geometry again.

msgcode: -3045

sqlstate: 38SV4

GSE3046N

The shape representation of the geometry contains an invalid type identifier type-id. The shape data is possibly corrupted. The spatial operation cannot construct the geometry successfully.

Verify and correct the shape representation of the geometry.

msgcode: -3046

sqlstate: 38SV5

GSE3047N

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. The spatial operation cannot construct the geometry successfully.

Verify and correct the shape representation of the geometry.

msgcode: -3047

sqlstate: 38SV6

GSE3048N

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. The spatial operation cannot construct the geometry successfully.

Correct the well-known text representation and construct the geometry again.

msgcode: -3048

sqlstate: 38SV7

GSE3049N

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. The spatial operation cannot construct the geometry successfully.

Correct the well-known text representation and construct the geometry again.

msgcode: -3049

sqlstate: 38SV8

GSE3050N

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. The spatial operation cannot construct the geometry successfully.

Correct the well-known text representation and construct the geometry again.

msgcode: -3050

sqlstate: 38SV9

GSE3051N

The end of the well-known text representation was reached unexpectedly. A parenthesis parenthesis was expected. The well-known text representation is not valid. The spatial operation cannot construct the geometry successfully.

Correct the well-known text representation and construct the geometry again.

msgcode: -3051

sqlstate: 38SVA

GSE3052N

The well-known text representation of the geometry contains an unknown type name of type. The well-known text representation is not valid. The spatial operation cannot construct the geometry successfully.

Correct the well-known text representation and construct the geometry again.

msgcode: -3052

sqlstate: 38SVB

GSE3053N

The well-known binary representation of the geometry contains an invalid type identifier type-id. The data is possibly corrupted. The spatial operation cannot construct the geometry successfully.

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

Verify and correct the well-known binary representation of the geometry.

msgcode: -3053

sqlstate: 38SVC

GSE3300N

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

Drop the grid index and create a new grid index using valid grid sizes only.

msgcode: -3300

sqlstate: 38SI0

GSE3301N

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

Drop the spatial z-order index and create a new index using only valid parameters.

msgcode: -3301

sqlstate: 38SI1

GSE3302N

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.

Do not insert a geometry that is not a point into a column that has a Z-Order index defined on it. Either drop the index or do not insert the geometry.

msgcode: -3302

sqlstate: 38SI2

GSE3303N

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.

Drop the spatial quad tree index and create a new index using only valid parameters.

msgcode: -3303

sqlstate: 38SI3

GSE3400C

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

Note the error and contact IBM Software Support.

msgcode: -3400

sqlstate: 38SS0

GSE3402C

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

Make more memory available to the database manager process that executes the function or method.

msgcode: -3402

sqlstate: 38SS2

GSE3403N

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

Specify a valid geometry. For more information, refer to the Spatial documentation.

msgcode: -3403

sqlstate: 38SS3

GSE3405N

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.

Specify the correct number of parts or supply all parts for the geometry.

msgcode: -3405

sqlstate: 38SS5

GSE3406N

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.

Either pass to the function or method a type of geometry that it can process, or use a function or method that accepts the type of geometry that you want to pass.

msgcode: -3406

sqlstate: 38SS6

GSE3407N

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).

Simplify the geometry - for example, by using the ST_Generalize function - or convert the geometry to its well-known binary representation.

msgcode: -3407

sqlstate: 38SS7

GSE3408N

An invalid parameter was encountered.

Refer to the Spatial documentation for the function's correct syntax and retry the operation. If the problem persists, contact IBM Software Support.

msgcode: -3408

sqlstate: 38SS8

GSE3409N

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.

Construct the geometry again from a valid representation.

msgcode: -3409

sqlstate: 38SS9

GSE3410N

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.

Specify geometries that the function or method accepts as valid input. To determine what types of geometries are valid for this function or method, refer to the Spatial documentation.

msgcode: -3410

sqlstate: 38SSA

GSE3411N

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

Use the ST_IsValid function to validate the geometry. Construct the geometry again from a correct representation if it is not valid.

msgcode: -3411

sqlstate: 38SSB

GSE3412N

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

Construct a geometry that contains fewer points. Or, if possible, remove some points. For performance and storage considerations, include only those points that are needed to render a geometry.

msgcode: -3412

sqlstate: 38SSC

GSE3413N

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.

Use a spatial reference system for the calculation which allows for a higher resolution. The ST_Transform function can be used to convert a geometry from one spatial reference system into another.

msgcode: -3413

sqlstate: 38SSD

GSE3414N

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.

When using Spatial Extender, refer to the DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, otherwise the SYSCAT.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, to determine the minimum and maximum absolute values for each of the dimensions. These values must not be exceeded by the calculated buffer.

Either reduce the distance to be used for the buffer calculation, or change the spatial reference system in which the calculation is done. The ST_Transform function can be used to convert geometries from one spatial reference system into another.

msgcode: -3414

sqlstate: 38SSE

GSE3415N

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

Use a correctly defined spatial reference system to represent the geometry.

msgcode: -3415

sqlstate: 38SSF

GSE3416N

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.

Determine whether the coordinate is correct. If it is, determine whether it fits within the extent of the spatial reference system that you are using. For information about this spatial reference system, consult the DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS catalog view for Spatial Extender, otherwise the SYSCAT.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, to determine the minimum and maximum absolute values for each of the dimensions.

msgcode: -3416

sqlstate: 38SSG

GSE3417N

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.

Verify the coordinate system definition of the spatial reference system. Alternatively, construct the geometry in a spatial reference system that is associated with a valid coordinate system. The ST_EqualCoordsys function can be used to verify the coordinate system definition by comparing it with itself.

msgcode: -3417

sqlstate: 38SSH

GSE3418N

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

Make sure that the geometry is within the legal domain of the projection.

msgcode: -3418

sqlstate: 38SSI

GSE3419N

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.

Specify the coordinates for the polygon that will not produce overlapping rings. Note that the scale factors of the spatial reference system for the geometry have an influence on the precision.

msgcode: -3419

sqlstate: 38SSJ

GSE3420N

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

Construct the geometry again from a valid set of points.

msgcode: -3420

sqlstate: 38SSK

GSE3421N

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.

Specify inner and outer rings for the polygon that have the same points for the start and end points in the X and Y dimension. If the polygon has Z coordinates, the start and end points of the Z coordinate points also have to be identical. If the polygon has measures, the start and end points can be different.

msgcode: -3421

sqlstate: 38SSL

GSE3422N

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.

Specify a geometry that consists of a valid set of interior and exterior rings, where the interior rings lie fully within the area that is enclosed by the exterior ring to represent it.

If the geometry has multiple polygons, use a multipolygon.

msgcode: -3422

sqlstate: 38SSM

GSE3423N

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.

Specify a polygon that encloses an area that is not empty. If the polygon is empty, construct an empty polygon.

msgcode: -3423

sqlstate: 38SSN

GSE3424N

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.

Specify coordinates for the polygon that will not produce overlapping rings.

Note that the scale factors of the spatial reference system have an influence on precision.

When using Spatial Extender, refer to the DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, otherwise the SYSCAT.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, for the scale factor used for the spatial reference system in which the geometry will be represented.

msgcode: -3424

sqlstate: 38SSO

GSE3425N

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.

Construct a valid polygon in which the rings do not intersect themselves.

When using Spatial Extender, refer to the DB2GSE.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, otherwise the SYSCAT.ST_SPATIAL_REFERENCE_SYSTEMS catalog view, for the scale factor used for the spatial reference system in which the geometry will be represented.

msgcode: -3425

sqlstate: 38SSP

GSE3426N

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.

Specify the correct number of parts or supply all parts for the geometry.

msgcode: -3426

sqlstate: 38SSQ

GSE3427N

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

Specify two compatible spatial reference systems.

msgcode: -3427

sqlstate: 38SSR

GSE3428N

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

Specify a valid binary representation of the geometry.

msgcode: -3428

sqlstate: 38SSS

GSE3429N

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

Construct the geometry again from a valid binary or text representation.

msgcode: -3429

sqlstate: 38SST

GSE3430N

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.

Specify a valid byte order in the binary representation for the geometry.

msgcode: -3430

sqlstate: 38SSU

GSE3431N

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

Edit the SQL statement that you submitted so that only non-empty geometries will be passed to the ST_AsBinary function. For example, you can use the ST_IsEmpty function in the WHERE clause to exclude empty geometries.

msgcode: -3431

sqlstate: 38SSV

GSE3432N

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

Specify a valid point to be appended.

msgcode: -3432

sqlstate: 38SSW

GSE3433N

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

Specify a point that does exist in the curve.

msgcode: -3433

sqlstate: 38SSX

GSE3500N

The function implementing the geocoder could not find the database manager instance path.

Verify the correct installation of the database product and the spatial feature. Check that the DB2INSTANCE environment variable is set for the user running the process executing the function.

If the problem persists, contact IBM Software Support.

msgcode: -3500

sqlstate: 38SG0

GSE3501N

The geocoder is optimized to geocode addresses and produce the resulting points all in same spatial reference system in a single SQL statement. But it encountered different spatial reference systems in the same SQL statement. The new spatial reference system is identified by new-srs-id; the spatial reference system used for the preceeding rows was identified by previous-srs-id.

Specify the default parameters and overwriting parameters for the column that the geocoder runs on. This should be done in such a way that the numerical spatial reference system identifier remains constant within an SQL statement that is used to geocode multiple addresses at once.

msgcode: -3501

sqlstate: 38SG1

GSE3502N

The path name specified for the locator file parameter or the base map parameter exceeds 256 bytes and is too long.

Use a shorter path name for the locator file parameter or the base map parameter. On Unix systems, symbolic links can be used to shorten the path name.

msgcode: -3502

sqlstate: 38SG2

GSE3503N

In the locator file, line line-number contains an invalid entry. Each entry in the file must be of the form "property name = property value".

Correct the locator file.

msgcode: -3503

sqlstate: 38SG3

GSE3504N

In the locator file, line line-number contains an entry where the quote characters are not balanced. If quoted, the property name as well as the property value must have an opening and a closing quote character.

Correct the locator file.

msgcode: -3504

sqlstate: 38SG4

GSE3505N

A failure occurred while handling properties defined in the locator file (.loc).

Correct the problem identified by the reason code; then retry the operation.

msgcode: -3505

sqlstate: 38SG5

GSE3506N

The copying of the properties into an internal buffer failed. Not enough memory is available.

Ensure that enough memory is available for the geocoder to copy the properties from the locator file to the internal buffer.

msgcode: -3506

sqlstate: 38SG6

GSE3507N

The locator file contains too many properties. At most 2048 properties can be specified in the locator file.

Reduce the number of properties specified in the locator file.

msgcode: -3507

sqlstate: 38SG7

GSE3508N

The geocoder produced a geometry that is not an ST_Point geometry.

Contact IBM Software Support.

msgcode: -3508

sqlstate: 38SG8

GSE3509N

The initialization of the geocoder failed.

Verify the installation of the spatial feature.

msgcode: -3509

sqlstate: 38SG9

GSE3510N

The geocoder could not normalize the address.

Contact IBM Software Support.

msgcode: -3510

sqlstate: 38SGA

GSE3511N

An internal error with reason code reason-code occurred during a file operation.

Correct the problem identified by the reason code; then retry the operation.

msgcode: -3511

sqlstate: 38SGB

GSE3512N

The geocoder failed with an internal error of reason code reason-code.

Note the internal error and contact IBM Software Support.

msgcode: -3512

sqlstate: 38SGC

GSE3600N

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

Specify a valid spatial index to retrieve the parameter information.

msgcode: -3600

sqlstate: 38SQ0

GSE3601N

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.

Specify an existing spatial index to retrieve the parameter information.

msgcode: -3601

sqlstate: 38SQ1

GSE3602N

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

Specify a valid parameter number for the spatial index. Consult the database system catalog for the type of the spatial index.

msgcode: -3602

sqlstate: 38SQ2

GSE3603N

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.

Specify an existing column which has a spatial index defined on it.

msgcode: -3603

sqlstate: 38SQ3

GSE3701N

An invalid distance was passed to the function or method that you invoked.

Specify a valid distance and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3701

sqlstate: 38SO9

GSE3702N

The geodetic workspace was not large enough to perform the operation.

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -3702

sqlstate: 38SOT

GSE3703N

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.

Resolve the memory shortage and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3703

sqlstate: 38SOU

GSE3704C

The spatial operation encountered an unexpected internal error in a geometry value.

Repeat the command. If the problem persists, contact IBM Software Support.

For more information, refer to the Spatial documentation.

msgcode: -3704

sqlstate: 38SOV

GSE3706C

The spatial operation encountered an unexpected internal error.

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -3706

sqlstate: 38SOX

GSE3708C

The spatial operation encountered an unexpected internal error in a geometry value.

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -3708

sqlstate: 38SOR

GSE3709C

The spatial operation encountered an unexpected internal error in a geometry value.

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -3709

sqlstate: 38SOY

GSE3712N

A latitude value must be in a valid range.

For latitude values that are measured in degrees, the valid range is between -90 and 90 degrees (inclusive).

For latitude values that are measured in grads, the valid range is between -100 and 100 grads (inclusive).

For latitude values that are measured in radians, the valid range is between -PI/2 and PI/2 radians (inclusive) where PI is approximately 3.14159265358979323846.

Specify a valid latitude value and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3712

sqlstate: 38SO7

GSE3713N

A longitude value must be in a valid range.

For longitude values that are measured in degrees, the valid range is between -180 and 180 degrees (inclusive).

For longitude values that are measured in grads, the valid range is between -200 and 200 grads (inclusive).

For longitude values that are measured in radians, the valid range is between -PI and PI radians (inclusive) where PI is approximately 3.14159265358979323846.

Specify a valid longitude value and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3713

sqlstate: 38SO8

GSE3714N

A non-empty ST_Polygon requires at least one ring.

Specify at least one ring and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3714

sqlstate: 38SOD

GSE3716N

A non-empty ST_LineString has too few points. An ST_LineString value must have at least 2 points and an ST_LineString value specified as a ring in an ST_Polygon must have at least 4 points.

Specify the correct number of points in the geometry value and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3716

sqlstate: 38SOL

GSE3721N

ST_GeomCollection values are not supported in the DB2 Geodetic Data Management Feature.

Use ST_MultiPoint, ST_MultiLineString or ST_MultiPolygon type instead of ST_GeomCollection and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3721

sqlstate: 38SP6

GSE3722N

The Well-known Binary value is of an unknown or unsupported type.

Use a known Well-known Binary type (ST_Point, ST_LineString, ST_Polygon, ST_MultiPoint, ST_MultiLineString, or ST_MultiPolygon) and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3722

sqlstate: 38SP7

GSE3724N

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

Repeat the command. If the problem persists, contact IBM Software Support.

msgcode: -3724

sqlstate: 38SON

GSE3726N

The geometry value contains an unsupported version.

Use a supported version and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3726

sqlstate: 38SOZ

GSE3733W

Polygon covers more than half the earth.

Verify counter-clockwise orientation of the vertex points.

For more information, refer to the Spatial documentation.

msgcode: +3733

sqlstate: 01HS5

GSE3734N

Invalid ring geometry; coincident consecutive points were found.

Remove coincident consecutive points and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3734

sqlstate: 38SQ4

GSE3735N

Invalid ring geometry; the sequence of coordinates crosses or touches itself.

Specify a ring that does not cross or touch.

For more information, refer to the Spatial documentation.

msgcode: -3735

sqlstate: 38SQ5

GSE3736N

Constituent polygon rings do not define a valid region.

Check the rotational sense of each ring.

For more information, refer to the Spatial documentation.

msgcode: -3736

sqlstate: 38SQ6

GSE3737N

Invalid polygon; the region has no boundary.

Specify a polygon with a boundary.

For more information, refer to the Spatial documentation.

msgcode: -3737

sqlstate: 38SQ7

GSE3739N

Invalid ring geometry; collinear segments were found.

Remove collinear segments.

For more information, refer to the Spatial documentation.

msgcode: -3739

sqlstate: 38SQ9

GSE3740N

The DB2 Geodetic Data Management Feature does not support the operation as indicated by the following reason code:

"1" The Geodetic License is not enabled.

"2" The function was invoked with an ST_Geometry value where the SRID null.

"3" The function was invoked with ST_Geometry values where the SRID values are not equal.

"4" The function was invoked with a spatial reference system that has a null definition.

"5" The function is not supported in Geodetic.

"6" The type of one or more ST_Geometry values is not supported in Geodetic.

"7" The function does not support being executed with Geodetic and non-Geodetic values.

"8" The Geodetic Voronoi Index does not support non-Geodetic values.

"9" The Spatial Grid Index does not support Geodetic values.

The action corresponding to the reason code is:

"1" Enable the Geodetic license.

"2" Ensure all ST_Geometry values have a valid SRID attribute value.

"3" For Geodetic operations, ensure all ST_Geometry values have the same SRID value.

"4" If the problem persists, contact IBM Software Support.

"5" Do not invoke this function or method with ST_Geometry values with an SRID in the geodetic range.

"6" Do not use this ST_Geometry type with an SRID in the geodetic range.

"7" Execute the function with all ST_Geometry values with an SRID in the geodetic range or not in the geodetic range.

"8" Use the Spatial Grid Index specification on columns with non-Geodetic values.

"9" Use the Geodetic Voronoi Index specification on columns with Geodetic values.

After correcting the problem, repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3740

sqlstate: 38SOP

GSE3743N

The specified Voronoi tessellation id is not defined.

Use a defined Voronoi tessellation id and repeat the command

For more information, refer to the Spatial documentation.

msgcode: -3743

sqlstate: 38SOC

GSE3744N

The geometry value cannot exceed its maximum value.

Specify fewer points in the geometry value and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3744

sqlstate: 38SOK

GSE3745N

The spatial reference system definition for this ST_Geometry value is not a geographic coordinate system or does not contain a DATUM definition that includes a SPHEROID definition.

Correct the spatial reference system definition and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3745

sqlstate: 38SOF

GSE3746N

The ellipsoid id is not defined in the DB2 Geodetic Data Management Feature.

Use a defined ellipsoid and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3746

sqlstate: 38SOG

GSE3748N

The start and end points of a ring in a polygon must be exactly equal.

Correct the ring definition by ensuring the start and end points are exactly equal and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3748

sqlstate: 38SOI

GSE3749N

This is a line segment where the two points are directly opposite each other as seen from the ellipsoid center. For example, the line definition (0 0, 180 0) may either pass through the north pole or the south pole.

Correct the linestring or ring definition to ensure there are no antipodal line segments by moving one of the two points in this line segment and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3749

sqlstate: 38SP0

GSE3750N

The spatial reference system definition for this ST_Geometry value is not a geographic coordinate system or does not contain a UNIT definition.

Correct the spatial reference system definition and repeat the command.

For more information, refer to the Spatial documentation.

msgcode: -3750

sqlstate: 38SP5