Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1138 | "The mirror '%1' does not match database '%2'" |
|---|---|
Constant | MIRROR_FILE_MISMATCH |
SAP Sybase Error Number | 2811 |
SQL State | WW090 |
SQL Code | -1138L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the mirror file |
Parameter 2 | The name of the database file |
Probable Cause | The named mirror file does not correspond to the database file. This could happen if the database was not shut down properly, or if the wrong mirror file was specified. The mirror file must be moved or discarded before proceeding, or a different mirror specified. |
| Error 1139 | "The remote data access feature is not supported on this platform" |
|---|---|
Constant | OMNI_FEATURE_NOT_SUPPORTED |
SAP Sybase Error Number | 2812 |
SQL State | 0AW18 |
SQL Code | -1139L |
ODBC 2 State | 37000 |
ODBC 3 State | 42000 |
Severity Code | |
Probable Cause | You attempted to use a remote data access feature; however, remote data access is not supported on this platform. |
| Error 1140 | "Unable to start database \"%1\": CHAR collation or tailoring not supported on this platform" |
|---|---|
Constant | CHAR_COLLATION_NOT_SUPPORTED |
SAP Sybase Error Number | 2813 |
SQL State | WC015 |
SQL Code | -1140L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The database name. |
Probable Cause | The specified CHAR collation is not supported on the current platform. |
| Error 1141 | "Unable to start database \"%1\": NCHAR collation or tailoring not supported on this platform" |
|---|---|
Constant | NCHAR_COLLATION_NOT_SUPPORTED |
SAP Sybase Error Number | 2814 |
SQL State | WC016 |
SQL Code | -1141L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The database name. |
Probable Cause | The specified NCHAR collation is not supported on the current platform. |
| Error 1142 | "Use of statement '%1', which requires feature '%2', is not allowed" |
|---|---|
Constant | SECURE_STATEMENT |
SAP Sybase Error Number | 2815 |
SQL State | 57W04 |
SQL Code | -1142L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the SQL statement. |
Parameter 2 | Name of the feature. |
Probable Cause | You have attempted to use a statement which requires a feature that was disabled by the server administrator when the database server was started. |
| Error 1143 | "Encryption has not been enabled." |
|---|---|
Constant | ENCRYPTION_NOT_ENABLED |
SAP Sybase Error Number | 2816 |
SQL State | 55W27 |
SQL Code | -1143L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You attempted to use encryption without first enabling it. Call ULEnableAesDBEncryption or ULEnableAesFipsDBEncryption to enable encryption. |
| Error 1144 | "'%1' cannot be used as the encoding specification for '%2' data" |
|---|---|
Constant | INVALID_OPENSTRING_ENCODING |
SAP Sybase Error Number | 2818 |
SQL State | WC017 |
SQL Code | -1144L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The encoding that has been specified |
Parameter 2 | The data type for which the encoding has been specified |
Probable Cause | The specified encoding cannot be used for interpreting the given data. For CHAR data, the encoding must be the database's CHAR character encoding and for NCHAR data, it must be the database's NCHAR character encoding. |
| Error 1145 | "Unable to connect: The server did not accept the requested encryption type" |
|---|---|
Constant | ENCRYPTION_TYPE_NOT_ACCEPTED |
SAP Sybase Error Number | 2819 |
SQL State | 08W97 |
SQL Code | -1145L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Probable Cause | The server only accepts certain encryption types, and the connection's encryption type is not one of the accepted types. The -ec server option is used to configure the encryption types that the server accepts. |
| Error 1146 | "LOAD TABLE not allowed on temporary table which has foreign key references from another table" |
|---|---|
Constant | INVALID_LOAD_TABLE_WITH_FOREIGN_KEY |
SAP Sybase Error Number | 2820 |
SQL State | WL009 |
SQL Code | -1146L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The LOAD TABLE statement removes all rows in a temporary table upon failure. If a temporary table being loaded caused an error then the foreign rows would be orphaned. |
| Error 1147 | "Database '%1' cannot be started on this platform. See http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_corruption_warning.html" |
|---|---|
Constant | POSSIBLE_DATABASE_CORRUPTION |
SAP Sybase Error Number | 2821 |
SQL State | 08W98 |
SQL Code | -1147L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The name of the database. |
Probable Cause | It was determined that the database may be corrupt. More information and instructions on how to proceed are available at: http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_corruption_warning.html |
| Error 1148 | "Feature not supported by the client version or the client interface" |
|---|---|
Constant | NOT_SUPPORTED_BY_CLIENT |
SAP Sybase Error Number | 2824 |
SQL State | 0AW19 |
SQL Code | -1148L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | You have attempted to use a feature which the server supports but the client does not. To use the feature, you must upgrade the client library or use a different client interface. Some features are not supported by the jConnect or Open Client client interfaces. |
| Error 1149 | "Database '%1' cannot be started on this platform. See http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_cant_change_platform.html" |
|---|---|
Constant | DATABASE_ENDIAN_FAILURE |
SAP Sybase Error Number | 2825 |
SQL State | 08W99 |
SQL Code | -1149L |
ODBC 2 State | 08001 |
ODBC 3 State | 08001 |
Severity Code | |
Parameter 1 | The name of the database. |
Probable Cause | It was determined that the database cannot be started on the current platform because doing so could possibly cause an endian related database file corruption. It will continue to start without problems on a platform with the opposite endian. More information and instructions on how to proceed are available at: http://ianywhere.com/developer/product_manuals/sqlanywhere/notes/en/endian_cant_change_platform.html |
| Error 1150 | "The SQL scripts DLL cannot be loaded" |
|---|---|
Constant | INVALID_SCRIPT_DLL |
SAP Sybase Error Number | 2826 |
SQL State | WW091 |
SQL Code | -1150L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | The SQL scripts DLL cannot be loaded. The DLL might be missing or the version found might not match the version of the database server being used. |
| Error 1151 | "The logging type ( '%1' ) specified is invalid, not supported or incompatible" |
|---|---|
Constant | INVALID_LOAD_LOGGING_TYPE |
SAP Sybase Error Number | 2827 |
SQL State | WL010 |
SQL Code | -1151L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The specified logging type. |
Probable Cause | The logging type specified for LOAD TABLE is not supported for the version of the database being used, is incompatible with other specifications of the statement or is not supported for the specific table being loaded into. |
| Error 1152 | "Password has expired" |
|---|---|
Constant | PASSWORD_EXPIRED |
SAP Sybase Error Number | 2828 |
SQL State | 08WA0 |
SQL Code | -1152L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | You attempted to connect using a valid user ID, but with an expired password. You can change your password by supplying the NewPassword connection parameter along with the current expired password. |
| Error 1153 | "Password has expired but cannot be changed because the database is read-only" |
|---|---|
Constant | PASSWORD_EXPIRED_READONLY_DB |
SAP Sybase Error Number | 2829 |
SQL State | 08WA1 |
SQL Code | -1153L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Probable Cause | You attempted to connect to a read-only database using a valid user ID, but with an expired password. The password cannot be changed unless the database is started without the -r option on the database server command line. Removing -r will permit modifications to the database. |
| Error 1154 | "Traced query (%1, %2) does not exist" |
|---|---|
Constant | INVALID_TRACED_PLAN |
SAP Sybase Error Number | 2830 |
SQL State | 55W28 |
SQL Code | -1154L |
ODBC 2 State | 28000 |
ODBC 3 State | 28000 |
Severity Code | |
Parameter 1 | The specified logging session ID. |
Parameter 2 | The specified query ID. |
Probable Cause | You attempted to generate a graphical plan for a query saved by diagnostic tracing, identified by a logging_session_id and query ID. However, no such query exists in this database. If it was traced, it was sent to a different database. |
| Error 1155 | "Unable to close the cursor on table \"%1\". LOAD TABLE cannot be executed." |
|---|---|
Constant | CANNOT_LOAD_TEMP_WITH_CURSOR |
SAP Sybase Error Number | 2831 |
SQL State | WL011 |
SQL Code | -1155L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The name of the table. |
Probable Cause | You cannot perform LOAD TABLE on a temporary table that has an open cursor on it. An attempt to close the cursor failed. A failed LOAD TABLE would cause all of the rows in the temporary table to be deleted thereby invalidating the cursor. |
| Error 1156 | "Argument \"%1\" must be a column reference." |
|---|---|
Constant | TEXT_BAD_COLUMN_REFERENCE |
SAP Sybase Error Number | 2832 |
SQL State | WT001 |
SQL Code | -1156L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | The argument number. |
Probable Cause | The CONTAINS argument must be a column reference. |
| Error 1157 | "All column reference arguments must refer to the same table." |
|---|---|
Constant | TEXT_TOO_MANY_TABLE_REFERENCES |
SAP Sybase Error Number | 2833 |
SQL State | WT002 |
SQL Code | -1157L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | All column references in a CONTAINS query must refer to the same table. |