Messages 20042 through 20061

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

Number Msg Type SQL State SQL Code Message Possible Cause
20042 Error QSA21 -1009021L "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.

20043 Error QSA22 -1009022L "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.

20044 Error QSA23 -1009023L "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.

20045 Error QSA24 -1009024L "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.

20046 Error QSA25 -1009025L "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.

20047 Error QSA26 -1009026L "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.

20048 Error QSA27 -1009027L "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.

20049 Error QSA28 -1009028L "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.

20050 Error QSA29 -1009029L "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.

20051 Error QSA30 -1009030L "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.

20052 Error QSA31 -1009031L "%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.

20053 Error QSA32 -1009032L "%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.

20054 Error QSA33 -1009033L "%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.

20055 Error QSA34 -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.

20056 Error QSA35 -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.

20057 Error QSA36 -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.

20058 Error QSA37 -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.

20059 Error QSA38 -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.

20060 Error QSA39 -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.

20061 Error QSA40 -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.


Created November 10, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com