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 |
|---|---|---|---|---|---|
| 20681 | Error | QNA10 | -1008010L | "A request was made to delete the primary key constraint, but the primary key cannot be found." | The user wanted to delete the primary key constraint on the table but the primary key could not be found. Click here for a list of possible parameters and odbc states. |
| 20682 | Error | QDA22 | -1000022L | "Index '%2' has an invalid index type: %3. %1" | This is an internal error. The index is of a type that is unknown to ASIQ. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| 20683 | Error | QDA23 | -1000023L | "The proposed join does not form a clearly connected list. (table '%2') %1" | Join Indexes can be entered in one of two ways. Using the order of the tables in the SQL statement or using primary<->foreign keys. When using the order method the order determines the relationships between the tables. The order is from a one to many or one to one. It is possible to ask for a join Index that can not be constructed. This error could be from one of the following: 1) The same table is specified twice. 2) The relationships of one to one/many are not consistent with the indexes defined. 3) A table specified has no relation to the tables previously encountered in the syntax. For example: A FULL OUTER JOIN B FULL OUTER JOIN C FULL OUTER JOIN D In this example C has no relation (fields in common) to A or B. The user intended C to Join with D. Some joins can not be defined using the ANSI syntax which depends on order to determine the one to one/many relationship. It is recommended to use the primary and foreign keys syntax to avoid any join definition problems. Click here for a list of possible parameters and odbc states. |
| 20684 | Error | QDA24 | -1000024L | "For table pair %2, table '%3' has a datatype mismatch for column %4. %1" | Corresponding columns' in the table pairs must be of the same datatype. (For example, INTEGER and INTEGER or CHAR and CHAR.) Matching datatypes such as CHAR and VARCHAR or INT and SMALLINT are not allowed. Click here for a list of possible parameters and odbc states. |
| 20685 | Error | QNA11 | -1008011L | "Cannot create the join index because the datatype of the underlying join virtual table column is not equal to the datatype of the corresponding base table column '%1'." | The underlying jvt column and the corresponding base table column must be of the same datatype in order to create a join index. One way to get this error is to create a join index on tables containing FLOAT columns with a client application that uses an open client (isql) or JDBC (Sybase Central) connection. For such connections, the database option FLOAT_AS_DOUBLE defaults to ON thereby creating jvt columns as type DOUBLE for the FLOAT columns in the base tables. To create the join using one of these tools, the user must first set FLOAT_TO_DOUBLE to OFF. See the 'Database Options' chapter in the ASIQ Reference Manual for details on Database Options. Click here for a list of possible parameters and odbc states. |
| 20686 | Error | QDA26 | -1000026L | "The join virtual table for table '%2' has duplicate columns in positions %3 and %4. %1" | The join virtual table for table has duplicate columns. Perhaps the join predicate is improperly specified. Click here for a list of possible parameters and odbc states. |
| 20687 | Error | QDA27 | -1000027L | "The join virtual table '%2' does not have any data. %1" | It was requested that the join index be opened only if it is not empty. 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. |
| 20688 | Error | QDA28 | -1000028L | "For table pair %2, table '%3' has a length value mismatch for column %4. %1" | Corresponding columns in the table pair must be of the same length. Click here for a list of possible parameters and odbc states. |
| 20689 | Error | QDA29 | -1000029L | "Cannot open the requested object for write in the current transaction (%2). Another user has write access in transaction %3. %1" | The ASIQ catalog allows only one transaction at a time to have write access to an object. The id of the user that is currently writing to the object can be found by running sp_iqtransaction and scanning the output for the transaction id of the writer that currently has write access. Click here for a list of possible parameters and odbc states. |
| 20690 | Warning | QDA30 | 1000030L | "\nMaster archive header information\n" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| 20691 | Warning | 00A31 | 1000031L | "Join Index '%1' created from the following join relations:" | This information message appears in the log when the CREATE JOIN command is executed. Click here for a list of possible parameters and odbc states. |
| 20692 | Warning | 00A32 | 1000032L | "The ultimate/top table is %1\n" | This information message appears in the log when the CREATE JOIN command is executed. Click here for a list of possible parameters and odbc states. |
| 20693 | Warning | QDA33 | 1000033L | "Database: %1" | This message is displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| 20694 | Warning | 00A34 | 1000034L | " Table Name Relationship" | This information message appears in the log when the CREATE JOIN command is executed. Click here for a list of possible parameters and odbc states. |
| 20695 | Error | QDA35 | -1000035L | "Using views in CREATE JOIN INDEX is not supported. %1" | Using views in CREATE JOIN INDEX is not supported. Click here for a list of possible parameters and odbc states. |
| 20696 | Warning | 00A36 | 1000036L | "%1. %2 joined to '%3' %4" | This information message appears in the log when the CREATE JOIN command is executed. Click here for a list of possible parameters and odbc states. |
| 20697 | Warning | 00A37 | 1000037L | "------------------------------------------------------------------" | This information message appears in the log when the CREATE JOIN command is executed. Click here for a list of possible parameters and odbc states. |
| 20698 | Warning | QDA38 | 1000038L | "Backup date: %1" | This message displays the backup date. Click here for a list of possible parameters and odbc states. |
| 20699 | Warning | QDA39 | 1000039L | "Backup created by: %1" | This message displays the user who created the backup. Click here for a list of possible parameters and odbc states. |
| 20700 | Warning | QDA40 | 1000040L | "Comment: %1" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |