Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1387 | "Failed to shut down the dbmlsync server. Check the dbmlsync log file for more details." |
|---|---|
Constant | MLA_SYNC_SHUTDOWN_FAIL |
SAP Sybase Error Number | 3065 |
SQL State | WW163 |
SQL Code | -1387L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The MobiLink agent adapter encountered an error while attempting to shut down the server. Check the dbmlsync log file for more details. |
| Error 1388 | "Failed to start the dbmlsync server. Check the dbmlsync log file for more details." |
|---|---|
Constant | MLA_SYNC_START_SERVER_FAIL |
SAP Sybase Error Number | 3066 |
SQL State | WW164 |
SQL Code | -1388L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The MobiLink agent adapter failed to start a new dbmlsync process or the server did not begin processing requests before the timeout expired. Check the dbmlsync log file for more details. |
| Error 1389 | "The value for the stoplist cannot be NULL." |
|---|---|
Constant | TEXT_STOPLIST_NULL |
SAP Sybase Error Number | 2727 |
SQL State | WT023 |
SQL Code | -1389L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The value for a text configuration stoplist cannot be NULL. To remove a stoplist, use the ALTER TEXT CONFIGURATION...DROP STOPLIST statement. |
| Error 1390 | "An incremental refresh is not possible when handles are exhausted." |
|---|---|
Constant | TEXT_HANDLES_EXHAUSTED |
SAP Sybase Error Number | 2724 |
SQL State | WT024 |
SQL Code | -1390L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Incremental refresh of a MANUAL or AUTO REFRESH text index is not possible when handles are exhausted. You need to rebuild the text index before you can use incremental refresh. |
| Error 1391 | "Invalid stoplist value." |
|---|---|
Constant | TEXT_INVALID_STOPLIST_VALUE |
SAP Sybase Error Number | 2725 |
SQL State | WT025 |
SQL Code | -1391L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The value specified for the stoplist is not valid. |
| Error 1392 | "Unique indexes with the clause WITH NULLS NOT DISTINCT are not supported for this database" |
|---|---|
Constant | UNIQUE_INDEX_NULLS_NOT_DISTINCT_NOT_SUPPORTED |
SAP Sybase Error Number | 3067 |
SQL State | 52W53 |
SQL Code | -1392L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database does not have support for unique indexes with the clause WITH NULLS NOT DISTINCT. To use this feature, upgrade your database to the most recent version. |
| Error 1393 | "Error initializing external term breaker" |
|---|---|
Constant | ERROR_INITIALIZING_EXT_TERMBREAKER |
SAP Sybase Error Number | 2717 |
SQL State | WT028 |
SQL Code | -1393L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The external term breaker could not be initialized because of an internal error. |
| Error 1394 | "Invalid external prefilter name specified" |
|---|---|
Constant | INVALID_EXT_PREFILTER_NAME |
SAP Sybase Error Number | 2682 |
SQL State | WT029 |
SQL Code | -1394L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | External prefilter name specified in the text configuration is invalid. |
| Error 1395 | "Invalid external term breaker name specified" |
|---|---|
Constant | INVALID_EXT_TERMBREAKER_NAME |
SAP Sybase Error Number | 2683 |
SQL State | WT026 |
SQL Code | -1395L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | External term breaker name specified in the text configuration is invalid. |
| Error 1396 | "Error initializing external prefilter" |
|---|---|
Constant | ERROR_INITIALIZING_EXT_PREFILTER |
SAP Sybase Error Number | 2718 |
SQL State | WT027 |
SQL Code | -1396L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The external prefilter could not be initialized because of an internal error. |
| Error 1397 | "The definition of temporary table '%1' has changed since last used" |
|---|---|
Constant | TEMP_TABLE_DEFINITION_CHANGED |
SAP Sybase Error Number | 3068 |
SQL State | WW165 |
SQL Code | -1397L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The table name |
Probable Cause | The definition of a temporary table has changed since it was last used in a stored procedure or trigger. The procedure must be recompiled. |
| Error 1398 | "VERIFY and RENAME cannot be used together" |
|---|---|
Constant | RENAME_WITH_VERIFY_NOT_ALLOWED |
SAP Sybase Error Number | 2681 |
SQL State | 42WE5 |
SQL Code | -1398L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Since VERIFY will never write to any dbspaces, renaming dbspaces cannot be done during restore verification. |
| Error 1399 | "Invalid intersection matrix '%1'" |
|---|---|
Constant | SLERR_INVALID_RELATE_MATRIX |
SAP Sybase Error Number | 3069 |
SQL State | 2FF04 |
SQL Code | -1399L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The intersection matrix string. |
Probable Cause | The provided value is not a valid intersection matrix string. A valid string contains nine characters, each is one of T, F, *, 0, 1, or 2. |
| Error 1400 | "Point is duplicated %1" |
|---|---|
Constant | SLERR_DUPLICATE_POINT |
SAP Sybase Error Number | 3070 |
SQL State | 2FF05 |
SQL Code | -1400L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The duplicated point |
Probable Cause | A linestring or circularstring geometry contains two adjacent points that are identical. This represents an invalid geometry. |
| Error 1401 | "Element is an empty set (near '%1')" |
|---|---|
Constant | SLERR_ELEMENT_IS_EMPTY |
SAP Sybase Error Number | 3071 |
SQL State | 2FF06 |
SQL Code | -1401L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The value or method where the empty geometry has been detected. |
Probable Cause | An element of a geometry is the empty set. Empty geometries cannot be used as the points in linestrings or circularstrings; empty curves cannot be used as elements of compoundcurves; empty curves cannot be used as rings of polygons. |
| Error 1402 | "Mixed spatial reference systems %1 and %2 (near %3)" |
|---|---|
Constant | SLERR_MIXED_SRS |
SAP Sybase Error Number | 3072 |
SQL State | 2FF10 |
SQL Code | -1402L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The SRID of the first spatial reference system. |
Parameter 2 | The SRID of the second spatial reference system. |
Parameter 3 | The value or method where the mixed spatial reference systems were detected. |
Probable Cause | The method does not support working with geometries from different spatial reference systems. |
| Error 1403 | "Non-contiguous curves near '%1'" |
|---|---|
Constant | SLERR_COMPOUNDCURVE_NOT_CONTIGUOUS |
SAP Sybase Error Number | 3073 |
SQL State | 2FF11 |
SQL Code | -1403L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The value or method where the non-contiguous curves were detected. |
Probable Cause | A compoundcurve geometry is composed of curves, and adjacent curves must be joined at their endpoints. |
| Error 1404 | "Unknown unit of measure '%1'" |
|---|---|
Constant | SLERR_UNKNOWN_UOM |
SAP Sybase Error Number | 3074 |
SQL State | 2FF14 |
SQL Code | -1404L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the unit of measure. |
Probable Cause | The name does not match a defined unit of measure. |
| Error 1405 | "Failed to transform geometry (error %1)" |
|---|---|
Constant | SLERR_TRANSFORM_FAIL |
SAP Sybase Error Number | 3075 |
SQL State | 2FF15 |
SQL Code | -1405L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The error code from the projection library. |
Probable Cause | An error occurred when performing a transform from one spatial reference system to another. This error may occur if a point in the first geometry is outside of the bounds for the transform definition. The error may also be reported for particular transform definitions. The integer error code from the transform library may be used to diagnose the transform definition. |
| Error 1406 | "Error parsing well-known-text (WKT) scanning '%1' at offset %2" |
|---|---|
Constant | SLERR_WKT_PARSE_NEAR |
SAP Sybase Error Number | 3076 |
SQL State | 2FF22 |
SQL Code | -1406L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The text where the problem was detected. |
Parameter 2 | The offset within the input string where the problem was detected. |
Probable Cause | An error was detected while parsing the well-known text of a geometry. |