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 |
|---|---|---|---|---|---|
| -264L | Error | 2143 | 42W26 | "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. |
| -265L | Error | 2144 | 52W09 | "Procedure '%1' not found" | You misspelled the name of a procedure, or you did not qualify a procedure name with a user name. Click here for a list of possible parameters and odbc states. |
| -267L | Error | 2146 | 42W28 | "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. |
| -268L | Error | 2147 | 52W10 | "Trigger '%1' not found" | You misspelled the name of a trigger, or you did not qualify a trigger name with a user name. Click here for a list of possible parameters and odbc states. |
| -269L | Error | 2148 | 53W06 | "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. |
| -270L | Error | 2149 | 55W04 | "Cannot drop a user that owns procedures in runtime server" | You attempted to drop a user that owns procedures while using the runtime server. This operation would result in dropping procedures. The runtime server cannot drop procedures. Use the full server. Click here for a list of possible parameters and odbc states. |
| -271L | Error | 2150 | 52W11 | "Trigger definition conflicts with existing triggers" | You attempted to create a trigger, but a trigger with the same name already exists. Click here for a list of possible parameters and odbc states. |
| -272L | Error | 2151 | 52W12 | "Invalid REFERENCES clause in trigger definition" | You supplied an invalid REFERENCES clause in a trigger definition. You may have specified an OLD correlation name in a BEFORE INSERT trigger, or a NEW correlation name in an AFTER DELETE trigger. In both cases, the values do not exist and cannot be referenced. Click here for a list of possible parameters and odbc states. |
| -273L | Error | 2152 | 2D501 | "COMMIT/ROLLBACK not allowed within trigger actions" | You attempted to execute a statement that is not allowed while performing a trigger action. COMMIT and ROLLBACK statements cannot be executed from a trigger. Click here for a list of possible parameters and odbc states. |
| -274L | Error | 2153 | 42W29 | "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. |
| -275L | Error | 2154 | 0AW04 | "Triggers and procedures not supported in runtime server" | You attempted to call a stored procedure or have modified a row in a table on which a trigger is defined and you are using the runtime server. Triggers and stored procedures are not supported in the runtime server. You must run the full server to use these features. Click here for a list of possible parameters and odbc states. |
| -280L | Error | 2155 | 5RW01 | "Publication '%1' not found" | You misspelled the name of a publication, or you did not qualify a publication name with a user name. Click here for a list of possible parameters and odbc states. |
| -281L | Error | 2156 | 5RW02 | "Table '%1' has publications" | You attempted to drop a table that has publications defined. Click here for a list of possible parameters and odbc states. |
| -282L | Error | 2157 | 5RW03 | "Subscription to '%1' for '%2' already exists" | You attempted to create a subscription that already exists. Click here for a list of possible parameters and odbc states. |
| -283L | Error | 2158 | 5RW04 | "Subscription to '%1' for '%2' not found" | You attempted to drop, start, or synchronize a subscription that does not exist. Click here for a list of possible parameters and odbc states. |
| -284L | Error | 2159 | 5RW05 | "User '%1' is already the publisher for this database" | You attempted to GRANT PUBLISH to a user ID, when a publisher already exists. Click here for a list of possible parameters and odbc states. |
| -285L | Error | 2160 | 5RW06 | "User '%1' is not a remote user for this database" | You attempted to execute a CREATE SUBSCRIPTION or PASSTHROUGH for a user that is not a remote user of this database. You must GRANT REMOTE or GRANT CONSOLIDATE for this user before proceeding with this operation. Click here for a list of possible parameters and odbc states. |
| -286L | Error | 2161 | 5RW07 | "Remote message type '%1' not found" | You referred to a remote message type that is not defined in this database. Use CREATE REMOTE TYPE to define remote message types. Click here for a list of possible parameters and odbc states. |
| -287L | Error | 2162 | 5RW08 | "Passthrough statement inconsistent with current passthrough" | Passthrough is additive, in that subsequent PASSTHROUGH statements add to the list of users receiving passthrough. The PASSTHROUGH statements must all be PASSTHROUGH ONLY or none should be PASSTHROUGH ONLY. Click here for a list of possible parameters and odbc states. |
| -288L | Error | 2163 | 5RW09 | "Remote statement failed" | This SQLSTATE can be signaled within a trigger to prevent the SQL Remote Message Agent (dbremote) from displaying an error message in the output. This exception will only occur when a trigger or procedure signals it. This is useful for ignoring replication errors that are permitted by design. Click here for a list of possible parameters and odbc states. |