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 |
|---|---|---|---|---|---|
| QDA43 | Warning | 20703 | 1000043L | "Number of files in backup: %1" | This message displays the number of files in the backup. Click here for a list of possible parameters and odbc states. |
| QDA44 | Error | 20704 | -1000044L | "The join for table '%2' does not have enough columns defined (%3). %1" | Cannot define a join with zero columns. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA45 | Error | 20705 | -1000045L | "Index %2 does not exist. %1" | User has specified an index which does not exist in any table within the current database. Click here for a list of possible parameters and odbc states. |
| QDA46 | Error | 20706 | -1000046L | "No Field passed to PutMCIField. %1" | This error should not occur during normal operation and should be reported to Sybase. See the iqmsg file for additional diagnostic information. Click here for a list of possible parameters and odbc states. |
| QDA47 | Error | 20707 | -1000047L | "For table pair %2, table '%3' has a precision mismatch in column %4. %1" | Corresponding columns in the join must have equal precision. Click here for a list of possible parameters and odbc states. |
| QDA48 | Error | 20708 | -1000048L | "For table pair %2, table '%3' has a scale mismatch in column %4. %1" | Corresponding columns in the join must have equal scale. Click here for a list of possible parameters and odbc states. |
| QDA49 | Error | 20709 | -1000049L | "'%2' is being used in a self join. Self joins are not allowed. %1" | Self joins are not allowed. Click here for a list of possible parameters and odbc states. |
| QDA50 | Error | 20710 | -1000050L | "Table '%2' is used in the join twice. %1" | A table cannot be used twice in a join. Click here for a list of possible parameters and odbc states. |
| QDA51 | Error | 20711 | -1000051L | "Cannot retrieve a row from the SYSIQJOINIXTABLE system table. %1" | This is an internal error. Cannot retrieve a row from the SYSIQJOINIXTABLE system table. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA52 | Error | 20712 | -1000052L | "Cannot delete a row from the SYSIQJOINIXTABLE system table. %1" | This is an internal error. Cannot delete a row from the SYSIQJOINIXTABLE system table. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA53 | Error | 20713 | -1000053L | "Cannot commit changes to the SYSIQJOINIXTABLE system table. %1" | This is an internal error. Cannot commit changes to the SYSIQJOINIXTABLE system table. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA54 | Error | 20714 | -1000054L | "Cannot open %2 in Meta (exclusive) mode. Object is already open. %1" | The object cannot be opened for exclusive access; it is already open. Click here for a list of possible parameters and odbc states. |
| QDA56 | Error | 20716 | -1000056L | "Cannot convert from datatype '%2' to '%3' for column '%4'. %1" | Implicit conversion for this column is not possible. Click here for a list of possible parameters and odbc states. |
| QDA57 | Error | 20717 | -1000057L | "Column '%2' has an unknown datatype: '%3'. %1" | The column is of a datatype that is unknown to ASIQ. 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. |
| QDA58 | Warning | 20718 | 1000058L | "Platform: %1" | This is an informational message reporting the platform type. Click here for a list of possible parameters and odbc states. |
| QDA60 | Error | 20720 | -1000060L | "Column '%2', PRECISION (%3) cannot be greater than %4. %1" | The precision requested by the user is larger than what is allowed for the datatype. Click here for a list of possible parameters and odbc states. |
| QDA61 | Error | 20721 | -1000061L | "Column %2, PRECISION (%3) cannot be less than 0. %1" | The precision specified by the user is less than zero. Click here for a list of possible parameters and odbc states. |
| QDA64 | Error | 20724 | -1000064L | "Column %2 can not be altered because it participates in join %3. %1" | A column/field that participates in a join cannot be altered. Joins on this field must be deleted before an ALTER can be performed. Click here for a list of possible parameters and odbc states. |
| QDA65 | Error | 20725 | -1000065L | "Table %2 must be owned by the creator of the join. %1" | This error message is given during CREATE JOIN when one of the tables specified is not owned by the owner of the join. Joins can only be created from tables of the same owner. Click here for a list of possible parameters and odbc states. |
| QDA66 | Error | 20726 | -1000066L | "ALTER on the column would interfere with the natural join to table %2 in join %3. %1" | This message is displayed when using the ALTER command or adding columns to a table that participates in a join. Click here for a list of possible parameters and odbc states. |