Messages 1487 through 1506

Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL Code Msg Type Number SQL State Message Possible Cause
-1487L Error 3157 2FW82 "Invalid polygon: curve is not a ring" One of the curves is not a ring and cannot be used to form a polygon.

Click here for a list of possible parameters and odbc states.

-1488L Error 3158 2FW83 "Invalid polygon: ring is larger than allowed for SRID=%1 (near '%2')" One of the rings is larger than the specified spatial reference system supports.

Click here for a list of possible parameters and odbc states.

-1489L Error 3159 01F01 "Position %1 is invalid (should be between %2 and %3)" The provided position is not valid. It should be between the specified minimum and maximum.

Click here for a list of possible parameters and odbc states.

-1490L Error 3160 01FW1 "Polygon ring order has been reoriented" The rings of a polygon were automatically reoriented on input. This is a notification only.

Click here for a list of possible parameters and odbc states.

-1491L Error 3161 01FW2 "CircularString with 3 points has been converted to use 5 points" A curve containing a CircularString with a 3-point circle has been converted to use a 5-point circle. This is a notification only.

Click here for a list of possible parameters and odbc states.

-1492L Error 2652 WT030 "Could not create a text index without external prefilter library on column \"%1\No message A text configuration object with a specified external prefilter library is required to build a text index on a binary column.

Click here for a list of possible parameters and odbc states.

-1493L Error 2644 WT031 "Could not create a text index with external prefilter library on column \"%1\No message 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.

Click here for a list of possible parameters and odbc states.

-1494L Error 3162 2FW84 "Geometries with CircularString not supported (near \"%1\")" The method or operation does not support geometries with CircularString elements.

Click here for a list of possible parameters and odbc states.

-1495L Error 3163 2FW85 "Geometries with CircularString are not supported in spatial reference system %1" The method does not support geometries with CircularString elements.

Click here for a list of possible parameters and odbc states.

-1496L Error 3164 WL017 "LOAD TABLE error: Invalid content encountered on row %1 of the data file" 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.

Click here for a list of possible parameters and odbc states.

-1497L Error 3165 28W17 "The synchronization failed because MobiLink returned authentication status '%1' with value '%2'" 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.

Click here for a list of possible parameters and odbc states.

-1498L Error 3166 WU001 "'%1' is an unknown property" The specified property is unknown.

Click here for a list of possible parameters and odbc states.

-1499L Error 3167 2FW86 "Invalid grid size %1" The specified grid size cannot be used with the spatial reference system. The grid size must be selected based on the bounds of space.

Click here for a list of possible parameters and odbc states.

-1500L Error 3168 2FW87 "Invalid tolerance %1" The specified tolerance cannot be used with the spatial reference system. The tolerance must be selected based on the bounds of space.

Click here for a list of possible parameters and odbc states.

-1501L Error 3169 2FW88 "Invalid bounds for coordinate %1 (near \"BETWEEN %2 AND %3\")" The specified coordinate bounds are not valid.

Click here for a list of possible parameters and odbc states.

-1502L Error 3170 2FW89 "ST_MultiSurface contains elements with an invalid intersection (near \"%1\")" 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).

Click here for a list of possible parameters and odbc states.

-1503L Error 3171 2FW90 "Operation not supported for ST_GeomCollection with intersecting elements (near \"%1\")" 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.

Click here for a list of possible parameters and odbc states.

-1504L Error 2642 WT032 "Error from external library: -%1: %2" The external library used by the text index has reported the specified error.

Click here for a list of possible parameters and odbc states.

-1505L Error 3172 42WE6 "Mirror server \"%1\" defined with type COPY does not include a parent definition" In a CREATE MIRROR SERVER statement for a server with type COPY, a parent server is not defined.

Click here for a list of possible parameters and odbc states.

-1506L Error 3174 WC018 "Unknown collation '%1'" The specified collation is unknown. Ensure the name is spelled correctly.

Click here for a list of possible parameters and odbc states.


Created November 10, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com