Messages QBA33 through QBA52

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
QBA33 Warning 20271 1006033L "team id %1 : # threads = %2" No additional information available.

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

QBA34 Error 20272 -1006034L No message No additional information available.

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

QBA35 Error 20273 -1006035L No message No additional information available.

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

QBA36 Error 20274 -1006036L No message No additional information available.

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

QBA37 Error 20275 -1006037L No message No additional information available.

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

QBA38 Error 20276 -1006038L No message No additional information available.

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

QBA39 Error 20277 -1006039L No message No additional information available.

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

QBA40 Error 20278 -1006040L No message No additional information available.

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

QBA41 Error 20279 -1006041L "No Mark Pointer Found %1" No additional information available.

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

QBA42 Error 20280 -1006042L "All available virtual memory has been used; allocation cancelled: [Extra info: %2] %1" No additional information available.

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

QBA43 Error 20281 -1006043L "No more event handlers %1" No additional information available.

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

QBA44 Error 20282 -1006044L "No more Mark Stack slots available %1" No additional information available.

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

QBA45 Error 20283 -1006045L "Not a Vector: delete[] was called on an object that is not a vector %1" No additional information available.

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

QBA46 Error 20284 -1006046L "Is a Vector: delete was called on an object that is a vector; use delete[] %1" No additional information available.

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

QBA47 Error 20285 -1006047L "Error Memory Object errnum %2 %1" No additional information available.

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

QBA48 Error 20286 -1006048L "hos_memArena: memory corrupt %1" No additional information available.

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

QBA49 Error 20287 -1006049L "hos_memArena: not all memory returned %1" No additional information available.

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

QBA50 Error 20288 -1006050L "hos_memArena: out of memory %1" No additional information available.

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

QBA51 Error 20289 -1006051L "hos_memArena: could not get memory during initialization %1" No additional information available.

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

QBA52 Error 20290 -1006052L "hos_memArena: unknown error %1" 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