Messages QBB90 through QBC09

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
QBB90 Error 20428 -1006190L "The semaphore variable was canceled %1" No additional information available.

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

QBB91 Error 20429 -1006191L "Unknown error was found on a lock (mutex,condvar,etc) Call %1" No additional information available.

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

QBB92 Error 20430 -1006192L "OS error was found on Thread Call: error = %2, %1" No additional information available.

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

QBB93 Error 20431 -1006193L "Unknown error was found on Thread Call %1" No additional information available.

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

QBB94 Error 20432 -1006194L "Could not get a thread %1" No additional information available.

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

QBB95 Error 20433 -1006195L "OS error was found on hos_threadman Call: error = %2 %1" No additional information available.

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

QBB96 Error 20434 -1006196L "hos_threadman: the environment variable HOS_NUM_OF_CPUS does not exist %1" No additional information available.

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

QBB97 Error 20435 -1006197L "Unknown error was found during hos_threadman Constructor %1" No additional information available.

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

QBB98 Error 20436 -1006198L "Unknown error was found during hos_threadman Destructor %1" No additional information available.

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

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

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

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

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

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.


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