SQL3500W The utility is beginning the phase phase at time timestamp.

Explanation

This is an informational message indicating that a phase is about to begin and that the previous phase has ended. The phases are (in order of appearance):

  • ANALYZE
  • LOAD
  • BUILD
  • DELETE

During the ANALYZE phase, if the target table for the LOAD command is a column-organized table, the compression dictionary is built. During the LOAD phase, data is loaded into your table. If there are any indexes to be built, BUILD phase will follow the LOAD phase. If there were any duplicate keys found for a unique index, the DELETE phase will follow the BUILD phase.

If the LOAD is terminated before the end of the LOAD, you need to know the phase at which you should restart the LOAD.

User response

No action is required.

SQL3501W The table space(s) in which the table resides will not be placed in backup pending state since forward recovery is disabled for the database.

Explanation

COPY NO was specified on the invocation of LOAD which results in the table space(s) in which the table resides being placed into backup pending state unless forward recovery is disabled for the database.

The utility continues.

User response

No action is required.

SQL3502N The utility has encountered number warnings which exceeds the total number of warnings allowed.

Explanation

The number of warnings issued during the command has exceeded the total number of warnings that the user specified at invocation of the utility.

The utility terminates.

User response

Ensure that the correct data is being loaded with the appropriate options or increase the number of warnings allowed. Resubmit the command.

SQL3503W The utility has loaded number rows which equals the total count specified by the user.

Explanation

The number of rows loaded has equaled the total number of rows that the user specified at invocation of the utility.

The utility has successfully completed.

User response

No response required.

SQL3504W A consistency point is being established.

Explanation

Consistency points will be established at times other than the regular interval specified in the SAVECOUNT parameter at invocation when:
  • the threshold for the amount of meta-data kept in memory or in temporary files has been reached.
  • A device error occurred for the copy image and the load must terminate.

User response

If the LOAD continues after this message, no action is required. If the LOAD terminates, it can be restarted after all errors are corrected (such as activating a device or decreasing the interval at which consistency points are to be established).

SQL3505N The length specified in the filetmod for the RECLEN option is not in the valid range of 1 to 32767.

Explanation

In the filetmod parameter, the RECLEN option was specified for an ASC file. The length specified is not valid.

User response

Correct the length specified and resubmit the command.

SQL3506W The value specified in the null indicator in row row-number and column column-number is not valid. A value of 'N' will be assumed.

Explanation

For ASC files, a null indicator column can be specified for each data column and should contain either a 'Y' or a 'N'. A 'Y' indicates that the column is a null value and a 'N' indicates that the column contains data. If neither of these values are in the null indicator column, it is assumed to be a 'N' and data will be loaded into the column.

User response

If the data or the null indicator are incorrect, correct the input file and resubmit the command.

SQL3507N The column number specified for a null indicator is not in the valid range of 0 to 32767 or the null indicator parameter is not valid.

Explanation

In the null_ind parameter, columns for null indicators were specified for an ASC file but one of the columns is not valid or the pointer passed in for the null indicators is not valid.

User response

Correct the parameter and resubmit the command.

SQL3508N Error in accessing a file or path of type file-type during load or load query. Reason code: reason-code. Path: path/file.

Explanation

An error occurred while trying to access a file during load or load query processing. The utility stops processing.

User response

If doing a load and the table space is not in load pending state, correct the problem and invoke the load utility again. If the table is in load pending state, then invoke the load utility in RESTART or REPLACE mode, or restore a backup of the table space(s). The state of the table space can be determined using the LOAD QUERY command.

The following is a list of reason codes:

1

Unable to open the file.

This could be caused by an incorrect file name or insufficient authority to access the file/directory. Correct the problem and either restart or rerun the load.

The load temporary file could have been destroyed or the database could have been restored from an earlier backup. Load restart is not supported under these circumstances. Use load terminate to bring the table out of load pending state.

2

Unable to read/scan the file.

This could be the result of a hardware error. If the error is a hardware error, take the appropriate action and restart or rerun the load.

3

Unable to write to or change size of the file.

