Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| -1000149L | Error | 20809 | QDB49 | "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. |
| -1000150L | Error | 20810 | QDB50 | "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. |
| -1000151L | Error | 20811 | QDB51 | "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. |
| -1000152L | Error | 20812 | QDB52 | "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. |
| -1000153L | Error | 20813 | QDB53 | "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. |
| -1000154L | Error | 20814 | QDB54 | "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. |
| -1000155L | Error | 20815 | QDB55 | "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. |
| -1000156L | Error | 20816 | QDB56 | "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. |
| -1000157L | Error | 20817 | QDB57 | "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. |
| -1000158L | Error | 20818 | QDB58 | "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. |
| 1000159L | Warning | 20819 | 00B59 | "\nIn table '%1', the %2 width insert of %3 columns will begin at record %4." | Informational message displayed during insert. Click here for a list of possible parameters and odbc states. |
| 1000160L | Warning | 20820 | 00B60 | "Option %1 has an invalid setting: %2." | The named OPTION is set to an invalid value. See the documentation for the valid values for the option. Click here for a list of possible parameters and odbc states. |
| 1000161L | Warning | 20821 | 01B61 | "You have %1 and %2 available, respectively." | Informational message displayed with other messages regarding available memory. Click here for a list of possible parameters and odbc states. |
| -1000162L | Error | 20822 | QDB62 | "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. |
| -1000163L | Error | 20823 | QNA32 | "%1 not supported." | The named operation is not supported. Click here for a list of possible parameters and odbc states. |
| -1000164L | Error | 20824 | QNA33 | "Only %1 supported." | Only UPDATE RESTRICT and DELETE RESTRICT supported Click here for a list of possible parameters and odbc states. |
| -1000165L | Error | 20825 | QNA34 | "Only a single foreign key constraint can be created on the same foreign key column(s) and same candidate key column(s)." | For a given set of foreign key columns and candidate key columns, Click here for a list of possible parameters and odbc states. |
| -1000166L | Error | 20826 | QDB66 | "Cannot specify IGNORE CONSTRAINT ALL or DATA VALUE when option CONVERSION_ERROR is on. %1" | When choosing to ignore DATA TYPE or ALL integrity constraint violations on LOAD command, you must also have option CONVERSION_ERROR set to 'off'. Click here for a list of possible parameters and odbc states. |
| -1000167L | Error | 20827 | QDB67 | "Cannot %3 table %2 because of RI concurrency conflict. %1" | The named table cannot be modified in the manner specified because of an RI concurrency conflict. Such a conflict arises under the following conditions. delete/truncate/update candidate key at the same time its corresponding foreign key is being loaded/inserted/updated Click here for a list of possible parameters and odbc states. |
| -1000168L | Error | 20828 | QNA35 | "Cannot create %1 HG index because one already exists on the given columns." | Only a single HG index of a given type can be created on the same column set. For example, you cannot have two unique HG indexes on the same column set, but you are allowed to have a unique HG and a non-unique HG index on the same set of columns. Click here for a list of possible parameters and odbc states. |