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 |
|---|---|---|---|---|---|
| QDC23 | Error | 20883 | -1000223L | "Column name '%2' is invalid. The column name must follow the format [OWNER.]TABLE.COLUMN. %1" | The column name must follow the format [OWNER.]TABLE.COLUMN. Click here for a list of possible parameters and odbc states. |
| QDC25 | Error | 20885 | -1000225L | "Cannot open table %2. The table has already been opened by a cursor declared FOR UPDATE in transaction %3. %1" | A table opened by a CURSOR that has been declared FOR UPDATE cannot be opened again by another operation. Click here for a list of possible parameters and odbc states. |
| QDC28 | Error | 20888 | -1000228L | "JP4&5" | This is an informational message displayed in context with other messages. Click here for a list of possible parameters and odbc states. |
| QDC31 | Error | 20891 | -1000231L | "You do not have permission to create join index %2%3%4. %1" | A user can only create a join index under the following conditions 1) They are the DBA account 2) They have DBA authority. 3) They did not specify a creator and have RESOURCE authority 4) The specified creator is the same as the current user and they have RESOURCE authority. Click here for a list of possible parameters and odbc states. |
| QDC32 | Error | 20892 | -1000232L | "Partial input record skipped at EOF. %1" | A partial input record was detected during a 'load' operation. This can occur as a result of an OS/hardware error or simply because the input data file was missing values for one or more columns in the table. Click here for a list of possible parameters and odbc states. |
| QDC33 | Error | 20893 | -1000233L | "Cannot SYNCHRONIZE join index %2. %1" | The requested SYNCHRONIZE operation for the named join index failed because not all read-write locks could be obtained for all tables and related joins/tables in the join indexes' transitive closure. Try the SYNCHRONIZE operation later when there are no access conflicts with other users. Click here for a list of possible parameters and odbc states. |
| QDC34 | Error | 20723 | -1000063L | "Cannot enforce the NOT NULL constraint. Column %2 has NULL data. %1" | The user tried ALTER MODIFY column NOT NULL on a column that used to allow nulls and has null data. The user has to first delete the null rows before altering the column to enforce the NOT NULL constraint. Click here for a list of possible parameters and odbc states. |
| QDC35 | Error | 20722 | -1000062L | "Cannot add column '%3' with 'not null' constraint on table %2 with data. %1" | The user tried to ALTER ADD a NOT NULL column to a table that has data. The newly added column would violate the NOT NULL constraint as it would have null data. Click here for a list of possible parameters and odbc states. |
| QDC36 | Error | 20996 | -1000226L | "The LOCATION string passed to the attached database insert is invalid. %1" | The user passed an invalid LOCATION string in an attached database insert. Check the format of the string. It must be of the form "servername.dbname". Click here for a list of possible parameters and odbc states. |
| QDC37 | Error | 20997 | -1000227L | "Cannot load data with both BINARY and delimited columns. %1" | You cannot load data with both BINARY and delimited columns in the same LOAD command. Click here for a list of possible parameters and odbc states. |
| QDC38 | Error | 20998 | -1000229L | "Only BINARY [WITH NULL BYTE] can be used as a column specification when using UNLOAD FORMAT. %1" | When using UNLOAD FORMAT, you cannot specify any column specification other than BINARY. If need to load null values for a column using the BINARY column spec, you must specify the WITH NULL BYTE option. You cannot use the [ROW] DELIMITED BY options with UNLOAD FORMAT. Click here for a list of possible parameters and odbc states. |
| QDC39 | Error | 20999 | -1000230L | "Columns that allow nulls must use the WITH NULL BYTE option. %1" | The user must use the WITH NULL BYTE option for a BINARY column spec for columns that allow nulls. Click here for a list of possible parameters and odbc states. |
| QDC40 | Error | 21000 | -1000234L | "The record size of the unloaded data: %2, does not match the record size of the load: %3. %1" | The record size of the unloaded data does not match the size of the record described by the LOAD command. Click here for a list of possible parameters and odbc states. |
| QDC41 | Warning | 20901 | 1000241L | "The insert to the table will be single threaded." | There are not enough threads available to do a multithreaded insert or load. The number of users doing parallel processing has limited the number of threads available for your insert/load. The insert/load will proceed, but will be done serially. Click here for a list of possible parameters and odbc states. |
| QDC42 | Error | 21001 | -1000235L | "The total number of columns of unloaded data: %2, does not match the total number of columns in the load: %3. %1" | The total number of columns in the unloaded data does not match the number of columns in the LOAD command. Click here for a list of possible parameters and odbc states. |
| QDC43 | Error | 21002 | -1000236L | "The total number of null columns in the unloaded data, %2, does not match the total number of null columns in the LOAD command, %3. %1" | The total number of null columns in the unloaded data does not match the number of null columns in the LOAD command. Click here for a list of possible parameters and odbc states. |
| QDC44 | Error | 21003 | -1000237L | "The total number of variable width columns in the unloaded data, %2, does not match the total number of variable width columns in the LOAD command, %3. %1" | The total number of variable width columns in the unloaded data does not match the number of variable width columns in the LOAD command. Click here for a list of possible parameters and odbc states. |
| QDC45 | Error | 21009 | -1000238L | "The platform type of the unloaded data, %2, does not match the platform type on the load, %3. %1" | The Platform ID of unloaded data does not match the Platform ID of load. The LOAD command detected that the platform on which the UNLOAD was performed, is not the same platform on which the LOAD is being attempted. Cross platform UNLOAD-LOAD cannot be done. Click here for a list of possible parameters and odbc states. |
| QDC46 | Error | 21010 | -1000239L | "UNLOAD version number: %2, does not match the LOAD version number: %3. %1" | The UNLOAD version number does not match the LOAD version number. The version number of the data on the tape being read does not match the version number of the LOAD command. The version numbers must match before the data on the tape can be loaded. Click here for a list of possible parameters and odbc states. |
| QDC47 | Error | 21011 | -1000240L | "The total number of blocks of unloaded data: %2, does not match the total number of blocks loaded: %3. %1" | Total number of blocks of unloaded data on the tape does not match the number of blocks of data that were just loaded. Click here for a list of possible parameters and odbc states. |