Messages 1000027 through 1000046

Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL Code Msg Type Number SQL State Message Possible Cause
-1000027L Error 20687 QDA27 "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.

-1000028L Error 20688 QDA28 "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.

-1000029L Error 20689 QDA29 "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.

1000030L Warning 20690 QDA30 "\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.

1000031L Warning 20691 00A31 "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.

1000032L Warning 20692 00A32 "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.

1000033L Warning 20693 QDA33 "Database: %1" This message is displayed in context with other messages.

Click here for a list of possible parameters and odbc states.

1000034L Warning 20694 00A34 " 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.

-1000035L Error 20695 QDA35 "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.

1000036L Warning 20696 00A36 "%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.

1000037L Warning 20697 00A37 "------------------------------------------------------------------" 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.

1000038L Warning 20698 QDA38 "Backup date: %1" This message displays the backup date.

Click here for a list of possible parameters and odbc states.

1000039L Warning 20699 QDA39 "Backup created by: %1" This message displays the user who created the backup.

Click here for a list of possible parameters and odbc states.

1000040L Warning 20700 QDA40 "Comment: %1" This is an informational message displayed in context with other messages.

Click here for a list of possible parameters and odbc states.

1000041L Warning 20701 QDA41 "Backup version: %1" This message displays the backup version.

Click here for a list of possible parameters and odbc states.

1000042L Warning 20702 QDA42 "Number of archive media in backup: %1" This message displays how many media are in the backup.

Click here for a list of possible parameters and odbc states.

1000043L Warning 20703 QDA43 "Number of files in backup: %1" This message displays the number of files in the backup.

Click here for a list of possible parameters and odbc states.

-1000044L Error 20704 QDA44 "The join for table '%2' does not have enough columns defined (%3). %1" Cannot define a join with zero columns. If this error occurs, it should be reported to Sybase.

Click here for a list of possible parameters and odbc states.

-1000045L Error 20705 QDA45 "Index %2 does not exist. %1" User has specified an index which does not exist in any table within the current database.

Click here for a list of possible parameters and odbc states.

-1000046L Error 20706 QDA46 "No Field passed to PutMCIField. %1" This error should not occur during normal operation and should be reported to Sybase. See the iqmsg file for additional diagnostic information.

Click here for a list of possible parameters and odbc states.


Created May 6, 2011. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com