Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| QSA34 | Error | 20055 | -1009034L | "%2: The number of blocks must be > 0; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA35 | Error | 20056 | -1009035L | "%2: The logical or physical block number must be > 0; buffer={%3} page={%4}. %1" | 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). Click here for a list of possible parameters and odbc states. |
| QSA36 | Error | 20057 | -1009036L | "%2: Invalid compression type; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA37 | Error | 20058 | -1009037L | "%2: Buffer was not locked when it should have been; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA38 | Error | 20059 | -1009038L | "%2: Tried to write to a readonly database; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA39 | Error | 20060 | -1009039L | "%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" | 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. Click here for a list of possible parameters and odbc states. |
| QSA40 | Error | 20061 | -1009040L | "%2: Memory & disk block number mismatch; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA41 | Error | 20062 | -1009041L | "%2: Memory & disk block type mismatch; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA42 | Error | 20063 | -1009042L | "%2: Attempted to write a page that was not dirty; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA43 | Error | 20064 | -1009043L | "%2: Memory & disk number of blocks mismatch. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA44 | Error | 20065 | -1009044L | "An IO error was encountered while reading a database page in %2 DBSpace. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA45 | Error | 20066 | -1009045L | "Bitmap failed internal checks. You may have a damaged index. Please check your IQ message file for additional information. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA46 | Error | 20067 | -1009046L | "%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" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA47 | Error | 20068 | -1009047L | "%2: Blockmap info error; bmp={%3}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA48 | Error | 20069 | -1009048L | "%2: Tried to destroy a userlocked buffer; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA49 | Error | 20070 | -1009049L | "%2: The buffer manager is in an inconsistent state; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA50 | Error | 20071 | -1009050L | "%2: Btype specific truncation method returned invalid size for btype. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA51 | Error | 20072 | -1009051L | "An index cannot be created on a char, varchar or varbinary column greater than 255 characters. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QSA52 | Error | 20073 | -1009052L | "Internal error. Index %2 does not yet support the requested operation. %1" | An operation, for example SUM, was forwarded to an index, for example HG, that does not directly implement the operation. Normally, this should not be possible, but can be forced by setting command options. Click here for a list of possible parameters and odbc states. |
| QSA53 | Error | 20074 | -1009053L | "%2: s_dbmvbio WriteCheck failed; buffer={%3} page={%4}. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |