Explanation

No RESTART or TERMINATE is necessary. The RESTART and TERMINATE modes of the LOAD utility should be used to resume or cancel a previously failed/interrupted LOAD operation. They are only supported on tables where a previous load operation failed and the table is in LOAD PENDING state. For tables that are not in LOAD PENDING state, only the INSERT and REPLACE modes of the LOAD utility are supported.

Explanation

This is an informational message indicating that a DB2 agent is about to begin on a given partition.

Explanation

This is an informational message indicating that an DB2 agent is about to begin on a given partition.

Explanation

The load utility analyzes the input data to determine the best encoding schemes for building column compression dictionaries. To build the best dictionaries and get the maximum possible compression, the entire set of data should be loaded at one time and enough utility heap memory should be available.

These message is return when the LOAD operation completed successfully but the compression dictionary that was built is not optimal for compression because of insufficient utility heap memory.

Explanation

You can efficiently move a large amount of data into a table by using the load utility.

In a partitioned database environment, you can perform a load operation on only a subset of the database partitions on which the table is defined by specifying the PARTITIONED DB CONFIG parameter with the LOAD command.

You can cause the load utility to build a new dictionary for the table by specifying one of the following parameters with the LOAD command: RESETDICTIONARY, RESETDICTIONARYONLY.

This message is returned when an attempt is made to load data into a column-organized table with the following unsupported combination of parameters passed to the LOAD command:

• The PARTITIONED DB CONFIG parameter is specified with a value of OUTPUT_DBPARTNUMS
• And either the RESETDICTIONARY parameter or the RESETDICTIONARYONLY parameter is specified

Explanation

This is an informational message indicating the record length used for the Load operation.

Explanation

This is an informational message indicating whether truncation checking is enabled or not.

Explanation

This is an informational message indicating that tracing is enabled for the first numofrecords record(s).

Explanation

This is an informational message indicating what delimiters are used for string, column and decimal point. In addition, this message also shows tracing is enabled for the first numofrecords record(s).

Explanation

This informational message indicates the input partition map file was opened successfully for reading.

Explanation

This informational message indicates that reading of the input partition map file is in progress.

Explanation

This informational message indicates that the input partition map file was successfully read.

Explanation

This informational message indicates the mode of operation for the partitioning agent.

Explanation

This is an informational message indicating that the output partitioning map file is not used.

Explanation

This is an informational message indicating that the output partitioning map file was opened successfully.

Explanation

You can cause the load utility to build a new dictionary for a table by specifying one of the following parameters with the LOAD command: RESETDICTIONARY, RESETDICTIONARYONLY. If no dictionary exist, then any LOAD command with either the INSERT parameter or the REPLACE parameter will build one.

This message is returned when the following sequence of events occurs:

1. The LOAD command is issued against a column-organized table that causes a new dictionary to be built.
2. The load operation fails.
3. The LOAD command is reissued for the same table, with one of the following parameter combinations specified:
   • The KEEPDICTIONARY parameter
   • The TERMINATE parameter in combination with the DBPARTNUM parameter

If the LOAD command is issued against a column-organized table, that causes a new dictionary to be built, and the operation fails, then the LOAD command may be reissued for the same table, but with the following restrictions:

• The KEEPDICTIONARY parameter may not be specified
• The TERMINATE parameter may not be specified in combination with the DBPARTNUM parameter

Explanation

This is an informational message indicating the name of the distribution file used in the utility.

Explanation

This informational message indicates the distribution file was opened successfully for writing.

Explanation

This informational message indicates the number of partitioning keys used in the utility.

Explanation

This informational message describes attributes of a partitioning key.

Explanation

This is an informational message indicating that the output data files are not created because the mode of operation is ANALYZE.

Explanation

The inability to convert the value might be due to a data type mismatch, such as trying to load a date into a Boolean column.

If the source of the value that could not be converted is:

• A delimited ASCII (DEL) file, the indicated column number identifies the ordinal position of the field that contains that value
• An ASCII file, the indicated column number identifies the byte location of the beginning of the field that contains that value

Explanation

The inability to convert the value might be due to a data type mismatch, such as trying to load a date into a Boolean column.

If the source of the value that could not be converted is:

• A delimited ASCII (DEL) file, the indicated column number identifies the ordinal position of the field that contains that value
• An ASCII file, the indicated column number identifies the byte location of the beginning of the field that contains that value

Explanation

This is an informational message indicating that the output data on partition partitionnum will be sent to standard output.

Explanation

This is an informational message indicating that numofrecords records (or lines) were processed.

Explanation

This informational message indicates which record is being processed. This message will only be reported when the TRACE option is specified.

Explanation

This informational message reports the result of the hashing function in both hex and decimal format.

Explanation

A record was rejected during load while attempting to determine what partition the record belongs to. If the 'dumpfile' load modifier was specified, the rejected record can be found in the partition-relative dumpfile at the partition-relative record number rec-num listed in this message.

An explanation of the error specified by the reason-code is as follows:

1. The string representation of the data type of a partitioning column is invalid. Either the syntax is invalid or the value is out of range.
2. The column values corresponding to the partitioning keys are not contained within the first 32K of the record.
3. The record is empty (all space characters).
4. The record length does not match the expected length.
5. The record is incomplete.
6. An error occurred while processing a generated column value.

Explanation

This is an informational message indicating that the output partition map is written to filename.

Explanation

This is an informational message indicating that the distribution map is written to filename.

Explanation

This is an informational message indicating that an DB2 agent has just completed operation on a given partition.

Explanation

This informational message reports the total time elapsed.

Explanation

This is an informational message indicating the throughput of a given DB2 agent.

Explanation

This informational message indicates the number of records processed for a given partition.

Explanation

This informational message indicates the utility program has terminated abnormally.

Explanation

This informational message reports there are number-of-warnings warning message(s) and number-of-rejected-records rejected record(s) encountered during the operation.

Explanation

This informational message reports the attributes of a given partition key.

Explanation

The input data file specified at line linenum of the configuration file is ignored. The command line option will be used if it is specified; otherwise, the first specification of input data file in the configuration file will be used.

Explanation

The output data file specified at line linenum of the configuration file is ignored. The command line option will be used if it is specified; otherwise, the first specification of output data in the configuration file will be used.

Explanation

The distribution file specified at line linenum of the configuration file is ignored. The command line option will be used if it is specified; otherwise, the first specification of distribution file in the configuration file will be used.

Explanation

Explanation

This informational message reports that the NEWLINE flag is ignored for binary or delimited input data files.

Explanation

This informational message reports that the NEWLINE flag is in effect.

Explanation

Explanation

The partitioned database configuration option named in the error message is incorrectly specified or is incompatible with one of the other load options specified.

The possible reason codes are as follows:

1

Partitioned database configuration options cannot be specified in a non-partitioned database environment or when the DB2_PARTITIONEDLOAD_DEFAULT registry variable is set to OFF.

2

Partitioned database configuration options may not be specified more than once.

3

Invalid pointer detected in the piPartLoadInfoIn input structure passed to the db2Load API.

4

Invalid pointer detected in the poPartLoadInfoOut output structure passed to the db2Load API.

5

The argument supplied to the MODE option must be one of the following:

• PARTITION_AND_LOAD
• PARTITION_ONLY
• LOAD_ONLY
• LOAD_ONLY_VERIFY_PART
• ANALYZE

6

The maximum number of partitioning agents must be less than or equal to the maximum number of partitions allowable in a cluster.

7

The maximum number of partition numbers in a partition list must be less than or equal to the maximum number of partitions allowable in a cluster.

8

The arguments supplied to the ISOLATE_PART_ERRS option must be one of the following:

• SETUP_ERRS_ONLY
• LOAD_ERRS_ONLY
• SETUP_AND_LOAD_ERRS
• NO_ISOLATION

9

The value supplied to the STATUS_INTERVAL option must be in the range 1-4000.

10

The maximum port number must be greater than or equal to the minimum port number.

11

The only legal arguments for the CHECK_TRUNCATION, NEWLINE and OMIT_HEADER options are TRUE and FALSE.

12

The argument supplied to RUN_STAT_DBPARTNUM must be a legal partition number.

13

If the mode is ANALYZE, the MAP_FILE_OUTPUT option must be specified.

14

