Cause: The data to be loaded has either not been partitioned, or was partitioned with a partitioning map other than the current one for the nodegroup to which the table belongs. The data cannot be loaded.
Action: If the data was not partitioned, use the db2split program to partition the data, then load the partitioned data.
If the data was partitioned, do one of the following:
Cause: The data to be loaded is associated with a node number that differs from the node number of the node to which the application is connected. The data cannot be loaded.
Action: Either find the data file associated with this node and try the request again with that data file, or connect to the node associated with this data file and issue the request at that node.
Cause: A parameter reserved for future capabilities has been set to a value that is not its default value. It should be set to the default value to ensure future compatibility.
Action: Ensure that the parameter "<name>" is set to the value, "<default-value>", then try the request again.
Cause: An unexpected utility error occurred.
Action: Record the message number (SQLCODE) and reason code in the message.
If trace was active, invoke the Independent Trace Facility at the operating system command prompt. See the Administration Guide for information on how to use this facility. Then contact your technical service representative with the following information:
Cause: The load utility does not support the creation of indexes, but the table to be loaded has at least one index defined on it. The index may have been explictly created with the CREATE INDEX statement or implicitly created when a primary key was defined for the table.
Action: Drop all indexes defined on the table with the DROP INDEX statement. Drop the primary key with the ALTER TABLE statement. Resubmit the command.
Use CREATE INDEX and ALTER TABLE as required to recreate indexes and primary key after the load completes successfully.
Cause: No logging is done by the Load utility. If you try to roll forward with a backup made before the load, the operation will fail when it encounters references to the data that was loaded.
Action: To ensure database recoverability after the load, do a backup before the data is modified.
Cause: The data to be loaded was specified as having no header information. However the target table specified is not a single-node table. The data cannot be loaded.
Action: The data must be split using db2split, then loaded without the "NOHEADER" option.
Cause: Either the data was not split with db2split or the db2split operation was not successful.
Action: Use the db2split program to partition the data and then try the request again with the partitioned data. If the insert-column option is being used, ensure that all of the partitioning columns are specified in the column list.
If the problem persists, contact your technical service representative with the following information:
Cause: The partitioning columns specified in the db2split configuration file were not correct. The data was not correctly split.
Action: Do the following:
Cause: In the db2split configuration file:
Action: Do the following:
Cause: The db2split configuration file is not correct.
Action: Do the following:
Cause: When the newlogpath parameter is updated, the system attempts to create a subdirectory under the specified path using the node name as the name of the subdirectory. One of the following operating system errors prevented the creation of the subdirectory:
The requested change is not made.
Action: Do one of the following, then try the request again:
If the problem persists, see your system administrator.
Cause: Three rules govern the settings of some configuration parameters. The rule that would be violated is indicated by the "<reason-code>":
Action: Ensure that the values you specify do not violate any of the above rules, then try the request again.