This could be the result of a disk full condition or a hardware error. Refer to the file type list provided later in this message, and either ensure there is enough space to run the load or specify a different location to be used. Restart or rerun the load. If the error is a hardware error, take the appropriate action an restart or rerun the load.

4

The file contains invalid data.

A file required by the load contains incorrect data. See the action described for TEMPFILES_PATH.

5

Unable to close the file.

If the load cannot be restarted or rerun, contact your IBM service representative.

6

Unable to delete the file.

If the load cannot be restarted or rerun, contact your IBM service representative.

7

Parameter specified incorrectly. Refer to the list of file types to determine the parameter in error and rerun the load with a valid parameter.

The following is a list of file types:

SORTDIRECTORY

Ensure that the workdirectory parameter is specified properly. There must be enough combined space in all the directories to hold twice the size of the index keys for the loaded data. For load insert and load restart there must also be room for twice the size of the index keys of the existing data in the table.

MSGFILE

Ensure that the messagefile parameter is specified properly. There must be enough disk space to write out the messages that occur during the load.

If this is a load query, ensure that the local message file parameter is NOT the same as the messagefile parameter used for the load whose status is being queried.

TEMPFILES_PATH

Ensure that the tempfiles path parameter is specified properly.

SQL3509W The utility has deleted number rows from the table.

Explanation

When a table with a unique index is loaded, rows causing violation of uniqueness of an index will be deleted from the table during the delete phase. This message provides information on how many rows have been deleted.

User response

No action is required.

SQL3510N The working directory for the sort phase cannot be accessed.

Explanation

One or more of the specified working directories for the sort phase either does not exist or has no read/write permission.

User response

Ensure that the specified working directories exist and the read/write permission is setup correctly and resubmit the command.

SQL3511W The file named in row row-number and column column-number cannot be found. A null was loaded.

Explanation

The filename in the specified field cannot be found. There may be a data type mismatch.

For delimited ASCII (DEL) files, the value of the column number specifies the field within the row that contains the value in question. For ASCII files, the value of the column number specifies the byte location within the row where the value in question begins.

A null value is loaded.

User response

Examine the input value. If necessary, correct the input file and resubmit the command or edit the data in the table.

SQL3512W The file named in row row-number and column column-number cannot be found, but the target column is not nullable. The row was not loaded.

Explanation

The filename in the specified field cannot be found. A null cannot be loaded because the output column in the table is not nullable.

For delimited ASCII (DEL) files, the value of the column number specifies the field within the row that contains the value in question. For ASCII files, the value of the column number specifies the byte location within the row where the value in question begins.

The row is not loaded.

User response

Correct the input file and resubmit the command or edit the data in the table.

SQL3513N The codepage of the file does not match the codepage of the database. The file cannot be loaded.

Explanation

DB2CS files cannot be loaded into a database with a codepage that differs from the original database.

User response

Change the codepage of the database and resubmit the command or use another filetype (such as PC/IXF) to move your data from the original database to the new database.

SQL3514N A utility system error occurred. Function code: function. Reason code: reason-code. Error code: error-code.

Explanation

A system error occurred during database utility processing.

User response

Different actions are required depending on the value of function.

The possible function codes are:
  • 1 - An error occurred while Load was sorting.

    Try to restart the load. If the error persists, provide the function, reason code and error code to your technical service representative.

  • 2 - An error occurred using the vendor sort utility.

    Try the load again using the IBM Data Server Client/DB2 Server sort utility instead of the vendor sort. To do this, reset the Profile Registry value at the server to blank. You may have to restart the Database Manager in order to pick up the new Profile Registry value. If the error persists, provide the function, reason code and error code to your vendor sort technical service representative.

SQL3515W The utility has finished the phase phase at time timestamp.

Explanation

This is an informational message indicating that a phase has finished. The phases are (in order of appearance):
  • LOAD
  • BUILD
  • DELETE

User response

No action is required.

SQL3516N The utility could not restart the load as specified.

Explanation

The Load Utility detected discrepancies in the last consistency point performed by Load before failure occurred. This condition might be caused either by a system error or an invalid log file.

