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 |
|---|---|---|---|---|---|
| QDC06 | Error | 20866 | -1000206L | "Within the join, there remain no rows to insert into table '%2' \nafter processing the INNER and OUTER rows. %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. |
| QDC07 | Error | 20867 | -1000207L | "Within the join, the portion for table '%2' has no data. \nINSERT INTO or LOAD this table first. %1" | The named table must be populated with data. Click here for a list of possible parameters and odbc states. |
| QDC08 | Error | 20868 | -1000208L | "Within the non-appending partial width insert into the join virtual table '%2', \nthere must be at least one other column besides the join field(s). %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. |
| QDC09 | Error | 20869 | -1000209L | "Within the partial width insert into the join virtual table '%2', \nrow %3 is no longer an inner join. %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. |
| QDC10 | Error | 20870 | -1000210L | "For the partial width insert into the join virtual table '%2', \nrow %3 is no longer a left outer. %1" | This is an internal error. If this error occurs, then it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDC11 | Error | 20871 | -1000211L | "For the partial width insert into the join virtual table '%2', \nrow %3 is no longer a right outer. %1" | This is an internal error. If this error occurs, then it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDC12 | Error | 20872 | -1000212L | "For the partial width insert into join virtual table '%2', \nrow %3 is now a duplicate row (but was not before or vice-versa). %1" | This is an internal error. If this error occurs, then it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDC14 | Error | 20874 | -1000214L | "Duplicate records seen in table %2. The SYNCHRONIZE operation will rollback. %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. |
| QDC15 | Error | 20875 | -1000215L | "An invalid filler option (e.g., filler()) was specified in the load statement. %1" | An invalid filler option was specified on the load statement. Click here for a list of possible parameters and odbc states. |
| QDC19 | Error | 20879 | -1000219L | "The specified indextype does not exist in the given target. %1" | The indextype the user requested to check with sp_iqcheckdb does not exist in the given table or database. Click here for a list of possible parameters and odbc states. |
| QDC22 | Error | 20882 | -1000222L | "JP3&4" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| QDC23 | Error | 20883 | -1000223L | "Column name '%2' is invalid. The column name must follow the format [OWNER.]TABLE.COLUMN. %1" | The column name must follow the format [OWNER.]TABLE.COLUMN. Click here for a list of possible parameters and odbc states. |
| QDC25 | Error | 20885 | -1000225L | "Cannot open table %2. The table has already been opened by a cursor declared FOR UPDATE in transaction %3. %1" | A table opened by a CURSOR that has been declared FOR UPDATE cannot be opened again by another operation. Click here for a list of possible parameters and odbc states. |
| QDC28 | Error | 20888 | -1000228L | "JP4&5" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| QDC31 | Error | 20891 | -1000231L | "You do not have permission to create join index %2%3%4. %1" | A user can only create a join index under the following conditions 1) They are the DBA account 2) They have DBA authority. 3) They did not specify a creator and have RESOURCE authority 4) The specified creator is the same as the current user and they have RESOURCE authority. Click here for a list of possible parameters and odbc states. |
| QDC32 | Error | 20892 | -1000232L | "Partial input record skipped at EOF. %1" | A partial input record was detected during a 'load' operation. This can occur as a result of an OS/hardware error or simply because the input data file was missing values for one or more columns in the table. Click here for a list of possible parameters and odbc states. |
| QDC33 | Error | 20893 | -1000233L | "Cannot SYNCHRONIZE join index %2. %1" | The requested SYNCHRONIZE operation for the named join index failed because not all read-write locks could be obtained for all tables and related joins/tables in the join indexes' transitive closure. Try the SYNCHRONIZE operation later when there are no access conflicts with other users. Click here for a list of possible parameters and odbc states. |
| QDC34 | Error | 20723 | -1000063L | "Cannot enforce the NOT NULL constraint. Column %2 has NULL data. %1" | The user tried ALTER MODIFY column NOT NULL on a column that used to allow nulls and has null data. The user has to first delete the null rows before altering the column to enforce the NOT NULL constraint. Click here for a list of possible parameters and odbc states. |
| QDC35 | Error | 20722 | -1000062L | "Cannot add column '%3' with 'not null' constraint on table %2 with data. %1" | The user tried to ALTER ADD a NOT NULL column to a table that has data. The newly added column would violate the NOT NULL constraint as it would have null data. Click here for a list of possible parameters and odbc states. |
| QDC36 | Error | 20996 | -1000226L | "The LOCATION string passed to the attached database insert is invalid. %1" | The user passed an invalid LOCATION string in an attached database insert. Check the format of the string. It must be of the form "servername.dbname". Click here for a list of possible parameters and odbc states. |