IBM Books

Messages Reference


SQL6500 - SQL6599

SQL6500W RESTARTCOUNT in the load command may cause some problems.

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.

SQL6501N Database name was not given 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.

SQL6502N The path name (parameter: data_path) for data file was not specified.

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.

SQL6504N There are errors in the output node list specification (parameter: outputnodes) in the configuration file.

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.

SQL6505N There are errors in the split node list specification (parameter: splitnodes) in the configuration file.

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.

SQL6506N The program failed to extract partitioning key information for table "<table-name>" from the system catalog table.

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.

SQL6507N Checking level (parameter: check_level) in the configuration file is not valid.

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.

SQL6508N The program failed to create the output pipe for the ftp process.

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.

SQL6509N The program failed to create input pipes for the splitter processes.

Cause: The program can not create temporary input pipes for the splitter processes.

Action: Please ensure your working space is clean.

SQL6510N The program failed to create the temporary directory at local non-NFS space of node "<node-num>".

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.

SQL6511N The program failed to create output for the splitter process at node "<node-num>".

Cause: The program can not create temporary output pipes for the splitter at node "<node-num>".

Action: Please ensure your working space is clean.

SQL6512N The program failed to create input pipes for the merging process at node "<node-num>".

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.

SQL6513N The program failed to create the input pipe for the loading process at node "<node-num>".

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.

SQL6514N The program can not read the node configuration file: "<node-cfg-file>".

Cause: Either the file does not exist, or it is not readable.

Action: Please check the existence and permissions of the node configuration file.

SQL6515N The program failed to find a load command in the 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.

SQL6516N The program failed to connect to database "<db-name>".

Cause: Either the database manager has not been started yet, or it encountered problems.

Action: Check your database manager status.

SQL6517N The program failed to extract the node list, where the table "<tbl-name>" is defined, from the system catalog table.

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.

SQL6518N The record length (reclen in the load command) is not valid.

Cause: Valid record is between 1 to 32768.

Action: Please correct the record length, and rerun the command.

SQL6519N The mode (parameter: mode) "<mode>" in the configuration file is not valid.

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.

SQL6520N The program failed to create output pipes for the process, which generates the header information for split 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.

SQL6521N The configuration file "<cfg-file>" for this program doesn't exist.

Cause: The program needs a configuration file.

Action: Please create a configuration file.

SQL6522N The program found a path name for the input data files in the load command.

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.

SQL6523N The element "<node-num>" in the split node list (parameter: SplitNodes) is not defined in the node configuration (db2nodes.cfg) 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.

SQL6524N The element "<node-num>" in the output node list (parameter: Outputnodes) is not a member of the node list where the table is defined.

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.

SQL6525N The program can not read the input data file "<file-name>".

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.

SQL6526N The program can not write in current working directory "<cwd>".

Cause: The current working directory is not writable.

Action: Please check the permission of current working directory.

SQL6527N The node where statistic data will be collected, (parameter: run_stat_node), is not a member of the output node list.

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.

SQL6528N Record length was not specified in the load command.

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.

SQL6529N The No Header option (NOHEADER) was not specified in 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.

SQL6530N The data type of one partitioning key is float or double.

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.

SQL6531N The program failed to reset tablespace quiesce.

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.

SQL6532N A savecount in the load command can not be set to non-zero.

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.

SQL6533N A restartcount in the load command can not be set to non-zero.

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.

SQL6534N There is an error in the .netrc file "<netrc-file>".

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.

SQL6535N The mode SPLIT_ONLT is not valid.

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.

SQL6536N The program "<progname>" failed to open file "<filename>" for reading.

Cause: An autoloader process can not successfully open a file or pipe for reading.

Action: Please ensure everything is correct in the configuration file.

SQL6537N The program "<progname>" failed to open file "<filename>" for writing.

Cause: An autoloader process can not successfully open a file or pipe for writing.

Action: Please ensure everything is correct in the configuration file.

SQL6538N The program failed to read the split file "<split-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.

SQL6539N There is at least one command in "<cmd-list>" not found in the working environment.

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.

SQL6540N File type "<file-type>" specified in the load command is not valid.

Cause: Valid file types are ASC (positional ASCII) or DEL (delimited ASCII).

Action: Correct the load command in the configuration file.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]