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 |
|---|---|---|---|---|---|
| QDB43 | Error | 20803 | -1000143L | "While inserting, table '%2' must be Complete(d) before it can be (re)Prepare(d). %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. |
| QDB44 | Error | 20804 | -1000144L | "Cannot insert into table '%2'. Column %3 does not have a name. %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. |
| QDB45 | Error | 20805 | -1000145L | "The insert for table '%2' has no insertable columns in the column list. %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. |
| QDB46 | Error | 20806 | -1000146L | "Cannot get the index buffer for the column '%2'. %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. |
| QDB47 | Error | 20807 | -1000147L | "Table '%2' must be Prepare(d) before inserting. %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. |
| QDB48 | Error | 20808 | -1000148L | "The table being inserted to does not have a name. %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. |
| QDB49 | Error | 20809 | -1000149L | "Unable to open table '%2' with Read/Write access for insert. %1" | The table cannot be opened for write access. The insert cannot proceed. Another user has this table open with write access. Click here for a list of possible parameters and odbc states. |
| QDB50 | Error | 20810 | -1000150L | "Cannot insert into the table. Column '%2' has no index. %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. |
| QDB51 | Error | 20811 | -1000151L | "NOT NULL column '%2' was not included in this insert. Data is needed at row %3. %1" | Data must be provided for insertion into columns defined as "NOT NULL". Click here for a list of possible parameters and odbc states. |
| QDB52 | Error | 20812 | -1000152L | "The NOT NULL column '%2' was not included in this insert. %1" | Data must be provided for insertion into columns defined as "NOT NULL". Click here for a list of possible parameters and odbc states. |
| QDB53 | Error | 20813 | -1000153L | "Table '%2', pass-x index count mismatch (%3/%4). %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. |
| QDB54 | Error | 20814 | -1000154L | "While inserting into table '%2', the record number recycled (%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. |
| QDB55 | Error | 20815 | -1000155L | "The attempted insert length (%3) for column %2 is longer than the maximum allowed (%4). %1" | The attempted insert length is too long. The maximum length allowed is 65535. Click here for a list of possible parameters and odbc states. |
| QDB56 | Error | 20816 | -1000156L | "Tried to insert into too many (%2) LOW FAST indexes at one time in table '%3'. %1" | The maximum number allowed is 32727. Click here for a list of possible parameters and odbc states. |
| QDB57 | Error | 20817 | -1000157L | "Columns for the index must be in ascending sort order. %1" | It is required that ASC (ascending) sort order be used for the columns in the indexes. Click here for a list of possible parameters and odbc states. |
| QDB58 | Error | 20818 | -1000158L | "An Identity size mismatch has occurred. The current transaction will rollback. %1" | IQ has encountered an Identity size mismatch. The current command will be rolled back. If this error occurs, the operation that caused it may be tried again. If the error occurs again, the server should be stopped and restarted. If the problem persists, Sybase should be notified of the error. Click here for a list of possible parameters and odbc states. |
| QDB59 | Error | 21082 | -1000269L | "DBCC: Multiple modes specified with a write mode. %1" | The user can only specify one mode if a mode that updates the database is present. Update modes are dbcc command REPAIR, server switch -iqdrplks, database options Convert_HG_To_1242 and Convert_Varchar_To_1242 Click here for a list of possible parameters and odbc states. |
| QDB60 | Error | 21083 | -1000270L | "DBCC: FP Recreate failed for index '%2'. %1" | If an FP re-create fails, the command must rollback Click here for a list of possible parameters and odbc states. |
| QDB61 | Error | 21084 | -1000271L | "Table '%2' is a temporary table, a view, or not an IQ table. %1" | The specified table was opened, but it was a non-IQ or temporary table or a view. Only non-temporary IQ tables can be processed. Click here for a list of possible parameters and odbc states. |
| QDB62 | Error | 20822 | -1000162L | "Unable to create the requested object. %1" | IQ is not able to create the object that was requested. This object may be an FP index that is being created during a CREATE TABLE. This error will occur if IQ finds that the index already exists in the table for which it is being created. This can happen if you FORCE DROP a table and then try to recreate the table that was dropped. If this error occurs after a FORCE DROP, the server needs to be rebooted before continuing. If this error occurs for some other reason, Sybase should be notified. Extra diagnostic information will have output to the iqmsg file. Click here for a list of possible parameters and odbc states. |