Messages 1006198 through 1006217

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
-1006198L Error 20436 QBB98 "Unknown error was found during hos_threadman Destructor %1" No additional information available.

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

-1006199L Error 20437 QBB99 "Unknown error was found on hos_threadman Call %1" No additional information available.

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

-1006200L Error 20438 QBC00 " and last packet was " No additional information available.

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

-1006201L Error 20439 QBC01 " and last packet was " No additional information available.

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

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

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

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

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

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

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

-1006205L Error 20443 QBC05 "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.

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

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

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

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

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

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

-1006209L Error 20447 QBC09 "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.

-1006210L Error 20448 QBC10 "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.

-1006211L Error 20449 QBC11 "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.

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

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

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

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

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

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

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

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

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

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

-1006217L Error 20455 QBC17 "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.


Created June 15, 2009. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com