Messages 1006031 through 1006050

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
-1006031L Error 20269 QBA31 "Invalid SQL code %1" No additional information available.

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

1006032L Warning 20270 QBA32 "\n=n*** File: %1\n\n" No additional information available.

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

1006033L Warning 20271 QBA33 "team id %1 : # threads = %2" No additional information available.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

-1006042L Error 20280 QBA42 "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.

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

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

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

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

-1006045L Error 20283 QBA45 "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.

-1006046L Error 20284 QBA46 "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.

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

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

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

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

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

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

-1006050L Error 20288 QBA50 "hos_memArena: out of memory %1" 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