Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1449 | "Invalid polygon: no exterior ring" |
|---|---|
Constant | SLERR_INVALID_POLY_NO_EXT |
SAP Sybase Error Number | 3119 |
SQL State | 2FW42 |
SQL Code | -1449L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The provided polygon is invalid as it does not have an exterior ring. |
| Error 1450 | "Invalid polygon nesting" |
|---|---|
Constant | SLERR_INVALID_POLY_NESTING |
SAP Sybase Error Number | 3120 |
SQL State | 2FW43 |
SQL Code | -1450L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The provided rings cannot be interpreted as a valid polygons. |
| Error 1451 | "Invalid polygon: multiple exterior rings" |
|---|---|
Constant | SLERR_INVALID_POLY_MULT_EXT |
SAP Sybase Error Number | 3121 |
SQL State | 2FW44 |
SQL Code | -1451L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | There are multiple exterior rings that do not form a single valid polygon. |
| Error 1452 | "Table '%1' contains a spatial column '%2' and no primary key" |
|---|---|
Constant | SLERR_UPDDEL_NO_PK |
SAP Sybase Error Number | 3122 |
SQL State | 2FW45 |
SQL Code | -1452L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The table name. |
Parameter 2 | The spatial column name. |
Probable Cause | 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. |
| Error 1453 | "Spatial column '%1' cannot be included in a primary key or unique index" |
|---|---|
Constant | SLERR_CREATE_INDEX_UNIQUE |
SAP Sybase Error Number | 3123 |
SQL State | 2FW46 |
SQL Code | -1453L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the spatial column. |
Probable Cause | A spatial column cannot be included in a primary key or unique index. |
| Error 1454 | "Spatial column '%1' cannot be included in an index because it is not constrained to a single SRID" |
|---|---|
Constant | SLERR_CREATE_INDEX_NOSRID |
SAP Sybase Error Number | 3124 |
SQL State | 2FW47 |
SQL Code | -1454L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the spatial column. |
Probable Cause | 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)". |
| Error 1455 | "The CONVERT USING clause must be specified when creating a unit of measure" |
|---|---|
Constant | SLERR_DDL_UOM_NOFACT |
SAP Sybase Error Number | 3125 |
SQL State | 2FW48 |
SQL Code | -1455L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A CREATE SPATIAL UNIT OF MEASURE statement was used without including the CONVERT USING clause. |
| Error 1456 | "The string '%1' is not a valid axis order" |
|---|---|
Constant | SLERR_DDL_SRS_AXISORDER |
SAP Sybase Error Number | 3126 |
SQL State | 2FW49 |
SQL Code | -1456L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The invalid axis order. |
Probable Cause | The specified string is not a valid axis order. |
| Error 1457 | "The string '%1' is not a valid coordinate name" |
|---|---|
Constant | SLERR_DDL_SRS_COORDNAME |
SAP Sybase Error Number | 3127 |
SQL State | 2FW50 |
SQL Code | -1457L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The invalid coordinate name. |
Probable Cause | The provided string is not the name of a coordinate. Coordinate names are X, Y, Z, M, Latitude and Longitude. |
| Error 1458 | "Unit of measure '%1' not found" |
|---|---|
Constant | SLERR_DDL_NO_UOM |
SAP Sybase Error Number | 3128 |
SQL State | 2FW51 |
SQL Code | -1458L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The unit of measure name. |
Probable Cause | The named unit of measure is not defined. |
| Error 1459 | "Spatial reference system '%1' not found" |
|---|---|
Constant | SLERR_DDL_NO_SRS |
SAP Sybase Error Number | 3129 |
SQL State | 2FW52 |
SQL Code | -1459L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the spatial reference system. |
Probable Cause | The named spatial reference system is not defined. |
| Error 1460 | "Unit of measure '%1' already exists" |
|---|---|
Constant | SLERR_DDL_UOM_EXISTS |
SAP Sybase Error Number | 3130 |
SQL State | 2FW53 |
SQL Code | -1460L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the unit of measure. |
Probable Cause | The named unit of measure is already defined. |
| Error 1461 | "Spatial reference system '%1' already exists" |
|---|---|
Constant | SLERR_DDL_SRS_EXISTS |
SAP Sybase Error Number | 3131 |
SQL State | 2FW54 |
SQL Code | -1461L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the spatial reference system. |
Probable Cause | The named spatial reference system already exists. |
| Error 1462 | "Spatial reference system must specify the SRID to use" |
|---|---|
Constant | SLERR_DDL_SRS_NOSRID |
SAP Sybase Error Number | 3132 |
SQL State | 2FW55 |
SQL Code | -1462L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | When creating a spatial reference system, the statement must specify IDENTIFIED BY to specify the SRID to use. |
| Error 1463 | "Error parsing definition string '%1'" |
|---|---|
Constant | SLERR_DDL_SRS_BADWKT |
SAP Sybase Error Number | 3133 |
SQL State | 2FW56 |
SQL Code | -1463L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Coordinate system name |
Probable Cause | The provided definition string is not a valid well known text of the coordinate system. |
| Error 1464 | "The spatial reference system type is not supported ('%1')" |
|---|---|
Constant | SLERR_DDL_SRS_BAD_SRS_TYPE |
SAP Sybase Error Number | 3134 |
SQL State | 2FW57 |
SQL Code | -1464L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The unsupported spatial reference system type. |
Probable Cause | The specified spatial reference system type is not supported. |
| Error 1465 | "Ellipsoid parameters missing for geographic spatial reference system" |
|---|---|
Constant | SLERR_DDL_SRS_NOELLIPSOID |
SAP Sybase Error Number | 3135 |
SQL State | 2FW58 |
SQL Code | -1465L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | 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. |
| Error 1466 | "Ellipsoid parameters specified for non-geographic spatial reference system" |
|---|---|
Constant | SLERR_DDL_SRS_ELLIPSOID |
SAP Sybase Error Number | 3136 |
SQL State | 2FW59 |
SQL Code | -1466L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The ELLIPSOID parameters can only be specified for geographic spatial reference systems. |
| Error 1467 | "Coordinate bounds missing for coordinate %1" |
|---|---|
Constant | SLERR_DDL_SRS_MUSTBOUND |
SAP Sybase Error Number | 3137 |
SQL State | 2FW60 |
SQL Code | -1467L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The coordinate name. |
Probable Cause | No bounds were specified for the named coordinate. |
| Error 1468 | "The specified axis order is not supported for this type of spatial reference system" |
|---|---|
Constant | SLERR_DDL_SRS_AXISORD |
SAP Sybase Error Number | 3138 |
SQL State | 2FW61 |
SQL Code | -1468L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The specified axis order is not supported for this type of spatial reference system. |