Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL State | Msg Type | Number | SQL Code | Message | Possible Cause |
|---|---|---|---|---|---|
| QDA77 | Warning | 20737 | 1000077L | "%1, %2%3%4" | This message is displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| QDA78 | Error | 20738 | -1000078L | "IQ PAGE SIZE of '%2' for database '%3' is not valid. %1" | An invalid IQ PAGE SIZE was specified. IQ PAGE SIZE must be one of 1024, 2048, 4096, 8192, 16384, 32768, 65536, 131072, 262144, 524288. See the Reference Manual and Admin and Performance Guide for IQ PAGE SIZE recommendations. Click here for a list of possible parameters and odbc states. |
| QDA79 | Error | 20739 | -1000079L | "IQ SIZE of '%2' for database '%3' is not valid. %1" | The maximum IQ SIZE is 128GB. Click here for a list of possible parameters and odbc states. |
| QDA81 | Error | 20741 | -1000081L | "The field array for table '%2' must have at least 1 entry; it has %3 entries. %1" | This is an internal error. At least one column must be specified to populate a join index. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA82 | Error | 20742 | -1000082L | "The insert must contain all of the table %2 columns because it participates in one or more joins. %1" | If a table participates in a join, then the user cannot load data into that table using a partial width insert. Click here for a list of possible parameters and odbc states. |
| QDA83 | Error | 20743 | -1000083L | "The field array entry must be given a name. %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. |
| QDA84 | Error | 20744 | -1000084L | "The %2th join field array entry for table '%3' must have a name. %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. |
| QDA85 | Error | 20745 | -1000085L | "The join field array for table '%2' must have at least one entry. %1" | This an internal error. If this error occurs, it should be reported to Sybase. Click here for a list of possible parameters and odbc states. |
| QDA86 | Warning | 20746 | 1000086L | "Length %1 %2%3%4" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| QDA87 | Warning | 20747 | 1000087L | "Delimiter %1 %2%3%4" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| QDA88 | Warning | 20748 | 1000088L | "Offset %1, Length %2, %3 nulls, %4%5%6 %7" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| QDA89 | Warning | 20749 | 1000089L | "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. |
| QDA90 | Warning | 20750 | 1000090L | "%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. |
| QDA91 | Warning | 20751 | 1000091L | "%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. |
| QDA92 | Error | 20752 | -1000092L | "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. |
| QDA93 | Warning | 20753 | 1000093L | "%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. |
| QDA94 | Error | 20754 | -1000094L | "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. |
| QDA95 | Warning | 20755 | 1000095L | "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. |
| QDA96 | Warning | 20756 | 1000096L | "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. |
| QDA97 | Error | 20757 | -1000097L | "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. |