User response

Restart the Load at the Build phase, to bring the table to a consistent state and create indexes (if applicable), or perform Load with the REPLACE option.

SQL3517N An unexpected record was read from the input source.

Explanation

The utility has encountered a record that is in a format that is not valid. The source may have been corrupted when copied from the original source.

Processing terminates.

User response

Copy the record from the original source in binary and restart the LOAD or Import.

SQL3518N The data in the source is not compatible to the table to be loaded.

Explanation

The source cannot be used to load this table because one of the following reasons:
  • the table definition does not match the table definition of the source.
  • the source was created on a different platform than the table that is being loaded.
  • the source was created from a table that had a different codepage from the table that is being loaded.

User response

Ensure that both the table and source are correctly specified. If you want to load data from a table with a different definition or from a different platform or codepage, use another filetype such as IXF or DEL.

SQL3519W Begin Load Consistency Point. Input record count = count.

Explanation

The Load Utility is about to attempt to perform a Consistency Point to commit the table data that has already been loaded.

User response

If message SQL3520W is not printed immediately after this message, then the Consistency Point failed. The Load will have to be restarted at the Build phase, to ensure that the table is brought back to a consistent state and all indexes (if any) created. It will then be possible to check which records have been loaded. Start the Load again with a RESTARTCOUNT set to the number of records successfully loaded to skip those rows and load the rest of the file.

If this message is followed by messages SQL3520W, then this message is informational only and no response is required.

SQL3520W Load Consistency Point was successful.

Explanation

The Consistency Point performed by Load was successful.

User response

This is an informational message only. No response is required.

SQL3521N The input source file sequence-num was not provided.

Explanation

A load was invoked with multiple input files but not all the files were provided. For the DB2CS filetype, all the input source files that were created originally must be provided. For the IXF filetype, all the input source files must be provided in the correct order.

The utility terminates.

User response

Restart the utility providing all the input source files and setting the RESTARTCOUNT appropriately for the data that was already loaded.

SQL3522N The load operation failed because the COPY YES parameter was specified but the database does not use recoverable logging.

Explanation

You can enable roll-forward recovery by using archive logging. You can configure log archiving by using the database configuration parameters logarchmeth1 and logarchmeth2.

You can load data into a table by using the LOAD command. You can cause a copy of the loaded data be saved by specifying the COPY YES parameter with the LOAD command. Specifying the COPY YES parameter with the LOAD command is only supported with databases that are enabled for roll-forward recovery.

This message is returned when an attempt is made to run the LOAD command, specifying the COPY YES parameter, with a database that is not enabled for roll-forward recovery.

User response

Respond to this message in one of the following ways:

  • Enable the database for roll-forward recovery and then call the LOAD command again with the COPY YES parameter.
  • Call the LOAD command again without specifying the COPY YES parameter.

SQL3523W There are no messages to be retrieved from the message file. Reason code: rc.

Explanation

No messages are returned from a query of the LOAD temporary message file. The possible return codes are:
1
No LOAD temporary message file exists.
2
There are no messages in the LOAD temporary message file.

User response

Ensure that a valid table name has been specified. If the table name is specified correctly and messages are expected, check the database monitor to verify that the utility is active and it is not waiting for resources such as locks. Note that the LOAD temporary message file will not be created until the LOAD utility is in progress and it will be deleted after the completion of the LOAD utility.

The syntax of the CLP command includes the keyword TABLE, for example: 
LOAD QUERY TABLE <tablename>

Neglecting the TABLE keyword will result in load query opening a binary load message file with the name tablename.

SQL3524N Option option has an invalid value of value.

Explanation

The value provided must be an integer value. Its range for each option is as follows:
  1. TOTALFREESPACE: the value must be in the range of 0 to 100, and is interpreted as a percentage of the total pages in the table that are to be appended to the end of the table as free space.
  2. PAGEFREESPACE: the value must be in the range of 0 to 100, and is interpreted as a percentage of each data page that is to be left as free space.
  3. INDEXFREESPACE: the value must be in the range of 0 to 99, and is interpreted as a percentage of each index page that is to be left as free space when loading indexes.

The utility stops processing.

User response

Correct the value and resubmit the command.

SQL3525N The option-1 option is incompatible with the option-2 option.

Explanation

Incompatible options have been provided to the utility.

User response

Remove or modify one of the options and resubmit the command. See the Command Reference for more information on valid options.

SQL3526N The modifier clause clause is inconsistent with the current load command. Reason code: reason-code.

Explanation

The load file type mode (modifier) indicated, is incompatible with your load/import/export command. This is because of one of the following reasons:

1

The current option requires you to specify the RECLEN and NOEOFCHAR file type modifiers. One or more of these options are missing from your command.

2

The indicated option, such as DEL or ASC, is inconsistent with the format of the input or output data file.

3

Generated or identity related file type modifiers have been specified but the target table contains no such columns.

4

When a pre-Version 8 client is used, it is not possible to load a table having a non-identity generated column in a unique index, unless the column is specified in the INCLUDE clause of the CREATE INDEX statement or the GENERATEDOVERRIDE file type modifier is used. For pre-Version 8 clients, it is also necessary to specify the GENERATEDOVERRIDE file type modifier when loading a table that has a non-identity generated column in its ORGANIZE BY clause.

5

The IDENTITYOVERRIDE file type modifier cannot be used when loading a table with a GENERATED BY DEFAULT identity column.

6

The LOBSINFILE file type modifier cannot be specified in a partitioned database load when a generated column, that is part of the partitioning key, is defined in terms of a long field or LOB column.

7

Use of the GENERATEDMISSING or IDENTITYMISSING modifier in the current load or import command would result in all columns in the table being excluded from the load operation.

8

If an identity column is part of the partitioning key or a generated column in the partitioning key depends upon an identity column that is not in the partitioning key, the IDENTITYOVERRIDE file type modifier must be specified if the current loading mode is either PARTITION_ONLY, LOAD_ONLY or LOAD_ONLY_VERIFY_PART, or if the value of the SAVECOUNT option is greater than 0.

9

When the target table contains a generated column thati s defined in terms of an identity column and the GENERATEDOVERRIDE file type modifier is specified, then the IDENTITYOVERRIDE file type modifier must be specified as well. This ensures that the generated column values are computed in a way that is consistent with the identity column values in the table.

10

The DUMPFILEACCESSALL file type modifier is only valid when the user has SELECT privileges on the load target table, DUMPFILE modifier is specified, and the database partition resides on an UNIX based operating system.

11

The USEDEFAULTS file type modifier cannot be used in conjunction with the IXF file type or ASC file type with RECLEN modifier.

12

Security label related file type modifiers have been specified, but the target table contains no such columns.

13

The IMPLICITLYHIDDENINCLUDE file type modifier cannot be specified, when loading a table without implicitly hidden columns.

14

The IMPLICITLYHIDDENINCLUDE file type modifier cannot be specified, when exporting a table without SELECT * query.

User response

Check the requirements of the option you are using. Reissue the command using modifier clauses (file type modes) and utility options that are consistent.

SQL3527N The number specified in the FILETMOD parameter for the CODEPAGE option is not valid.

Explanation

In the FILETMOD parameter, the CODEPAGE option was invalid.

User response

Correct the codepage number and resubmit the command.

SQL3528W The delimiter (column delimiter, string delimiter, or decimal point) specified in the CLP command may get translated from the application codepage to the database codepage.

Explanation

When a CLP command is sent from the client to the server, it may get translated from the codepage of client to the codepage of server, if they are different.

User response

To ensure that delimiters are not converted, they should be specified in hex format.

SQL3529N The operation-name operation encountered the unsupported data type data-type in column column-number.

Explanation

The operation-name operation does not support data type data-type found in column column-number.

User response

Please check your table definition and the Data Movement Guide for supported data types.

SQL3530I The Load Query utility is monitoring agenttype progress on partition partitionnumber.

Explanation

The Load Query utility was invoked in an MPP environment.

