| 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):
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:
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 space 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 LIST TABLESPACES command.
The following is a list of reason codes:
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.
This could be the result of a hardware error. If the error is a hardware error, take the appropriate action as specified in the Troubleshooting Guide for hardware problems and restart or rerun the load.
This could be the result of a disk full condition or a hardware error. Refer to the file type list below 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 as specified in the Troubleshooting Guide for hardware problems and restart or rerun the load.
A file required by the load contains incorrect data. See the action described for TEMPFILES_PATH.
If the load cannot be restarted or rerun, contact your IBM service representative.
If the load cannot be restarted or rerun, contact your IBM service representative.
The following is a list of file types:
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.
| 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:
Try to restart the load. If the error persists, provide the function, reason code and error code to your technical service representative.
Try the load again using the DB2 Client/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):
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.
| 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:
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 | A copy target cannot be provided when both log retain and user exits are disabled. |
Explanation: A copy target has been specified on invocation of load for a database that has both log retain and user exits disabled. Copy targets are not valid for such databases.
The utility stops processing.
User Response: Verify that the database should have log retain and user exits disabled and invoke the load without specifying a copy target.
| 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:
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.
| 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:
The utility stops processing.
User Response: Correct the value and resubmit the command.
| SQL3525W | 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 options. 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:
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 Load progress on node "<node>". |
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 DB2 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 encounetered 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:
| 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.