Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1303 | "Too many MESSAGE...FOR CONNECTION messages" |
|---|---|
Constant | CONNECTION_MESSAGE_QUEUE_FULL |
SAP Sybase Error Number | 2991 |
SQL State | 54W16 |
SQL Code | -1303L |
ODBC 2 State | 37000 |
ODBC 3 State | 54000 |
Severity Code | |
Probable Cause | You executed a MESSAGE...FOR CONNECTION statement and the maximum number of messages for the connection have already been queued. |
| Error 1304 | "Could not create a new text index for this table with the same settings as \"%1\No message |
|---|---|
Constant | TEXT_INDEX_SAME_SETTING_IDX |
SAP Sybase Error Number | 2992 |
SQL State | WT021 |
SQL Code | -1304L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the other text index with the same settings. |
Probable Cause | Two text indexes with the same column list and configuration settings cannot be created for a table. |
| Error 1305 | "MobiLink communication error -- code: %1, parameter: %2, system code: %3" |
|---|---|
Constant | MOBILINK_COMMUNICATIONS_ERROR |
SAP Sybase Error Number | 2993 |
SQL State | 0AWD5 |
SQL Code | -1305L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | The MobiLink communication error code. |
Parameter 2 | The parameter to the MobiLink communication error if one exists. |
Parameter 3 | The system error code. |
Probable Cause | An error was encountered while communicating with a MobiLink server. |
| Error 1306 | "IN DBSPACE clause cannot be used for column '%1' since table '%2' is a partitioned table." |
|---|---|
Constant | IN_DBSPACE_NOT_ALLOWED |
SAP Sybase Error Number | 2994 |
SQL State | WW238 |
SQL Code | -1306L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The column name |
Parameter 2 | The table name |
Probable Cause | Entire column cannot be assigned to a dbspace using the IN DBSPACE clause, if the table is a partitioned table. |
| Error 1307 | "Database mirroring options are not supported for this database" |
|---|---|
Constant | MIRRORING_OPTIONS_NOT_SUPPORTED |
SAP Sybase Error Number | 2995 |
SQL State | WW130 |
SQL Code | -1307L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database does not have catalog support for database mirroring servers and options. To use this feature, upgrade your database to the most recent version. |
| Error 1308 | "Mirror server \"%1\" not found" |
|---|---|
Constant | MIRROR_SERVER_NOT_FOUND |
SAP Sybase Error Number | 2996 |
SQL State | WW131 |
SQL Code | -1308L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the mirror server. |
Probable Cause | The named mirror server was not found in the database. |
| Error 1309 | "Mirror server \"%1\" already exists" |
|---|---|
Constant | MIRROR_SERVER_ALREADY_EXISTS |
SAP Sybase Error Number | 2997 |
SQL State | WW132 |
SQL Code | -1309L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the mirror server. |
Probable Cause | An attempt was made to create a mirror server that already exists in the database. |
| Error 1310 | "Mirror server \"%1\" is referenced by another server" |
|---|---|
Constant | MIRROR_SERVER_IN_USE |
SAP Sybase Error Number | 2998 |
SQL State | WW133 |
SQL Code | -1310L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the mirror server. |
Probable Cause | An attempt was made to drop a mirror server that is referenced by another mirror server in the database. |
| Error 1311 | "Principal mirror servers are already defined" |
|---|---|
Constant | MIRROR_PARTNERS_ALREADY_DEFINED |
SAP Sybase Error Number | 2999 |
SQL State | WW134 |
SQL Code | -1311L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An attempt was made to create a mirror server without a parent server, but two principal mirror servers are already defined in the database. |
| Error 1312 | "Mirror server \"%1\" is not a valid parent server" |
|---|---|
Constant | INVALID_MIRROR_PARENT |
SAP Sybase Error Number | 3000 |
SQL State | WW135 |
SQL Code | -1312L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the mirror server. |
Probable Cause | An attempt was made to define a parent for a mirror server that would result in a cycle. |
| Error 1313 | "Maximum string length exceeded" |
|---|---|
Constant | MAX_STRING_LENGTH_EXCEEDED |
SAP Sybase Error Number | 2969 |
SQL State | 54W17 |
SQL Code | -1313L |
ODBC 2 State | 37000 |
ODBC 3 State | 54000 |
Severity Code | |
Probable Cause | A string operation attempted to create a string longer than the maximum allowed by the server. |
| Error 1314 | "Cannot force failover when current server is marked as preferred" |
|---|---|
Constant | CANNOT_FORCE_FAILOVER_ON_PREFERRED |
SAP Sybase Error Number | 3001 |
SQL State | WW136 |
SQL Code | -1314L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An attempt was made to execute ALTER DATABASE SET PARTNER FAILOVER but the current server is marked as preferred. Attempting to force a failover in this situation is not allowed. |
| Error 1315 | "Script file missing statement \"go\" delimiter on a separate line" |
|---|---|
Constant | SCRIPT_MISSING_DELIMITER |
SAP Sybase Error Number | 2931 |
SQL State | WW046 |
SQL Code | -1315L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | For UltraLite, all non-comment SQL statements in a script file (including the final one) must be followed by "go" on a line by itself. For strings, you can use "\ngo" to end a statement. |
| Error 1316 | "Unsupported load column specification used for a catalog store table." |
|---|---|
Constant | IQ_LOAD_TABLE_UNSUPPORTED_COLUMN_SPEC |
SAP Sybase Error Number | 2930 |
SQL State | 0AW25 |
SQL Code | -1316L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | For catalog store tables, only some of the load column specifications (for example, filler) are permitted. |
| Error 1317 | "Multiplex server '%1' is shutting down due to a successful configuration change" |
|---|---|
Constant | MPX_CONFIG_CHANGES_SRV_SHUTDOWN |
SAP Sybase Error Number | 2919 |
SQL State | WW239 |
SQL Code | -1317L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the multiplex server. |
Probable Cause | Successful execution of certain statements to change multiplex configuration forces a server shutdown. You will get the above error if you issue such a command. |
| Error 1318 | "More articles are being dropped from publication '%1' than are defined" |
|---|---|
Constant | TOO_MANY_ARTICLES_DELETED |
SAP Sybase Error Number | 2890 |
SQL State | 42W89 |
SQL Code | -1318L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Parameter 1 | Name of the publication from which the article could not be dropped. |
Probable Cause | The number of articles in a publication can never fall below one. Your ALTER PUBLICATION has more drop/delete article clauses than the current number of articles in the publication. |
| Error 1319 | "Synchronization schema changes and script versions are not supported for this database" |
|---|---|
Constant | SYNC_SCHEMA_UPGRADE |
SAP Sybase Error Number | 3002 |
SQL State | WW137 |
SQL Code | -1319L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database does not have catalog support for synchronization schema changes and script versions. To use this feature, upgrade your database to the most recent version. |
| Error 1320 | "Error raised by user-defined function: %1" |
|---|---|
Constant | EMSG_UDF_RAISED_ERROR |
SAP Sybase Error Number | 2822 |
SQL State | QFA62 |
SQL Code | -1320L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Error message provided by UDF to accompany UDF SQLCODE. |
Probable Cause | An error was raised by a user-defined function. |
| Error 1321 | "Table or view '%1' is not valid for use with this statement" |
|---|---|
Constant | INVALID_TABLE_TYPE |
SAP Sybase Error Number | 3004 |
SQL State | WW139 |
SQL Code | -1321L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of table |
Probable Cause | The named table or view cannot be used with this statement. For example, the statement may not allow temporary tables or views. |
| Error 1322 | "A synchronization schema change is already in progress" |
|---|---|
Constant | SYNC_SCHEMA_IN_PROGRESS |
SAP Sybase Error Number | 3005 |
SQL State | WW140 |
SQL Code | -1322L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A START SYNCHRONIZATION SCHEMA CHANGE statement is already in progress. |