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 |
|---|---|---|---|---|---|
| QUA37 | Error | 20960 | -1012037L | "IQ store dbfile %2 exists. Restore will not be done. %1" | File must not exist when restoring from a full backup, unless restore is RO selective or restoring from virtual backup, or the file was created after the dependent backup when restoring from inc backup. Click here for a list of possible parameters and odbc states. |
| QUA38 | Error | 20961 | -1012038L | "IQ store dbfile %2 does not exist. Restore will not be done. %1" | File must exist when restoring from inc backup, unless it was created after the dependant backup, or when restoring from virtual backup. Click here for a list of possible parameters and odbc states. |
| QUA39 | Error | 20962 | -1012039L | "The maximum number of backup devices allowed is %2. %1" | A database can be backed up to a maximum of the stated number of devices. Click here for a list of possible parameters and odbc states. |
| QUA40 | Error | 20963 | -1012040L | "IQ store dbspace %2 is online. Restore will not be done. %1" | dbspace to restore must be offline, both in catalog and dynamically Click here for a list of possible parameters and odbc states. |
| QUA41 | Warning | 20964 | 2012041L | No message | No additional information available. Click here for a list of possible parameters and odbc states. |
| QUA50 | Error | 20974 | -1012050L | "Bad opcode detected during restore. Expected opcode is '%2', but '%3' was seen. %1" | This is an internal error. If this error occurs it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QUA51 | Error | 20975 | -1012051L | "An invalid database segment number (%2, %3) has been detected. %1" | This is an internal error. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QUA52 | Error | 20976 | -1012052L | "Programming error: looking for hole '%2', but only have '%3'. %1" | This is an internal error. If this error occurs it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QUA53 | Error | 20977 | -1012053L | "Fatal internal error: looking for segment containing hole {%2,%3}, but none was found. %1" | This is an internal error. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QUA54 | Error | 20978 | -1012054L | "Fatal internal error: looking for segment containing block '%2', but none was found. %1" | This is an internal error. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QVA00 | Error | 20000 | -1011000L | "Vertical Projection Cursor state error %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QVA01 | Error | 20001 | -1011001L | "Cannot find index for a given dfe %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QVA02 | Error | 20002 | -1011002L | "The number of existing indexes exceeds the current maximum number of indexes. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QVA03 | Error | 20003 | -1011003L | "Vertical Projection Cursor does not support AD-HOC joins. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QVA05 | Error | 20005 | -1011005L | "Force_Drop of a Join Index is not allowed on a multiplex coordinator. %1" | A join index cannot be dropped on a multiplex coordinator when the Force_Drop option is set to 'ON'. If it is necessary to force drop a join index on a multiplex coordinator, the server will first need to be brought up in simplex mode. Click here for a list of possible parameters and odbc states. |
| QVA06 | Error | 20006 | -1011006L | "the pattern argument in a like predicate must have string datatype." | No additional information available. Click here for a list of possible parameters and odbc states. |
| QVA07 | Error | 20007 | -1011007L | "the escape argument in a like predicate must be a one byte character." | No additional information available. Click here for a list of possible parameters and odbc states. |
| QVA09 | Error | 20009 | -1011009L | "Group (L)" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QVA10 | Error | 20010 | -1011010L | "Group (S)" | No additional information available. Click here for a list of possible parameters and odbc states. |
| QVA11 | Error | 20011 | -1011011L | "Aggregate (L)" | No additional information available. Click here for a list of possible parameters and odbc states. |