Messages QBC01 through QBC20

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

SQL State Msg Type Number SQL Code Message Possible Cause
QBC01 Error 20439 -1006201L " and last packet was " No additional information available.

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

QBC02 Error 20440 -1006202L "Syntax error in conversion of string to DATETIME value." No additional information available.

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

QBC03 Error 20441 -1006203L "Syntax error in conversion of string to DATE value." No additional information available.

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

QBC04 Error 20442 -1006204L "Syntax error in conversion of string to TIME value." No additional information available.

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

QBC05 Error 20443 -1006205L "A lock was acquired on an object which has inconsistent state" No additional information available.

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

QBC06 Error 20444 -1006206L No message No additional information available.

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

QBC07 Error 20445 -1006207L "ACCESS exception: OS error %1" No additional information available.

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

QBC08 Error 20446 -1006208L "CONSTRAINT exception: OS error %2 %1" No additional information available.

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

QBC09 Error 20447 -1006209L "The exception handler's memory manager could not get memory during initialization" No additional information available.

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

QBC10 Error 20448 -1006210L "The exception handler's memory manager has run out of memory" No additional information available.

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

QBC11 Error 20449 -1006211L "Not all memory was returned to the exception handler's memory manager" No additional information available.

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

QBC12 Error 20450 -1006212L "The exception handler's memory manager has been corrupted" No additional information available.

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

QBC13 Error 20451 -1006213L "Unable to use shared memory because " No additional information available.

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

QBC14 Error 20452 -1006214L "the semaphore for shared memory did not exist" No additional information available.

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

QBC15 Error 20453 -1006215L "the semaphore for shared memory was deleted" No additional information available.

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

QBC16 Error 20454 -1006216L "of insufficient system semaphore resources" No additional information available.

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

QBC17 Error 20455 -1006217L "the system limit on the number of processes allowed to request semaphore undos would be exceeded" No additional information available.

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

QBC18 Error 20456 -1006218L "the system limit on the number of semaphore undo requests allowed per process (semume) would be exceeded" No additional information available.

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

QBC19 Error 20457 -1006219L "the creation of a new semaphore would exceed the system limit on either the maximum number of semaphores allowed or the maximum number of semaphore identifiers allowed" No additional information available.

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

QBC20 Error 20458 -1006220L "of insufficient system shared memory resources" 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