Explanation

The maximum length of a line in the configuration file must be less than 255 bytes.

Explanation

If new line checking is required for a fixed length ASC data file (NEWLINE parameter is YES and RECLEN parameter is not zero), the actual length of each record has to match the expected record.

Explanation

The codepage specification is not valid. It must be a positive integer.

Explanation

The program failed to get the territory code and codepage of its environment.

Explanation

The database does not support codepage conversion between those two codepages.

Explanation

Valid format of decimal data is SQL_PACKEDDECIMAL_FORMAT, SQL_CHARSTRING_FORMAT, or SQL_IMPLIEDDECIMAL_FORMAT, mutually exclusive.

Explanation

A cluster caching facility (CF) structure is a memory resource for a database in a DB2 pureScale environment. The CF structures include Group Buffer Pool (GBP), Shared Communication Area (SCA), and Lock (LOCK). The corresponding configuration parameters for CF structures are CF_GBP_SZ, CF_SCA_SZ, and CF_LOCK_SZ, respectively.

The database configuration parameter named CF_DB_MEM_SZ controls the total CF memory limit for this database. All CF structure memory is included within this limit.

If the value of the database configuration parameter named parameter-name exceeds the parameter value of CF_DB_MEM_SZ, the request cannot be completed and the operation will time-out.

This message is returned when an update to CF structure memory has not completed and another request is made to update the memory for the same CF structure.

Explanation

Specify either the table name or the database partition group name, but not both.

Explanation

The utility needs to know where the database manager is installed, then it can find its bind file.

Explanation

The table tbl-name cannot be located in sysibm.systables.

Explanation

The database partition group db-partition-group cannot be located in SYSCAT.DBPARTITIONGROUPDEF.

Explanation

The utility cannot open the output partition map file for writing. It will write the output to stdout.

Explanation

The size of the partition map is not correct. Data is corrupted in the database.

Explanation

There is an invalid command line option.

Explanation

The distribution map has been expanded from 4096 entries to 32768 entries, and cannot be returned by the deprecated API.

Explanation

While running the load utility in the LOAD_ONLY partitioning mode, data file records were found that do not match the database partition that the records were being loaded into.

Explanation

The utility failed to add, drop, or change the database partition because the input parameters specified are invalid as indicated by the reason code:

1

The database partition number is not specified

2

The TCP/IP host name is not specified

3

The computer name is not specified

4

The database partition number is invalid.

5

The port number is invalid.

6

The TCP/IP host name is invalid.

7

The port value is not defined for your instance in the services file.

8

The port value is not in the valid range defined for your instance in the services file.

9

The database partition number is not unique.

10

The host name/port couple is not unique.

11

The host name value has no corresponding port 0.

Explanation

DB2NCRT /n:node
        /u:username,password
        [/i:instance]
        [/h:host]
        [/m:machine]
        [/p:port]
        [/o:instance owning
          machine]
        [/g:netname]

Explanation

DB2NCHG /n:node
        [/h:host]
        [/m:machine]
        [/p:port]
        [/i:instance]
        [/u:username,
          password]
        [/g:netname]

Explanation

DB2NDROP /n:node
         [/i:instance]

Explanation

DB2NLIST [/i:instance]
         [/s]

Explanation

An error has occurred during an attempt to create, drop, or add a database partition. The reason code indicates the reason for the error:

1

Unable to register the service

2

Unable to set the required User Rights Policy

3

Unable to set the Logon Account for the service

4

Unable to delete the service

Explanation

DB2NDROP failed because the node does not exist.

Explanation

DB2NCRT failed because the node already exists.

Explanation

The DB2NDROP processing has completed successfully.

Explanation

The DB2NCRT processing has completed successfully.

Explanation

The DB2NCHG processing has completed successfully.

Explanation

The command is only valid if the instance is a partitioned database instance.

Explanation

db2drvmp add     node_number
                 from_drive to_drive
       drop      node_number
                 from_drive
       query     [node_number]
                 [from_drive]
       reconcile [node_number]
                 [from_drive]

Explanation

The drive mapping was added successfully.

Explanation

The drive mapping was deleted successfully.

Explanation

Informational message.

Explanation

The ingest utility uses the distribution key to determine the partition number and routes input records to one of that partition's flushers. Because of the condition that the reason code specifies, the ingest utility will route records to a random flusher. The reason codes are:

1

The NUM_FLUSHERS_PER_PARTITION configuration parameter was set to 0, so there is only 1 flusher for all partitions.

2

The target table is a type that does not have a distribution key.

3

At least one of the distribution key columns has a type that is a user-defined type (UDT) or a DB2SECURITYLABEL.

4

If the SQL statement is INSERT or REPLACE, the column list does not specify all the distribution key columns. If the SQL statement is UPDATE, DELETE, or MERGE, the WHERE or ON clause does not specify all the distribution key columns.

5

If the SQL statement is INSERT or REPLACE, a value in the VALUES list is not a field name or constant. If the SQL statement is UPDATE, DELETE, or MERGE, one or more of the following is true:

• The comparison to a distribution key column is not an equality comparison.
• The value compared to a distribution key column is not a field name or constant.
• The distribution key column corresponds to more than one field name or constant.

6

The SQL statement is UPDATE, DELETE, or MERGE and the WHERE or ON clause is not of the form:

(dist-key-col1 = value1) AND (dist-key-col2 = value2) AND ... (dist-key-colN = valueN)

where dist-key-col1 to dist-key-colN includes all the distribution key columns and each value is a field name or constant.

7

There is at least one distribution key column that has a numeric type, but its corresponding field does not have the exact same numeric type, including the same precision and scale.

Explanation

The ingest utility completed successfully, but returned some errors or warnings. Refer to the specified messages file to determine what those errors or warnings are.

The number of errors includes errors from which the utility could not recover, but does not include errors from which the utility recovered.

Explanation

The ingest utility completed successfully, but returned some errors or warnings.

The number of errors includes errors from which the utility could not recover, but does not include errors from which the utility recovered.

Explanation

The INGEST SET or INGEST command completed successfully, but a user-specified configuration parameter was overridden. If this message is issued for an INGEST SET command, the overriding value remains in effect for the remainder of the CLP session. If this message is issued for an INGEST command, the overriding value remains in effect only for the INGEST DATA command.

The explanation corresponding to the reason code is:

1

The commit_count and commit_period configuration parameters cannot be set to 0 on the same INGEST command. commit_period has been set to 1.

2

The commit_count configuration parameter must be set to a multiple of 1000, so it has been rounded to the nearest multiple of 1000.

3

The commit_count configuration parameter has been reduced because either the lock list or the transaction log ran out of space. The new value is the number of rows that had been committed right before the lock list or transaction log ran out of space.

4

The commit_period configuration parameter has been has been reduced because either the lock list or the transaction log ran out of space. The new value is the number of seconds between the time of the last commit and the time when the lock list or transaction log ran out of space.

10

The num_flushers_per_partition configuration parameter has been adjusted to 0 because one of the following is true:

• For an UPDATE operation, there are no appropriate columns in the search key, or all columns in the search key are also in the update key (specified on the SET clause).
• For a DELETE operation, there are no appropriate columns in the search key.

The search key is the set of all columns c1, c2, ... specified on a WHERE or ON clause of the form:

(c1 = $field_1) AND (c2 = $field_2) 
    AND ... (cn = $field_n)
   [AND (<any other conditions<)]

(The last AND condition enclosed in square brackets is optional.)

11

The num_flushers_per_partition configuration parameter has been adjusted to 0 in a partitioned database environment because at least one column in the table's distribution key is also in the update key (specified on the SET clause).

12

The num_flushers_per_partition configuration parameter has been adjusted to 1 because there is no index that contains at least one column that is in the search key (specified on the WHERE clause) but not in the update key (specified on the SET clause).

14

The num_flushers_per_partition configuration parameter has been adjusted to the value of the max_connections database manager configuration parameter because it cannot be greater than max_connections.

15

The num_flushers_per_partition configuration parameter has been adjusted to floor(128/(number of members)) because the target table is a column-organized table. Column-organized tables are structured such that the maximum ingest performance is achieved when a total of 128 parallel insert threads are employed over all members.

16

The num_flushers_per_partition configuration parameter has been adjusted to 50 because the target table is a column-organized table. Column-organized tables are structured such that the maximum ingest performance is achieved when 50 parallel insert threads are employed.

Explanation

The specified field has a value that is longer than the field's length. The value has been truncated. For example, if the field is defined as CHAR(3) but the value is "ABCDEF", the value is truncated to "ABC".

Explanation

This message provides the identification of the line and input file where the error occurred for the following message listed.

The table is either the one specified on the SQL statement of the INGEST command or the exception table. If the table is the one specified on the SQL statement, and the SQL statement is INSERT or REPLACE, and the INGEST command specified an exception table, the ingest utility attempts to insert the record into the exception table. Otherwise, the ingest utility discards the record.

Explanation

This message provides the identification of the line and input pipe where the error occurred for the following message listed.

The table is either the one specified on the SQL statement of the INGEST command or the exception table. If the table is the one specified on the SQL statement, and the SQL statement is INSERT or REPLACE, and the INGEST command specified an exception table, the ingest utility will attempt to insert the record into the exception table. Otherwise, the ingest utility will discard the record.

Explanation

This message provides the identification of the line and input TCP/IP port where the error occurred for the following message listed.

The table is either the one specified on the SQL statement of the INGEST command or the exception table. If the table is the one specified on the SQL statement, and the SQL statement is INSERT or REPLACE, and the INGEST command specified an exception table, the ingest utility will attempt to insert the record into the exception table. Otherwise, the ingest utility will discard the record.

Explanation

This message provides the identification of the input pipe where the error occurred for the following message listed.

Explanation

This message provides the identification of the input TCP/IP port where the error occurred for the following message listed.

Explanation

When modifiers are specified on a field, they must be specified on all fields that have a similar type. For example: If a decimal field specifies RADIX POINT, the same RADIX POINT character must be specified on all other INTEGER, DECIMAL, DECLFOAT, and FLOAT fields. If a format string is specified on a DATE field, the same format string must be specified on all other DATE fields. If an INTEGER field specifies EXTERNAL, then EXTERNAL must be specified on all other INTEGER, DECFLOAT, and FLOAT fields. (Fields of type DECIMAL, however, can specify PACKED or ZONED. But all fields of type DECIMAL must specify the same EXTERNAL, PACKED, or ZONED modifier as all other DECIMAL fields.)

Explanation

The INGEST command specified a binary field type, but the input file format is not POSITIONAL. The command failed.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. If any input fields are a binary data type, the length of those binary fields must be specified with the INGEST command or db2Ingest API call.

This message is returned when an attempt is made to ingest data that contains binary fields and the length of those binary fields is not specified.

Explanation

INGEST commands that specify FORMAT POSITIONAL must specify or imply the field length, or the POSITION parameter must specify the end position. The command failed.

Explanation

The ingest utility is starting. The job ID is the one specified on the RESTART parameter or if none was specified, a default job ID that the utility generated. The job ID can be used on the INGEST GET STATS command while the INGEST command is running. If the INGEST command fails, the job ID can be used on a later INGEST command with the RESTART CONTINUE or RESTART TERMINATE parameter.

Explanation

The length specified by RECORDLEN on the INGEST command must be greater than or equal to the sum of the field lengths specified on each field definition. The command failed.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. How the ingest utility modifies the target table is controlled by specifying an SQL statement with the INGEST command or db2Ingest API call.

This message is returned when an attempt is made to perform an ingest operation with an SQL statement that references no fields.

Explanation

You can specify the maximum size of Inter Process Communication (IPC) shared memory by setting the SHM_MAX_SIZE ingest utility configuration parameter.

This message is returned when the ingest operation fails because the SHM_MAX_SIZE configuration parameter is not large enough.

Explanation

The INGEST command failed because of an invalid combination of keywords.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can stream data into multiple types of tables, including the following examples:

• Multidimentional clustering tables
• Materialized query tables
• Partitioned tables
• Others

This message is returned when an attempt is made to ingest data into a type of table that the ingest utility does not support.

Explanation

An INGEST command that specifies an SQL statement that uses a WHERE or ON clause must include a search condition that specifies at least one field. The command failed.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify to the ingest utility how the data is defined in the input stream by describing the fields into which the data is separated.

