Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1591 | "Invalid use of BEFORE operator in text query." |
|---|---|
Constant | TEXT_INVALID_BEFORE |
SAP Sybase Error Number | 3233 |
SQL State | WT040 |
SQL Code | -1591L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Only terms and prefixes are allowed as arguments to a BEFORE operator. |
| Error 1592 | "Text indexes on materialized views are not supported for this database." |
|---|---|
Constant | TEXT_MV_UPGRADE_REQUIRED |
SAP Sybase Error Number | 3234 |
SQL State | WT041 |
SQL Code | -1592L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database does not have catalog support for text indexes on materialized views. To use this feature, upgrade your database to the most recent version. |
| Error 1593 | "Unable to copy file %1 to destination %2" |
|---|---|
Constant | UNABLE_TO_COPY_DB_FILE_INTO_CLOUD |
SAP Sybase Error Number | 3235 |
SQL State | 08WB2 |
SQL Code | -1593L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The file name of the file on the client computer |
Parameter 2 | The file name of the destination within the cloud |
Probable Cause | The client database file could not be copied to the requested cloud destination. |
| Error 1594 | "LDAP server definition of \"%1\" is incomplete. A search URL, access distinguished name, password, and authentication URL are required." |
|---|---|
Constant | LDAPSERVER_INCOMPLETE_DEF |
SAP Sybase Error Number | 3236 |
SQL State | WW208 |
SQL Code | -1594L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the LDAP server. |
Probable Cause | The named LDAP server is missing one or more of the values required to search for a user's distinguished name or authenticate a user. Use ALTER LDAP SERVER <server name> to specify any missing values. |
| Error 1595 | "Column '%1' not found in variable '%2'" |
|---|---|
Constant | COLUMN_NOT_FOUND_IN_VARIABLE |
SAP Sybase Error Number | 3237 |
SQL State | 52006 |
SQL Code | -1595L |
ODBC 2 State | S0002 |
ODBC 3 State | 42S22 |
Severity Code | |
Parameter 1 | Name of the column that could not be found. |
Parameter 2 | Name of the row variable that was supposed to contain the column. |
Probable Cause | You misspelled the name of a column or variable, or the variable has a different schema than you expect. |
| Error 1596 | "Database contains users with 'SYS_' prefix and '_ROLE' suffix." |
|---|---|
Constant | INVALID_USER_NAME |
SAP Sybase Error Number | 3238 |
SQL State | 08WB3 |
SQL Code | -1596L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The database to be upgraded contains users with 'SYS_' prefix and '_ROLE' suffix. Drop or migrate these users before upgrading the database. |
| Error 1597 | "The transaction may not be committed because the primary server lost quorum" |
|---|---|
Constant | LOST_QUORUM_ON_COMMIT |
SAP Sybase Error Number | 2363 |
SQL State | WW166 |
SQL Code | -1597L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to commit a transaction on a primary server that just lost quorum with the partner and arbiter servers. The transaction may or may not have been committed. The partner servers will attempt to determine which server will become the new primary server. |
| Error 1598 | "Array element error: array index '%1' is out of range" |
|---|---|
Constant | INVALID_ARRAY_INDEX |
SAP Sybase Error Number | 3239 |
SQL State | 2202E |
SQL Code | -1598L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Value of the array index expression |
Probable Cause | You tried to access an array element with an index outside the declared size of the array. For an array of size N, valid array elements are numbered 1 through N. |
| Error 1599 | "Invalid use of collection type" |
|---|---|
Constant | INVALID_USE_OF_COLLECTION |
SAP Sybase Error Number | 3240 |
SQL State | WW210 |
SQL Code | -1599L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You tried to use an ARRAY or ROW type in an unsupported context. You cannot store these values in tables or read them directly from client interfaces such as ODBC, ESQL, and JDBC. You must extract the individual values you are interested in. |
| Error 1600 | "The bind to URL '%1' failed. The most recently reported LDAP API error is: '%2'" |
|---|---|
Constant | LDAPUA_BINDFAIL |
SAP Sybase Error Number | 3241 |
SQL State | WW211 |
SQL Code | -1600L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The LDAP URL used with bind(). |
Parameter 2 | The LDAP API error message. |
Probable Cause | The message is reported from the LDAP API client with context from the LDAP User Authentication methods. An LDAP administrator or Sybase Tech Support may use these low level messages to direct the DBA how to resolve a problem. |
| Error 1601 | "Password encryption failed. Error message '%1'." |
|---|---|
Constant | PWD_CIPHER_ERROR |
SAP Sybase Error Number | 3242 |
SQL State | WW212 |
SQL Code | -1601L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | The error message reported by block encrypter. |
Probable Cause | Run-time block encrypter initialization failed. |
| Error 1602 | "The specified distinguished name '%1' does not match the search result '%2'." |
|---|---|
Constant | LDAPUA_DN_NOMAT |
SAP Sybase Error Number | 3243 |
SQL State | WW213 |
SQL Code | -1602L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The expected distinguished name that was specified in command. |
Parameter 2 | The result distinguished name returned by LDAP search. |
Probable Cause | VALIDATE LDAP SERVER command did a successful search to find a user distinguished name, but the value differs from the expected distinguished name specified in the command. |
| Error 1603 | "The search using '%1' failed due to one or more invalid values set." |
|---|---|
Constant | LDAPUA_SEARCHFAIL |
SAP Sybase Error Number | 3244 |
SQL State | WW214 |
SQL Code | -1603L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The LDAP server name or search URL specifying the search. |
Probable Cause | An LDAPUA search or validate failed returning LDAP_INVALID_CREDENTIALS, LDAP_INSUFFICIENT_ACCESS, LDAP_INVALID_DN_SYNTAX, LDAP_NO_SUCH_OBJECT, or LDAP_FILTER_ERROR due to the invalid settings. Check the access account values for the named LDAP server or search URL. |
| Error 1604 | "Cannot use logical server policy clause more than once" |
|---|---|
Constant | LS_POLICY_USED_TWICE |
SAP Sybase Error Number | 3245 |
SQL State | WQ022 |
SQL Code | -1604L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | ls policy clause appeared more than once in a create/alter logical server policy statement |
| Error 1605 | "Table Parameterized Functions and V4 TableUDFs are not supported for this database." |
|---|---|
Constant | TPF_UPGRADE_REQUIRED |
SAP Sybase Error Number | 3246 |
SQL State | WP020 |
SQL Code | -1605L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The current database does not have catalog support for table parameterized functions. To use this feature, upgrade your database to the most recent version. |
| Error 1606 | "Multiple table parameters are not supported." |
|---|---|
Constant | ONLY_SINGLE_TABLE_PARM_SUPPORTED |
SAP Sybase Error Number | 3247 |
SQL State | WP021 |
SQL Code | -1606L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Table parameterized functions are limited to only having at most a single table parameter. |
| Error 1607 | "Outer references are not allowed for TPF input tables." |
|---|---|
Constant | TPF_OUTER_REFERENCES_NOT_ALLOWED |
SAP Sybase Error Number | 3249 |
SQL State | WP022 |
SQL Code | -1607L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Outer references in the select list for a TPF input table are not allowed. |
| Error 1608 | "Unable to delete file %1" |
|---|---|
Constant | UNABLE_TO_DELETE_FILE |
SAP Sybase Error Number | 3250 |
SQL State | 08WB4 |
SQL Code | -1608L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The file name of the file to be deleted |
Probable Cause | The request to delete a file failed |
| Error 1609 | "File %1 already exists" |
|---|---|
Constant | FILE_ALREADY_EXISTS |
SAP Sybase Error Number | 3251 |
SQL State | 08WB5 |
SQL Code | -1609L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The file name of the file that already exists |
Probable Cause | The request to create a file or directory failed because the file or directory already exists |
| Error 1610 | "Unable to create directory %1" |
|---|---|
Constant | UNABLE_TO_CREATE_DIRECTORY |
SAP Sybase Error Number | 3252 |
SQL State | 08WB6 |
SQL Code | -1610L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The file name of the directory that could not be created |
Probable Cause | The request to create a directory failed |