Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1009163 | "Segment %2 cannot be smaller than %3 blocks. %1" |
|---|---|
Constant | EMSG_SDBEXT_SEGMENTTOOSMALL |
SAP Sybase Error Number | 20201 |
SQL State | QSB59 |
SQL Code | -1009163L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Database segment. |
Parameter 3 | Minimum size in blocks |
Probable Cause | Database structures may need to be relocated in order to drop a segment or make it readonly. This space must be available on other segments. |
| Error 1009164 | "You cannot drop the last dbspace. %1" |
|---|---|
Constant | EMSG_DATABASE_LASTDBSPACE |
SAP Sybase Error Number | 20202 |
SQL State | QSB60 |
SQL Code | -1009164L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | You can drop the last dbspace only if it is a temp dbspace |
| Error 1009165 | "Cannot perform requested command as the SYSIQFILE table is locked by another transaction. %1" |
|---|---|
Constant | EMSG_IQSTORE_INREADSYSFILE |
SAP Sybase Error Number | 20203 |
SQL State | QSB61 |
SQL Code | -1009165L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | A CREATE DBSPACE, ALTER DPSACE or DROP DBSPACE command was issued when there was another command or stored procedure accessing the system table SYSIQFILE. |
| Error 1009166 | "%3 %4 is in use by dropped dbspace %2 on a secondary server. The drop dbspace command has not yet propagated through the multiplex. %1" |
|---|---|
Constant | EMSG_SDBEXT_IN_USE_BY_QUERY_SERVER |
SAP Sybase Error Number | 20204 |
SQL State | QSB62 |
SQL Code | -1009166L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | DBSpace name |
Parameter 3 | Description of field in use (i.e. File, Name, File ID) |
Parameter 4 | Value of field in use |
Probable Cause | Fields for dropped dbspaces cannot be re-used until the drop dbspace commands have propagated through the multiplex |
| Error 1009167 | "dbspace %2 failed to open since it's definition conflicts with dbspace %3. Secondary server may need to be synchronized. %1" |
|---|---|
Constant | EMSG_SDBEXT_DBSPACE_BLOCK_RANGE |
SAP Sybase Error Number | 20207 |
SQL State | QSB63 |
SQL Code | -1009167L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of DBSpace that was already open |
Parameter 3 | Name of DBSpace that failed to open |
Probable Cause | The server has an invalid dbspace configuration. New dbspaces may fail to open or the server may fail to start until this is corrected. |
| Error 1009168 | "The WORD SKIP limit (%2) has been exceeded. %1" |
|---|---|
Constant | EMSG_SVIOLATION_WORDSKIP_LIMIT_EXCEEDED |
SAP Sybase Error Number | 20208 |
SQL State | QSB64 |
SQL Code | -1009168L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | The WORD SKIP limit specified in the LOAD TABLE statement. |
Probable Cause | The number of words encountered that are longer than the limit specified when the word index was create has been exceeded for the load. The load will rollback. |
| Error 1009169 | "Cannot write to RO DBSpace %2. %1" |
|---|---|
Constant | EMSG_RODBSPACE_ILLEGAL_ACCESS |
SAP Sybase Error Number | 20222 |
SQL State | QSB65 |
SQL Code | -1009169L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | dbspace name |
Probable Cause | No additional information available.. |
| Error 1009170 | "You have run out of space in %2 DBSpace. %1" |
|---|---|
Constant | EMSG_OUT_OF_DBSPACE |
SAP Sybase Error Number | 20223 |
SQL State | QSB66 |
SQL Code | -1009170L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | name of dbspace |
Probable Cause | No additional information available.. |
| Error 1009171 | "An IO error was encountered while writing a database page in %2 DBSpace. %1" |
|---|---|
Constant | EMSG_BUFMAN_BIO_WRITE_ERROR |
SAP Sybase Error Number | 20224 |
SQL State | QSB67 |
SQL Code | -1009171L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | dbspace name |
Probable Cause | No additional information available.. |
| Error 1009172 | "%2 is in use by another sp_iqemptyfile or ALTER DBSPACE command. %1" |
|---|---|
Constant | EMSG_DBSPACE_FILE_IN_USE_BY_ALTER_OR_EMPTY |
SAP Sybase Error Number | 20226 |
SQL State | QSB68 |
SQL Code | -1009172L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of the FILE or DBSPACE locked. |
Probable Cause | sp_iqemptyfile or ALTER DBSPACE commands disallow status change for the FILE(s) or DBSPACE. No other ALTER DBSPACE or sp_iqemptyfile command can run on those FILE(s) or DBSPACE. |
| Error 1009173 | "Operation not permitted on an OFFLINE DBSpace %2. %1" |
|---|---|
Constant | EMSG_OFFLINE_DBSPACE_ILLEGAL_ACCESS |
SAP Sybase Error Number | 20227 |
SQL State | QSB69 |
SQL Code | -1009173L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | dbspace name |
Probable Cause | No additional information available.. |
| Error 1009174 | "Operation not yet supported. Sort metadata sources have incompatible record descriptors. %1" |
|---|---|
Constant | EMSG_SORT_METADATADESC_MISMATCH |
SAP Sybase Error Number | 20228 |
SQL State | QSB70 |
SQL Code | -1009174L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available.. |
| Error 1009175 | "Database segment '%2' is not valid. Reserve Blocks found in the header: %3 Reserve Blocks expected: %4. This segment cannot be used. %1" |
|---|---|
Constant | EMSG_SDBEXT_BAD_RESERVE |
SAP Sybase Error Number | 20229 |
SQL State | QSB71 |
SQL Code | -1009175L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Location of the exception. |
Parameter 2 | Name of the segment. |
Parameter 3 | Reserve blocks found in the disk header. |
Parameter 4 | Reserve blocks expected. |
Probable Cause | The start block of the disk segment that was found in the disk segment header is not the same as what was expected. The disk segment cannot be used. You will need to restore your database from backup. |
| Error 1009176 | "Create temporary dbspace not allowed. %1" |
|---|---|
Constant | EMSG_DBSPACE_TEMP_NOT_ALLOWED |
SAP Sybase Error Number | 20230 |
SQL State | QSB72 |
SQL Code | -1009176L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | Additional dbspaces may not be created in temp store. Temp space may only be added to IQ_SYSTEM_TEMP. |
| Error 1009177 | "%2 is already %3. %1" |
|---|---|
Constant | EMSG_DBSPACE_ATTRIB_UNCHANGED |
SAP Sybase Error Number | 20231 |
SQL State | QSB73 |
SQL Code | -1009177L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | dbspace name |
Parameter 3 | READONLY, READWRITE, ONLINE, OFFLINE |
Probable Cause | The dbspace being altered already had the requested attributes |
| Error 1009178 | "Operation not allowed on dbspaces that contain multiple files. %1" |
|---|---|
Constant | EMSG_DBSPACE_NOT_FOR_MULTI_DBSPACE |
SAP Sybase Error Number | 20232 |
SQL State | QSB74 |
SQL Code | -1009178L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The specified operation cannot be applied to a file the contains multiple files |
| Error 1009179 | "The last file in a dbspace may only be removed by DROP DBSPACE. %1" |
|---|---|
Constant | EMSG_DBSPACE_CANT_DROP_LAST_FILE |
SAP Sybase Error Number | 20233 |
SQL State | QSB75 |
SQL Code | -1009179L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | A dbspace must contain at least one file. The last file can only be removed by dropping the dbspace that contains it. |
| Error 1009180 | "%2 is not allowed on system dbspace %3. %1" |
|---|---|
Constant | EMSG_DBSPACE_NOT_ALLOWED_SYSTEM |
SAP Sybase Error Number | 20234 |
SQL State | QSB76 |
SQL Code | -1009180L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | disallowed command |
Parameter 3 | dbspace name |
Probable Cause | The requested DDL operation is not allowed on system dbspaces |
| Error 1009181 | "Multiple FILE clauses are not allowed for this command. %1" |
|---|---|
Constant | EMSG_DBSPACE_SINGLE_FILE_CLAUSE |
SAP Sybase Error Number | 20235 |
SQL State | QSB77 |
SQL Code | -1009181L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | Some alter dbspace commands do not allow multiple files to be specified |
| Error 1009182 | "DBFile name %2 is already in use. %1" |
|---|---|
Constant | EMSG_DBSPACE_DBFILE_NAME_IN_USE |
SAP Sybase Error Number | 20236 |
SQL State | QSB78 |
SQL Code | -1009182L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | logical filename |
Probable Cause | logical filenames must be unique for dbfiles |