This message is returned when an attempt is made to perform an ingest operation with an SQL statement that references a data field that does not exist in the input source data.

Explanation

This message provides the identification of the input file where the error occurred for the following message listed.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify the data type of input fields when you invoke the ingest operation.

This message is returned when an invalid field type is specified.

Explanation

Fields that specify the DEFAULTIF parameter cannot be used in a predicate or in an expression. The command failed.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can cause the ingest utility to insert a default value into the target table whenever a certain character appears in the input data by using the DEFAULTIF parameter.

If the DEFAULTIF parameter is specified with a field definition, the column that corresponds to that field must have a default value.

This message is returned when the DEFAULTIF parameter is specified but the corresponding target table column does not have a default value.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can cause the ingest utility to insert a default value into the target table whenever a certain character appears in the input data by using the DEFAULTIF parameter.

If the DEFAULTIF parameter is specified with the ingest utility, the default value of the corresponding target table column must be a constant or NULL.

This message is returned when the DEFAULTIF parameter is specified but the default value of the corresponding target table column is neither constant nor NULL.

Explanation

There might be a data type mismatch because the value in the specified field cannot be converted to the field's data type.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility.

This message is returned when an attempt is made to invoke the ingest utility, but the specified input source is not a file or named pipe.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility.

This message is returned when the ingest utility could not open, read from, or close the specified input file or named pipe.

Explanation

The ingest utility failed to allocate an interprocess IPC resource after the specified number of attempts. The resource type can be one of the following:

1. Shared memory
2. Listener queue
3. Semaphore

This message normally follows earlier messages that indicate the error or errors that occurred when trying to allocate the resource.

Explanation

The INGEST command failed.

If the parameter is PIPE_TIMEOUT, the INGEST command did not receive any data from the pipe for at least the specified number of seconds after the command opened the pipe.

Explanation

The port number specified (or resolved to) in the INGEST command must be within the allowable range. The INGEST command failed.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify the properties such as data type or length of input fields when you invoke the ingest operation.

When a field has a value that is longer than the defined length of the field, the value will be truncated. For example, if the field is defined as CHAR(3) but the value is "ABCDEF", the value is truncated to "ABC".

This message is returned when an input field has a value that is longer than the defined length of the field.

Explanation

The INGEST command cannot use that port because it is being used by another running application. The INGEST command failed.

Explanation

The INGEST command specified the DEFAULTIF clause, but the input file format is not POSITIONAL. The command failed.

Explanation

The field specification for locating the input data for the indicated database column within the input non-delimited ASCII file is not valid for the reason indicated by the following reason codes:

1

The start position is 0.

2

The end position is less than the start position.

3

The end position is greater than 32 767.

4

Fields of type SMALLINT, INTEGER, BIGINT, DECIMAL, REAL, FLOAT, and DECFLOAT with the EXTERNAL modifier have a maximum length of 50.

5

If a format string is specified for fields of type DATE, TIME, and TIMESTAMP(p), the field length must be greater than or equal to length of the shortest value that matches the format string.

6

If a format string is not specified:

• For DATE fields, the field length must be between 8 and 10, inclusive.
• For TIME fields, the field length must be between 4 and 8, inclusive.
• For TIMESTAMP fields, the field length must be between 19 and 32, inclusive.

The INGEST command failed.

Explanation

The current value for the indicated command parameter is not valid because it is outside the allowable range.

The command failed.

Explanation

The ingest utility does not support ingesting data into tables that are on versions of the database server earlier than the version shown in the message.

Explanation

The field type on the field definition specifies a length, precision, or scale that is not valid. Examples of this error are:

• A field definition that specifies CHAR(70000) is not valid because the maximum length of a field is 32767.

Explanation

When a field definition specifies DEFAULTIF, the field must be assigned to one and only one column and cannot be part of an expression that is assigned to that column. For example, consider the following INGEST command:

INGEST FROM FILE my_file.txt FORMAT DELIMITED
  ...
  UPDATE my_table
  SET (c1, c2, c3, c4, c5) =
      ($field1, $field2, $field2, 
          $field3, $field4+$field5) 
  WHERE $field3 = 1;

Only $field1 can specify DEFAULTIF. $field2 cannot because it is assigned to multiple columns. $field3 cannot because it is also used in a predicate. $field4 and $field5 cannot because they are used in an expression.

Explanation

When either of the following is true, the ingest utility cannot insert into or update the table:

• The SQL statement on the INGEST command is INSERT (including as part of a MERGE statement) and one of the following is true:
  • All the columns specified after the table name are defined as GENERATED ALWAYS.
  • No columns are specified after the table name, but all the table's non-hidden columns are defined as GENERATED ALWAYS.
• The SQL statement on the INGEST command is UPDATE (including as part of a MERGE statement) and all the columns specified on the SET clause are defined as GENERATED ALWAYS.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. How the ingest utility modifies the target table is controlled by specifying an SQL statement with the INGEST command or db2Ingest API call.

When the ingest utility is used with an INSERT statement that does not have a VALUES clause, the number of fields must be the same as the number of specified or implied table columns. (The number of implied columns is the number of non-hidden columns in the table.)

For example, the following INGEST command is not valid because two fields are specified but there are three columns:

INGEST FROM FILE my_file.del FORMAT DELIMITED
  ($field1 INTEGER EXTERNAL, $field2 CHAR(32))
  INSERT INTO my_table(col1, col2, col3);

Explanation

When the INGEST command specifies FORMAT DELIMITED, every field of type DB2SECURITYLABEL must specify the NAME or STRING modifier.

Explanation

The INGEST command can omit the field list only when the format is delimited. If the format is positional, you must specify the field list.

Explanation

The command failed because the ingest job with the specified identifier was not found.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. There are some restrictions on the data types that are supported with the ingest utility.

This message is returned when an attempt is made to ingest data into a column that is an unsupported data type.

Explanation

This message is preceded by a message that identifies the input source name and line number. One of the fields in the specified input record is too long or out of range for the table column.

Explanation

When you ingest into an updateable view and the view has multiple base tables, all the base tables that are protected by a security policy must be protected by the same security policy.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. A security administrator can use security policies to define criteria that determine who has write access and who has read access to individual rows and individual columns of tables.

This message is returned when an attempt is made to ingest data into a table that is protected by a security policy but catalog view SYSCAT.SECURITYPOLICIES has no security policy with that ID.

Explanation

The INPUT CODEPAGE parameter on the INGEST command specifies a code page number that is not valid for one of the following reasons:

• The number is not a valid code page.
• DB2 or the INGEST command does not support the code page.
• The code page is not compatible with the client code page.

Explanation

There might be a data type mismatch because the field value at the specified byte position cannot be converted to the field's data type.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify a list of field definitions for the ingested data, but there is an upper limit to the number of field definitions that you can specify. The maximum allowable number of field definitions is given in the runtime token maximum-number.

This message is returned when an attempt is made to specify more field definitions than the ingest utility can support.

Explanation

A file that the ingest utility requires could not be found. The installation of the DB2 Data Server Client or DB2 Data Server Runtime client might be incomplete or damaged.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify to the ingest utility how the data is defined in the input stream by passing data structures such as db2IngestStruct, db2IngestCfgList, and db2IngestFormat to the db2Ingest API call.

This message is returned when an invalid value is specified for a field in one of the input data structures.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. If the ingest utility fails before completing, you can restart the ingest operation from the last commit point. To make an ingest operation restartable, a restart log table must be created before the ingest operation is initiated.

This message is returned when an attempt is made to restart the ingest utility but the ingest utility could not find the restart log table.

Explanation

The INGEST command specified RESTART CONTINUE. In order to restart a failed INGEST command, the restarted command must meet the following requirements:

• The NUM_FLUSHERS_PER_PARTITION configuration parameter must be the same as on the original command.
• If the input is from files or pipes, the number of input files or pipes must be the same as on the original command.

Explanation

The ingest utility received the error that followed this message, but recovered from the error by issuing a COMMIT or issuing a ROLLBACK and reissuing the SQL statements. The utility reissued the statements the number of times specified in the message. The reason code indicates how the utility recovered from the error:

1

The utility recovered by issuing a commit earlier than requested by ingest configuration parameters COMMIT_PERIOD or COMMIT_COUNT. For this reason code, the number of reconnects and number of retires is "0".

