Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1009024 | "Cannot create a WD index with a max permitted word size less than 1 byte. %1" |
|---|---|
Constant | EMSG_ERROR_WD_NOTALLOWED_WL2SMALL |
SAP Sybase Error Number | 20045 |
SQL State | QSA24 |
SQL Code | -1009024L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
| Error 1009025 | "Cannot create a WD index with a max permitted word size greater than 255 bytes. %1" |
|---|---|
Constant | EMSG_ERROR_WD_NOTALLOWED_WL2LARGE |
SAP Sybase Error Number | 20046 |
SQL State | QSA25 |
SQL Code | -1009025L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
| Error 1009026 | "Cannot create a WD index with a separator string this long. %1" |
|---|---|
Constant | EMSG_ERROR_WD_NOTALLOWED_SS2LARGE |
SAP Sybase Error Number | 20047 |
SQL State | QSA26 |
SQL Code | -1009026L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
| Error 1009027 | "Cannot create a WD index with a separator string containing a character fragment. %1" |
|---|---|
Constant | EMSG_ERROR_WD_NOTALLOWED_SSFRAG |
SAP Sybase Error Number | 20048 |
SQL State | QSA27 |
SQL Code | -1009027L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
| Error 1009028 | "Cannot create a WD index with more than 256 separators. %1" |
|---|---|
Constant | EMSG_ERROR_WD_NOTALLOWED_NS2LARGE |
SAP Sybase Error Number | 20049 |
SQL State | QSA28 |
SQL Code | -1009028L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
| Error 1009029 | "Words exceeding the maximum permitted word length not supported. %1" |
|---|---|
Constant | EMSG_ERROR_WD_TRUNCWORD_NOT_SUPPORTED |
SAP Sybase Error Number | 20050 |
SQL State | QSA29 |
SQL Code | -1009029L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
| Error 1009030 | "Cannot create a WD index with the database IQ pagesize less than 4KB. %1" |
|---|---|
Constant | EMSG_ERROR_WD_NOTALLOWED_PS2SMALL |
SAP Sybase Error Number | 20051 |
SQL State | QSA30 |
SQL Code | -1009030L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | No additional information available. |
| Error 1009031 | "%2: All buffer cache pages are in use, ask your DBA to increase the size of the buffer cache. %1" |
|---|---|
Constant | EMSG_BUFMAN_ALLSLOTSLOCKED |
SAP Sybase Error Number | 20052 |
SQL State | QSA31 |
SQL Code | -1009031L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Probable Cause | No additional information available. |
| Error 1009032 | "%2: Bio ptr must be non-null; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_BADBIOP |
SAP Sybase Error Number | 20053 |
SQL State | QSA32 |
SQL Code | -1009032L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009033 | "%2: Blocksize must be a multiple of sizeof(hos_mrdtype & hos_uint) and > 0; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_BADBLOCKSIZE |
SAP Sybase Error Number | 20054 |
SQL State | QSA33 |
SQL Code | -1009033L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009034 | "%2: The number of blocks must be > 0; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_BADNUMOFBLKS |
SAP Sybase Error Number | 20055 |
SQL State | QSA34 |
SQL Code | -1009034L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009035 | "%2: The logical or physical block number must be > 0; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_BADBLOCKNUMBER |
SAP Sybase Error Number | 20056 |
SQL State | QSA35 |
SQL Code | -1009035L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | Typically, production builds will abort here if trying to Find() a page that does not exist (non-existent pages have a 0 pbn in the blockmap entry). |
| Error 1009036 | "%2: Invalid compression type; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_BADCTYPE |
SAP Sybase Error Number | 20057 |
SQL State | QSA36 |
SQL Code | -1009036L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009037 | "%2: Buffer was not locked when it should have been; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_MUSTBEACTIVEBUF |
SAP Sybase Error Number | 20058 |
SQL State | QSA37 |
SQL Code | -1009037L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009038 | "%2: Tried to write to a readonly database; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_MUSTHAVERWACCESS |
SAP Sybase Error Number | 20059 |
SQL State | QSA38 |
SQL Code | -1009038L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009039 | "%2: An error was detected on a database page. You may have a damaged index. For additional information, please check your IQ message file or run sp_iqcheckdb. %1" |
|---|---|
Constant | EMSG_BUFMAN_INCORRECT_DISKBLOCKHEADER |
SAP Sybase Error Number | 20060 |
SQL State | QSA39 |
SQL Code | -1009039L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Probable Cause | When we read a page from the database, we detected that its header was either corrupt or that the header did not correspond to the page we thought we were reading. This is normally a fatal error; the database itself is likely to be corrupt. |
| Error 1009040 | "%2: Memory & disk block number mismatch; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_BIO_MISMATCH_BLOCK |
SAP Sybase Error Number | 20061 |
SQL State | QSA40 |
SQL Code | -1009040L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009041 | "%2: Memory & disk block type mismatch; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_BIO_MISMATCH_BTYPE |
SAP Sybase Error Number | 20062 |
SQL State | QSA41 |
SQL Code | -1009041L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009042 | "%2: Attempted to write a page that was not dirty; buffer={%3} page={%4}. %1" |
|---|---|
Constant | EMSG_BUFMAN_BIO_NOTDIRTY |
SAP Sybase Error Number | 20063 |
SQL State | QSA42 |
SQL Code | -1009042L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Parameter 3 | 3) Information about the sbuf involved, if any. |
Parameter 4 | 4) Information about the disk block header involved, if any. |
Probable Cause | No additional information available. |
| Error 1009043 | "%2: Memory & disk number of blocks mismatch. %1" |
|---|---|
Constant | EMSG_BUFMAN_BIO_MISMATCH_NBLKS |
SAP Sybase Error Number | 20064 |
SQL State | QSA43 |
SQL Code | -1009043L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | 1) location of the exception |
Parameter 2 | 2) The particular buffer cache throwing the exception. |
Probable Cause | No additional information available. |