SQL3201N The specified table cannot be replaced because another table is dependent on it.
Cause: A table that is a parent in a relationship with another table cannot be replaced.
The command cannot be processed.
Action: Select a different option, such as INSERT, or select a different target for the utility operation.
SQL3203N The INSERT_UPDATE option is not permitted for the specified target because it has no primary key or all columns are in the primary key.
Cause: The INSERT_UPDATE option is only valid when the target table has a primary key and the target columns include all columns of the primary key. In addition, the target table should contain at least one column that is not part of the primary key.
The command cannot be processed.
Action: Select a different option such as INSERT, or choose a different target for the utility operation.
SQL3204N The INSERT_UPDATE option may not be applied to a view.
Cause: The INSERT_UPDATE option is not valid for views and a view has been selected as the target of the utility operation.
The command cannot be processed.
Action: Select a different option such as INSERT, or choose a different target for the utility operation.
SQL3205N The specified view cannot be replaced because the base table has a dependent.
Cause: A view whose base table is a parent table in a referential relationship with any table (including itself) cannot be replaced.
The command cannot be processed.
Action: Select a different option such as INSERT, or choose a different target for the utility operation.
SQL3206N The specified view cannot be replaced because its definition involves a subquery.
Cause: A view whose definition involves a subquery cannot be replaced. If the view definition depends on the definition of other views, the other views cannot contain subqueries. The use of a subquery anywhere in the definition of any view on which the target view is based prohibits the REPLACE option.
The command cannot be processed.
Action: Select a different option, such as INSERT, or choose a different target for the utility operation.
SQL3220W Volume <volume-name> was not found in the <directory-name> directory. Copy the volume into this directory and continue the LOAD/IMPORT.
Cause: An attempt to LOAD/IMPORT a multiple IXF file was made, but one of the files is missing from the directory specified. LOAD/IMPORT tries to find the parts in the same directory as the first part.
The import will terminate.
Action:
SQL3221W ...Begin COMMIT WORK. Input Record Count = <count>
Cause: The import is about to attempt a COMMIT of the work performed.
Action: If the SQL3222W message is not printed immediately after this message, then the COMMIT failed and you will need to check your table or view to see which records have been imported. You can then start the import again with a RESTARTCOUNT set to the number of records successfully imported to skip those rows and import the rest of the file. (If you had been doing a CREATE or REPLACE_CREATE or REPLACE, call the second import with INSERT option.)
SQL3222W ...COMMIT of any database changes was successful.
Cause: The COMMIT was successful.
Action: None necessary if you get this message.
SQL3223N The parameter of type pointer to <parameter> is not specified properly.
Cause: The parameter of type <parameter> is not specified properly. The types are one of "struct sqluimpt_in", "struct sqluimpt_out", "struct sqluexpt_out", "struct sqluload_in", "struct sqluload_out", "struct sqluunld_in", or "struct sqluunld_out". The pointer should be either a NULL pointer or should point to the appropriate structure and its sizeOfStruct field should be initialized to one of SQLUIMPT_IN_SIZE for struct sqluimpt_in, SQLUIMPT_OUT_SIZE for struct sqluimpt_out, SQLUEXPT_OUT_SIZE for struct sqluexpt_out, SQLULOAD_IN_SIZE for struct sqluload_in, SQLULOAD_OUT_SIZE for struct sqluload_out, SQLUUNLD_IN_SIZE for struct sqluunld_in or SQLUUNLD_OUT_SIZE for struct sqluunld_out.
The command cannot be processed.
Action: Call the utility again with a proper parameter.
SQL3225N The RESTARTCOUNT value is greater than the number of rows in the file. No rows were loaded.
Cause: The utility was called with a RESTARTCOUNT value which was greater than the number of rows in the input file resulting in no rows being loaded into the table/view.
Action: Ensure that the RESTARTCOUNT value is correct or call the utility again with the REPLACE or INSERT option and a correct RESTARTCOUNT value.
SQL3250N COMPOUND="<value>" is an invalid value or is not allowed in conjunction with other import parameters.
Cause: The COMPOUND=x option was specified for the import utility and cannot be processed due to one of the following reasons:
Action: Change the filetmod option to correct the usage of COMPOUND=x.
SQL3251N "number" more errors occurred during the import.
Cause: The utility encountered more errors than can be relayed in the sqlca (maximum number is 7) while using the COMPOUND option. Messages for these errors will not be printed to the message file.
The utility continues processing.
Action: If you desire all the error messages for each row inserted during an import, do not use the COMPOUND option or use a COMPOUND value less than or equal to 7.