User response

No action is necessary.

SQL3531I A LOAD RESTART has occurred.

Explanation

The RESTART option was given for the Load currently being queried.

User response

No action is necessary.

SQL3532I The Load utility is currently in the phase phase.

Explanation

This is an informational message indicating the phase of the Load currently being queried.

User response

No action is necessary.

SQL3533I The Load utility is currently building index number of number.

Explanation

This is an informational message returned if the Load currently being queried is in the BUILD phase.

User response

No action is necessary.

SQL3534I The Load DELETE phase is approximately number percent complete.

Explanation

This is an informational message returned if the Load currently being queried is in the DELETE phase.

User response

No action is necessary.

SQL3535W The LOAD command parameter parameter-name is no longer supported; its value will be ignored by the LOAD utility.

Explanation

Your LOAD command contains a parameter that is no longer supported.

User response

Please refer to the documentation for information on temporary sort space for LOAD and suggestions related to LOAD performance tuning.

SQL3536N System temporary table space table-space-name is full.

Explanation

The LOAD utility has encountered a table space full condition while sorting index keys.

User response

Ensure that there is enough space allocated to the system temporary table space table-space-name, at least two times the total size of the indexes being built. Restart the LOAD utility.

SQL3537N Sort memory could not be allocated during the execution of the LOAD utility.

Explanation

Insufficient process virtual memory is available to the LOAD utility for sort processing.

User response

Terminate the application on receipt of this message. Ensure there is enough virtual memory available for sort processing.

Possible solutions include:
  • Disconnect all applications from the database and decrease the size of the sort heap parameter (sortheap) in the corresponding database configuration file.
  • Remove background processes and/or terminate other currently executing applications.
  • Increase the amount of virtual memory available.

SQL3538N The LOAD QUERY utility failed because multiple LOADs are using the same temporary files path.

Explanation

At least one other LOAD was invoked using the same TEMPFILES PATH as the queried LOAD and is still in progress. The LOAD QUERY utility cannot uniquely determine which LOAD to query.

User response

Use the TABLE parameter of LOAD QUERY instead.

SQL3539N LOAD RESTART cannot proceed because LOAD TERMINATE has been attempted at least once.

Explanation

LOAD TERMINATE can only be followed by LOAD TERMINATE.

User response

User can proceed with LOAD TERMINATE only.

SQL3550W The field value in row row-number and column column-number is not NULL, but the target column has been defined as GENERATED ALWAYS.

Explanation

A non NULL field value was encountered in the input file. Because the target column is of type GENERATED ALWAYS, the value cannot be loaded. The column number specifies the field within the row of the missing data.

User response

For LOAD, an explicit, non NULL field value can be loaded into a GENERATED ALWAYS identity column only if the identityoverride file type modifier is used. For non-identity GENERATED ALWAYS columns, the generatedoverride file type modifier can be used to load explicit, non NULL values into a row. If using these modifiers is not appropriate, the field value must be replaced with a NULL if LOAD is to accept the row.

For IMPORT there is no way to override a GENERATED ALWAYS column. The field value must be removed and replaced with a NULL if the utility is to accept the row.

SQL3551W The table contains at least one GENERATED ALWAYS column that the utility will override.

Explanation

An "override" file type modifier (for example, IDENTITYOVERRIDE or GENERATEDOVERRIDE) has been specified.

For IDENTITYOVERRIDE, this may violate the uniqueness property of an identity column defined as GENERATED ALWAYS.

For GENERATEDOVERRIDE, this may result in a non-identity GENERATED ALWAYS column containing a value that does not correspond to its column definition.

User response

No action is required.

SQL3600N The IMMEDIATE CHECKED option of the SET INTEGRITY statement is not valid because the table table-name is a user-maintained materialized query table, a shadow table, or is not in Set Integrity Pending state.

Explanation

The IMMEDIATE CHECKED option of the SET INTEGRITY statement is valid only if the table has been placed in Set Integrity Pending state, is not a user-maintained materialized query table, is not a shadow table, or if one of its ancestors that has been placed in Set Integrity Pending state is also in the invocation list, and all intermediate ancestors are also in the list.

User response

  1. Use the SET INTEGRITY statement with the OFF option to place the table in Set Integrity Pending state.
  2. Use the IMMEDIATE UNCHECKED option for a user-maintained materialized query table or a shadow table.
  3. Include an ancestor of the table to the list of tables to be checked. The ancestor must be in Set Integrity Pending state and all intermediate ancestors must also be in the list.
  4. If the table is in No Data Movement state but it is not in Set Integrity Pending state, issue the SET INTEGRITY statement with the FULL ACCESS option to force the table out of No Data Movement state. Note that all dependent immediate materialized query tables that remain in Set Integrity Pending state are also forced to be fully recomputed in subsequent REFRESH TABLE statements, and all dependent immediate staging tables that remain in Set Integrity Pending state can no longer be used to refresh their dependent materialized query tables.

sqlcode: -3600

sqlstate: 51027

SQL3601W The statement caused one or more tables to automatically be placed in the Set Integrity Pending state.

Explanation

Tables have been placed in the Set Integrity Pending state to enforce integrity constraints or to enforce the data relationship between the base table, the descendent immediate materialized query tables, and the descendent staging tables. Specifically, the following statements caused at least one of the listed tables to be placed in the Set Integrity Pending state.

  • ALTER TABLE ... ATTACH statement forced the target table of the ATTACH into the Set Integrity Pending state
  • ALTER TABLE ... DETACH statement forced descendent immediate materialized query tables or descendent staging tables into the Set Integrity Pending state
  • SET INTEGRITY statement forced descendent foreign key tables, descendent immediate materialized or descendent staging tables into the Set Integrity Pending state

A detached partition that is a newly created detached table is not accessible until its detached dependent materialized query tables and staging tables are maintained.

User response

To validate the integrity for tables in the Set Integrity Pending state, execute the SET INTEGRITY statement with the IMMEDIATE CHECKED or IMMEDIATE UNCHECKED option for these tables. To determine which tables are in the Set Integrity Pending state, issue the following query:

SELECT TABSCHEMA, TABNAME, STATUS
FROM SYSCAT.TABLES
WHERE STATUS = 'C'

To determine which detached tables have been created by the ALTER TABLE ... DETACH statement and are not yet accessible, issue the following query:

SELECT TABSCHEMA, TABNAME, TYPE
FROM SYSCAT.TABLES
WHERE TYPE = 'L'

sqlcode: +3601

sqlstate: 01586

SQL3602W Check data processing found constraint violations and moved them to exception tables.

Explanation

There are rows that violate constraints that were specified to be checked by the SET INTEGRITY statement execution. These were moved to exceptions tables.

User response

Check the exception tables for rows that violate constraints. The rows have been deleted from the original table but can be corrected and transferred back from the exception tables.

sqlcode: +3602

sqlstate: 01603

SQL3603N Integrity processing through the SET INTEGRITY statement has found an integrity violation involving a constraint, a unique index, a generated column, or an index over an XML column. The associated object is identified by name.

Explanation

A row has been found to violate the integrity of a table checked by the SET INTEGRITY statement. The integrity violation was caused by one of the following.

  • A table constraint was violated. The table constraint is identified by name.
  • A unique index was violated. The unique index is identified by name.
  • The column value of a generated column does not match the result of the generation expression. The generated column is identified by name.
  • The table contains an index over an XML column that had an integrity violation. The XML column is identified by name.

The row has not been deleted from the table. The table remains in Set Integrity Pending state.

User response

Execute the SET INTEGRITY statement again using the FOR EXCEPTION option and use the information from the exception tables to correct the data.

sqlcode: -3603

sqlstate: 23514

SQL3604N The statement or command failed because the following exception table is invalid: exception-table-name. Table to which the exception table corresponds: table-name. Reason code: reason-code.

Explanation

You can validate table constraints by using the SET INTEGRITY statement with the IMMEDIATE CHECKED option. Table constraints are also validated when the LOAD utility is being used to move data into newly created tables. When you are validating table constraints, you can use exception tables to store copies of the rows that violate constraints in the tables being checked.

