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 |
---|---|---|---|---|---|
QFA47 | Error | 21097 | -1001051L | "Query returns %2 data > 2GB. Use %3 %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QFA48 | Error | 21098 | -1001052L | "Parameter %2 must be long binary/varchar type. %3 %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QFA49 | Error | 21099 | -1001053L | "Wrong number of parameters to function %2 %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QFA50 | Error | 21100 | -1001054L | "You cannot specify long binary/varchar column in the ORDER/GROUP by clause or in an aggregate function. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QFA51 | Warning | 21101 | 1001055L | "An error occurred loading %1 column, %2, for %3, rowid %4. " | No additional information available. Click here for a list of possible parameters and odbc states. |
QFA52 | Warning | 21102 | 1001056L | "An error occurred extracting %1 column, %2, for %3. " | No additional information available. Click here for a list of possible parameters and odbc states. |
QFA53 | Error | 21103 | -1001057L | "You must use BFILE() to extract %2 column. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QFA54 | Error | 21104 | -1001058L | "The secondary file name, %2, is too long. %1" | No additional information available. Click here for a list of possible parameters and odbc states. |
QFA55 | Error | 20560 | -1001061L | "extract error: incorrect \"%2\" size: valid sizes \"0 to %3\" %1" | either a column delimeter or a row delimiter is of incorrect length Click here for a list of possible parameters and odbc states. |
QFA56 | Error | 20561 | -1001063L | "Encrypt/Decrypt: Currently only AES algorithm is supported." | when the algorithm string is other than AES. Click here for a list of possible parameters and odbc states. |
QFA57 | Error | 20562 | -1001064L | "Decryption error: %2. %1" | An error occurred during decryption. Click here for a list of possible parameters and odbc states. |
QFA58 | Error | 20563 | -1001065L | "Encryption/Decryption for %2 datatype is not supported. %1" | An error occurred during encryption/decryption. Click here for a list of possible parameters and odbc states. |
QFA59 | Error | 20564 | -1001066L | "Encrypt/Decrypt Error: %2. %1" | An error occurred during encryption/decryption. Click here for a list of possible parameters and odbc states. |
QFA60 | Error | 20565 | -1001067L | "Encrypt/Decrypt Error: %2. %1" | An error occurred during encryption/decryption. Click here for a list of possible parameters and odbc states. |
QFA61 | Error | 20567 | -1001068L | "Datatype, %2 is not supported for this operation. %1" | The reported datatype is not supported by Sybase IQ. Click here for a list of possible parameters and odbc states. |
QFA62 | Error | 2822 | -1320L | "Error raised by user-defined function: %1" | An error was raised by a user-defined function. Click here for a list of possible parameters and odbc states. |
QFA63 | Error | 20569 | -1001070L | "Unable to load shared library for user-defined function. %1" | Shared library for the UDF could not be loaded. Click here for a list of possible parameters and odbc states. |
QFA64 | Error | 20572 | -1001071L | "No valid license found for user-defined function. Feature: %2 %1" | No valid license found for UDF feature. Click here for a list of possible parameters and odbc states. |
QFA65 | Error | 20573 | -1001072L | "User-defined function %2 internal programming error. %3 . %1" | User-defined function has an internal programming error. Click here for a list of possible parameters and odbc states. |
QFA66 | Error | 20574 | -1001073L | "The result datatype for function '%2' exceeds the maximum supported numeric precision of 255. Please set the proper value for precision in numeric function, %1" | Precision requested for numeric function is larger than what is allowed. Please set the proper value for precision if not set. Click here for a list of possible parameters and odbc states. |