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 |
|---|---|---|---|---|---|
| 2153 | Error | 42W29 | -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. |
| 2154 | Error | 0AW04 | -275L | "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. |
| 2155 | Error | 5RW01 | -280L | "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. |
| 2156 | Error | 5RW02 | -281L | "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. |
| 2157 | Error | 5RW03 | -282L | "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. |
| 2158 | Error | 5RW04 | -283L | "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. |
| 2159 | Error | 5RW05 | -284L | "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. |
| 2160 | Error | 5RW06 | -285L | "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. |
| 2161 | Error | 5RW07 | -286L | "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. |
| 2162 | Error | 5RW08 | -287L | "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. |
| 2163 | Error | 5RW09 | -288L | "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. |
| 2164 | Error | 09W05 | -295L | "Cannot uniquely identify rows in cursor" | You opened a UNIQUE cursor on a SELECT statement for which a set of columns uniquely identifying each row cannot be generated. One of the tables may not be defined with a primary key or uniqueness constraint, or the SELECT statement may involve a UNION, INTERSECT, EXCEPT, or GROUP BY. Click here for a list of possible parameters and odbc states. |
| 2165 | Error | 53W07 | -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. |
| 2166 | Error | 53W08 | -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. |
| 2167 | Error | 42W16 | -200L | "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. |
| 2168 | Error | 42W17 | -201L | "Invalid setting for option '%1'" | You supplied an invalid value for an option in the SET statement. Some options allow only numeric values, while other options allow only the values On and Off. Click here for a list of possible parameters and odbc states. |
| 2169 | Error | 42W18 | -210L | "User '%1' has the row in '%2' locked" | You attempted to read or write a row that is locked by another user, while the database option 'blocking' is set to Off. Click here for a list of possible parameters and odbc states. |
| 2170 | Error | 42W19 | -211L | "Not allowed while '%1' is using the database" | You attempted a data definition language operation that cannot be completed while another user is connected. Click here for a list of possible parameters and odbc states. |
| 2171 | Error | 42W20 | -212L | "CHECKPOINT statement requires a rollback log" | You cannot use a CHECKPOINT statement when the database server is running in bulk mode without a rollback log. Click here for a list of possible parameters and odbc states. |
| 2172 | Error | 42W21 | -214L | "Table in use" | You attempted to ALTER or DROP a table that is being used by other active users of the database. Click here for a list of possible parameters and odbc states. |