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 |
---|---|---|---|---|---|
20164 | Error | QTA10 | -1005010L | "The field '%2' is not unique and needs to be qualified, %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
20165 | Error | QTA11 | -1005011L | "There are two tables named '%2'. Please specify an alias for one of them. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
20166 | Error | QTA12 | -1005012L | "The field '%2' specified in the query cannot be found, %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
20167 | Error | QTA13 | -1005013L | "The FROM clause must have at least one table identifier %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
20168 | Error | QTA14 | -1005014L | "Non-space text found after ending quote character for an enclosed field. %1" | Non-space text found after ending quote character for an enclosed field. Click here for a list of possible parameters and odbc states. |
20169 | Error | QTA15 | -1005015L | "The optimizer was unable to find a query plan that avoided cartesian product joins larger than the Max_Cartesian_Result setting %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
20170 | Error | QTA16 | -1005016L | "Aggregate functions are not allowed in a GROUP BY clause %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
20171 | Error | QTA17 | -1005017L | "You cannot DELETE from a join virtual table. (%2) %1" | If this message occurs, it means that the user has tried to DELETE from a join virtual table. This is not permitted. Click here for a list of possible parameters and odbc states. |
20172 | Error | QHA00 | -1003000L | "Datatype %2, returned by Client Library, is not valid in Sybase IQ. %1" | Sybase IQ doesn't support a number of datatypes that ASE does (text or image, for example). Refer to documentation for the respective products to see what datatypes are supported. Click here for a list of possible parameters and odbc states. |
20173 | Error | QHA01 | -1003001L | "Cannot convert to Sybase IQ datatype: %2 from Client Library datatype %3. %1" | Error converting CSLIB datatype to IQ datatype. Click here for a list of possible parameters and odbc states. |
20174 | Error | QHA02 | -1003002L | "CtLibrary Error: %2, Severity: %3, Origin: %4, Layer: %5\nError Message: %6\nOS Error: %7, OS Message: %8. %1" | General CTLIB/CSLIB error message. Refer to the CTLibrary/CSLibrary for error information. Click here for a list of possible parameters and odbc states. |
20175 | Error | QHA03 | -1003003L | "Adaptive Server Error: %2, Severity: %3, State: %4, Line: %5\nServer Name: %6, Procedure Name: %7\nError Message: %8. %1" | ASE error. Refer to the ASE error documentation for information regarding the error. Click here for a list of possible parameters and odbc states. |
20176 | Error | QHA04 | -1003004L | "COMPUTE values cannot be used in attached database queries. %1" | Sybase IQ doesn't process COMPUTE clauses. Click here for a list of possible parameters and odbc states. |
20177 | Error | QHA05 | -1003005L | "Connectivity libraries cannot be found (check your dynamic library search path). Selects from attached databases are not possible without these libraries. %1" | Cannot process attached DB request without the connectivity libraries. Check your dynamic library search path to make sure it is correct. Click here for a list of possible parameters and odbc states. |
20178 | Error | QHA06 | -1003006L | "A call to ct_con_props failed trying to get the msglist from the connection. %1" | While trying to report an error condition, another error occurred trying to retrieve the original error from the connection in order to report it to the user. If this error occurs, retry the operation that caused it. Click here for a list of possible parameters and odbc states. |
20179 | Error | QHA07 | -1003007L | "%2 functionality is not licensed on this server. %1" | The named feature is not licensed on the server. Click here for a list of possible parameters and odbc states. |
20180 | Error | QHA08 | -1003008L | "Licensing error. Code = %2. %1" | An error occurred while verifying the license. Refer to the documentation for information about the Code reported in the error. Click here for a list of possible parameters and odbc states. |
20181 | Error | QHA09 | -1003009L | "The specified target contains no indexes on which to report. %1" | sp_iqindexfragmentation will report this error if it is run on a table that contains only FP indexes. Click here for a list of possible parameters and odbc states. |
20182 | Error | QHA10 | -1003010 | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
20183 | Error | QHA11 | -1003011L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |