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 |
|---|---|---|---|---|---|
| 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. |
| QDB76 | Error | 20836 | -1000176L | "Cannot perform foreign key create/alter operation because one is already in progress. %1" | Concurrent foreign key create/alter operations are not supported. This error means that there is such an operation already in progress. Consequetly, this new operation will be denied. Click here for a list of possible parameters and odbc states. |
| QDB77 | Warning | 20837 | 1000177L | "Only the catalog entry for the '%1' index was created, no data was available to populate the index." | This is an internal error. The new index was to be populated from another, existing index but a source index could not be found. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDB78 | Error | 20838 | -1000178L | "The DATA parameter must have a non-NULL value. %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. |
| QDB79 | Error | 20839 | -1000179L | "The column length (%2) must be [if variable sized, between 0 and] %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. |
| QDB80 | Error | 20840 | -1000180L | "The maximum column length (%2) must be between 0 and %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. |
| QDB81 | Error | 20841 | -1000181L | "The maximum column length (%2) is less than the actual length (%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. |
| QDB82 | Error | 20842 | -1000182L | "Table %2 cannot be opened because it is currently involved in a foreign key create/alter operation. %1" | The named table cannot be opened for read or write access because it is currently undergoing a create/alter foreign operation. Click here for a list of possible parameters and odbc states. |
| QDB83 | Error | 20843 | -1000183L | "Attempt to insert data into column '%2' with a non-insertable datatype (%3) ignored. %1" | This is an internal error. The datatype IQ is inserting to is unknown. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDB84 | Error | 20844 | -1000184L | "When inserting into join index '%2', the START ROW ID (%3) must 0 or 1. %1" | The START ROW ID for insert to a join must be 0 or 1. Click here for a list of possible parameters and odbc states. |