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 |
|---|---|---|---|---|---|
| 2FW45 | Error | 3122 | -1452L | "Table '%1' contains a spatial column '%2' and no primary key" | An update or delete statement cannot be performed for a table that contains a spatial column unless there is a primary key defined for the table. Click here for a list of possible parameters and odbc states. |
| 2FW46 | Error | 3123 | -1453L | "Spatial column '%1' cannot be included in a primary key or unique index" | A spatial column cannot be included in a primary key or unique index. Click here for a list of possible parameters and odbc states. |
| 2FW47 | Error | 3124 | -1454L | "Spatial column '%1' cannot be included in an index because it is not constrained to a single SRID" | The named spatial column cannot be included in a spatial index because the column is not constrained to have values from a single spatial reference system. The column definition should be of the form "col ST_Geometry(SRID=0)". Click here for a list of possible parameters and odbc states. |
| 2FW48 | Error | 3125 | -1455L | "The CONVERT USING clause must be specified when creating a unit of measure" | A CREATE SPATIAL UNIT OF MEASURE statement was used without including the CONVERT USING clause. Click here for a list of possible parameters and odbc states. |
| 2FW49 | Error | 3126 | -1456L | "The string '%1' is not a valid axis order" | The specified string is not a valid axis order. Click here for a list of possible parameters and odbc states. |
| 2FW50 | Error | 3127 | -1457L | "The string '%1' is not a valid coordinate name" | The provided string is not the name of a coordinate. Coordinate names are X, Y, Z, M, Latitude and Longitude. Click here for a list of possible parameters and odbc states. |
| 2FW51 | Error | 3128 | -1458L | "Unit of measure '%1' not found" | The named unit of measure is not defined. Click here for a list of possible parameters and odbc states. |
| 2FW52 | Error | 3129 | -1459L | "Spatial reference system '%1' not found" | The named spatial reference system is not defined. Click here for a list of possible parameters and odbc states. |
| 2FW53 | Error | 3130 | -1460L | "Unit of measure '%1' already exists" | The named unit of measure is already defined. Click here for a list of possible parameters and odbc states. |
| 2FW54 | Error | 3131 | -1461L | "Spatial reference system '%1' already exists" | The named spatial reference system already exists. Click here for a list of possible parameters and odbc states. |
| 2FW55 | Error | 3132 | -1462L | "Spatial reference system must specify the SRID to use" | When creating a spatial reference system, the statement must specify IDENTIFIED BY to specify the SRID to use. Click here for a list of possible parameters and odbc states. |
| 2FW56 | Error | 3133 | -1463L | "Error parsing definition string '%1'" | The provided definition string is not a valid well known text of the coordinate system. Click here for a list of possible parameters and odbc states. |
| 2FW57 | Error | 3134 | -1464L | "The spatial reference system type is not supported ('%1')" | The specified spatial reference system type is not supported. Click here for a list of possible parameters and odbc states. |
| 2FW58 | Error | 3135 | -1465L | "Ellipsoid parameters missing for geographic spatial reference system" | When creating a geographic spatial reference system, the ellipsoid parameters must be specified, either in the DEFINITION clause or explicitly. These parameters are used to calculate the distance between points. Click here for a list of possible parameters and odbc states. |
| 2FW59 | Error | 3136 | -1466L | "Ellipsoid parameters specified for non-geographic spatial reference system" | The ELLIPSOID parameters can only be specified for geographic spatial reference systems. Click here for a list of possible parameters and odbc states. |
| 2FW60 | Error | 3137 | -1467L | "Coordinate bounds missing for coordinate %1" | No bounds were specified for the named coordinate. Click here for a list of possible parameters and odbc states. |
| 2FW61 | Error | 3138 | -1468L | "The specified axis order is not supported for this type of spatial reference system" | The specified axis order is not supported for this type of spatial reference system. Click here for a list of possible parameters and odbc states. |
| 2FW62 | Error | 3139 | -1469L | "The specified polygon format '%1' is not supported for this type of spatial reference system" | The specified polygon format is not supported for this type of spatial reference system. Click here for a list of possible parameters and odbc states. |
| 2FW63 | Error | 3140 | -1470L | "Invalid storage format '%1'" | The specified storage format string is not valid. Click here for a list of possible parameters and odbc states. |
| 2FW64 | Error | 3141 | -1471L | "Spatial reference system %1 cannot be modified because it is in use" | The coordinate system is currently in use and cannot be dropped. Click here for a list of possible parameters and odbc states. |