Messages 1006190 through 1006209

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

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

-1006191L Error 20429 QBB91 "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.

-1006192L Error 20430 QBB92 "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.

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

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

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

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

-1006195L Error 20433 QBB95 "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.

-1006196L Error 20434 QBB96 "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.

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

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

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


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