Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
Error 1691 | "You are not authorized to change the secure feature key named '%2' using %1" |
---|---|
Constant | SFC_NO_AUTH_FOR_KEY |
SAP Sybase Error Number | 3333 |
SQL State | 08S07 |
SQL Code | -1691L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the procedure. |
Parameter 2 | The secure feature key name. |
Probable Cause | The user is not authorized to change the named secure feature key. |
Error 1692 | "Call to %1 failed - the maximum number of secure feature keys has already been created" |
---|---|
Constant | SFC_HIT_MAX_LIMIT |
SAP Sybase Error Number | 3334 |
SQL State | 08S08 |
SQL Code | -1692L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the procedure. |
Probable Cause | The limit on the number of secure feature keys has been reached. |
Error 1693 | "Call to %1 failed - the secure feature key named '%2' already exists" |
---|---|
Constant | SFC_KEY_EXISTS |
SAP Sybase Error Number | 3335 |
SQL State | 08S09 |
SQL Code | -1693L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the procedure. |
Parameter 2 | The secure feature key name. |
Probable Cause | The user attempted to create a secure feature key with the name of a key that already exists. |
Error 1694 | "Call to %1 failed - the secure feature key named '%2' does not exist" |
---|---|
Constant | SFC_NOT_FOUND |
SAP Sybase Error Number | 3336 |
SQL State | 08S10 |
SQL Code | -1694L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the procedure. |
Parameter 2 | The secure feature key name. |
Probable Cause | The user attempted to reference a secure feature key that does not exist. |
Error 1695 | "Call to %1 failed - the authorization key specified for the secure feature key named '%2' is incorrect" |
---|---|
Constant | SFC_NOT_MATCH |
SAP Sybase Error Number | 3337 |
SQL State | 08S11 |
SQL Code | -1695L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the procedure. |
Parameter 2 | The secure feature key name. |
Probable Cause | The provided authorization key did not match the value stored for the specified named key. |
Error 1696 | "Call to %1 failed - the key named '%2' is the last key with the MANAGE_FEATURES and MANAGE_KEYS features" |
---|---|
Constant | SFC_CANNOT_REMOVE_LAST |
SAP Sybase Error Number | 3338 |
SQL State | 08S12 |
SQL Code | -1696L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the procedure. |
Parameter 2 | The secure feature key name. |
Probable Cause | The call attempted to remove the last secure feature key that would enable both MANAGE_FEATURES and MANAGE_KEYS and this is not allowed. |
Error 1697 | "Database upgrade not possible; LD Index in use." |
---|---|
Constant | IQ_LDINDEX_PRESENT |
SAP Sybase Error Number | 3339 |
SQL State | WQ039 |
SQL Code | -1697L |
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 LD indexes have been dropped from the database. |
Error 1698 | "change_password_dual_control is enabled for this user. Use ALTER USER to change password." |
---|---|
Constant | CHANGE_PWD_DUAL_CONTROL_ENABLED |
SAP Sybase Error Number | 3340 |
SQL State | 28W21 |
SQL Code | -1698L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to change a password while the change_password_dual_control option is set for this user. When this option is set, you must use the ALTER USER statement to change the dual password. |
Error 1699 | "Cannot convert database to multiplex. An RLV dbspace exists." |
---|---|
Constant | MPX_CONVERSION_NOT_ALLOWED_WITH_RLV_STORE |
SAP Sybase Error Number | 3341 |
SQL State | WQ040 |
SQL Code | -1699L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A simplex database with RLV dbspace cannot be converted to a multiplex database. |
Error 1700 | "TDS login requests with unencrypted passwords are not permitted" |
---|---|
Constant | UNENCRYPTED_TDS_LOGIN_REQUESTS_NOT_PERMITTED |
SAP Sybase Error Number | 3342 |
SQL State | 28W22 |
SQL Code | -1700L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | You attempted to perform a TDS login without using RSA encryption for the password. The current TDS login setting does not allow unencrypted TDS login requests. Change the tdsl server option setting or connect using an RSA encrypted password. |
Error 1701 | "TDS login requests with RSA encrypted passwords must also use a nonce" |
---|---|
Constant | RSA_ENCRYPTED_TDS_LOGIN_MUST_HAVE_NONCE |
SAP Sybase Error Number | 3343 |
SQL State | 28W23 |
SQL Code | -1701L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | You attempted to perform a TDS login with a client that does not use a nonce with the RSA encrypted password. The current TDS login setting does not allow RSA encrypted TDS login requests without a nonce. Change the tdsl server option setting or connect using a TDS client that supports a nonce with the RSA encrypted password. |
Error 1702 | "Collection types not supported" |
---|---|
Constant | COLLECTION_TYPES_NOT_SUPPORTED |
SAP Sybase Error Number | 3344 |
SQL State | 0AW28 |
SQL Code | -1702L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | The current database is an older database and does not have support for row or array types. To use this feature, upgrade your database to the most recent version. |
Error 1703 | "The user name specified must be the user name of the current connection" |
---|---|
Constant | CREATE_SCHEMA_USER_DOES_NOT_MATCH |
SAP Sybase Error Number | 3345 |
SQL State | 42WD5 |
SQL Code | -1703L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | In the CREATE SCHEMA AUTHORIZATION clause, you specified a user name other than the user name of the current connection. |
Error 1704 | "Remote column %1 has been specified with the wrong case" |
---|---|
Constant | OMNI_RMT_COLUMN_WRONG_CASE |
SAP Sybase Error Number | 3346 |
SQL State | WO035 |
SQL Code | -1704L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The complete name of the remote column. |
Probable Cause | The remote server requires that columns be specified in the correct case. |
Error 1705 | "Illegal RLV Merge Type '%1'" |
---|---|
Constant | RLV_ILLEGAL_MERGE_TYPE |
SAP Sybase Error Number | 3347 |
SQL State | WQ041 |
SQL Code | -1705L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The illegal merge string |
Probable Cause | Legal RLV Merge Types: BLOCKING, NONBLOCKING |
Error 1706 | "The use of foreign keys in a RLV table is not supported" |
---|---|
Constant | RLV_FOREIGNKEY_UNSUPPORTED |
SAP Sybase Error Number | 3348 |
SQL State | WQ043 |
SQL Code | -1706L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to use a foriegn key within a RLV table which is unsupported |
Error 1707 | "The datatype '%1' cannot be used with RLV enabled" |
---|---|
Constant | RLV_UNSUPPORTED_DATATYPE |
SAP Sybase Error Number | 3349 |
SQL State | WQ042 |
SQL Code | -1707L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the unsupported datatype |
Probable Cause | You attempted to use an datatype that is not supported in combination with RLV. |
Error 1708 | "The option '%1' cannot be used with RLV enabled" |
---|---|
Constant | RLV_UNSUPPORTED_OPTION |
SAP Sybase Error Number | 3350 |
SQL State | WQ044 |
SQL Code | -1708L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the unsupported option |
Probable Cause | You attempted to use an option that is not supported in combination with RLV. |
Error 1000000 | "ESCAPES option must be OFF. %1" |
---|---|
Constant | EMSG_INVALIDQUOTESESCAPES |
SAP Sybase Error Number | 20660 |
SQL State | QDA00 |
SQL Code | -1000000L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | Sybase IQ only supports 'LOAD TABLE' commands where the ESCAPES options must be OFF. |
Error 1000002 | "Cannot get the index id for %2 from the catalog. %1" |
---|---|
Constant | EMSG_CAT_CANTGETINDEXID |
SAP Sybase Error Number | 20662 |
SQL State | QDA02 |
SQL Code | -1000002L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | index id |
Probable Cause | This is an internal error. Join processing is not able to find an index in the catalog. If this error occurs, it should be reported to Sybase. |