Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 2105 | Error | 22003 | -158L | "Value %1 out of range for destination" | You supplied to or fetched from the database a value that is out of range for the destination column or host variable. For example, the value 10 may have been supplied for a DECIMAL(3,2) field. Click here for a list of possible parameters and odbc states. |
| 2106 | Error | 42W13 | -159L | "Invalid column number" | You gave an invalid column number, or the column you are looking for is in a different table. Click here for a list of possible parameters and odbc states. |
| 2107 | Error | 07005 | -160L | "Can only describe a SELECT statement" | In the C language interface, you attempted to describe the SELECT list of a statement other than a SELECT statement. In UltraLite this error can result from trying to retrieve the schema of any statement other than a SELECT. Click here for a list of possible parameters and odbc states. |
| 2108 | Error | 07W01 | -161L | "Invalid type on DESCRIBE statement" | A Java type specified on a DESCRIBE statement has no corresponding SQL type. Click here for a list of possible parameters and odbc states. |
| 2109 | Error | 24W01 | -170L | "Cursor has not been declared" | You attempted to OPEN a cursor that has not been declared. Click here for a list of possible parameters and odbc states. |
| 2110 | Error | 07003 | -171L | "Error opening cursor" | You attempted to open a cursor on a statement that is not SELECT, CALL or EXEC. Click here for a list of possible parameters and odbc states. |
| 2111 | Error | 24502 | -172L | "Cursor already open" | You attempted to OPEN a cursor that is already open. Click here for a list of possible parameters and odbc states. |
| 2112 | Error | 24501 | -180L | "Cursor not open" | You attempted to use a cursor that has not been opened. Click here for a list of possible parameters and odbc states. |
| 2113 | Error | 22002 | -181L | "No indicator variable provided for NULL result" | You tried to retrieve a value from the database that was NULL, but you did not provide an indicator variable for that value. Click here for a list of possible parameters and odbc states. |
| 2114 | Error | 07002 | -182L | "Not enough fields allocated in SQLDA" | There are not enough fields in the SQLDA to retrieve all of the values requested. Click here for a list of possible parameters and odbc states. |
| 2116 | Error | 21000 | -185L | "SELECT returns more than one row" | You tried to use a SELECT statement without a cursor, but the statement cursor returns more than one row. Only a single row SELECT statement can be used in this context. Click here for a list of possible parameters and odbc states. |
| 2117 | Error | 21W01 | -186L | "Subquery cannot return more than one row" | You used a subquery that returns more than one row, in a context where only a single row can be used. If the subquery is in the WHERE clause, you might be able to use the IN keyword. Click here for a list of possible parameters and odbc states. |
| 2118 | Error | 09W02 | -187L | "Illegal cursor operation attempt" | You attempted an illegal cursor operation. For example, you may be attempting to OPEN a cursor for a statement that is neither a SELECT nor a BATCH. Click here for a list of possible parameters and odbc states. |
| 2119 | Error | 07001 | -188L | "Not enough values for host variables" | You have not provided enough host variables for either the number of bind variables, or the statement, or the number of SELECT list items. Click here for a list of possible parameters and odbc states. |
| 2120 | Error | WI005 | -189L | "Unable to find in index '%1' for table '%2'" | This is an internal error. If it can be reproduced, it should be reported to iAnywhere. You should be able to work around the error by dropping and recreating the index. Click here for a list of possible parameters and odbc states. |
| 2121 | Error | 53W02 | -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. |
| 2122 | Error | 42W32 | -191L | "Cannot modify column '%1' in table '%2'" | You may have tried to modify a column that you do not have permission to modify. You may have tried to modify a column defined as an expression (such as column1+column2) in a view. Click here for a list of possible parameters and odbc states. |
| 2123 | Error | 42W31 | -192L | "Update operation attempted on non-updatable query" | You attempted an insert, update, or delete operation on a query that is implicitly read-only. Queries that contain DISTINCT, GROUP BY, HAVING, EXCEPT, INTERSECT or UNION, or that contain aggregate functions, or that involve a join, are implicitly read-only. If the query references a view then the view may be non-updatable. Click here for a list of possible parameters and odbc states. |
| 2124 | Error | 23W01 | -193L | "Primary key for table '%1' is not unique: Primary key value ('%2')" | You attempted to add a new row to a table, but the new row has the same primary key as an existing row. The database has not added the incorrect row to the database. For example, you might have added a student with student number 86004 and there is already a row for a student with that number. Click here for a list of possible parameters and odbc states. |
| 2125 | Error | 23503 | -194L | "No primary key value for foreign key '%1' in table '%2'" | You attempted to insert or update a row that has a foreign key for another table. The value for the foreign key is not NULL and there is not a corresponding value in the primary key. Click here for a list of possible parameters and odbc states. |