2

The utility recovered by issuing a ROLLBACK and reconnecting or retrying the specified number of times.

Explanation

A field definition specifies DB2SECURITYLABEL STRING, but the value of the corresponding field in the input source is not a valid security label string. The row is not loaded.

Explanation

The INGEST command failed because it has more than the allowable number of input file names or pipe names.

Explanation

The ingest utility issues this message when all of the following are true:

• The INGEST command omits the RESTART parameter or specifies RESTART NEW or RESTART CONTINUE.
• The target table is a nickname.
• When trying to insert into or update the nickname, the utility receives message SQL30090N with reason code 18.

The SQL30090N error occurs because the utility needs to update both the remote table that the nickname refers to and the restart log table, which is local. This requires the two-phase commit protocol, but the server definition that contains the nickname is not defined with server option DB2_TWO_PHASE_COMMIT set to 'Y'.

Explanation

You can ingest data to a database table from an input file or pipe by using the INGEST command. You can specify that each input record is a sequence of text or binary fields by using the POSITIONAL parameter with the INGEST command. You can specify the starting position and ending position of each field within a record by using the POSITION clause in the field definition.

This message is returned when an invalid starting or ending position is specified with the POSITION clause.

Explanation

The INGEST command specifies a job ID that is currently in use, as indicated by the reason code:

1

The command specifies RESTART NEW, RESTART CONTINUE, or RESTART TERMINATE, but an INGEST command with the specified job ID is already running.

2

The command specifies RESTART NEW, but the restart table (SYSTOOLS.INGESTRESTART) already contains an INGEST command with the specified job ID.

Explanation

This message identifies the table being operated on when the error in the following message occurred. If the table is the restart table (systools.ingestrestart), the restart table might be corrupted, damaged, or missing.

Explanation

When the ingest utility connects to the database and gets a warning or error, the utility issues this message followed by the warning or error message. If you connected without explicitly specifying the user ID, the user-ID field is empty.

Explanation

When the ingest utility runs in a DPF environment and it can determine values for each of the target table's distribution keys, it connects directly to each database partition. When the utility connects to the database partition and gets a warning or error, the utility issues this message followed by the warning or error message.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify to the ingest utility how the data is defined in the input stream by describing the fields into which the data is separated.

This message is returned when one of the fields in the specified input record has a non-numeric value, but is used where a numeric value is expected.

Explanation

In a partitioned database environment, the utility examines the values of fields that map to distribution key columns and uses those values to determine the partition to send the record to. The utility issues this message when the field value is invalid or out of range for the corresponding distribution key column type. For example, the utility issues this message if the distribution key column type is INTEGER, but the field contains "ABC". The column type is the type of the distribution key column that corresponds to the field. The column length is the length of the column in bytes.

The utility will not send the record to DB2. If the DUMPFILE parameter is specified, the utility will write the record to the dump file.

Explanation

The database directory contains an entry for the specified database and the entry specifies a node that does not exist.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify to the ingest utility how the data is defined in the input stream by passing data structures such as db2IngestStruct, db2IngestCfgList, and db2IngestFormat to the db2Ingest API call.

The fields of some db2Ingest input structures contain an array of objects:

• The first field of the db2IngestFormat structure is an array of db2IngestFieldDefn objects.
• The first field of the db2IngestCfgList structure is an array of db2IngestCfgParam objects.

This message is returned when one object in an array of objects contains an invalid field value. The runtime token index-number indicates which element in the array of objects has a problem. The index starts at zero.

Explanation

This message is returned when an attempt is made to restart an ingest operation, but one or more of the following is true:

Scenario 1: The target table and the restart log table (SYSTOOLS.INGESTRESTART) are in different table spaces, but the two table spaces are at different product code levels.

Scenario 2: The records in the restart log table that belong to the specified ingest job ID have been modified outside of the ingest utility.

Scenario 3: The input files or pipes for the restarted ingest operation do not provide the same records in the same order as the input files or pipes for the original command.

Scenario 4: One of more of the following parameters are different from the original ingest operation:

• The SQL statement.
• The field definition list, including the number of fields and all field attributes.

Scenario 5: One or more of the target table columns that the SQL command updates have a different definition than they had at the time of the original ingest operation.