If the mode is PARTITION_ONLY or LOAD_ONLY and a remote client is being used, then the PART_FILE_LOCATION option must be specified. If the mode is PARTITION_ONLY or LOAD_ONLY then if the file type is CURSOR, the PART_FILE_LOCATION option must be used and must specify a file name.

15

The load actions RESTART and TERMINATE can only be used when the mode is PARTITION_AND_LOAD, LOAD_ONLY or LOAD_ONLY_VERIFY_PART.

16

The HOSTNAME option cannot be specified unless the FILE_TRANSFER_CMD option is also specified.

17

The partition isolation error modes LOAD_ERRS_ONLY and SETUP_AND_LOAD_ERRS cannot be used when both the ALLOW READ ACCESS or COPY YES options of the load command are used.

18

The LOAD_ONLY and LOAD_ONLY_VERIFY_PART modes are not compatible with the CLIENT option of the load command.

18

The partitioned database configuration option is not allowed on a random distribution table using the random by generation method.

Explanation

When loading from an input file of type CURSOR, the PART_FILE_LOCATION option must specify a fully qualified base filename instead of a directory.

Explanation

The ROWCOUNT option of the load command is not supported except when the mode is ANALYZE.

Explanation

A Load was issued with the COPY NO parameter, but the value of the DB2_LOAD_COPY_NO_OVERRIDE registry variable was not valid.

Explanation

A Load command was issued with the COPY NO parameter, however the DB2_LOAD_COPY_NO_OVERRIDE registry variable overrides the parameter.

Explanation

The COPY NO recoverability parameter of the Load has been converted to NONRECOVERABLE. This occurred because the Load was issued within an HADR environment and the DB2_LOAD_COPY_NO_OVERRIDE registry variable was not set.

Explanation

An incompatible combination of import options is specified by the user.

The command cannot be processed.

Explanation

This message can be returned for several reasons. For example, this message could be returned if application dropped the target table and created a new table with the same name while an online import was running.

The utility stops processing.

Explanation

The atomic compound database operation failed to insert a sequence of rows of data read from the input file. One or more of the fields in the input file is not compatible with the database field where the field is being inserted.

Processing continues with the next row of input data.

Explanation

Some of the data partitions are in the attached or detached state. The utility treats these data partitions as invisible. Any input source records belonging to those data partitions will be rejected by the import utility or the load utility. The rows rejected by the load utility can be recovered from the exception table, if one was specified. The export utility will not process any data that might exist in those data partitions.

Explanation

Some of the data partitions might be in the attached or detached state, but the utility was unable to confirm this. The utility treats these data partitions as invisible. Any input source records belonging to those data partitions will be rejected by the import utility or the load utility. The rows rejected by the load utility can be recovered from the exception table, if one was specified. The export utility will not process any data that might exist in those data partitions.

Explanation

Vendor Load API (sqluvtld) is no longer supported. DB2 Load utility is the only supported bulk loader. DB2 Load utility can be executed via db2Load API.

Explanation

The LOAD target table has detached data partitions and has dependent materialized query tables or dependent staging tables that have not been incrementally refreshed with respect to the detached data partition. This condition prevents the LOAD utility running in insert mode or restart mode from rebuilding a unique index.

Explanation

You can export data from a database to a file by using the export utility. You can then import the data from that file to recreate those tables by using the import utility.

This message is returned when the export utility is unable to export all of the information for one or more tables, which means that the output file that the export utility created would not be able to be used by the import utility to create or recreate the tables.

The reason code indicates the type of information that was not exported:

1

Index information has not been saved because the index column names contain hexadecimal values of 0x2B or 0x2D.

2

XML column definitions have not been saved.

3

Multidimensional clustered table (MDC) key definitions have not been saved.

4

Table partitioning key definitions have not been saved.

5

Index names have been truncated due to code page conversion.

6

Information about protected tables has not been saved.

7

Action strings other than 'SELECT * FROM <TABLE-NAME>' have not been saved.

8

Column names specified with the METHOD N parameter were not used because the METHOD N parameter is not supported when hierarchical data is being exported.

9

A column name that was too long for the Integration Exchange Format (IXF) format has been truncated.

10

A user-defined type name that was too long for the IXF format has been truncated.

11

Typed table information has been truncated due to codepage conversion.

12

The name of a schema that is associated with a user-defined type was too long for the IXF format. The schema name has been truncated.

