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 |
|---|---|---|---|---|---|
| 1000089L | Warning | 20749 | QDA89 | "Length %1, %2 nulls, %3%4%5 %6" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| 1000090L | Warning | 20750 | QDA90 | "%1, %2 nulls, %3%4%5 %6" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| 1000091L | Warning | 20751 | QDA91 | "%1, %2 nulls, %3%4%5 %6" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| -1000092L | Error | 20752 | QDA92 | "Table %2 must have a name for the join field array. %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. |
| 1000093L | Warning | 20753 | QDA93 | "%1, %2 nulls, %3%4%5 %6" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| -1000094L | Error | 20754 | QDA94 | "Sufficient memory cannot be found for the LOAD. Increasing the Load_Memory_MB or decreasing the BLOCK FACTOR or BLOCK SIZE will allow the LOAD to proceed. %1" | When the user explicitly sets Load_Memory_MB, the LOAD process applies various heuristics for load parameters in an attempt to find a combination such that the memory required is not more than what the user specified. For a fixed width LOAD, BLOCK FACTOR indicates the minimal number of rows that must be read into memory for each read. The default BLOCK FACTOR is 10,000. Decreasing the BLOCK FACTOR will make the LOAD's internal memory requirements smaller. For a variable length input LOAD, BLOCK SIZE represents the size in bytes in which input data should be read. The default BLOCK SIZE is 500,000 bytes. Decreasing the BLOCK SIZE for a variable width input load will reduce LOAD's memory requirements. Alternatively, the Load_Memory_MB option setting could be raised. Click here for a list of possible parameters and odbc states. |
| 1000095L | Warning | 20755 | QDA95 | "The join index %1 could not be used in the query because it needs synchronization." | A join index was found to help execute the query, but it could not be used because it requires synchronization. Use the SYNCHRONIZE command to synchronize the join index. Click here for a list of possible parameters and odbc states. |
| 1000096L | Warning | 20756 | QDA96 | "Delimiter %1 %2 nulls, %3%4%5 %6" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| -1000097L | Error | 20757 | QDA97 | "Parse Error in Command String at '%2'. %1" | Consult the IQ reference manual for the DBCC grammar Click here for a list of possible parameters and odbc states. |
| -1000098L | Error | 20758 | QDA98 | "Creating a join index on a column of type 'varchar' or 'varbinary' with size > 255 is not supported. %1" | IQ does not support creating a join index on columns that are of datatype 'varchar' whose size is greater than 255. Click here for a list of possible parameters and odbc states. |
| -1000099L | Error | 20759 | QDA99 | "The PAGE SIZE divided by the BLOCK SIZE must be equal to 2, 4, 8, or 16. DATABASE: %2 PAGE SIZE: %3 BLOCK SIZE: %4 %1" | (PAGE SIZE)/(BLOCK SIZE) must be one of 2, 4, 8, 16. Adjust the PAGE SIZE or the BLOCK SIZE in the CREATE DATABASE statement. Click here for a list of possible parameters and odbc states. |
| -1000100L | Error | 20760 | QDB00 | "Cannot INSERT, LOAD, or UPDATE a join virtual table. %1" | The user is not allowed to INSERT to or LOAD a join virtual table. Instead you must INSERT to or LOAD the tables which participate in the join and and execute the SYNCHRONIZE command. Click here for a list of possible parameters and odbc states. |
| -1000101L | Error | 20761 | QDB01 | "%2 not supported by Sybase IQ. %1" | The statement in question is not supported by Sybase IQ. Click here for a list of possible parameters and odbc states. |
| -1000102L | Error | 20762 | QDB02 | "Cannot update table %2 because it is defined in one or more join indexes. %1" | The user cannot update a table that is defined on a join index. Click here for a list of possible parameters and odbc states. |
| -1000103L | Error | 20763 | QDB03 | "Cannot find an index for field '%2'. Every field must have at least one index. Current IndexCount = %3. %1" | This error should not occur during normal operation. Every field in ASIQ will have at least one index (the automatically generated FP index). This error occurs, the operation should be retried. If the error persists, it should be reported to Sybase. Extra information may have been output to the iqmsg file. Click here for a list of possible parameters and odbc states. |
| 1000104L | Warning | 20764 | 01B04 | "in join virtual table '%1'%2" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| 1000105L | Warning | 20765 | 01B05 | "%1" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| -1000106L | Error | 20766 | QDB06 | "Local temporary table, %2, must be committed in order to create an index. %1" | To be able to create an index for a local temporary table, the table must be in a committed state. If this message occurs, the user has tried to execute a CREATE INDEX on a local temporary table that has had data inserted, deleted, or updated that has not yet been committed. Click here for a list of possible parameters and odbc states. |
| 1000107L | Warning | 20767 | 01B07 | "For table '%1' in join virtual table '%2', \n%3 left outer rows with %4 columns will be moved (inserted/deleted).\n" | This is an informational message displayed in context with other messages. The message displays the number of rows moved during an insert to or delete from a join. Click here for a list of possible parameters and odbc states. |
| 1000108L | Warning | 20768 | 01B08 | "The DELETE where clause yielded %1 rows, but table '%2' has no data." | This is an internal error. This warning should not occur during normal use. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |