Messages 42W26 through 42W42

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
42W26 Error 2143 -264L "Wrong number of variables in FETCH" You specified a number of variables in a FETCH statement that does not match the number of SELECT list items.

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

42W28 Error 2146 -267L "COMMIT/ROLLBACK not allowed within atomic operation" You attempted a COMMIT or ROLLBACK statement while executing within an atomic operation.

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

42W29 Error 2153 -274L "Procedure or trigger calls have nested too deeply" You may have defined a procedure or trigger that causes unlimited recursion.

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

42W30 Error 2236 -633L "Update operation attempted on a read-only cursor" You attempted an update operation on a cursor that was explicitly declared as read-only.

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

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

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

42W33 Error 2081 -141L "Table '%1' not found" You misspelled the name of a table, or you did not qualify a table name with the owner name. For example, you might have referred to "Employees" instead of "DBA"."Employees".

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

42W34 Error 2069 -312L "User '%1' already has membership in group '%2'" You attempted to give a membership in a group to a user that already has such membership.

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

42W35 Error 2372 -728L "Update operation attempted on non-updatable remote query" You attempted an update or delete operation on a remote table that is currently not supported. Examples of such operations include positioned updates or deletes and updates or deletes that involve a join between local and proxy tables. Updates or deletes that involve a join between proxy tables on different remote servers will also give this error.

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

42W36 Error 2460 -813L "FOR UPDATE has been incorrectly specified for a READ ONLY cursor" You attempted to declare a cursor FOR UPDATE on a query that is not updatable. Queries that contain DISTINCT, GROUP BY, HAVING, INTERSECT, EXCEPT, or UNION, or that contain aggregate functions are read-only. If the ansi_update_constraints option is on, then queries that contain a join are 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.

42W37 Error 2461 -814L "Cannot update column '%1' since it appears in the ORDER BY clause" You attempted to update a column that appears in the ORDER BY clause. The ansi_update_constraints option controls whether this update is allowed.

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

42W38 Error 2462 -815L "Cannot update column '%1' since it does not appear in the SELECT clause" You attempted to update a column that does not explicitly appear in the SELECT list. The ansi_update_constraints option controls whether this update is allowed.

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

42W39 Error 2797 -1125L "Conflicting INSTEAD OF trigger and WITH CHECK OPTION on view '%1'" You attempted an operation that involves a WITH CHECK OPTION clause that conflicts with an INSTEAD OF trigger. A view defined with the WITH CHECK OPTION clause cannot refer to a view (possibly nested) with an INSTEAD OF trigger.

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

42W3A Error 2798 -1126L "Operation failed because table or view '%1' has an INSTEAD OF trigger" You attempted an operation that cannot succeed because an INSTEAD OF trigger is defined on a target table or view (possibly nested in another view).

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

42W3B Error 2799 -1127L "Positioned update operation attempted on a view with an INSTEAD OF trigger" You attempted a positioned update, positioned delete, put, or wide insert operation that would involve an INSTEAD OF trigger on a view (possibly nested). These operations are not supported with INSTEAD OF triggers on views.

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

42W3C Error 2805 -1133L "Invalid trigger type for view '%1'" You attempted to create a trigger on a view, but the type of trigger is supported on base tables only. Only INSTEAD OF triggers can be created on views.

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

42W3D Error 2806 -1134L "Triggers cannot be created on materialized view '%1'" You attempted to create a trigger on a materialized view. A materialized view is not a valid target for a trigger.

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

42W40 Error 2242 -636L "Duplicate referencing column" You supplied a duplicate column name in the list of referencing columns.

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

42W41 Error 2243 -637L "Duplicate insert column" You supplied a duplicate column name in the list of insert columns.

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

42W42 Error 2245 -639L "Parameter name missing in call to procedure '%1'" Positional parameters were specified after named parameters in a call to this procedure.

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