13

Decimal floating-point column definitions have not been saved.

14

Hidden columns information has not been saved.

15

Information about indexes with random ordering was not saved.

16

Table column orientation in column-organized tables has not been saved.

17

Information about expression-based indexes

18

Indexes created with the BUSINESS_TIME WITHOUT OVERLAPS clause have not been saved.

19

Information about columns where STRINGUNITS has been specified as CODEUNITS32 has not been saved.

20

BINARY or VARBINARY column definitions have not been saved.

21

Information that the table was created as a random distribution table was not saved.

Explanation

Autoloader executable (db2atld) is no longer supported. The Load utility is the only supported bulk loader. The Load utility is executed via a db2Load API, LOAD CLP command, or SYSPROC.ADMIN_CMD stored procedure.

Explanation

Data has not been affected during Export but the file cannot be used in Import with Method N because some column information is missing.

Explanation

Data has not been affected during Export but the file cannot be used in Import using Method N since some column information is missing.

Explanation

When loading a partitioned database using the load utility with LOAD_ONLY_VERIFY_PART mode, any rows in the input file that are found to be on the wrong partition will be discarded. If the "dumpfile" modifier is specified, the discarded rows will be saved to the dump file. This message will appear only once per partition per load job, even when there are multiple partition violations present.

Explanation

Too many partitioning agents have been specified in the PARTITIONING_DBPARTNUMS partitioned database configuration option of the load command. The maximum number of partitioning agents is specified by the MAX_NUM_PART_AGENTS load option, which defaults to 25 if not specified.

Explanation

Load has detected a valid partitioning map at the beginning of the file. The Load mode specified would cause the utility to treat this as user data, possibly causing undesired results.

Explanation

The statistics profile does not exist in the catalog table SYSIBM.SYSTABLES. The statistics profile must be created before the load is executed.

The load utility continues processing.

Explanation

The clause SESSION_USER, CURRENT_USER, SYSTEM_USER, or CURRENT_SCHEMA has been specified for column column-num, but this column was either defined with a length that is less than 128 bytes (SESSION_USER only) or the column-value inserted into this column may exceed the target length after codepage conversion. Load may truncate the column-value.

Explanation

The target of the requested IMPORT operation resides in a remote database and is referenced locally by a nickname. The options specified for the IMPORT command do not meet the constraints required to allow the operation. The operation was rejected.

The explanation corresponding to the reason code is:

1

The federated wrapper which manages the operations on the nickname is non-relational. Only nicknames managed by relational wrappers are supported. The ODBC wrapper is also not supported.

2

The DATALINK SPECIFICATION clause was specified, but is not supported.

3

One of the following unsupported filetype modifiers was specified: indexixf or indexschema.

4

The dldelfiletype modifier, which is unsupported, was specified.

5

One of the following unsupported filetype modifiers was specified: nodefaults or usedefaults.

6

The no_type_idfiletype modifier, which is unsupported, was specified.

7

One of the following unsupported filetype modifiers was specified: generatedignore, generatedmissing, identityignore, identitymissing, periodignore, periodmissing, transactioidignore, or transactionidmissing.

8

The COMMITCOUNT clause was not specified or was specified with the value AUTOMATIC. If the COMMITCOUNT clause is used, a non zero number must be specified.

9

The ALLOW WRITE ACCESS clause, which is required, was not specified.

10

An unsupported filetype was specified. Only files of type IXF, ASC, or DEL are supported.

11

An unsupported import action was specified. Only the INSERT INTO or INSERT_UPDATE INTO actions are supported.

12

Target table contains one of unsupported column types: LOB columns, XML columns, generated columns, datalink columns, or target table is a hierarchy table (typed table).

13

The lobsinfile filetype modifier, which is unsupported, was specified.

14

Either the remote target is not a table, or insufficient privileges prevent the utility from accessing the nickname. Import operation is only permitted when nickname is defined on a table, and PASSTHRU privilege is granted on the user.

15

The necessary stored procedures do not exist against the target database. Update the the database system catalog and cause built-in SQL routines and views to be recreated by calling the version of the db2updv* command that is appropriate for the recently installed fix pack.

16

The target table is a random distribution table using the random by generation method, which is unsupported.