SQL6100N The partitioning map in the data file and the partitioning map for the database are not the same.
Explanation: 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.
User Response: 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:
SQL6101N This data file contains data for node "<node-1>" but the Load utility is connected to node "<node-2>".
Explanation: 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.
User Response: 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.
SQL6102W The parameter "<name>" is reserved for future use. Its value should be set to "<default-value>".
Explanation: 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.
User Response: Ensure that the parameter "<name>" is set to the value, "<default-value>", then try the request again.
SQL6103C An unexpected utility error occurred. Reason code = "<reason-code>".
Explanation: An unexpected utility error occurred.
User Response: 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:
SQL6104N The load utility does not support the creation of indexes.
Explanation: 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.
User Response: 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.
SQL6105W The Load utility has completed processing. A Rollforward done to a point in time after the load will not succeed. Take a database backup now if database recoverability is required.
Explanation: 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.
User Response: To ensure database recoverability after the load, do a backup before the data is modified.
SQL6106N The filetype modifier "NOHEADER" was specified, but the nodegroup on which the table is defined is not a single-node nodegroup.
Explanation: 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.
User Response: The data must be split using db2split, then loaded without the "NOHEADER" option.
SQL6107N The partitioning key information in the data file is not correct.
Explanation: Either the data was not split with db2split or the db2split operation was not successful.
User Response: 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:
SQL6108N The number of partitioning keys defined in the data file header ("<number-1>") does not match the number of partitioning keys defined for the table ("<number-2>").
Explanation: The partitioning columns specified in the db2split configuration file were not correct. The data was not correctly split.
User Response: Do the following:
SQL6109N Utility expected partitioning column "<column-name-1>", but found partitioning column "<column-name-2>".
Explanation: In the db2split configuration file:
User Response: Do the following:
SQL6110N Utility expected partitioning column type "<column-type-1>" for column "<column-name-1>", but the data file lists it as type "<column-type-2>".
Explanation: The db2split configuration file is not correct.
User Response: Do the following:
SQL6111N Cannot create a subdirectory under the path specified by newlogpath.
Explanation: 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.
User Response: Do one of the following, then try the request again:
If the problem persists, see your system administrator.
SQL6112N The requested change cannot be done. The resulting configuration parameter settings are not valid. Reason code "<reason-code>".
Explanation: Three rules govern the settings of some configuration parameters. The rule that would be violated is indicated by the "<reason-code>":
User Response: Ensure that the values you specify do not violate any of the above rules, then try the request again.