Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 21142 | Error | QDB73 | -1010042 | "\"drop leaks\" is not allowed without executing post-sync secondary server replay. %1" | Disallow DBCC to drop leaked blocks on a MPX secondary server without executing post-sync local TLV replay. Click here for a list of possible parameters and odbc states. |
| 21143 | Error | QTA29 | -1005029L | "You cannot SELECT from a join virtual table. (%2) %1" | location of the exception the details of syntax error Click here for a list of possible parameters and odbc states. |
| 21144 | Error | QXA42 | -1010043L | "dbspace %2 is currently not open. %1" | The specifed dbspace exists but is not currently open. Click here for a list of possible parameters and odbc states. |
| 21145 | Error | QTA30 | -1005030L | "Query has an ambiguous table reference between prepare and open cursor (%2). %1" | SA allows a base and temp table to both have the same table name. In some places, such as when a temp table is created in a stored procedure between the describe and open, IQ can find the base table in the describe and the temp table in the open, giving inconsistent results. Click here for a list of possible parameters and odbc states. |
| 21146 | Error | QXA43 | -1010044L | "Plan not available." | "User request for the plan and there is no plan in the cache to be returned. cases when this error will be returned :1. User makes a connection and executes select graphical_plan() or select html_plan(). 2. When the the SQL function graphical_plan and html_plan is used to get the plan for an IQ query for which IQ does not generate plan. " Click here for a list of possible parameters and odbc states. |
| 21147 | Error | QXA44 | -1010045L | "Plan not available. Plan type is not supported for Sybase IQ queries." | "IQ supports only graphical_plan and html_plan SQL functions. Other SA plan functions (plan, explanation etc.) are not supported for Sybase IQ." Click here for a list of possible parameters and odbc states. |
| 21148 | Error | QXA45 | -1010046L | "Plan not available. The database option QUERY_PLAN_TEXT_ACCESS is off." | "The plan can be accessed on the client by the user only when DBA sets option QUERY_PLAN_TEXT_ACCESS to ON for the user." Click here for a list of possible parameters and odbc states. |
| 21149 | Warning | QCB17 | 1000297L | "%1. Message logging stopped." | Message log management operation failed due to error in file renaming / deletion / creation. Or log could not be written in the IQMSG file because some DISK IO error occurred. Click here for a list of possible parameters and odbc states. |
| 21150 | Warning | QCB18 | 1000298L | " Message logging resumed." | Engine has detected that reason behind message log management / message logging failure has been resolved. Message logging is resumed now. Click here for a list of possible parameters and odbc states. |
| 21151 | Error | QBC68 | -1006268L | "The current operation has been cancelled: Max_Temp_Space_Per_Connection exceeded" | User has exhausted maximum temp dbspace limit for this connection Click here for a list of possible parameters and odbc states. |
| 21152 | Error | QDC79 | -1000299L | " Partition key of %2 is unsupported. %1" | Partiiton key of LOB/CLOB/char/varchar/binary/varbinary over 255 is not supported. Click here for a list of possible parameters and odbc states. |
| 21153 | Error | QDC80 | -1000300L | " Table that participates in a join index cannot be partitioned. %1" | A partitioned table cannot participate in join. Click here for a list of possible parameters and odbc states. |
| 21154 | Error | QDC81 | -1000301L | " Join index cannot be created on a partitioned table. %1" | Join index cannot be created on a partitioned table. Click here for a list of possible parameters and odbc states. |
| 21155 | Error | QDC82 | -1000302L | " Exceed maximum number of partitions. %1" | Exceed maximum number of partitions. Click here for a list of possible parameters and odbc states. |
| 21156 | Error | QDC83 | -1000303L | " Object %2 not usable in current context. %1" | Table of TBLTYP_PARTITION type cannot be used. Click here for a list of possible parameters and odbc states. |
| 21157 | Error | QDC84 | -1000304L | " Cannot drop a partition key column. %1" | Can not drop a partition key column. Click here for a list of possible parameters and odbc states. |
| 21158 | Error | QDC85 | -1000305L | " Allocation failure. %1" | DBCC allocation failure Click here for a list of possible parameters and odbc states. |
| 21159 | Error | QCB19 | -1009419 | "The width of one or more columns are too large to fit into database's page." | The LOAD Engine cannot fit a column into the page. Click here for a list of possible parameters and odbc states. |
| 21160 | Error | QCB20 | -1009420L | "Value of row's partition-key columns do not fit into any of the table's partitions." | The value for the partition key columns for a specific row do not fit within any of the table's partitions. Click here for a list of possible parameters and odbc states. |
| 21161 | Error | QBC69 | -1006269L | "No SYSAM License Available" | SYSAM license for the product is either not available or not configured. Click here for a list of possible parameters and odbc states. |