Messages 1009097 through 1009116

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
-1009097L Error 20118 QSA97 "Cumulative total (%2) for all integrity constraint violations exceeded. %1" The total number of NULL, UNIQUE, DATA VALUE, and FOREIGN KEY integrity constraint violations has exceeded the user specified limit.

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

-1009098L Error 20119 QSA98 "Invalid MESSAGE LOG or ROW LOG filename. %1" A bad filename (perhaps zero-length) was specified for either the MESSAGE LOG or ROW LOG files on the LOAD statement.

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

-1009099L Error 20120 QSA99 "%1" No additional information available.

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

-1009100L Error 20121 QSB00 "Database segment '%2' is not valid. It is of type '%3'. Type BTYPE_DBEXT was expected. This segment cannot be used. %1" The segment type written to the segment header was found not to be of the expected type. You will need to restore your database from backup.

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

-1009101L Error 20122 QSB01 "Database segment '%2' is not valid. PhysicalNBlocks Found: %3 PhysicalNBlocks Expected: 1. This segment cannot be used. %1" The number of physical blocks read from the segment header is incorrect. You will need to restore your database from backup.

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

-1009102L Error 20123 QSB02 "Incorrect HG Index Version (%2): Index must be dropped by previous version of Sybase IQ and recreated. %1" No additional information available.

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

-1009103L Error 20124 QSB03 "Number of unique values exceeded for index. %2 %3 %1" No additional information available.

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

-1009104L Error 20125 QSB04 "Bad args, both values must be >= 1 (%2 %3). %1" No additional information available.

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

-1009105L Error 20126 QSB05 "Could not find block: %2. %1" No additional information available.

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

-1009106L Error 20127 QSB06 "DBFILE '%2' is not valid. The catalog file id is incorrect. FileID found: %3 FileID expected: %4. This segment cannot be used. %1" The FileID information stored on the disk segment's header is not correct. The disk segment cannot be used.

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

-1009107L Error 20128 QSB07 "Duplicate entry for block: %2, record %3. %1" No additional information available.

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

-1009108L Error 20129 QSB08 "Database segment '%2' is not valid. Startblock found in the header: %3 Startblock expected: %4. This segment cannot be used. %1" 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.

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

-1009109L Error 20130 QSB09 "Key size %2 is more than the maximum %3. %1" No additional information available.

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

-1009110L Error 20131 QSB10 "%1" No additional information available.

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

-1009111L Error 20132 QSB11 "Could not find record %2 within block %3. %1" No additional information available.

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

-1009112L Error 20133 QSB12 "%1" No additional information available.

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

-1009113L Error 20134 QSB13 "Secondary error noted" No additional information available.

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

-1009114L Error 20135 QSB14 "Tried to put too many records %2 into block %3. %1" No additional information available.

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

-1009115L Error 20136 QSB15 "Database segment '%2' is not valid. %3 imaginary freelist blocks were found, but %4 imaginary freelist blocks were expected. This segment cannot be used. %1" When a database segment is opened, the segment header is read and the number of freelist blocks read from the header is compared with the number of freelist blocks that are expected to be read from the segment header. If the numbers do not match, the segment cannot be used and the database must be restored from backup.

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

-1009116L Error 20137 QSB16 "Wrong new() was called. %1" No additional information available.

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


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