Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1531 | "Geometry expressions cannot be used in the ORDER BY specification (near '%1')" |
|---|---|
Constant | SLERR_GEOM_ORDER_BY |
SAP Sybase Error Number | 3186 |
SQL State | 2FW92 |
SQL Code | -1531L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The geometry expression. |
Probable Cause | Geometry expressions cannot be used in the ORDER BY clause. The ST_LinearHash() method may be used in the ORDER BY specification to order geometry values using the same rules used for spatial indexes, or a conversion method such as ST_AsText() may be used to order the rows by their string representation. |
| Error 1532 | "Failed to transform point %1 (error %2)" |
|---|---|
Constant | SLERR_TRANSFORM_POINT_FAIL |
SAP Sybase Error Number | 3187 |
SQL State | 2FF17 |
SQL Code | -1532L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The point that could not be transformed. |
Parameter 2 | The error code from the projection library. |
Probable Cause | An error occurred when performing a transform from one spatial reference system to another. This error may occur if a point in the first geometry is outside of the bounds for the transform definition. The error may also be reported for particular transform definitions. The integer error code from the transform library may be used to diagnose the transform definition. |
| Error 1533 | "Logical server policy \"%1\" not found" |
|---|---|
Constant | LS_POLICY_NOT_FOUND |
SAP Sybase Error Number | 2445 |
SQL State | WQ008 |
SQL Code | -1533L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the logical server policy. |
Probable Cause | The named logical server policy was not found in the database. |
| Error 1534 | "Logical server operations not allowed on a simplex database." |
|---|---|
Constant | LS_OPS_DISALLOWED_ON_SIMPLEX |
SAP Sybase Error Number | 2443 |
SQL State | WQ009 |
SQL Code | -1534L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Logical server operations are disallowed on a simplex database. |
| Error 1535 | "System Privileges and Roles feature is not supported in this database" |
|---|---|
Constant | ROLES_NOT_SUPPORTED |
SAP Sybase Error Number | 3188 |
SQL State | 0AW27 |
SQL Code | -1535L |
ODBC 2 State | 42000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | The current database is an older database and does not have catalog support for System Privileges and Roles feature. To use this feature, upgrade your database to the most recent version. |
| Error 1536 | "Invalid user ID or role name '%1' specified" |
|---|---|
Constant | INVALID_USER_ROLE_NAME |
SAP Sybase Error Number | 3189 |
SQL State | 28000 |
SQL Code | -1536L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the invalid user or role that was specified. |
Probable Cause | You supplied an invalid name for a user or role. |
| Error 1537 | "Role \"%1\" already exists" |
|---|---|
Constant | ROLE_ALREADY_EXISTS |
SAP Sybase Error Number | 3190 |
SQL State | 28000 |
SQL Code | -1537L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the role. |
Probable Cause | An attempt was made to create a role that already exists in the database. |
| Error 1538 | "User or Role ID '%1' does not exist" |
|---|---|
Constant | UNKNOWN_USER_ROLE_ID |
SAP Sybase Error Number | 3191 |
SQL State | 28000 |
SQL Code | -1538L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the user or role that could not be found. |
Probable Cause | You used a user or role ID that does not exist. |
| Error 1539 | "Use of WITH NO SYSTEM PRIVILEGE INHERITANCE OPTION is not allowed with %1" |
|---|---|
Constant | INVALID_ROLE_GRANT_OPTION |
SAP Sybase Error Number | 3192 |
SQL State | 28000 |
SQL Code | -1539L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the role. |
Probable Cause | WITH NO SYSTEM PRIVILEGE INHERITANCE OPTION can be specified only with user defined roles corresponding to legacy non-inheritable authorities. |
| Error 1540 | "Operation would cause a role cycle" |
|---|---|
Constant | ROLE_CYCLE |
SAP Sybase Error Number | 3193 |
SQL State | 28000 |
SQL Code | -1540L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to grant role to a grantee that would result in a grantee belonging to itself. Role membership may be direct or indirect. |
| Error 1541 | "Specified System Privilege '%1' is Invalid" |
|---|---|
Constant | INVALID_SYSTEM_PRIVILEGE |
SAP Sybase Error Number | 3194 |
SQL State | 28000 |
SQL Code | -1541L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the system privilege. |
Probable Cause | System Privilege specified does not exist in the database. |
| Error 1542 | "Invalid logical server combination for ADD or SET clause." |
|---|---|
Constant | LS_INVALID_COMBINATION_FOR_ADD_SET |
SAP Sybase Error Number | 2442 |
SQL State | WQ010 |
SQL Code | -1542L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The specified logical server combination for ADD or SET clause of ALTER LOGIN POLICY is invalid. SERVER and NONE cannot be specified with ADD clause. SERVER and NONE cannot be specified with any other logical server. |
| Error 1543 | "Logical server configuration of the user's login policy does not allow access to the current multiplex server." |
|---|---|
Constant | CONNECTION_DISALLOWED_BY_LOGIN_POLICY_LS_CONFIG |
SAP Sybase Error Number | 2428 |
SQL State | WQ011 |
SQL Code | -1543L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Logical server configuration of the user's login policy does not allow access to the current multiplex server. You may need to change logical server configuration of user's login policy to allow access to the current multiplex server. |
| Error 1544 | "Login disallowed. User does not have sufficient authority to access SERVER logical server." |
|---|---|
Constant | CONNECTION_DISALLOWED_TO_SERVER_LS |
SAP Sybase Error Number | 2423 |
SQL State | WQ012 |
SQL Code | -1544L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | Accessing SERVER logical server requires either DBA or MULTIPLEX ADMIN authority. |
| Error 1545 | "Cannot create logical server named '%1'. Choose another name for logical server." |
|---|---|
Constant | INVALID_LS_NAME |
SAP Sybase Error Number | 2422 |
SQL State | WQ013 |
SQL Code | -1545L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of logical server. |
Probable Cause | Logical server names ALL, NONE, SERVER, OPEN, DEFAULT and COORDINATOR are reserved for the current or future releases. |
| Error 1546 | "Cannot drop Multiplex server '%1' as it is part of a Logical Server. Use the \"WITH DROP MEMBERSHIP\" clause." |
|---|---|
Constant | IQ_MPX_SRV_IS_LS_MEMBER |
SAP Sybase Error Number | 2387 |
SQL State | WQ014 |
SQL Code | -1546L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of multiplex server. |
Probable Cause | If an MPX server is part of a Logical Server then the DROP MPX command should have WITH MEMBERSHIP clause to drop it. |
| Error 1547 | "Cannot drop Multiplex server '%1' without dropping all the logical servers as it will convert the Multiplex to Simplex. Use the \"WITH DROP LOGICAL SERVER\" clause." |
|---|---|
Constant | IQ_MPX_SRV_IS_LAST_SEC_MEMBER |
SAP Sybase Error Number | 2371 |
SQL State | WQ015 |
SQL Code | -1547L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of multiplex server. |
Probable Cause | If dropping the secondary server will result in conversion from MPX to SPX then all the user created logical servers should be dropped. |
| Error 1548 | "Cannot drop Multiplex server '%1'. This is not the last secondary server. Remove the \"WITH DROP LOGICAL SERVER\" clause." |
|---|---|
Constant | IQ_MPX_SRV_IS_NOT_LAST_SEC_MEMBER |
SAP Sybase Error Number | 2370 |
SQL State | WQ016 |
SQL Code | -1548L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of multiplex server. |
Probable Cause | WITH DROP LOGICAL SERVER clause should be used ONLY when dropping the last secondary Server. |
| Error 1549 | "Cannot set the '%1' option as Login Policy option '%2' is set to off." |
|---|---|
Constant | LS_LP_MODIFY_OPT_NOT_ALLOWED |
SAP Sybase Error Number | 2369 |
SQL State | WQ017 |
SQL Code | -1549L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the temporary option |
Parameter 2 | The name of the Login Policy Option. |
Probable Cause | If an option of the login policy is set to off then user cannot set the temporary option which is directly depending on it. For example, if the login policy option DQP_ENABLED is set to Off, then the temporary option DQP_ENABLED cannot be set to On. |
| Error 1550 | "Overriding ROOT login policy options for logical servers is not allowed." |
|---|---|
Constant | LS_ROOT_LP_OVERRIDE_NOT_ALLOWED |
SAP Sybase Error Number | 2368 |
SQL State | WQ018 |
SQL Code | -1550L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | A user cannot override login policy options of ROOT login policy for logical servers. |