Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1490 | "Polygon ring order has been reoriented" |
|---|---|
Constant | SLWARN_POLYGON_RING_REORIENTED |
SAP Sybase Error Number | 3160 |
SQL State | 01FW1 |
SQL Code | -1490L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The rings of a polygon were automatically reoriented on input. This is a notification only. |
| Error 1491 | "CircularString with 3 points has been converted to use 5 points" |
|---|---|
Constant | SLWARN_CIRCULARSTRING_3POINT |
SAP Sybase Error Number | 3161 |
SQL State | 01FW2 |
SQL Code | -1491L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A curve containing a CircularString with a 3-point circle has been converted to use a 5-point circle. This is a notification only. |
| Error 1492 | "Could not create a text index without external prefilter library on column \"%1\No message |
|---|---|
Constant | TEXT_INDEX_NO_PREFILTER |
SAP Sybase Error Number | 2652 |
SQL State | WT030 |
SQL Code | -1492L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the column for which external prefilter library is required. |
Probable Cause | A text configuration object with a specified external prefilter library is required to build a text index on a binary column. |
| Error 1493 | "Could not create a text index with external prefilter library on column \"%1\No message |
|---|---|
Constant | TEXT_INDEX_PREFILTER_NOT_ALLOWED |
SAP Sybase Error Number | 2644 |
SQL State | WT031 |
SQL Code | -1493L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the column for which external prefilter library is not allowed. |
Probable Cause | A text configuration object without external prefilter library is required if any column in the text index is not of a binary or string data type. |
| Error 1494 | "Geometries with CircularString not supported (near \"%1\")" |
|---|---|
Constant | SLERR_CIRCULAR_METHOD |
SAP Sybase Error Number | 3162 |
SQL State | 2FW84 |
SQL Code | -1494L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The method or context where the CircularString was detected. |
Probable Cause | The method or operation does not support geometries with CircularString elements. |
| Error 1495 | "Geometries with CircularString are not supported in spatial reference system %1" |
|---|---|
Constant | SLERR_CIRCULAR_SRS |
SAP Sybase Error Number | 3163 |
SQL State | 2FW85 |
SQL Code | -1495L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The SRID of the round-Earth spatial reference system. |
Probable Cause | The method does not support geometries with CircularString elements. |
| Error 1496 | "LOAD TABLE error: Invalid content encountered on row %1 of the data file" |
|---|---|
Constant | LOAD_TABLE_DATA_FILE_ERROR |
SAP Sybase Error Number | 3164 |
SQL State | WL017 |
SQL Code | -1496L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Line number of the data file where the invalid content occurred. |
Probable Cause | The LOAD TABLE statement failed because a scanning error occurred on the indicated line of the data file specified in the statement. This error can occur if a line is truncated or if delimiters are missing. |
| Error 1497 | "The synchronization failed because MobiLink returned authentication status '%1' with value '%2'" |
|---|---|
Constant | MOBILINK_AUTHENTICATION_FAILED |
SAP Sybase Error Number | 3165 |
SQL State | 28W17 |
SQL Code | -1497L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Parameter 1 | The authentication status number. |
Parameter 2 | The authentication value number. |
Probable Cause | MobiLink returned an authentication status to the remote database indicating failure. The status and value numbers indicate why the authentication failed. For example, the password was invalid, or a synchronization is already in progress for this remote. |
| Error 1498 | "'%1' is an unknown property" |
|---|---|
Constant | UNKNOWN_PROPERTY |
SAP Sybase Error Number | 3166 |
SQL State | WU001 |
SQL Code | -1498L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The property name (or ID). |
Probable Cause | The specified property is unknown. |
| Error 1499 | "Invalid grid size %1" |
|---|---|
Constant | SLERR_INVALID_GRID_SIZE |
SAP Sybase Error Number | 3167 |
SQL State | 2FW86 |
SQL Code | -1499L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The grid size that is not valid. |
Probable Cause | The specified grid size cannot be used with the spatial reference system. The grid size must be selected based on the bounds of space. |
| Error 1500 | "Invalid tolerance %1" |
|---|---|
Constant | SLERR_INVALID_TOLERANCE |
SAP Sybase Error Number | 3168 |
SQL State | 2FW87 |
SQL Code | -1500L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The invalid tolerance. |
Probable Cause | The specified tolerance cannot be used with the spatial reference system. The tolerance must be selected based on the bounds of space. |
| Error 1501 | "Invalid bounds for coordinate %1 (near \"BETWEEN %2 AND %3\")" |
|---|---|
Constant | SLERR_INVALID_BOUNDS |
SAP Sybase Error Number | 3169 |
SQL State | 2FW88 |
SQL Code | -1501L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The coordinate with the invalid bounds. |
Parameter 2 | The first value of the invalid bounds. |
Parameter 3 | The second value of the invalid bounds. |
Probable Cause | The specified coordinate bounds are not valid. |
| Error 1502 | "ST_MultiSurface contains elements with an invalid intersection (near \"%1\")" |
|---|---|
Constant | SLERR_INVALID_MULTISURF_I |
SAP Sybase Error Number | 3170 |
SQL State | 2FW89 |
SQL Code | -1502L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The method or context where the invalid ST_MultiSurface was detected. |
Probable Cause | The interiors of any two ST_Surface values in an ST_MultiSurface shall not intersect. The boundaries of any two elements in an ST_MultiSurface may intersect at a finite number of points (and not, for example, in a line segment). |
| Error 1503 | "Operation not supported for ST_GeomCollection with intersecting elements (near \"%1\")" |
|---|---|
Constant | SLERR_GEOM_COLL_INTERSECT |
SAP Sybase Error Number | 3171 |
SQL State | 2FW90 |
SQL Code | -1503L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The method or context where the invalid ST_GeomCollection was detected. |
Probable Cause | The ST_GeomCollection contains elements that intersect in a way that is not valid for an ST_MultiSurface. The operation is not supported for this kind of geometry. |
| Error 1504 | "Error from external library: -%1: %2" |
|---|---|
Constant | TEXT_USER_SPECIFIED_ERROR |
SAP Sybase Error Number | 2642 |
SQL State | WT032 |
SQL Code | -1504L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Error number specified by the external library |
Parameter 2 | Error message specified by the external library |
Probable Cause | The external library used by the text index has reported the specified error. |
| Error 1505 | "Mirror server \"%1\" defined with type COPY does not include a parent definition" |
|---|---|
Constant | COPY_SERVER_NEEDS_PARENT |
SAP Sybase Error Number | 3172 |
SQL State | 42WE6 |
SQL Code | -1505L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The mirror server name |
Probable Cause | In a CREATE MIRROR SERVER statement for a server with type COPY, a parent server is not defined. |
| Error 1506 | "Unknown collation '%1'" |
|---|---|
Constant | UNKNOWN_COLLATION |
SAP Sybase Error Number | 3174 |
SQL State | WC018 |
SQL Code | -1506L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name that is not a database collation. |
Probable Cause | The specified collation is unknown. Ensure the name is spelled correctly. |
| Error 1507 | "The materialized view cannot be changed to immediate because the ON conditions refer to tables which are not in the null-supplying and preserved sides of the OUTER JOINs." |
|---|---|
Constant | UPDATABLE_MATVIEW_OUTERREFERENCE_ON_CONDITION |
SAP Sybase Error Number | 3175 |
SQL State | 42WE7 |
SQL Code | -1507L |
ODBC 2 State | 42000 |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to change the refresh type to immediate for a materialized view whose definition contains an illegal ON condition. |
| Error 1508 | "The materialized view cannot be changed to immediate because at least one non-nullable column from any null-supplying side of an OUTER JOIN must exist in the SELECT list." |
|---|---|
Constant | UPDATABLE_MATVIEW_ISNOTNULL |
SAP Sybase Error Number | 3176 |
SQL State | 42WE8 |
SQL Code | -1508L |
ODBC 2 State | 42000 |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to change the refresh type to immediate for a materialized view whose SELECT list doesn't contain at least one non-nullable column for any null-supplying side of an OUTER JOIN. |
| Error 1509 | "The materialized view cannot be changed to immediate because the primary key columns of any table in the preserved side of an OUTER JOIN must exist in the SELECT list." |
|---|---|
Constant | UPDATABLE_MATVIEW_PK |
SAP Sybase Error Number | 3177 |
SQL State | 42WE9 |
SQL Code | -1509L |
ODBC 2 State | 42000 |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to change the refresh type to immediate for a materialized view whose SELECT list doesn't contain the primary key columns of any table in the preserved side of an OUTER JOIN. |