Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1366 | "Sequence '%1' in use by another connection" |
|---|---|
Constant | SEQUENCE_IN_USE |
SAP Sybase Error Number | 3046 |
SQL State | 42WE3 |
SQL Code | -1366L |
ODBC 2 State | 40001 |
ODBC 3 State | 40001 |
Severity Code | |
Parameter 1 | Name of user. |
Probable Cause | You have attempted to drop a sequence that is currently being used by another connection. |
| Error 1367 | "User owns sequences in use" |
|---|---|
Constant | USER_OWNS_SEQUENCES_IN_USE |
SAP Sybase Error Number | 3047 |
SQL State | 42WE2 |
SQL Code | -1367L |
ODBC 2 State | 40001 |
ODBC 3 State | 40001 |
Severity Code | |
Probable Cause | You attempted to drop a user that owns a sequence being used by other active users of the database. |
| Error 1369 | "Sequence generators are not supported for this database" |
|---|---|
Constant | SEQUENCES_NOT_SUPPORTED |
SAP Sybase Error Number | 3049 |
SQL State | 52W52 |
SQL Code | -1369L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database does not have catalog support for sequence generators. To use this feature, upgrade your database to the most recent version. |
| Error 1370 | "Text queries cannot contain more than 300 terms." |
|---|---|
Constant | TEXT_QUERY_TOO_LONG |
SAP Sybase Error Number | 3050 |
SQL State | WT022 |
SQL Code | -1370L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A text query should contain 300 terms or less. |
| Error 1371 | "The materialized view cannot be changed to immediate because the ON conditions must refer to both sides of the OUTER JOIN." |
|---|---|
Constant | UPDATABLE_MATVIEW_PSNS_ON_CONDITION |
SAP Sybase Error Number | 3051 |
SQL State | 42WE4 |
SQL Code | -1371L |
ODBC 2 State | 42000 |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to change the refresh type to immediate for a materialized view whose definition contains an illegal ON condition. |
| Error 1372 | "The server is not able to establish TCP/IP connections." |
|---|---|
Constant | TCP_CONNECTIONS_NOT_ENABLED |
SAP Sybase Error Number | 2736 |
SQL State | 08WA3 |
SQL Code | -1372L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | This database server is not able to establish TCP/IP connections. The personal server (dbeng) does not permit TCP/IP connections by default. This error may also occur if a network server (dbsrv) was started with the -xd command line option. The ability to establish TCP/IP connections is required to use diagnostic tracing and application profiling. |
| Error 1373 | "Synchronization failed with internal error: %1" |
|---|---|
Constant | SYNCCMD_INTERNAL_ERROR |
SAP Sybase Error Number | 3052 |
SQL State | 5RW43 |
SQL Code | -1373L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The internal error number |
Probable Cause | An internal error occurred during the execution of the SYNCHRONIZE statement. |
| Error 1374 | "Synchronization failed. Check the results of the call to sp_get_last_synchronize_result( %1 ) for more information." |
|---|---|
Constant | SYNCCMD_SYNCH_FAILED |
SAP Sybase Error Number | 3053 |
SQL State | 5RW44 |
SQL Code | -1374L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The connection ID on which the failed synchronization took place |
Probable Cause | The synchronization completed, but the exit code from the synchronization indicates that the synchronization was not successful. Check the results of the call to sp_get_last_synchronize_result() for more information. |
| Error 1375 | "Failed to start the dbmlsync server" |
|---|---|
Constant | SYNCCMD_START_SERVER_FAIL |
SAP Sybase Error Number | 3054 |
SQL State | 5RW45 |
SQL Code | -1375L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The database server failed to start a new dbmlsync process or failed to connect to an existing dbmlsync server running on the port number specified in the SYNCHRONIZE statement. |
| Error 1376 | "Failed to connect to the dbmlsync server" |
|---|---|
Constant | SYNCCMD_CONNECT_SERVER_FAIL |
SAP Sybase Error Number | 3055 |
SQL State | 5RW46 |
SQL Code | -1376L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The database server failed to make a connection to the dbmlsync server. |
| Error 1377 | "The SYNCHRONIZE statement timed out" |
|---|---|
Constant | SYNCCMD_TIMEOUT |
SAP Sybase Error Number | 3056 |
SQL State | 5RW47 |
SQL Code | -1377L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The SYNCHRONIZE statement did not complete within the timeout value specified. Check the results of the call to sp_get_last_synchronize_result() for more information. |
| Error 1378 | "The database server failed to shut down the dbmlsync server" |
|---|---|
Constant | SYNCCMD_SHUTDOWN_FAIL |
SAP Sybase Error Number | 3057 |
SQL State | 5RW48 |
SQL Code | -1378L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The database server started a new dbmlsync server to process the SYNCHRONIZE statement, but encountered an error while attempting to shut the process down. |
| Error 1379 | "The dbmlsync server failed to shut down in a timely manner" |
|---|---|
Constant | SYNCCMD_SHUTDOWN_SLOW |
SAP Sybase Error Number | 3058 |
SQL State | 5RW49 |
SQL Code | -1379L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The database server started a new dbmlsync server to process the SYNCHRONIZE statement, was successful in requesting that the process shut down, but the process did not shut down within the timeout value that was specified. |
| Error 1380 | "Client redirected more than once" |
|---|---|
Constant | TOO_MANY_REDIRECTS |
SAP Sybase Error Number | 3059 |
SQL State | 08WA4 |
SQL Code | -1380L |
ODBC 2 State | 08S01 |
ODBC 3 State | 08S01 |
Severity Code | |
Probable Cause | The connection was redirected by the primary server to another server, which also attempted to redirect the connection. |
| Error 1381 | "Database server name '%1' cannot be the same as either the primary or mirror server" |
|---|---|
Constant | MIRROR_SERVER_NAME_CONFLICT |
SAP Sybase Error Number | 3060 |
SQL State | WW159 |
SQL Code | -1381L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The server name |
Probable Cause | The mirror servers defined with type PRIMARY or MIRROR cannot have names that match actual server names. |
| Error 1382 | "Download failed due to an invalid or unsupported row value" |
|---|---|
Constant | INVALID_DOWNLOAD_VALUE |
SAP Sybase Error Number | 3061 |
SQL State | 0AW26 |
SQL Code | -1382L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The synchronization download failed because a downloaded row contained a column value that was either invalid or not supported. |
| Error 1383 | "The licensed maximum number of mirror servers with type COPY has been exceeded" |
|---|---|
Constant | MIRROR_COPY_SERVER_LIMIT_EXCEEDED |
SAP Sybase Error Number | 3062 |
SQL State | WW160 |
SQL Code | -1383L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The maximum number of mirror servers with type COPY that may be defined is limited by the database server license. An attempt was made to create a new mirror server with type COPY when the maximum allowed number of such servers already existed. |
| Error 1384 | "Unable to stop specified database: %1" |
|---|---|
Constant | UNABLE_TO_STOP_DATABASE |
SAP Sybase Error Number | 2728 |
SQL State | 08WA5 |
SQL Code | -1384L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | Reason the database could not be stopped, if known. |
Probable Cause | The database server was unable to stop the specified database. |
| Error 1385 | "Synchronization failed. Check the dbmlsync log file for more details." |
|---|---|
Constant | MLA_SYNC_FAILED |
SAP Sybase Error Number | 3063 |
SQL State | WW161 |
SQL Code | -1385L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The synchronization was not successful. Check the dbmlsync log file for more details. |
| Error 1386 | "Failed to connect to the dbmlsync server. Check the dbmlsync log file for more details." |
|---|---|
Constant | MLA_SYNC_CONNECT_SERVER_FAIL |
SAP Sybase Error Number | 3064 |
SQL State | WW162 |
SQL Code | -1386L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The MobiLink agent adapter failed to make a connection to the dbmlsync server. Check the dbmlsync log file for more details. |