Messages 1149 through 1168

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
-1149L Error 2825 08W99 "Database '%1' cannot be started on this platform. See http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_cant_change_platform.html" It was determined that the database cannot be started on the current platform because doing so could possibly cause an endian related database file corruption. It will continue to start without problems on a platform with the opposite endian. More information and instructions on how to proceed are available at: http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_cant_change_platform.html

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

-1150L Error 2826 WW091 "The SQL scripts DLL cannot be loaded" The SQL scripts DLL cannot be loaded. The DLL might be missing or the version found might not match the version of the database server being used.

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

-1151L Error 2827 WL010 "The logging type ( '%1' ) specified is invalid, not supported or incompatible" The logging type specified for LOAD TABLE is not supported for the version of the database being used, is incompatible with other specifications of the statement or is not supported for the specific table being loaded into.

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

-1152L Error 2828 08WA0 "Password has expired" You attempted to connect using a valid user ID, but with an expired password. You can change your password by supplying the NewPassword connection parameter along with the current expired password.

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

-1153L Error 2829 08WA1 "Password has expired but cannot be changed because the database is read-only" You attempted to connect to a read-only database using a valid user ID, but with an expired password. The password cannot be changed unless the database is started without the -r option on the database server command line. Removing -r will permit modifications to the database.

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

-1154L Error 2830 55W28 "Traced query (%1, %2) does not exist" You attempted to generate a graphical plan for a query saved by diagnostic tracing, identified by a logging_session_id and query id. However, no such query exists in this database. If it was traced, it was sent to a different database.

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

-1155L Error 2831 WL011 "Unable to close the cursor on table \"%1\". LOAD TABLE cannot be executed." You cannot perform LOAD TABLE on a temporary table that has an open cursor on it. An attempt to close the cursor failed. A failed LOAD TABLE would cause all of the rows in the temporary table to be deleted thereby invalidating the cursor.

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

-1156L Error 2832 WT001 "Argument \"%1\" must be a column reference." The CONTAINS argument must be a column reference.

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

-1157L Error 2833 WT002 "All column reference arguments must refer to the same table." All column references in a CONTAINS query must refer to the same table.

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

-1158L Error 2834 WT003 "No matching text index." A single text index must exist on all columns referenced in a CONTAINS query.

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

-1159L Error 2835 WT004 "Non-constant or unknown text query string." The query string argument to a CONTAINS query must be a constant, or a non-null value in a variable.

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

-1160L Error 2836 WT005 "Text configuration \"%1\".\"%2\" not found." The specified text configuration does not exist.

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

-1161L Error 2837 WT006 "Text configuration \"%1\" already exists." The specified text configuration name already exists.

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

-1162L Error 2838 WT007 "Term length outside allowed range." The minimum and maximum term lengths must both be greater than 0 and less than or equal to 60 characters.

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

-1163L Error 2839 WT008 "Invalid collation: \"%1\"." The collation was not found, or the tailoring options were invalid.

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

-1164L Error 2840 WT009 "Text query parser error: %1" The text query could not be parsed.

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

-1165L Error 2841 WT010 "Error creating text index \"%1\" on table \"%2\No message There was an internal error creating a text index.

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

-1166L Error 2842 WT011 "Text indexes are not supported for this database." The current database does not have catalog support for text indexes. To use this feature, upgrade your database to the most recent version.

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

-1167L Error 2843 55W12 "Cannot drop a user that owns text configurations" You attempted to drop a user that is the creator of a text configuration. The text configuration must be dropped first.

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

-1168L Error 2844 WT012 "Cannot alter or drop a text configuration referenced by a text index." It is not possible to alter or drop a text configuration referenced by a populated text index or currently being used by a text procedure. Either copy the configuration and alter the copy, or close all cursors on text procedures and truncate all indexes that use the configuration.

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


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