Messages 1009021 through 1009040

Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL Code Msg Type Number SQL State Message Possible Cause
-1009021L Error 20042 QSA21 "This server must first be started in Multiplex single-node mode (-iqmpx_sn 1) %1" The tlv log has an incorrect format

Click here for a list of possible parameters and odbc states.

-1009022L Error 20043 QSA22 "Cannot create a WD index on a column narrower than 3 bytes. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009023L Error 20044 QSA23 "Cannot create a WD index on a column wider than 32767 bytes. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009024L Error 20045 QSA24 "Cannot create a WD index with a max permitted word size less than 1 byte. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009025L Error 20046 QSA25 "Cannot create a WD index with a max permitted word size greater than 255 bytes. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009026L Error 20047 QSA26 "Cannot create a WD index with a separator string this long. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009027L Error 20048 QSA27 "Cannot create a WD index with a separator string containing a character fragment. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009028L Error 20049 QSA28 "Cannot create a WD index with more than 256 separators. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009029L Error 20050 QSA29 "Words exceeding the maximum permitted word length not supported. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009030L Error 20051 QSA30 "Cannot create a WD index with the database IQ pagesize less than 4KB. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009031L Error 20052 QSA31 "%2: All buffer cache pages are in use, ask your DBA to increase the size of the buffer cache. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009032L Error 20053 QSA32 "%2: Bio ptr must be non-null; buffer={%3} page={%4}. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009033L Error 20054 QSA33 "%2: Blocksize must be a multiple of sizeof(hos_mrdtype & hos_uint) and > 0; buffer={%3} page={%4}. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009034L Error 20055 QSA34 "%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.

-1009035L Error 20056 QSA35 "%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.

-1009036L Error 20057 QSA36 "%2: Invalid compression type; buffer={%3} page={%4}. %1" No additional information available.

Click here for a list of possible parameters and odbc states.

-1009037L Error 20058 QSA37 "%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.

-1009038L Error 20059 QSA38 "%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.

-1009039L Error 20060 QSA39 "%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.

-1009040L Error 20061 QSA40 "%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.


Created June 15, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com