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 |
|---|---|---|---|---|---|
| 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 Large Objects Management 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. |
| 20184 | Error | QHA12 | -1003012L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20185 | Error | QHA13 | -1003013L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20186 | Error | QHA14 | -1003014L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20188 | Warning | QSB43 | 1009147L | "Space has become available in the %1 store of database %2. Sybase IQ (TM) is no longer waiting for more dbspace." | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20189 | Error | QSB45 | -1009149L | "%2 Internal Inconsistency: %1 (%3,%4,%5)" | A corrupt index container was found. DBCC cannot repair the container. The database object using the container must be re-created. Click here for a list of possible parameters and odbc states. |
| 20190 | Error | QSB46 | -1009150L | "Cannot delete/truncate CK %2 because of RI violation - FK has non-nulls. %1" | No additional information available. Cannot truncate or delete all from candidate table if there exists any associated foreign key which has any all non-null data. Click here for a list of possible parameters and odbc states. |
| 20191 | Error | QSB47 | -1009151L | "Cannot %2 CK %3 row %4 because of RI violation. %1" | No additional information available. Cannot delete/update CK if there exists same value in associated FK. any associated foreign key which has any all non-null data. Click here for a list of possible parameters and odbc states. |
| 20192 | Error | QSB48 | -1009152L | "Cannot %2 FK %3 row %4 because of RI violation. %1" | No additional information available. Cannot insert/update FK if there does not exist same value in associated CK any associated foreign key which has any all non-null data. Click here for a list of possible parameters and odbc states. |
| 20193 | Error | QSB49 | -1009153L | "Cannot remove row %3 from CK %2 during LOAD cleanup because of RI violation. %1" | No additional information available. If removing self-referential CK during LOAD cleanup phase and there exists a FK of removed value, we roll back the whole operation. Click here for a list of possible parameters and odbc states. |
| 20194 | Error | QSB51 | -1009156L | "Drop disallowed for dbspace %2. One or more of the file(s) are in use by the database. %1" | A segment must contain no user data and no database structures to drop Click here for a list of possible parameters and odbc states. |
| 20195 | Error | QSB52 | -1009157L | "There is insufficient reserve space to add %3 blocks to segment %2. Only %4 blocks or less may be added. %1" | Since a segment must use a contiguous range of block numbers, it can only be resized larger when the blocks following it are not in use by the next segment. Click here for a list of possible parameters and odbc states. |
| 20196 | Error | QSB53 | -1009158L | "Cannot resize segment %2 since the truncated region is in use. %1" | A segment can only be resized smaller when no blocks in the truncated are in use. Click here for a list of possible parameters and odbc states. |
| 20197 | Error | QSB54 | -1009159L | "The status specified for segment %2 is unchanged. %1" | The "alter dbspace status" syntax requires the new status to be different than the original status. Click here for a list of possible parameters and odbc states. |