Cause: Since multiple loading processes for the same table are completely independent, it is almost impossible to have an identical restartcount for those multiple loading processes.
Action: Please make sure you have the correct load command in the configuration file.
Cause: Database name has to be specified in the configuration file.
Action: Please specify the database name and rerun the command.
Cause: If the input data file is remote, the file will be transferred locally. The path to the file on the remote machine must be supplied.
Action: Please specify the path name to the remote data file and rerun the command.
Cause: The output node list specification is not valid.
Action: Check the sample configuration file, correct your output node list specification, and rerun the command.
Cause: The split node list specification is not valid.
Action: Check the sample configuration file, correct your split node list specification, and rerun the command.
Cause: Either the table is not defined, or it is not defined in an MPP environment.
Action: Make sure you have the table properly defined.
Cause: Checking level (parameter: check_level) can be either CHECK or NOCHECK. The default is CHECK.
Action: Correct the parameter in the configuration file, and rerun the command.
Cause: If input data files are remote, they will be transferred to a local pipe. If this local pipe already exists, the process will fail.
Action: Please ensure your working space is clean.
Cause: The program can not create temporary input pipes for the splitter processes.
Action: Please ensure your working space is clean.
Cause: The program needs a temporary working directory at local non-NFS space of all splitting and output nodes.
Action: Please ensure your working space is clean.
Cause: The program can not create temporary output pipes for the splitter at node "<node-num>".
Action: Please ensure your working space is clean.
Cause: The program can not create temporary input pipes for the merging process at node "<node-num>".
Action: Please ensure your working space is clean.
Cause: The program can not create temporary input pipe for the loading process at node "<node-num>".
Action: Please ensure your working space is clean.
Cause: Either the file does not exist, or it is not readable.
Action: Please check the existence and permissions of the node configuration file.
Cause: A CLP load command must be supplied in the configuration file.
Action: Please specify a CLP load command in the configuration file.
Cause: Either the database manager has not been started yet, or it encountered problems.
Action: Check your database manager status.
Cause: Either the table is not defined, or it is not defined in an MPP environment.
Action: Check how the table was defined in the database.
Cause: Valid record is between 1 to 32768.
Action: Please correct the record length, and rerun the command.
Cause: The running mode of this program can be: SPLIT_ONLY, LOAD_ONLY, SPLIT_AND_LOAD (default), or ANALYZE.
Action: Please correct the mode in the configuration file.
Cause: The program can not create output pipes for the process, which generates the header information for split file.
Action: Please ensure your working space is clean.
Cause: The program needs a configuration file.
Action: Please create a configuration file.
Cause: Path name for input data files in the load command is not allowed. There is a separate parameter (data_path) for this purpose.
Action: Please correct the configuration file.
Cause: All nodes in the split node list must have an entry in the node configuration file.
Action: Please correct your split node list.
Cause: All nodes in the output node list must be members of the node list where the table is defined.
Action: Please correct your output node list.
Cause: Either the input data file was not found, or it is not readable.
Action: Please check the existence and permissions of the input data file.
Cause: The current working directory is not writable.
Action: Please check the permission of current working directory.
Cause: The node where statistic data will be collected must be a member of the output node list.
Action: Please correct the run_stat_node parameter.
Cause: If the BINARYNUMERICS or PACKEDDECIMAL modifier is specified in the load command, record length (reclen) must be specified in the load command as well.
Action: Please correct the load command.
Cause: If a table is defined in a single node nodegroup, the NOHEADER modifier must be specified in the load command.
Action: Please correct the load command.
Cause: If the input file is a non-binary data file, float or double columns can not be defined as partitioning key.
Action: Supply a binary data file, or change the definition of your table.
Cause: There are probably on-going loading processes. Make sure all previous loading processes are completed before another autoloader session can be started.
Action: Check the processes status on your machine.
Cause: The savecount in the load command can not be set to non-zero if there are multiple splitting nodes, the mode is SPLIT_AND_LOAD, and the command is either a REPLACE INTO or INSERT INTO load command.
Action: Please correct the load command.
Cause: Because multiple splitting nodes produce random order of records for loading process(es), using RESTART INTO with a restartcount can not guarantee a successful recovery.
Action: Please correct the load command.
Cause: Either the .netrc file could not be found, or there is no entry for remote host "<machine>", or the permissions of the file are not correct.
Action: Please check the existence and permission of the .netrc file.
Cause: If a table is defined in a single node nodegroup, either splitting or analyzing is not necessary.
Action: Please change the mode from SPLIT_ONLT to LOAD_ONLY or SPLIT_AND_LOAD.
Cause: An autoloader process can not successfully open a file or pipe for reading.
Action: Please ensure everything is correct in the configuration file.
Cause: An autoloader process can not successfully open a file or pipe for writing.
Action: Please ensure everything is correct in the configuration file.
Cause: When the program is invoked in LOAD_ONLY mode, the input data file must have already been split, and all split files must be readable by the program.
Action: Check whether or not the input data file has been split, and the access permissions of the resulting split files.
Cause: The execution of this program depends on a number of common Unix commands. The process fails if any one of them is not available in the working environment.
Action: Make sure you have all necessary commands properly installed on your system.
Cause: Valid file types are ASC (positional ASCII) or DEL (delimited ASCII).
Action: Correct the load command in the configuration file.
Cause: The file name and path for the partitioning map could not be opened. An error occurred.
Action: Confirm that the partitioning map file name and file path were specified correctly and that the file can be openned for writing.
Cause: A filesystem error occurred when writing to the partitioning map file.
Action: Check that the file path is correct, and that the target device has sufficient space to hold the partitioning map output.
Cause: The file name and path for a temporary file could not be opened. An error occurred.
Action: Confirm that the utility temporary file storage path was specified correctly and that the path allows for files to be openned for writing.
Cause: A filesystem error occurred when writing to a temporary file.
Action: Check that the file path is correct, and that the target device has sufficient space for the file data.
Cause: The utility attempted to start a child process on a different database partition, but an error occurred.
Action:
Cause: The utility encountered an error attempting one of the following operations:
Action:
Cause: An incomplete data record was found at the end of a data file provided to the utility by the user.
Action: Examine the source data for syntactical correctness.
Cause: The utility attempted to determine a default node number, but was unable to.
Action: State source and target node numbers explicitly in the utility configuration file, or contact DB2 Service for assistance.
Cause: The utility attempted to determine the current working directory and/or drive but encountered an error.
Action: Contact DB2 Service for assistance.
Cause: The user specified a command line option for the Autoloader utility which is either not supported, or obsolete.
Action: Refer to the Autoloader documentation, or online help, for the supported options and features.
Cause: A node specified as an execution node for splitting does not appear to be a member in the db2nodes.cfg file. The work inteded to complete on this node can not be started.
Action: Add the node to the node list definition in the db2nodes.cfg file, or specify an alternate node for the split operation which is a member of the node configuration.
Cause: A node was specified as a target node for loading, but this node is apparently not a member of the node group being loaded.
Action: Check the nodegroup definition and confirm that the target node specified for loading is part of this nodegroup. If the node is not part of the nodegroup correct the utility target node specification to include the correct list of nodes. If the node is part of the nodegroup, please contact DB2 Service for assistance.
Cause: The utility attempted to retrieve the instance name but encountered an error.
Action: Confirm that the utility is running on a node with DB2 installed, and a valid instance is running. For additional help, please contact DB2 Service.
Cause: The utility attempted to retrieve the current user ID for the ID, but an error was encountered.
Action: Contact DB2 Service.
Cause: The user supplied an explicit password to the utility, but the password is not valid.
Action: Supply a valid password.
Cause: The Autoloader configuration file is a user supplied file which contains the LOAD command to be executed, the target database, and a several optional parameters that the user may specify. The sample configuration file, 'autoloader.cfg', supplied in the samples directory contains inline comments which describe the available options and their defaults.
Action: Refer to the DB2 documentation for further details about the Autoloader utility.
Cause: The LOAD command is missing from the Autoloader configuration file. The parameter must be specified.
Action: Ensure that you have specified the correct configuration file for the Autoloader, and that the LOAD command is specified inside.
Cause: An option parameter was specified multiple times inside the Autoloader configuration file.
Action: Correct the configuration file so that each option appears at most only once.
Cause: The Autoloader is starting the LOAD operation on each of the target LOAD partitions.
Action: This is an informational message.
Cause: The Autoloader is now issuing the split operation on each of the target split partitions.
Action: This is an informational message.
Cause: The Autoloader is waiting for all splitters to complete.
Action: This is an informational message.
Cause: The Autoloader is waiting for LOAD operations to complete.
Action: This is an informational message.
Cause: The LOAD operation has begun on the specified partition.
Action: This is an informational message.
Cause: The remote execution of the splitter utility on the specified partition has completed.
Action: This is an informational message.
Cause: This information is generated periodically to provide status to the user on the progress of large Autoloader jobs.
Action: This is an informational message.
Cause: This message is written at the completion of the Autoloader run to indicate the total volume of user data that has been processed.
Action: This is an informational message.
Cause: The following is an explanation of the reason code "<reason-code>":
Action: Ensure that you are running on an operating system which supports threaded applications, and that your thread limit per process is sufficient. The thread requirements are as follows:
Cause: The ROWCOUNT option in the load command is not supported in the autoloader program.
Action: Correct your load command in the autoloader configuration file, and resubmit your command.