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 |
|---|---|---|---|---|---|
| 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. |
| QDB63 | Error | 21085 | -1000272L | "Invalid table name '%2'. %1" | The table name must follow the format [OWNER.]TABLE Click here for a list of possible parameters and odbc states. |
| QDB64 | Error | 21086 | -1000273L | "Invalid index name '%2'. %1" | The index name must follow the format [OWNER.]TABLE.INDEX Click here for a list of possible parameters and odbc states. |
| QDB65 | Error | 21087 | -1000274 | "DBCC: Upgrade options can be used only with CHECK or REPAIR mode. %1" | Upgrade options (such as Convert_HG_To_1242) can be used only with CHECK or REPAIR. They cannot be used with ALLOCATION. Click here for a list of possible parameters and odbc states. |
| QDB66 | Error | 20826 | -1000166L | "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. |
| QDB67 | Error | 20827 | -1000167L | "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. |
| QDB68 | Error | 21088 | -1000275 | "Cannot process object '%2' at the current transaction level. %1" | The requested object cannot be opened because it was created by a future transaction. A COMMIT or ROLLBACK must be issued before the object can be opened Click here for a list of possible parameters and odbc states. |
| QDB69 | Error | 21094 | -1000276 | "At least one mode and target must be specified. %1" | DBCC has no default target or mode. The user must explicitly specify both a mode and target. Click here for a list of possible parameters and odbc states. |
| QDB70 | Error | 21095 | -1000277 | "\"dropleaks {database|dbspace dbspace-name}\" is the only command allowed in drop leaks mode. %1" | Modes are restricted to avoid long DBCC sessions during forced recovery Click here for a list of possible parameters and odbc states. |
| QDB71 | Error | 21096 | -1000278 | "\"resetclks\" must be run in single-node mode with \"allocation database\". %1" | resetclks is restricted to allocation mode and single-node mode, and requires checking entire DB Click here for a list of possible parameters and odbc states. |
| QDB72 | Error | 21116 | -1000282 | "DBCC must be restricted to the MAIN or LOCAL store only. %1" | DBCC is restricted to either the main or the local store only. It may not combine checking of tables in both main and local in the same dbcc run. Click here for a list of possible parameters and odbc states. |
| QDB73 | Error | 21142 | -1010042 | "\"drop leaks\" is not allowed without executing post-sync secondary server replay. %1" | Disallow DBCC to drop leaked blocks on a MPX secondary server without executing post-sync local TLV replay. Click here for a list of possible parameters and odbc states. |