Messages WW225 through WX005

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
WW225 Error 2933 -1250L "Table '%1' is not a partitioned table" This table is not partitioned.

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

WW226 Error 2934 -1251L "Table '%1' is already partitioned" This table is already partitioned.

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

WW227 Error 2935 -1252L "Dbspace '%1' is the incorrect type" Tried to put data into the incorrect dbspace (for example, putting a primary key into the wrong store).

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

WW228 Error 2938 -1255L "Cannot merge partition '%1' into '%2' for column '%3'" These column partitions cannot be merged.

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

WW229 Error 2964 -1277L "Parameter '%1' cannot be null" The specified parameter cannot be null.

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

WW230 Error 2965 -1278L "Operation is not allowed" The requested operation is not allowed while schema is being modified.

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

WW231 Error 2966 -1279L "Operation '%1' failed for reason: '%2'" The requested operation failed.

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

WW232 Error 2967 -1280L "Underflow when converting '%1'" An underflow occurred when converting the specified type. The source type may be too small (for example zero length binary) or value may be too small to be represented by the destination type.

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

WW233 Error 2971 -1284L "Invalid partition key specification: must use '%1'. " Partition key cannot be changed for ALTER TABLE ADD PARTITION. It must specify the same partition key column as the CREATE TABLE did.

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

WW234 Warning 2972 149L "Automatic database upgrade applied" The database is from an older version of the software. An automatic database upgrade occurs during startup. Subsequently the database can no longer be opened with the older version of the software.

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

WW235 Error 2979 -1291L "Column '%1' Partition '%2' may not be assigned to a dbspace because partitioning is not supported for datatype '%3'." The column storage for certain datatypes (such as the BIT datatype) cannot be assigned to a dbspace.

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

WW236 Error 2980 -1292L "Column '%1' may not be assigned to a dbspace because partitioning is not supported for datatype '%2'." The column storage for certain datatypes (such as the BIT datatype) cannot be assigned to a dbspace.

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

WW237 Error 2981 -1293L "Partition key of '%1' is unsupported." Partitioning over the specified datatype is not supported.

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

WW238 Error 2994 -1306L "IN DBSPACE clause cannot be used for column '%1' since table '%2' is a partitioned table." Entire column cannot be assigned to a dbspace using the IN DBSPACE clause, if the table is a partitioned table.

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

WW239 Error 2919 -1317L "Multiplex server '%1' is shutting down due to a successful configuration change" Successful execution of certain statements to change multiplex configuration forces a server shutdown. You will get the above error if you issue such a command.

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

WX001 Error 2526 -874L "Column must be named: %1" Unnamed columns cannot be used as XML element or attribute names. Name unnamed columns in the SELECT list using AS.

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

WX002 Error 2550 -888L "XML parser error: %1" An XML instance will only parse correctly if it is well-formed as defined by the XML 1.0 specification.

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

WX003 Error 2555 -892L "XPath parser error: %1" The XPath expression is illegal or uses features that are not currently supported.

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

WX004 Error 2556 -893L "Illegal flags value passed to OPENXML" The flags value passed to OPENXML as the third argument must be either 1 (attribute-centric mapping), or 2 (element-centric mapping).

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

WX005 Error 2563 -897L "Illegal FOR XML EXPLICIT tag value: '%1'" FOR XML EXPLICIT tag values must be greater than 0 and less than 256. Also, NULL values are not allowed in the Tag column.

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