Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1571 | "The attempt to drop LDAP server \"%1\" failed, suspend the server to drop it." |
|---|---|
Constant | INVALID_STATE_CHANGE |
SAP Sybase Error Number | 3214 |
SQL State | WW204 |
SQL Code | -1571L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the LDAP Server. |
Probable Cause | An attempt to drop an LDAP Server failed because it was in the READY or ACTIVE state. Use WITH SUSPEND to change state before dropping server. |
| Error 1572 | "LDAP User Authentication feature is not supported in this database" |
|---|---|
Constant | LDAPUA_NOT_SUPPORTED |
SAP Sybase Error Number | 3215 |
SQL State | WW205 |
SQL Code | -1572L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database is an older database and does not have catalog support for LDAP User Authentication feature. To use this feature, upgrade your database to the most recent version. |
| Error 1573 | "Mirror server class is not supported for IQ databases" |
|---|---|
Constant | OMNI_NO_MIRROR_FOR_IQ |
SAP Sybase Error Number | 3216 |
SQL State | WO029 |
SQL Code | -1573L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to create a remote data access server of type mirror while connected to an IQ database. The Mirror server class is not supported for IQ databases. |
| Error 1574 | "You must upgrade your database in order to use the mirror server class" |
|---|---|
Constant | OMNI_MIRROR_NEEDS_UPGRADE |
SAP Sybase Error Number | 3217 |
SQL State | WO030 |
SQL Code | -1574L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to create a remote data access server of type mirror while connected to a database that was created with older software. You must upgrade your database in order to make use of the mirror server class. |
| Error 1575 | "Database upgrade not possible; the name or ID of new IQ_SHARED_TEMP dbspace is already in use." |
|---|---|
Constant | IQ_SHTEMP_DBSPACE_CONFLICT |
SAP Sybase Error Number | 2364 |
SQL State | WQ020 |
SQL Code | -1575L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | An attempt to upgrade a database failed. Retry upgrade of the database when no existing dbspace is using the name or ID of the IQ_SHARED_TEMP dbspace. |
| Error 1576 | "LDAP server \"%1\" is in use by login policy \"%2\"." |
|---|---|
Constant | LDAPSERVER_IN_USE |
SAP Sybase Error Number | 3218 |
SQL State | WW206 |
SQL Code | -1576L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the LDAP server. |
Parameter 2 | The name of the login policy. |
Probable Cause | The named login policy references the LDAP server. The login policy must be changed to avoid referencing the LDAP server before the LDAP server can be dropped. Or use DROP LDAP SERVER <server name> WITH DROP ALL REFERENCES to remove any references in login policies to the LDAP server. |
| Error 1577 | "Invalid error raised by user-defined function: (%1) %2." |
|---|---|
Constant | EMSG_UDF_RAISED_INVALID_ERROR |
SAP Sybase Error Number | 3219 |
SQL State | QFA67 |
SQL Code | -1577L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Invalid error code used by UDF. |
Parameter 2 | Error message provided by UDF to accompany UDF SQLCODE. |
Probable Cause | An error was raised by a user-defined function that is outside reserved range. |
| Error 1578 | "Table parameterized functions are not allowed across server types." |
|---|---|
Constant | TPF_NOT_ALLOWED_ACROSS_SERVERS |
SAP Sybase Error Number | 3220 |
SQL State | WO009 |
SQL Code | -1578L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Table parameterized functions are not allowed across server types if a query is not processed in full-passthrough mode. |
| Error 1579 | "External procedures or functions are not allowed across server types." |
|---|---|
Constant | PROC_NOT_ALLOWED_ACROSS_SERVERS |
SAP Sybase Error Number | 3221 |
SQL State | WO031 |
SQL Code | -1579L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | External procedure or function calls are not allowed across server types if the query is not processed in full-passthrough mode. |
| Error 1580 | "Failed to load the MobiLink client support libraries." |
|---|---|
Constant | COULD_NOT_LOAD_SYNC_LIBRARY |
SAP Sybase Error Number | 3222 |
SQL State | WW207 |
SQL Code | -1580L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | To use the SYNCHRONIZE command, a MobiLink client must be installed on the same computer where the database server is running. |
| Error 1581 | "Database name must be specified when connecting to a cloud database server" |
|---|---|
Constant | NO_DEFAULT_DATABASE |
SAP Sybase Error Number | 3223 |
SQL State | 08WA7 |
SQL Code | -1581L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | When connecting to a cloud database server, a database name must be specified by the connection string. Cloud database servers do not have a default database. |
| Error 1582 | "Server name can only be specified when connecting to a cloud database server with NODETYPE=DIRECT" |
|---|---|
Constant | SERVER_NAME_NOT_ALLOWED |
SAP Sybase Error Number | 3224 |
SQL State | 08WA8 |
SQL Code | -1582L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | When connecting to a cloud database server, specifying a server name on the connection string is only allowed for NODETYPE=DIRECT. When using other NODETYPE values to connect to a cloud database server, specifying the server name is not allowed. Typically, for connections to a cloud database server the HOST connection parameter or HOST protocol option is used to specify the address of one or more cloud database servers. |
| Error 1583 | "Cannot upgrade the database. The database can be upgraded only after starting the coordinator in single node mode." |
|---|---|
Constant | IQ_MPX_MUST_BE_SINGLE_NODE |
SAP Sybase Error Number | 3225 |
SQL State | WQ021 |
SQL Code | -1583L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | In order to run ALTER DATABASE UPGRADE on the database, the coordinator must be started in single node mode using the '-iqmpx_sn 1' server startup option. |
| Error 1584 | "Unable to load the dbrsakp shared object" |
|---|---|
Constant | RSA_LOAD_FAILED |
SAP Sybase Error Number | 3226 |
SQL State | 08WA9 |
SQL Code | -1584L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The server was unable to load the dbrsakp DLL on Windows platforms or the libdbrsakp shared object on Unix platforms. |
| Error 1585 | "Invalid tool name or admin user for generating security token" |
|---|---|
Constant | INVALID_TOOL_NAME_OR_ADMIN_USER |
SAP Sybase Error Number | 3227 |
SQL State | 08WB1 |
SQL Code | -1585L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The tool name or admin user supplied is invalid for generating a security token. |
| Error 1586 | "Error modifying refresh type for text index \"%1\" on materialized view \"%2\No message |
|---|---|
Constant | TEXT_INDEX_MV_ALTER_ERROR |
SAP Sybase Error Number | 3228 |
SQL State | WT039 |
SQL Code | -1586L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the text index. |
Parameter 2 | The name of the materialized view. |
Probable Cause | Internal error encountered while changing the refresh type of the text index dependent on the materialized view. |
| Error 1587 | "Storing certificates is not supported for this database" |
|---|---|
Constant | CERTIFICATES_NOT_SUPPORTED |
SAP Sybase Error Number | 3229 |
SQL State | 55W42 |
SQL Code | -1587L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database does not have catalog support for certificates. To use this feature, upgrade your database to the most recent version. |
| Error 1588 | "The specified certificate is not valid" |
|---|---|
Constant | INVALID_CERTIFICATE |
SAP Sybase Error Number | 3230 |
SQL State | 55W43 |
SQL Code | -1588L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The certificate value does not represent a valid certificate. |
| Error 1589 | "Certificate '%1' not found" |
|---|---|
Constant | CERTIFICATE_NOT_FOUND |
SAP Sybase Error Number | 3231 |
SQL State | 55W44 |
SQL Code | -1589L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the certificate that could not be found |
Probable Cause | You misspelled the name of a certificate, or the certificate does not exist. |
| Error 1590 | "You cannot use a security token when making remote connections" |
|---|---|
Constant | INVALID_USE_OF_SECURITY_TOKEN |
SAP Sybase Error Number | 3232 |
SQL State | WO032 |
SQL Code | -1590L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A security token cannot be used to make remote data access connections |