Messages 1009157 through 1009176

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
-1009157L Error 20195 QSB52 "There is insufficient reserve space to add %3 blocks to segment %2. Only %4 blocks or less may be added. %1" Since a segment must use a contiguous range of block numbers, it can only be resized larger when the blocks following it are not in use by the next segment.

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

-1009158L Error 20196 QSB53 "Cannot resize segment %2 since the truncated region is in use. %1" A segment can only be resized smaller when no blocks in the truncated are in use.

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

-1009159L Error 20197 QSB54 "The status specified for segment %2 is unchanged. %1" The "alter dbspace status" syntax requires the new status to be different than the original status.

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

-1009160L Error 20198 QSB56 "There must be at least one readwrite dbspace (%2). %1" There must at least one readwrite segment

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

-1009161L Error 20199 QSB57 "Cannot resize segment %2 since it is readonly. %1" A readonly segment cannot be resized

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

-1009162L Error 20200 QSB58 "Insufficient space to relocate structures on %2. %1" Database structures may need to be relocated in order to drop a segment or make it readonly. This space must be available on other segments.

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

-1009163L Error 20201 QSB59 "Segment %2 cannot be smaller than %3 blocks. %1" Database structures may need to be relocated in order to drop a segment or make it readonly. This space must be available on other segments.

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

-1009164L Error 20202 QSB60 "You cannot drop the last dbspace. %1" You can drop the last dbspace only if it is a temp dbspace

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

-1009165L Error 20203 QSB61 "Cannot perform requested command as the SYSIQFILE table is locked by another transaction. %1" A CREATE DBSPACE, ALTER DPSACE or DROP DBSPACE command was issued when there was another command or stored procedure accessing the system table SYSIQFILE.

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

-1009166L Error 20204 QSB62 "%3 %4 is in use by dropped dbspace %2 on a secondary server. The drop dbspace command has not yet propagated through the multiplex. %1" Fields for dropped dbspaces cannot be re-used until the drop dbspace commands have propagated through the multiplex

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

-1009167L Error 20207 QSB63 "dbspace %2 failed to open since it's definition conflicts with dbspace %3. Secondary server may need to be synchronized. %1" The server has an invalid dbspace configuration. New dbspaces may fail to open or the server may fail to start until this is corrected.

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

-1009168L Error 20208 QSB64 "The WORD SKIP limit (%2) has been exceeded. %1" The number of words encountered that are longer than the limit specified when the word index was create has been exceeded for the load. The load will rollback.

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

-1009169L Error 20222 QSB65 "Cannot write to RO DBSpace %2. %1" No additional information available..

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

-1009170L Error 20223 QSB66 "You have run out of space in %2 DBSpace. %1" No additional information available..

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

-1009171L Error 20224 QSB67 "An IO error was encountered while writing a database page in %2 DBSpace. %1" No additional information available..

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

-1009172L Error 20226 QSB68 "%2 is in use by another sp_iqemptyfile or ALTER DBSPACE command. %1" sp_iqemptyfile or ALTER DBSPACE commands disallow status change for the FILE(s) or DBSPACE. No other ALTER DBSPACE or sp_iqemptyfile command can run on those FILE(s) or DBSPACE.

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

-1009173L Error 20227 QSB69 "Operation not permitted on an OFFLINE DBSpace %2. %1" No additional information available..

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

-1009174L Error 20228 QSB70 "Operation not yet supported. Sort metadata sources have incompatible record descriptors. %1" No additional information available..

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

-1009175L Error 20229 QSB71 "Database segment '%2' is not valid. Reserve Blocks found in the header: %3 Reserve Blocks 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. You will need to restore your database from backup.

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

-1009176L Error 20230 QSB72 "Create temporary dbspace not allowed. %1" Additional dbspaces may not be created in temp store. Temp space may only be added to IQ_SYSTEM_TEMP.

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