Messages 1006178 through 1006197

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
-1006178L Error 20416 QBB78 "DateTime is invalid because of the MicroSeconds from 1/1/0000 (%2) %1" No additional information available.

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

-1006179L Error 20417 QBB79 "Cannot allocate space for CS context %1 " No additional information available.

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

-1006180L Error 20418 QBB80 "Cannot allocate space for CS locale %1 " No additional information available.

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

-1006181L Error 20419 QBB81 "Cannot set CS locale %1 " No additional information available.

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

-1006182L Error 20420 QBB82 "Cannot configure CS context %1 " No additional information available.

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

-1006183L Error 20421 QBB83 "Raw device is not open %1" No additional information available.

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

-1006184L Error 20422 QBB84 "Unable to query raw device %1" No additional information available.

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

-1006185L Error 20423 QBB85 "Unsupported raw device type %1" No additional information available.

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

-1006186L Error 20424 QBB86 "Program error on raw device %1" No additional information available.

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

-1006187L Error 20425 QBB87 "OS error was found on a lock (mutex,condvar,etc) Call: error = %2 %1" No additional information available.

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

-1006188L Error 20426 QBB88 "USEAGE 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.

-1006189L Error 20427 QBB89 "The condition variable was killed %1" No additional information available.

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

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


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