Messages on this page are sorted by Sybase error code. Locate the appropriate code in the table below, and click the link for a full description of the message.
| Number | Msg Type | SQL State | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| 20980 | Error | QXA07 | -1010007L | "The number of blocks (%3) for dbspace '%2' must be less than or equal to the number of blocks in the raw partition (%4). %1" | When creating a dbspace on a raw partition, if the user specifies the dbspace's size, then it must exactly match the size of the raw partition. Click here for a list of possible parameters and odbc states. |
| 20981 | Error | QXA08 | -1010008L | "For an IQ PAGE SIZE of %2, the dbspace '%3' must have at least %4 MB. %1" | The named dbspace must have the stated minimum size in megabytes. Click here for a list of possible parameters and odbc states. |
| 20982 | Error | QSB33 | -1009133L | "You have run out of space during the CHECKPOINT operation. %1" | The checkpoint operation in progress needs to allocate blocks so that it can construct and save required checkpoint information. When space is exhausted during a checkpoint operation, it is not possible to add more space via a CREATE DBSPACE command. Consequently, the checkpoint operation will fail. Click here for a list of possible parameters and odbc states. |
| 20983 | Error | QCA91 | -1013091L | "Column pairs %2=%3 could not be matched. %1" | The columns specified in CREATE JOIN could not be matched in the tables specified. Click here for a list of possible parameters and odbc states. |
| 20984 | Error | QCA92 | -1013092L | "The MONITOR for this database, connection and buffer cache already exists. %1" | A monitor has already been started for this database, connection and buffer cache. Click here for a list of possible parameters and odbc states. |
| 20985 | Warning | 00A93 | 1013093L | "Insert started: %1\n" | This is an informational message displayed during insert. Click here for a list of possible parameters and odbc states. |
| 20986 | Error | QCA94 | -1013094L | "A matching column can not be found for the foreign keys in %2. %1" | This message is returned during CREATE JOIN INDEX when the KEY options is used. Be sure that the tables specified in the join have foreign keys pointing to the table in the message. Click here for a list of possible parameters and odbc states. |
| 20987 | Error | QCA95 | -1013095L | "CREATE JOIN does not support joining joins. %1" | This message is returned during CREATE JOIN INDEX when the left hand side and right hand side of a 'FULL OUTER JOIN' keyword set are both joins ie (A FOJ B) FOJ (C FOJ D) the join of a-b is being joined to c-d. Click here for a list of possible parameters and odbc states. |
| 20988 | Error | QCA96 | -1013096L | "Index %2 could not be created. The datatype does not support an index of %3. %1" | You cannot create an index of the type specified for the column's datatype. Click here for a list of possible parameters and odbc states. |
| 20989 | Error | QTA18 | -1005018L | "Illegal ORDER BY item %2, %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
| 20990 | Error | QNA12 | -1008012L | "This unique index/constraint must be ENFORCED." | This unique index/constraint must be ENFORCED (The UNENFORCED keyword not allowed for this index/constraint). Click here for a list of possible parameters and odbc states. |
| 20991 | Error | QNA13 | -1008013L | "This multi-column unique index/constraint must be UNENFORCED." | This multi-column unique index/constraint must be UNENFORCED (The UNENFORCED keyword is required for this index/constraint). Click here for a list of possible parameters and odbc states. |
| 20992 | Error | QNA14 | -1008014L | "This foreign key must be UNENFORCED." | This foreign key must be UNENFORCED (The UNENFORCED keyword is required for this foreign key). Click here for a list of possible parameters and odbc states. |
| 20993 | Error | QNA15 | -1008015L | "This check constraint must be ENFORCED." | The keyword UNENFORCED is not supported. Click here for a list of possible parameters and odbc states. |
| 20994 | Error | QNA16 | -1008016L | "Cannot ALTER DELETE a column that has a unique or primary key constraint." | Cannot ALTER DELETE a column that has a unique or primary key constraint. This is a duplicate of an SA error code. Click here for a list of possible parameters and odbc states. |
| 20995 | Error | QNA17 | -1008017L | "Cannot ALTER DELETE a column that has multi-column index." | Cannot ALTER DELETE a column that has multi-column index. This is a duplicate of an SA error code. Click here for a list of possible parameters and odbc states. |
| 20996 | Error | QDC36 | -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. |
| 20997 | Error | QDC37 | -1000227L | "Cannot load data with both BINARY and delimited columns. %1" | You cannot load data with both BINARY and delimited columns in the same LOAD command. Click here for a list of possible parameters and odbc states. |
| 20998 | Error | QDC38 | -1000229L | "Only BINARY [WITH NULL BYTE] can be used as a column specification when using UNLOAD FORMAT. %1" | When using UNLOAD FORMAT, you cannot specify any column specification other than BINARY. If need to load null values for a column using the BINARY column spec, you must specify the WITH NULL BYTE option. You cannot use the [ROW] DELIMITED BY options with UNLOAD FORMAT. Click here for a list of possible parameters and odbc states. |
| 20999 | Error | QDC39 | -1000230L | "Columns that allow nulls must use the WITH NULL BYTE option. %1" | The user must use the WITH NULL BYTE option for a BINARY column spec for columns that allow nulls. Click here for a list of possible parameters and odbc states. |