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 |
|---|---|---|---|---|---|
| 53005 | Error | 2095 | -152L | "Invalid ORDER BY specification" | Either you used an integer in an ORDER BY list and the integer is larger than the number of columns in the SELECT list, or you specified an ORDER BY expression that is semantically invalid. For example, with UNION queries you can only use integers to specify an ordering of the result. Click here for a list of possible parameters and odbc states. |
| 53011 | Error | 2051 | -114L | "Number of columns defined for the view does not match SELECT statement" | You attempted to create a view, but the column list specified as part of the CREATE VIEW statement does not correspond to the list of items in the view's SELECT statement. Click here for a list of possible parameters and odbc states. |
| 53017 | Error | 2533 | -162L | "Cannot convert %1 to a %2. The bad value was supplied for column '%3' on row %4 of the data file" | The data file supplied to LOAD TABLE contains a value that cannot be converted to the required data type. Click here for a list of possible parameters and odbc states. |
| 53018 | Error | 2104 | -157L | "Cannot convert %1 to a %2" | An error occurred while trying to convert a value to another data type. Click here for a list of possible parameters and odbc states. |
| 53019 | Error | 2333 | -705L | "Return type of void from procedure '%1' cannot be used in any expression" | The Java type void does not map onto any SQL type, hence a procedure returning void cannot be used in any SQL expression. Click here for a list of possible parameters and odbc states. |
| 53020 | Error | 3041 | -1361L | "TREAT AS can only be used with extended types. Cannot treat %1 as a %2." | An error occurred while trying to treat a value as another data type. Click here for a list of possible parameters and odbc states. |
| 53021 | Error | 3042 | -1362L | "Cannot treat value '%1' as type %2. The dynamic type is %3." | An error occurred while trying to treat a value as another data type. The dynamic type of the value does not match the destination type. Click here for a list of possible parameters and odbc states. |
| 53023 | Error | 2094 | -151L | "Subquery allowed only one SELECT list item" | You entered a subquery that has more than one column in the SELECT list. Change the SELECT list to have only one column. Click here for a list of possible parameters and odbc states. |
| 53026 | Error | 2096 | -153L | "Select lists in UNION, INTERSECT, or EXCEPT do not match in length" | You specified a UNION, INTERSECT, or EXCEPT, but the SELECT statements involved in the operation do not have the same number of columns in the SELECT list. Click here for a list of possible parameters and odbc states. |
| 53030 | Error | 2050 | -113L | "Column '%1' in foreign key has a different definition than primary key" | The data type of the column in the foreign key is not the same as the data type of the column in the primary key. Change the definition of one of the columns using ALTER TABLE. Click here for a list of possible parameters and odbc states. |
| 53W01 | Error | 2057 | -125L | "ALTER clause conflict" | A primary key clause, foreign key clause, or a uniqueness clause must be the only clause of an ALTER TABLE statement. Click here for a list of possible parameters and odbc states. |
| 53W02 | Error | 2121 | -190L | "Cannot update an expression" | You tried to update a column in a query that is a database expression rather than a column in a table. Click here for a list of possible parameters and odbc states. |
| 53W04 | Error | 2086 | -146L | "There is no way to join '%1' to '%2'" | You may have attempted a KEY JOIN between two tables and there is no foreign key on one of the tables that references the primary key of the other table. You may have attempted a NATURAL JOIN between two tables that have no common column names. Click here for a list of possible parameters and odbc states. |
| 53W05 | Error | 2059 | -127L | "Cannot alter a column in an index" | You may have attempted to delete or modify the definition of a column that is part of a primary or foreign key. You may have attempted to delete a column that has an index on it. In this case, DROP the index or key, perform the ALTER statement, and then add the index or key again. Click here for a list of possible parameters and odbc states. |
| 53W06 | Error | 2148 | -269L | "Cannot delete or rename a column referenced in a trigger definition" | You attempted to delete or rename a column referenced in a trigger definition. Drop the trigger before performing the ALTER statement. Click here for a list of possible parameters and odbc states. |
| 53W07 | Error | 2165 | -296L | "Error number %1 for RAISERROR must not be less than 17000" | You supplied an invalid error number in a RAISERROR statement. The number must be greater than or equal to 17000. Click here for a list of possible parameters and odbc states. |
| 53W08 | Error | 2166 | -294L | "Format string argument number %1 is invalid" | You supplied an invalid argument number in the format string for a PRINT or RAISERROR statement. The number must be between 1 and 20 and must not exceed the number of arguments provided. Click here for a list of possible parameters and odbc states. |
| 53W09 | Error | 2218 | -609L | "Invalid data type for column in WRITETEXT or READTEXT" | You referenced a column in a WRITETEXT or READTEXT statement that is not defined for storing text or image data. Click here for a list of possible parameters and odbc states. |
| 54003 | Error | 2061 | -250L | "Identifier '%1' too long" | An identifier that was specified is longer than 128 bytes. Click here for a list of possible parameters and odbc states. |
| 54W01 | Error | 2553 | -890L | "Statement size or complexity exceeds server limits" | The statement contains one or more constructs whose size make it impossible to process. Increasing the maximum cache size, page size, or stack size may resolve this error. Consider rewriting the query so that the internal limit is not exceeded. For example, if the query contains a large IN-list, consider inserting the IN-list's values into a temporary table. Then rewrite the query to join this temporary table to the other table(s) in the original statement. Click here for a list of possible parameters and odbc states. |