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.
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.
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.
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.
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.
Cause: The traversal-order-list/subtable-list provided is invalid.The explanation for the reason code is:
Action: The user action, based on the reason code, is:
Cause: User specified to import data from typed tables into regular table. Please note, object_id column will not be cast while importing.
Action: Please make sure such operation is intentional.
Cause: When CREATE option is used, neither subtable name nor attribute names can be renamed.
Action: Please check your IMPORT command and make sure no subtable-list is specified.
Cause: "<option>" is not compatible with hierarchy in EXPORT, IMPORT, or LOAD.
Action: Please check the command syntax for hierarchical support.
Cause: LOAD does not support typed tables. Please consider IMPORT instead.
Action: Please use IMPORT to bring hierarchical data into the database.
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:
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.)
Cause: The COMMIT was successful.
Action: None necessary if you get this message.
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.
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.
Cause: An error or warning was encountered during LOAD, IMPORT or EXPORT of a table. CPU parallelism was greater than 1 at the time the problem was encountered, and an SQL message was written which identified the user record with a special unique token. This message serves to map the unique record token to the record number of the source user data.
Action: Refer to the original SQL message returned for appropriate action.
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.
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.