Messages on this page are sorted by Sybase error code. Locate the appropriate code for a full description of the message.
| Error 1000003 | "Cross-database joins are not supported. (%2 and %3) %1" |
|---|---|
Constant | EMSG_CAT_CROSSDBJOIN |
SAP Sybase Error Number | 20663 |
SQL State | QDA03 |
SQL Code | -1000003L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Fully qualified name of table specified in join. |
Parameter 3 | Fully qualified name of table specified in join. |
Probable Cause | Cannot join tables from different databases. |
| Error 1000004 | "Index '%2' already exists in the catalog. %1" |
|---|---|
Constant | EMSG_CAT_DUPINDEXID |
SAP Sybase Error Number | 20664 |
SQL State | QDA04 |
SQL Code | -1000004L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of index that already exists. |
Probable Cause | This is an internal error. Join processing is trying to create an index id that already exists. If this error occurs, it should be reported to Sybase. |
| Error 1000006 | "Only %2 NULL specifications on a column are permitted. %1" |
|---|---|
Constant | EMSG_TOO_MANY_NULL_STRINGS |
SAP Sybase Error Number | 20666 |
SQL State | QDA06 |
SQL Code | -1000006L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | maximum NULL specifications permitted |
Probable Cause | A column specification in a LOAD statement can have a maximum number of NULL clauses. |
| Error 1000008 | "Unknown error. %1" |
|---|---|
Constant | EMSG_CAT_UNKNOWN |
SAP Sybase Error Number | 20668 |
SQL State | QDA08 |
SQL Code | -1000008L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | An error condition was encountered for which there is no message. If this error occurs, it should be reported to Sybase. |
| Error 1000009 | "Cannot DISABLE index '%2'. It is open Read/Write and may have updates pending. %1" |
|---|---|
Constant | EMSG_CAT_INDEXENABLERW |
SAP Sybase Error Number | 20669 |
SQL State | QDA09 |
SQL Code | -1000009L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Name of the index user is attempting to disable. |
Parameter 2 | The index the user is attempting to disable. |
Probable Cause | This index cannot be DISABLED. It is open for write access and may have updates pending. Wait until no other users are using the index. |
| Error 1000010 | "Cannot DISABLE index '%2'. The index is in use. %1" |
|---|---|
Constant | EMSG_CAT_INDEXENABLESINDEX |
SAP Sybase Error Number | 20670 |
SQL State | QDA10 |
SQL Code | -1000010L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of the index user is attempting to disable. |
Probable Cause | This index cannot be DISABLED. It is in use. Wait until no other users are using the index. |
| Error 1000011 | "Transaction %2 attempted to access '%4' created by transaction %3. %1" |
|---|---|
Constant | EMSG_CAT_FUTUREVERSION |
SAP Sybase Error Number | 20671 |
SQL State | QDA11 |
SQL Code | -1000011L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | The current transaction ID. |
Parameter 3 | The transaction ID that created the object the user is attempting to access. |
Parameter 4 | table name |
Probable Cause | Table Level Versioning doesn't allow access to versions newer than your current transaction ID. |
| Error 1000012 | "Index '%2' cannot be closed because it has %3 users. %1" |
|---|---|
Constant | EMSG_CAT_INDEXINUSE |
SAP Sybase Error Number | 20672 |
SQL State | QDA12 |
SQL Code | -1000012L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | Name of the index that is being closed. |
Parameter 3 | The number of users currently using the index. |
Probable Cause | This is an internal error. The index cannot be closed because it is in use. If this error occurs, it should be reported to Sybase. |
| Error 1000014 | "%2 MB is not sufficient for the load, update, or delete. %1" |
|---|---|
Constant | EMSG_INSUFFICIENT_LOAD_MEMORY |
SAP Sybase Error Number | 20674 |
SQL State | QDA14 |
SQL Code | -1000014L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | user specified upper bound on megabytes of heap memory load/delete/update can actually use |
Probable Cause | The user can control the amount of heap memory a load/delete/update process (LOAD, INSERT VALUE, DELETE, SYNCHRONIZE, UPDATE) can use via the Load_Memory_MB option. If this memory limit isn't sufficient for the load/delete/update to run, then this exception is raised. To proceed, the user must either turnoff the limit (i.e., set Load_Memory_MB to zero) or increase the limit. |
| Error 1000018 | "The object cannot be opened for DROP or ALTER. It is already open. %1" |
|---|---|
Constant | EMSG_CAT_CANNOTOPENFORMETA |
SAP Sybase Error Number | 20678 |
SQL State | QDA18 |
SQL Code | -1000018L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Probable Cause | The object that you have requested to DROP or ALTER cannot be opened for META access. Either the current connection or another connection has a cursor open on the table you are trying to DROP or ALTER or on the table to which the field or index you are trying open for META belongs. In order to proceed, all cursors open on this object must be closed. |
| Error 1000022 | "Index '%2' has an invalid index type: %3. %1" |
|---|---|
Constant | EMSG_CAT_INDEXBADTYPE |
SAP Sybase Error Number | 20682 |
SQL State | QDA22 |
SQL Code | -1000022L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | The index which has a bad type. |
Parameter 3 | The bad index type in question. |
Probable Cause | 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. |
| Error 1000024 | "For table pair %2, table '%3' has a datatype mismatch for column %4. %1" |
|---|---|
Constant | EMSG_CAT_JINDEXDATATYPE |
SAP Sybase Error Number | 20684 |
SQL State | QDA24 |
SQL Code | -1000024L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | tablename |
Parameter 3 | table number |
Parameter 4 | column number |
Probable Cause | 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. |
| Error 1000026 | "The join virtual table for table '%2' has duplicate columns in positions %3 and %4. %1" |
|---|---|
Constant | EMSG_CAT_JINDEXDUPFIELDS |
SAP Sybase Error Number | 20686 |
SQL State | QDA26 |
SQL Code | -1000026L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | tablename |
Parameter 3 | column position |
Parameter 4 | column position |
Probable Cause | The join virtual table for table has duplicate columns. Perhaps the join predicate is improperly specified. |
| Error 1000028 | "For table pair %2, table '%3' has a length value mismatch for column %4. %1" |
|---|---|
Constant | EMSG_CAT_JINDEXKEYSIZE |
SAP Sybase Error Number | 20688 |
SQL State | QDA28 |
SQL Code | -1000028L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | table pair |
Parameter 3 | table name |
Parameter 4 | column number |
Probable Cause | Corresponding columns in the table pair must be of the same length. |
| Error 1000029 | "Cannot open the requested object for write in the current transaction (%2). Another user has write access in transaction %3. %1" |
|---|---|
Constant | EMSG_CAT_ONLY1WRITER |
SAP Sybase Error Number | 20689 |
SQL State | QDA29 |
SQL Code | -1000029L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | location of the exception |
Parameter 2 | The transaction id of the hopeful writer. |
Parameter 3 | The transaction id of the user currently writing. |
Probable Cause | 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. |
| Warning 1000030 | "\nMaster archive header information\n" |
|---|---|
Constant | EMSG__DB_HEADER_MSG1 |
SAP Sybase Error Number | 20690 |
SQL State | QDA30 |
SQL Code | 1000030L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Probable Cause | This is an informational message displayed in context with other messages. |
| Warning 1000032 | "The ultimate/top table is %1\n" |
|---|---|
Constant | EMSG_CAT_JINDEXLOADMSGLINKTABLE1 |
SAP Sybase Error Number | 20692 |
SQL State | 00A32 |
SQL Code | 1000032L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | table name |
Probable Cause | This information message appears in the log when the CREATE JOIN command is executed. |
| Warning 1000033 | "Database: %1" |
|---|---|
Constant | EMSG_DB_HEADER_MSG2 |
SAP Sybase Error Number | 20693 |
SQL State | QDA33 |
SQL Code | 1000033L |
ODBC 2 State | ERROR |
ODBC 3 State | ERROR |
Severity Code | |
Parameter 1 | Database |
Probable Cause | This message is displayed in context with other messages. |
| Warning 1000034 | " Table Name Relationship" |
|---|---|
Constant | EMSG_CAT_JINDEXLOADMSGLINKTABLE3 |
SAP Sybase Error Number | 20694 |
SQL State | 00A34 |
SQL Code | 1000034L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Probable Cause | This information message appears in the log when the CREATE JOIN command is executed. |
| Warning 1000036 | "%1. %2 joined to '%3' %4" |
|---|---|
Constant | EMSG_CAT_JINDEXLOADMSGTABLE |
SAP Sybase Error Number | 20696 |
SQL State | 00A36 |
SQL Code | 1000036L |
ODBC 2 State | OK |
ODBC 3 State | OK |
Severity Code | |
Parameter 1 | argument 1 comment |
Parameter 2 | argument 2 comment |
Parameter 3 | argument 3 comment |
Parameter 4 | argument 4 comment |
Probable Cause | This information message appears in the log when the CREATE JOIN command is executed. |