Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2FF71 | Error | 3080 | -1410L | "An ST_CircularString cannot be constructed from %1 points (near '%2')" | A circularstring geometry should consist of three points followed optionally by an arbitrary number of pairs of points. Click here for a list of possible parameters and odbc states. |
| 2FF72 | Error | 3180 | -1516L | "The intermediate point (%3) of the ST_CircularString segment between %1 and %2 is collinear with but not between the start and end points." | When the intermediate point of a ST_CircularString segment is collinear with the start and end point the result is interpreted as a straight line between the start and the end point. In this case, the intermediate point must be located on the line segment between the start and end point. Click here for a list of possible parameters and odbc states. |
| 2FW02 | Error | 3082 | -1412L | "Support for spatial is not available for this database" | Operations involving spatial support cannot be used with this database because it needs to be upgraded to use spatial features. Click here for a list of possible parameters and odbc states. |
| 2FW03 | Error | 3083 | -1413L | "Spatial feature %1 is not supported" | The specified feature is not supported. Click here for a list of possible parameters and odbc states. |
| 2FW05 | Error | 3084 | -1414L | "Error parsing well-known-text (WKT): inconsistent dimensions at offset %1" | There was a mixture of coordinate dimensions detected at the specified offset. For example, one geometry in a collection might have a Z value while another doesn't. Click here for a list of possible parameters and odbc states. |
| 2FW06 | Error | 3085 | -1415L | "Error parsing geometry internal serialization at offset %1" | There was an error parsing the internal serialization string. Click here for a list of possible parameters and odbc states. |
| 2FW08 | Error | 3087 | -1417L | "Error parsing well-known-binary (WKB): type code %1 at offset %2 is invalid" | The well-known binary string contains a type code that is not supported. Click here for a list of possible parameters and odbc states. |
| 2FW09 | Error | 3088 | -1418L | "Error parsing well-known-binary (WKB): type code %1 at offset %2 is not a valid subtype of the parent" | The well-known binary string contains a child geometry within a parent geometry and the child is not one of the types allowed by the parent. Click here for a list of possible parameters and odbc states. |
| 2FW10 | Error | 3089 | -1419L | "Error parsing well-known-binary (WKB): unexpected end of input" | A well-known binary string was shorter than expected. Click here for a list of possible parameters and odbc states. |
| 2FW11 | Error | 3090 | -1420L | "Error parsing well-known-binary (WKB): inconsistent dimensions at offset %1" | The well-known binary string contains geometries with different numbers of coordinate dimensions. For example, it could contain a point with a Z value and another without a Z value. Click here for a list of possible parameters and odbc states. |
| 2FW12 | Error | 3091 | -1421L | "Error parsing well-known-binary (WKB): invalid byte order mark %1 at offset %2" | The well-known binary string has an invalid byte order mark. This could happen if a binary string that is not in the well-known binary format is used. Click here for a list of possible parameters and odbc states. |
| 2FW13 | Error | 3092 | -1422L | "Error parsing shapefile record" | The shapefile contains an invalid record. Click here for a list of possible parameters and odbc states. |
| 2FW14 | Error | 3093 | -1423L | "Error parsing shapefile attributes" | The shapefile contains invalid attributes. Click here for a list of possible parameters and odbc states. |
| 2FW15 | Error | 3094 | -1424L | "Invalid shapefile filename" | The specified shapefile filename is not valid. Click here for a list of possible parameters and odbc states. |
| 2FW16 | Error | 3095 | -1425L | "The multi patch shapefile shape is not supported" | The shapefile contains a multi patch object; this type is not supported. Click here for a list of possible parameters and odbc states. |
| 2FW19 | Error | 3096 | -1426L | "The embedded SRID (%1) conflicts with the provided SRID (%2)." | A call to a spatial method had a string with an embedded SRID that differed from the SRID parameter to the method. Click here for a list of possible parameters and odbc states. |
| 2FW20 | Error | 3097 | -1427L | "The embedded SRID are inconsistent (%1 and %2)." | A geometry in a string representation contains objects from different spatial reference systems. Click here for a list of possible parameters and odbc states. |
| 2FW21 | Error | 3098 | -1428L | "The format type '%1' is not recognized." | The specified format type is not recognized. Click here for a list of possible parameters and odbc states. |
| 2FW22 | Error | 3099 | -1429L | "The format type '%1' cannot be used here." | The specified format type cannot be used in this context. Click here for a list of possible parameters and odbc states. |
| 2FW23 | Error | 3100 | -1430L | "An input string in '%1' format cannot be used here." | A string with the specified format cannot be used in this context. Click here for a list of possible parameters and odbc states. |