Messages 1009144 through 1009163

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
1009144L Warning 21069 QSB41 " %1 SortMergeDone: Ave mem %2 M, %3 Secs, %4 passes, %5 reads, %6 M data= %7 pgs, %8 phases, %9 M on disk" This information is provided at the end of Phase II to summarize the resource usage of the whole merge sort. The last pass of the sort is separately reported on by an EMSG_SORT_INFOMERGED1 message.

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

-1009145L Error 21070 QFA2E "Data exception - data type conversion is not possible. %2, %1" No additional information available.

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

-1009146L Error 21071 QSB42 "Cannot perform requested command as there is a DBCC command in progress. %1" A CHECKPOINT command was issued when there was already a DBCC command in progress.

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

1009147L Warning 20188 QSB43 "Space has become available in the %1 store of database %2. Sybase IQ (TM) is no longer waiting for more dbspace." No additional information available.

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

-1009148L Error 21049 QSB44 "Cannot use -iqfrec to start a multiplex secondary server. %1" A sp_iqcheckdb procedure call was issued on an IQ multiplex secondary server, or it was started in drop-leaks or forced recovery mode. These operations are only allowed on the coordinator

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

-1009149L Error 20189 QSB45 "%2 Internal Inconsistency: %1 (%3,%4,%5)" A corrupt index container was found. DBCC cannot repair the container. The database object using the container must be re-created.

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

-1009150L Error 20190 QSB46 "Cannot delete/truncate CK %2 because of RI violation - FK has non-nulls. %1" No additional information available. Cannot truncate or delete all from candidate table if there exists any associated foreign key which has any all non-null data.

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

-1009151L Error 20191 QSB47 "Cannot %2 CK %3 row %4 because of RI violation. %1" No additional information available. Cannot delete/update CK if there exists same value in associated FK. any associated foreign key which has any all non-null data.

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

-1009152L Error 20192 QSB48 "Cannot %2 FK %3 row %4 because of RI violation. %1" No additional information available. Cannot insert/update FK if there does not exist same value in associated CK any associated foreign key which has any all non-null data.

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

-1009153L Error 20193 QSB49 "Cannot remove row %3 from CK %2 during LOAD cleanup because of RI violation. %1" No additional information available. If removing self-referential CK during LOAD cleanup phase and there exists a FK of removed value, we roll back the whole operation.

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

-1009154L Error 21118 QSB50 "Cannot alter dbspace when a backup is in progress" An alter dbspace operation was attempted while a backup was running. The alter dbspace operation cannot proceed since it may modify internal database structures that are being backed up.

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

-1009155L Error 22000 QSB55 "Cannot perform requested command as there is an ALTER DBSPACE command in progress. %1" A CREATE DBSPACE or a DROP DBSPACE command was issued when there was already an ALTER DBSPACE command in progress.

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

-1009156L Error 20194 QSB51 "Drop disallowed for dbspace %2. One or more of the file(s) are in use by the database. %1" A segment must contain no user data and no database structures to drop

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

-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.


Created April 27, 2010. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com