SQL3500W The utility is beginning the "<phase>" phase at time "<timestamp>".
Cause: 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.
Action: 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.
Cause: 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.
Action: No action is required.
SQL3502W The utility has encountered "<number>" warnings which exceeds the total number of warnings allowed.
Cause: 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.
Action: 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.
Cause: 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.
Action: No response required.
SQL3504W A consistency point is being established.
Cause: Consistency points will be established at times other than the regular interval specified in the SAVECOUNT parameter at invocation when:
Action: 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.
Cause: In the filetmod parameter, the RECLEN option was specified for an ASC file. The length specified is not valid.
Action: 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.
Cause: 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.
Action: 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.
Cause: 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.
Action: Correct the parameter and resubmit the command.
SQL3508N Error in accessing a file of type "<file-type>" during load or load query. Reason code: "<reason-code>". Path: "<path/file>".
Cause: An error occurred while trying to access a file during load or load query processing. The utility stops processing.
Action: 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 REMOTE_FILE.
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.
One reason for getting this message could be that two loads are running using the same remote file (or defaulting to the same value). The remotefile parameter must be specified when running load in order to ensure that each load uses a different set of files.
If the file in the third token has the extension ".msg", make sure there is enough disk space to write out the message information for messages that occur during the load. If this is a load query, the remotefile parameter must be the same as the remotefile parameter used for the load whose status is being queried.
If the file in the third token has the extension ".rid", and this is a restart of a load in the delete phase, ensure that the remotefile parameter is the same as the first load. This file created from the original load is required by a load being restarted in the delete phase. If the correct remotefile parameter was used, it is possible that the file was removed or corrupted and the load must be restarted in the build phase.
If the file in the third token has the extension ".log", ensure that there is enough disk space to write temporary meta-data in this directory. If this is a RESTART, the remotefile parameter must be the same as the remotefile parameter used for the original load since this file which is created during the original load is required by load restart. If the correct remotefile parameter was used and sufficient disk space is available, it is possible that the logfile was removed or corrupted, and either a load replace must be done or the table space must be restored from an existing backup.
SQL3509W The utility has deleted "<number>" rows from the table.
Cause: 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.
Action: No action is required.
SQL3510N The working directory for the sort phase cannot be accessed.
Cause: One or more of the specified working directories for the sort phase either does not exist or has no read/write permission.
Action: 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.
Cause: 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.
Action: 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.
Cause: 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.
Action: 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.
Cause: DB2CS files cannot be loaded into a database with a codepage that differs from the original database.
Action: 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>".
Cause: A system error occurred during database utility processing.
Action: 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>".
Cause: This is an informational message indicating that a phase has finished. The phases are (in order of appearance):
Action: No action is required.
SQL3516N The utility could not restart the load as specified.
Cause: 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.
Action: 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.
Cause: 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.
Action: 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.
Cause: The source cannot be used to load this table because one of the following reasons:
Action: 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>".
Cause: The Load Utility is about to attempt to perform a Consistency Point to commit the table data that has already been loaded.
Action: 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.
Cause: The Consistency Point performed by Load was successful.
Action: This is an informational message only. No response is required.
SQL3521N The input source file "<sequence-num>" was not provided.
Cause: 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.
Action: 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.
Cause: 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.
Action: 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>".
Cause: No messages are returned from a query of the remote file. The possible reason codes are:
Action: Ensure that the correct remote file has been specified. If the remote file 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 remote file will not be created until the utility is in progress and it will be deleted after the completion of the utility.
SQL3524N Option "<option>" has an invalid value of "<value>". It must be in the range of 0 and 100 inclusive.
Cause: The value provided must be an integer and in the range of 0 and 100.
For option TOTALFREESPACE, the value 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.
For option PAGEFREESPACE, the value is interpreted as a percentage of each data page that is to be left as free space.
The utility stops processing.
Action: Correct the value and resubmit the utility in either REPLACE or RESTART mode.
SQL3525W The "<option-1>" option is incompatible with the "<option-2>" option.
Cause: Incompatible options have been provided to the utility.
Action: 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>".
Cause: The load file type mode (modifier) indicated, is incompatible with your load/import/export command. This is because of one of the following reasons:
Action: Check the requirements of the option you are using. Reissue the command using modifier clauses (file type modes) and utility options that are consistent. * SQLULA_INVALID_CODEPAGE
SQL3527N The number specified in the FILETMOD parameter for the CODEPAGE option is not valid.
Cause: In the FILETMOD parameter, the CODEPAGE option was invalid.
Action: 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.
Cause: 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.
Action: To ensure that delimiters are not converted, they should be specified in hex format.