Messages WT012 through WW011

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

SQL State Msg Type Number SQL Code Message Possible Cause
WT012 Error 2844 -1168L "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.

WT013 Error 2846 -1169L "Cannot access a table that is part of a text index." It is not possible to directly manipulate tables created as part of a text index.

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

WT014 Error 2851 -1174L "Cannot create text configuration '%1' because option '%2' has an inappropriate setting" You attempted an operation that needs to create or alter the database options settings for a text configuration, but one of the options is currently set to a value not permitted for a text configuration.

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

WT015 Error 2859 -1182L "Command not allowed on IMMEDIATE REFRESH text index" You cannot use REFRESH TEXT INDEX or TRUNCATE TEXT INDEX on an index that is created with immediate refresh. You cannot alter a text index to use or stop using immediate refresh.

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

WT016 Error 2884 -1207L "Invalid use of NEAR operator in text query." Only terms, prefixes, or other NEAR operators are allowed as arguments to a NEAR operator.

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

WT017 Error 2894 -1216L "The arguments to this procedure must be literal strings." This procedure only accepts literal strings as arguments.

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

WT018 Error 2920 -1240L "The provided stoplist is too long." A text configuration stop list must be less than 8000 bytes.

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

WT019 Error 2936 -1253L "The text index %1 needs to be refreshed" There is a text index that matches the query, but it needs to be refreshed before it is used.

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

WT020 Error 2970 -1283L "A CONTAINS query is not allowed on the view or derived table '%1'." A view or derived table can only be queried using CONTAINS if it does not use TOP, FIRST, DISTINCT, GROUP BY, or FOR XML. In addition, the list of columns to search must all come from a single base table in the FROM clause of the view. They cannot come from multiple tables, or from another view or derived table in the FROM clause.

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

WW001 Error 2215 -606L "The pattern is too long" The pattern for the LIKE operator is too long. All patterns of 126 characters or less are supported. Some patterns as long as 254 characters are supported, depending on their contents. Patterns longer than 254 characters are not supported.

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

WW002 Error 2216 -607L "Cannot stop the database server" The server has determined that it cannot be shut down at this time. Normally, this error should not occur.

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

WW003 Error 2220 -617L "Calling functions outside the database server is not supported" You attempted to call a stored procedure that, in turn, calls a function in a dynamically loaded module. The operating system on which this stored procedure was called does not support such an action.

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

WW004 Error 2221 -618L "Mismatch between external function platform specifier and current operating system" A call to an external entry point in a dynamically loaded module was qualified by an operating system that was not the operating system on which the server is currently executing.

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

WW005 Error 2222 -619L "Need a dynamic library name" You must provide a library name specifier in the name of the external function to call.

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

WW006 Error 2223 -620L "Could not load dynamic library '%1'" This error is usually caused by a failure to load a dynamic library named in an external function call.

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

WW007 Error 2224 -621L "Could not find '%1' in dynamic library '%2'" The external function could not be found in the dynamic library.

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

WW008 Error 2225 -622L "Could not allocate resources to call external function" The external function could not be called due to a shortage of operating system resources. If the operating system supports threads, the maximum thread count should be increased.

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

WW009 Error 2227 -624L "Expression has unsupported data type" Either an external function or Java method is declared to have a parameter or result data type that is not supported, or a Java field reference with an unsupported result type was attempted.

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

WW010 Error 2228 -625L "Too many parameters to this external procedure call" There is a maximum of 256 parameters to an external function call in 32-bit Windows.

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

WW011 Error 2229 -626L "A thread used internally could not be started" This is a Windows 95 specific error. An operating system thread could not be started that is required to execute external functions.

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


Created June 15, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com