Messages 1384 through 1403

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
-1384L Error 2728 08WA5 "Unable to stop specified database: %1" The database server was unable to stop the specified database.

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

-1385L Error 3063 WW161 "Synchronization failed. Check the dbmlsync log file for more details." The synchronization was not successful. Check the dbmlsync log file for more details.

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

-1386L Error 3064 WW162 "Failed to connect to the dbmlsync server. Check the dbmlsync log file for more details." The MobiLink agent adapter failed to make a connection to the dbmlsync server. Check the dbmlsync log file for more details.

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

-1387L Error 3065 WW163 "Failed to shut down the dbmlsync server. Check the dbmlsync log file for more details." The MobiLink agent adapter encountered an error while attempting to shut down the server. Check the dbmlsync log file for more details.

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

-1388L Error 3066 WW164 "Failed to start the dbmlsync server. Check the dbmlsync log file for more details." 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.

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

-1389L Error 2727 WT023 "The value for the stoplist cannot be NULL." The value for a text configuration stoplist cannot be NULL. To remove a stoplist, use the ALTER TEXT CONFIGURATION...DROP STOPLIST statement.

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

-1390L Error 2724 WT024 "An incremental refresh is not possible when handles are exhausted." 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.

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

-1391L Error 2725 WT025 "Invalid stoplist value." The value specified for the stoplist is not valid.

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

-1392L Error 3067 52W53 "Unique indexes with the clause WITH NULLS NOT DISTINCT are not supported for this database" 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.

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

-1393L Error 2717 WT028 "Error initializing external term breaker" The external term breaker could not be initialized because of an internal error.

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

-1394L Error 2682 WT029 "Invalid external prefilter name specified" External prefilter name specified in the text configuration is invalid.

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

-1395L Error 2683 WT026 "Invalid external term breaker name specified" External term breaker name specified in the text configuration is invalid.

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

-1396L Error 2718 WT027 "Error initializing external prefilter" The external prefilter could not be initialized because of an internal error.

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

-1397L Error 3068 WW165 "The definition of temporary table '%1' has changed since last used" The definition of a temporary table has changed since it was last used in a stored procedure or trigger. The procedure must be recompiled.

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

-1398L Error 2681 42WE5 "VERIFY and RENAME cannot be used together" Since VERIFY will never write to any dbspaces, renaming dbspaces cannot be done during restore verification.

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

-1399L Error 3069 2FF04 "Invalid intersection matrix '%1'" 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.

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

-1400L Error 3070 2FF05 "Point is duplicated %1" A linestring or circularstring geometry contains two adjacent points that are identical. This represents an invalid geometry.

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

-1401L Error 3071 2FF06 "Element is an empty set (near '%1')" 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.

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

-1402L Error 3072 2FF10 "Mixed spatial reference systems %1 and %2 (near %3)" The method does not support working with geometries from different spatial reference systems.

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

-1403L Error 3073 2FF11 "Non-contiguous curves near '%1'" A compoundcurve geometry is composed of curves, and adjacent curves must be joined at their endpoints.

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