Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 263 | "Invalid absolute or relative offset in FETCH" |
|---|---|
Constant | INVALID_FETCH_POSITION |
SAP Sybase Error Number | 2142 |
SQL State | 42W25 |
SQL Code | -263L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You specified an offset in a FETCH that was invalid or NULL. |
| Error 264 | "Wrong number of variables in FETCH" |
|---|---|
Constant | WRONG_NUM_OF_FETCH_VARIABLES |
SAP Sybase Error Number | 2143 |
SQL State | 42W26 |
SQL Code | -264L |
ODBC 2 State | S1002 |
ODBC 3 State | 07009 |
Severity Code | |
Probable Cause | You specified a number of variables in a FETCH statement that does not match the number of SELECT list items. |
| Error 265 | "Procedure '%1' not found" |
|---|---|
Constant | PROCEDURE_NOT_FOUND |
SAP Sybase Error Number | 2144 |
SQL State | 52W09 |
SQL Code | -265L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the procedure that could not be found. |
Probable Cause | You misspelled the name of a procedure, or you did not qualify a procedure name with a user name. |
| Error 267 | "COMMIT/ROLLBACK not allowed within atomic operation" |
|---|---|
Constant | ATOMIC_OPERATION |
SAP Sybase Error Number | 2146 |
SQL State | 42W28 |
SQL Code | -267L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted a COMMIT or ROLLBACK statement while executing within an atomic operation. |
| Error 268 | "Trigger '%1' not found" |
|---|---|
Constant | TRIGGER_NOT_FOUND |
SAP Sybase Error Number | 2147 |
SQL State | 52W10 |
SQL Code | -268L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the trigger that could not be found. |
Probable Cause | You misspelled the name of a trigger, or you did not qualify a trigger name with a user name. |
| Error 269 | "Cannot delete or rename a column referenced in a trigger definition" |
|---|---|
Constant | COLUMN_IN_TRIGGER |
SAP Sybase Error Number | 2148 |
SQL State | 53W06 |
SQL Code | -269L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to delete or rename a column referenced in a trigger definition. Drop the trigger before performing the ALTER statement. |
| Error 270 | "Cannot drop a user that owns procedures in runtime server" |
|---|---|
Constant | USER_OWNS_PROCEDURES |
SAP Sybase Error Number | 2149 |
SQL State | 55W04 |
SQL Code | -270L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 271 | "Trigger definition conflicts with existing triggers" |
|---|---|
Constant | TRIGGER_DEFN_CONFLICT |
SAP Sybase Error Number | 2150 |
SQL State | 52W11 |
SQL Code | -271L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S01 |
Severity Code | |
Probable Cause | You attempted to create a trigger, but a trigger with the same name already exists. |
| Error 272 | "Invalid REFERENCES clause in trigger definition" |
|---|---|
Constant | INVALID_TRIGGER_COL_REFS |
SAP Sybase Error Number | 2151 |
SQL State | 52W12 |
SQL Code | -272L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 273 | "COMMIT/ROLLBACK not allowed within trigger actions" |
|---|---|
Constant | INVALID_TRIGGER_STATEMENT |
SAP Sybase Error Number | 2152 |
SQL State | 2D501 |
SQL Code | -273L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | 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. |
| Error 274 | "Procedure or trigger calls have nested too deeply" |
|---|---|
Constant | NESTING_TOO_DEEP |
SAP Sybase Error Number | 2153 |
SQL State | 42W29 |
SQL Code | -274L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You may have defined a procedure or trigger that causes unlimited recursion. |
| Error 280 | "Publication '%1' not found" |
|---|---|
Constant | PUBLICATION_NOT_FOUND |
SAP Sybase Error Number | 2155 |
SQL State | 5RW01 |
SQL Code | -280L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the publication that could not be found. |
Probable Cause | You misspelled the name of a publication, or you did not qualify a publication name with a user name. |
| Error 281 | "Table '%1' has publications" |
|---|---|
Constant | TABLE_HAS_PUBLICATIONS |
SAP Sybase Error Number | 2156 |
SQL State | 5RW02 |
SQL Code | -281L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the table that has publications. |
Probable Cause | You attempted to drop a table that has publications defined. |
| Error 282 | "Subscription to '%1' for '%2' already exists" |
|---|---|
Constant | SUBSCRIPTION_NOT_UNIQUE |
SAP Sybase Error Number | 2157 |
SQL State | 5RW03 |
SQL Code | -282L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the publication. |
Parameter 2 | Name of the user. |
Probable Cause | You attempted to create a subscription that already exists. |
| Error 283 | "Subscription to '%1' for '%2' not found" |
|---|---|
Constant | SUBSCRIPTION_NOT_FOUND |
SAP Sybase Error Number | 2158 |
SQL State | 5RW04 |
SQL Code | -283L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the publication. |
Parameter 2 | Name of the user. |
Probable Cause | You attempted to drop, start, or synchronize a subscription that does not exist. |
| Error 284 | "User '%1' is already the publisher for this database" |
|---|---|
Constant | ONLY_ONE_PUBLISHER |
SAP Sybase Error Number | 2159 |
SQL State | 5RW05 |
SQL Code | -284L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of the publisher. |
Probable Cause | You attempted to GRANT PUBLISH to a user ID, when a publisher already exists. |
| Error 285 | "User '%1' is not a remote user for this database" |
|---|---|
Constant | NOT_REMOTE_USER |
SAP Sybase Error Number | 2160 |
SQL State | 5RW06 |
SQL Code | -285L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of user. |
Probable Cause | 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. |
| Error 286 | "Remote message type '%1' not found" |
|---|---|
Constant | NOT_REMOTE_TYPE |
SAP Sybase Error Number | 2161 |
SQL State | 5RW07 |
SQL Code | -286L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Parameter 1 | Name of remote message type. |
Probable Cause | You referred to a remote message type that is not defined in this database. Use CREATE REMOTE TYPE to define remote message types. |
| Error 287 | "Passthrough statement inconsistent with current passthrough" |
|---|---|
Constant | PASSTHROUGH_INCONSISTENT |
SAP Sybase Error Number | 2162 |
SQL State | 5RW08 |
SQL Code | -287L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Probable Cause | 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. |
| Error 288 | "Remote statement failed" |
|---|---|
Constant | REMOTE_STATEMENT_FAILED |
SAP Sybase Error Number | 2163 |
SQL State | 5RW09 |
SQL Code | -288L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S02 |
Severity Code | |
Probable Cause | 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. |