This message is returned when an attempt is made to use an exception table, such as when the SET INTEGRITY statement is executed, or when the LOAD utility or the INGEST utility is being used, and there is something invalid or mismatched about the exception table

The reason code indicates the reason the statement or command failed:

1

The exception table is in the Set Integrity Pending state.

2

The exception table does not have the proper column structure.

3

The exception table has constraints.

4

The exception table has triggers.

5

The exception table has generated columns.

6

The exception table has unique indexes.

7

The exception table is a materialized query table or is a staging table.

8

The exception table has dependent refresh immediate materialized query tables or dependent propagate immediate staging tables.

9

The exception table is the same as the table being loaded into.

10

The exception table is a range clustered table.

11

The exception table is a data partitioned table.

12

The exception table is a detached table.

13

The exception table does not have the same security policy or does not have the same set of protected columns as the table being checked.

14

The exception table has been defined with indexes over XML data.

15

The table has row or column level access control and the exception table does not.

16

An attempt was made to create an expression-based index on an exception table.

User response

Create the exception table as indicated in the relevant section of the documentation and re-run the statement or utility.

sqlcode: -3604

sqlstate: 428A5

SQL3605N Table table-name named in the SET INTEGRITY statement is either not listed to be checked or is an exception table specified more than once.

Explanation

When the FOR EXCEPTION clause is specified in the SET INTEGRITY statement, this error could be caused by one of the following :
  • The table is missing from the list of tables to be checked
  • The table to be checked is the same as an exception table
  • The exception table is specified for more than one table to be checked

User response

Correct the table names and execute the command again.

sqlcode: -3605

sqlstate: 428A6

SQL3606N There is a mismatch in the number of tables being checked and in the number of exception tables specified in the SET INTEGRITY statement.

Explanation

There must be a one-to-one correspondence between the exception tables and the tables that are not materialized query tables or staging tables provided in the invocation list. The tables in the invocation list that are materialized query tables or staging tables must not have corresponding exception tables.

User response

Create the missing exception table for the table that is not a materialized query table or staging table if it does not already exist and specify it in the invocation list in order to execute the command again. Do not specify exception tables for materialized query tables and staging tables.

sqlcode: -3606

sqlstate: 428A7

SQL3608N Cannot check a dependent table dependent-table-name using the SET INTEGRITY statement while the parent table or underlying table parent-table-name is in the Set Integrity Pending state or if it will be put into the Set Integrity Pending state by the SET INTEGRITY statement.

Explanation

The parent table or underlying table must not be in the Set Integrity Pending state either before or after the SET INTEGRITY statement, or it must be included in the invocation list in order to check a dependent table.

User response

Ensure that the parent table is not in the Set Integrity Pending state by executing the SET INTEGRITY statement to check the parent table. If the dependent table is a materialized query table or staging table, ensure that the underlying table is not in the Set Integrity Pending state by executing the SET INTEGRITY statement to check the underlying table.

If the dependent table is not a materialized query table or staging table, it is recommended to check the parent table first. It is also possible to check the dependent table and include the parent table in the invocation list. In this case, the statement could still fail if there are rows in the parent table which violate the constraint and these rows are not deleted and put into an exception table. This can happen if the FOR EXCEPTION option is not used.

If the dependent table is a materialized query table or staging table, it is recommended to check the underlying table first. It is also possible to refresh the dependent materialized query table and include the underlying table in the invocation list. In this case, the statement could still fail if there are rows in the parent table which violate the constraint and these rows are not deleted and put into an exception table. This can happen if the FOR EXCEPTION option is not used.

In the case of a referential cycle, all tables must be included in the invocation list.

sqlcode: -3608

sqlstate: 428A8

SQL3700W Device device is full. There are active-devices other active devices. Please mount new media or take appropriate action.

Explanation

The media on the specified device is full. This device is one of the active-devices + 1 target devices to which unloaded data is being directed.

User response