Scenario 6: In a multiple database partition environment:

• Database partitions were added or removed since the original ingest operation was run.
• Data was redistributed across the partitions since the original ingest operation was run.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. When a field in the input stream is a date, time, or timestamp, you can specify the format of the field by providing a format string.

This message is returned when a field definition specifies a date, time, or timestamp format string that is not valid.

Explanation

You can stream data from files and pipes into DB2 database tables by using the ingest utility. If the ingest utility fails before completing, you can restart the ingest operation from the last commit point.

This message is returned when the primary database connection was lost during the initialization of the ingest operation.

Explanation

The RECONNECT_COUNT ingest configuration parameter is set to a value greater than 0 and the INGEST command omits the RESTART parameter (so it defaults to NEW) or specifies RESTART NEW or RESTART CONTINUE.

Explanation

There is a conflict between the field length and the field end position. The indicated reason code describes the conflict and how the utility resolves it:

1

The field type is SMALLINT, INTEGER, or BIGINT in binary. The length specified by (end position) - (start position) + 1 is 2, 4, or 8, but does not match the length of the field type. The utility will use the specified end position.

For example, if the field definition is SMALLINT POSITION(1:4), the utility will read 4 bytes even though a SMALLINT is 2 bytes. If the field contains a value outside the range of a SMALLINT, the utility will issue an error when it tries to convert the field value to a SMALLINT.

2

The field type is SMALLINT, INTEGER, or BIGINT in binary, but the length specified by (end position) - (start position) + 1 is not 2, 4, or 8. The utility will adjust the end position to match the length of the field type.

For example, if the field definition is SMALLINT POSITION(1:3), the utility will adjust the end position to 2 (because a SMALLINT is 2 bytes).

3

The field type is DECIMAL, REAL, FLOAT, or DECFLOAT in binary, but the length specified by (end position) - (start position) + 1 conflicts with the length of the field type. The utility will adjust the end position to match the length of the field type.

For example, if the field definition is REAL POSITION(1:5), the utility will adjust the end position to 4 (because a REAL is 4 bytes).

4

The field length specified on the field type conflicts with (end position) - (start position) + 1. If the specified length exceeds (end position) - (start position) + 1, the utility will adjust the length to (end position) - (start position) + 1. If the specified length is less than (end position) - (start position) + 1, the utility will adjust the end position to (start position) + length - 1.

For example, if the field definition is CHAR(10) POSITION(1:8), the utility will adjust the length to 8. If the field definition is CHAR(8) POSITION(1:10), the utility will adjust the end position to 8.

Explanation

The utility received an error that prevents it from continuing. The utility will exit.

Rows that were committed prior to the error remain in the table.

Explanation

Ingest configuration parameter RECONNECT_COUNT or RETRY_COUNT has a value greater than 0 and the utility received a recoverable error. The utility attempted to recover from the error but could not for the reason indicated by the reason code:

1

The number of reconnect attempts reached the value of the RECONNECT_COUNT ingest configuration parameter.

2

The number of retries reached the value of the RETRY_COUNT ingest configuration parameter.

3

The utility was interrupted or a terminating error occurred.

Explanation

The ingest utility is starting at the indicated timestamp. The utility will also issue a message indicating the job ID.

Explanation

The ingest utility completed with no warnings or errors.

Explanation

An unexpected error occurred calling an operating system function or command. The reason codes are:

1

The command was not found in /usr/bin or /bin. For this reason code, the "Additional tokens" field in the message is blank.

2

The function or command failed with the system error code shown in the "Additional tokens" field of the message. On UNIX, error codes are defined in system header file errno.h. For information on Windows error codes, consult Microsoft documentation.

3

The function or command did not return output in the expected format. The "Additional tokens" field of the message shows the last line of output.

Explanation

You can monitor the progress of ingest operations being run by the authorization ID that is connected to the database by using the INGEST LIST command or the INGEST GET STATS command.

This message is returned when either the INGEST LIST command or the INGEST GET STATS command was issued, but the authorization ID that is currently connected to the database is not running any ingest operations on the current machine. If the authorization ID recently started an ingest operation from another session, the command might not have completed initialization or might have already finished.