Messages 182 through 200

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
-182L Error 2114 07002 "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.

-183L Error 2063 52W03 "Cannot find index named '%1'" You attempted to perform an operation using an index that does not exist. Check for spelling errors. Check whether the index name must be qualified with a user ID.

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

-184L Error 2531 23501 "Column '%1' in table '%2' cannot be NULL. The invalid data was supplied to LOAD TABLE in a data file on line %3" You either have not supplied a value where a value is required or a data conversion was necessary that resulted in a NULL value. The column definition prohibits NULL values or the column is part of a NOT NULL foreign key.

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

-185L Error 2116 21000 "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.

-186L Error 2117 21W01 "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.

-187L Error 2118 09W02 "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.

-188L Error 2119 07001 "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.

-189L Error 2120 WI005 "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.

-190L Error 2121 53W02 "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.

-191L Error 2122 42W32 "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.

-192L Error 2123 42W31 "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.

-193L Error 2124 23W01 "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.

-194L Error 2125 23503 "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.

-195L Error 2126 23502 "Column '%1' in table '%2' cannot be NULL" You have not supplied a value where a value is required. The column definition prohibits NULL values or the column is part of a NOT NULL foreign key.

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

-196L Error 2127 23505 "Index '%1' for table '%2' would not be unique" You attempted to insert or update a row that has the same value as another row in some column, and there is a constraint that does not allow two rows to have the same value in that column.

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

-197L Error 2128 24503 "No current row of cursor" You attempted to perform an operation on the current row of a cursor, but the cursor is not positioned on a row. The cursor is before the first row of the cursor, after the last row, or is on a row that has since been deleted.

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

-198L Error 2129 23W05 "Primary key for row in table '%1' is referenced by foreign key '%2' in table '%3'" You attempted to delete or modify a row whose primary key value is referenced elsewhere in the database.

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

-199L Error 2130 09W04 "INSERT/DELETE on cursor can modify only one table" You attempted to insert into a cursor and have specified values for more than one table, or you attempted to delete from a cursor that involves a join. Insert into one table at a time. For DELETE, use the FROM clause to specify the table you want to delete from.

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

200L Warning 2009 01000 "Warning: %1" A warning has occurred. The message indicates the condition that caused the warning.

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

-200L Error 2167 42W16 "Invalid option '%1' -- no PUBLIC setting exists" You may have misspelled the name of an option in the SET OPTION statement. You can only define an option for a user if the database administrator has supplied a PUBLIC value for that option.

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


Created April 27, 2010. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com