Take ONE of the following actions:
  • Mount a new target media on the specified device and continue unloading by invoking unload with caller action 1 (SQLU_CONTINUE).

    OR

  • If active-devices is not zero, continue the unload without this device by invoking the UNLOAD utility with the caller action 4 (SQLU_DEVICE_TERMINATE).

    OR

  • Cancel the unload by invoking the UNLOAD utility with caller action 2 (SQLU_TERMINATE).

SQL3701W The lobpaths parameter was specified, but the table does not contain any LOB or Long data. This parameter will be ignored.

Explanation

The lobpaths parameter specifies a separate target for LOB and Long data. The table does not contain any LOB or Long data, so the targets specified by the lobpaths parameter will not be used.

User response

No action required.

SQL3702W Warning. SQLCODE sqlcode was received for device device. Unload will attempt to continue without this device.

Explanation

SQLCODE sqlcode was detected for the specified device which is one of the targets for the unload. Unload will continue but will ignore this device.

User response

The media loaded on the specified device will not contain any unloaded data and should not be included with the media supplied to the LOAD utility when the unloaded data is being loaded. In order to fix the problem with the device, look up the returned SQLCODE in the Message Reference.

SQL3703W xxx of yyy number of type type pages have been unloaded and sent to be written out to the target media.

Explanation

The table being unloaded consists of yyy pages of the specified type of data. xxx of these have been processed by the UNLOAD utility and have been sent to a media writer which will write the data to the target media.

type is one of:
  • 0 for regular data
  • 2 for Long data and allocation information
  • 3 for LOB data
  • 4 for LOB allocation information

Note that for Long and LOB data, xxx may be less than yyy when unload is complete, because unused space is not unloaded, but will be recreated when the data is reloaded.

Even for regular data, a final message where xxx = yyy may not be issued. Instead message 3105 is used to indicate that the unload completed successfully.

User response

This is an informational message. No action is required.

SQL3704N The num_buffers parameter specified is invalid.

Explanation

The num_buffers parameter determines the number of buffers that the utility will use. The minimum is 2 if the lobpaths parameter is not specified and 3 if the lobpaths parameter is specified. This is the minimum required to allow the utility to work. There is, however, an optimal number of buffers that the utility will use if this parameter is not specified. This optimal number is based on the number of internal processes that the utility will have running and whether or not the lobpaths parameter was specified. If the number of buffers specified is less than the optimal number, some processes will be waiting for buffers to use. Therefore, it is recommended to specify 0 for this parameter and let the utility choose the number of buffers. Only specify this parameter if, due to the size of the utility storage heap, it is necessary to limit the amount of memory that the utility uses.

User response

Resubmit the command using a valid num_buffers parameter.

SQL3705N The buffer size parameter specified is not valid. The buffer size must be specified as 0 or be between 8 and 250000 inclusive. For multiple buffers, the total buffer size must not exceed 250000.

Explanation

The application calling the utility has supplied a buffer size parameter that is not valid. The buffer size is used to determine the internal buffer size. The value is the number of 4K pages that are obtained for this buffer. The value must be specified as 0 or be between 8 and 250000 inclusive. If there are multiple buffers, the number of buffers multiplied by the buffer size must not exceed 250000.

When 0 is specified:
  • for a table whose regular data is in a database managed storage table space, the default buffer size chosen is the extent size for the table space or 8, whichever is larger.
  • for a table whose regular data is in a system managed storage table space, the default buffer size chosen is 8.

User response

Reissue the command with a valid buffer size.

SQL3706N A disk full error was encountered on path/file.

Explanation

A disk full error was encountered during the processing of a database utility. The utility stops.

User response

Ensure enough disk space is available for the utility or direct the output to other media such as tape.

SQL3707N The sort memory size parameter specified size1 is not valid. The minimum size required is size2.

Explanation

The sort memory size is not large enough for sorting the keys of the index(es).

User response

Reissue the command with a valid sort memory size.

To ensure that only the minimum amount of storage is used, specify a value of 0 (to let it default). However, using more than the minimum should improve the performance of the sort.