SQL3000-3999

SQL3001C

A system I/O error occurred while opening the output file.

The command cannot be processed. No data is processed.

For IMPORT/LOAD, verify that the output file exists. For EXPORT, verify that the output media has enough free space. Resubmit the command with a valid output file name, including the correct path. Look in the message file for additional information.

SQL3002C

A system I/O error occurred while writing to the output data file. The output may be incomplete or the disk may be full.

The utility stops processing.

If the output data file is incomplete, erase it and resubmit the command.

SQL3003C

A system I/O error occurred while closing the output data file.

The file is not closed.

If the output data file is incomplete, erase it and resubmit the command.

SQL3004N

You can insert data from a file into a database using the load and import utilities, and you can export data from a database to a file using the export utility. Only certain file formats are supported for use with these utilities.

This message is returned when an attempt is made to use an unsupported file type with one of the load, import, or export utilities.

The command cannot be processed.

Resubmit the command or API specifying a valid value for the parameter named filetype.

SQL3005N

An interrupt was received during processing. The user may have pressed the interrupt key sequence.

The utility stops processing. Any database updates not committed are rolled back.

Resubmit the command. If doing an import, see Command Reference for information on how to use commitcount and restartcount parameters. If doing a load, see Command Reference for information on how to restart the load.

SQL3006C

A system I/O error occurred while opening the message file. This error can refer to a problem on either the client or the server.

The command cannot be processed.

Resubmit the command with a valid message file name, including the correct path.

SQL3007C

A system I/O error occurred while writing to the message file.

Processing may not have finished.

If the message file is incomplete, erase it and resubmit the command.

SQL3008N

The IMPORT or EXPORT utility could not connect to the database.

No data is imported or exported.

Look at the error number in the message for more information. Make changes and resubmit the command.

SQL3009N

The Action String (for example, "REPLACE into ..." for Export or "INSERT into ..." for Import and Load) parameter in the command is not valid. The Action String pointer may be incorrect. The Action String structure may contain characters that are not valid. The Action String structure may contain characters that are not valid. Either the deprecated or new parameter may be used for Action String.

The command cannot be processed.

Verify the Action String pointer and the structure it points to. Resubmit the command with a valid Action String.

SQL3010N

The METHOD parameter in the command is not valid. The METHOD pointer may be incorrect. The structure that the METHOD points to may be incorrect. The METHOD structure may contain characters that are not valid.

The command cannot be processed.

Examine the METHOD pointer and the structure it points to. Resubmit this command with a valid METHOD.

SQL3011C

A memory allocation error occurred. Not enough memory is available to process the command, or there was an error freeing storage.

The command cannot be processed.

SQL3012C

An operating system error occurred.

The command cannot be processed.

Check your message file, correct the problem and resubmit the command.

SQL3013N

The filetmod specified is outside the acceptable range (greater than or equal to zero and less than or equal to 8000).

The command cannot be processed.

Examine the filetmod pointer and the structure it points to. Resubmit the command with a valid filetmod.

SQL3014C

A system I/O error occurred while closing the message file.

The message file is not closed.

If the message file is incomplete, resubmit the command.

SQL3015N

An SQL error occurred during the utility call.

The utility stops processing.

Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.

SQL3016N

A keyword that does not apply to the filetype for the utility was found in the filetype modifier (the filetmod parameter or the phrase following MODIFIED BY in a CLP command).

The utility stops processing.

Remove the filetype modifier or specify at least one valid keyword in the filetype modifier. See the Command Reference for more information on filetype modifiers.

SQL3017N

For delimited ASCII files (DEL for the IMPORT or LOAD commands, and FORMAT DELIMITED for the INGEST command), one of two errors occurred:

• The character specified for either the column delimiter, character string delimiter, or decimal point character is not valid.
  • For SBCS or UTF-8 data, the valid range for the delimiters is 0x00 - 0x7F inclusive.
  • For MBCS data, the valid range for the delimiters is 0x00 - 0x3F inclusive.
  • For EBCDIC MBCS data, the valid range for the delimiters is 0x00 - 0x3F inclusive with the exception that the delimiters cannot be the SHIFT-OUT (0x0E) or the SHIFT-IN (0x0F) characters.
• The same character is specified for more than one of the preceding items.

The command cannot be processed.

Examine the specified delimiters for validity and uniqueness. Resubmit the command with valid delimiter overrides.

SQL3018N

For Delimited ASCII (DEL), the period cannot be specified as the character string delimiter.

The command cannot be processed.

Resubmit the command with valid delimiter overrides.

SQL3019N

No Action String (for example, "REPLACE into ...") parameter is specified for this utility call. This parameter is required.

The command cannot be processed.

Resubmit the command with an Action String parameter.

SQL3020N

The user attempted to export data without having DATAACCESS authority, or either the CONTROL privilege or the SELECT privilege for each table involved in the export.

The export action is not performed.

Request appropriate authorization before exporting data from tables.

SQL3021N

The user attempted to import data without the appropriate authorization for the specified option and table.

Importing by using the INSERT option requires one of the following authorizations:

• DATAACCESS authority
• CONTROL privilege on the table, view, or entire hierarchy
• INSERT and SELECT privileges on the table, view, or entire hierarchy.

Note: "entire hierarchy" refers to all subtables or object views in the hierarchy.

Importing into an existing table or view by using the INSERT_UPDATE, REPLACE, or REPLACE_CREATE option requires one of the following authorizations:

• DATAACCESS authority
• CONTROL privilege on the table, view, or entire hierarchy.

Note: "entire hierarchy" refers to all subtables or object views in the hierarchy.

Importing into a table that does not exist by using the CREATE or REPLACE_CREATE option requires one of the following authorizations:

• DBADM authority
• CREATETAB authority on the database and one of the following authorizations:
  • IMPLICIT_SCHEMA authority on the database, if the schema name of the table does not exist
  • CREATEIN privilege on the schema, if the schema name of the table exists

The import operation is not performed.

Ensure that you are authorized to perform the import operation.

SQL3022N

In IMPORT or EXPORT, during processing of the SELECT string from the Action String (for example, "REPLACE into ...") structure, an SQL error occurred.

The command cannot be processed.

Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.

SQL3023N

The database name parameter is not valid. See the SQLERRD[0] field in the SQLCA for more information.

The database name must contain 1 to 8 characters and the characters must be from the database manager base character set.

The command cannot be processed.

Resubmit the statement with a valid database name parameter.

SQL3024N

A system I/O error occurred while opening the format file. This error can refer to a problem on either the client or the server.

A possible cause may be that the format file is in use by another application.

The command cannot be processed.

Ensure that the format file is valid, including the path, and that it is not currently in use by another application.

Resubmit the command. Look in the diagnostics log file for additional information.

SQL3025N

The parameter contains a path, directory, or file name that is not valid.

For IMPORT and EXPORT, verify the datafile parameter.

For LOAD, verify that each entry in the parameters of type sqlu_media_list: datafile should contain valid filenames; lobpaths copytarget, and workdirectory should contain valid paths on the server including the final separator and a null terminator.

The pointer to lobpaths, copytarget and workdirectory must be valid or null.

The pointer to the targets in these structures must be valid.

Check that sessions and media_type are specified correctly.

Also, if the lobpaths parameter is specified, check that the media_type is the same as that specified for the datafile structure.

If the filetype is IXF, the length of the file name may be too long.

This error is also returned when the database manager does not have read access permission for the specified file or path.

The command cannot be processed.

Ensure the database manager has read access permission for the specified file or path.

Resubmit the statement with a valid parameter.

SQL3026N

For IMPORT or EXPORT, the msgfile parameter contains a path, directory, or file name that is not valid.

For LOAD, either the msgfile parameter contains a path, directory, or file name that is not valid on the client, or the tempfiles path is not valid on the server.

If the database to which the application is connected is a remote database, the msgfile must be fully qualified. For a local database the utility will attempt to fully qualify the msgfile if it is not already fully qualified. Also verify that the pointer to the msgfile is valid.

The command cannot be processed.

Resubmit the statement with a valid msgfile and/or tempfiles path parameter.

SQL3027N

A system I/O error occurred while reading from the format file. This error can refer to a problem on either the client or the server.

The command cannot be processed.

Verify that the format file is readable.

SQL3028N

The export method indicator must be either N for Names or D for Default.

The command cannot be processed.

Resubmit the statement with a valid method indicator.

SQL3029N

The filetype parameter was either not specified or null. The system does not know which format to use for the data file.

The command cannot be processed.

Resubmit the statement with a valid filetype.

SQL3030C

A system I/O error occurred while opening the input file. This error can refer to a problem on either the client or the server.

A possible cause may be that the input file is in use by another application.

The command cannot be processed.

Ensure that the input file is valid, including the path, and that it is not currently in use by another application.

Resubmit the command.

SQL3031C

A system I/O error occurred while reading from the input file. This error can refer to a problem on either the client or the server.

The command cannot be processed.

Verify that the input file is readable.

SQL3032N

For the IXF filetype, the LOAD/IMPORT method indicator must be either N for Names, P for Positional, or D for Default.

The command cannot be processed.

Resubmit the command with a valid method indicator.

SQL3033N

For IMPORT, the Action String (for example, "REPLACE into ...") parameter does not contain the keyword INSERT, REPLACE, CREATE, INSERT_UPDATE, or REPLACE_CREATE. For LOAD, the Action String parameter does not contain the keyword INSERT, REPLACE, or RESTART. The keyword must be followed by at least one blank.

The command cannot be processed.

Resubmit the command with a valid Action String parameter.

SQL3034N

The INTO keyword is missing or spelled incorrectly. INTO must be followed by at least one blank.

The command cannot be processed.

Resubmit the command with a valid Action String (for example, "REPLACE into ...") parameter.

SQL3035N

For IMPORT, the tablename in the Action String (for example, "REPLACE into ...") is not valid. For LOAD, the tablename or the exception tablename in the Action String is not valid.

The command cannot be processed.

Resubmit the command with a valid tablename. Also ensure that all command keywords and parameters are entered in the correct order.

SQL3036N

The tcolumn-list must be delimited by parentheses. The list was not terminated by the closed parenthesis.

The command cannot be processed.

Resubmit the statement with a valid, complete column list in the Action String (for example, "REPLACE into ...") parameter.

SQL3037N

An SQL error occurred during processing of the Action String (for example, "REPLACE into ...") parameter.

The command cannot be processed.

Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.

SQL3038N

For IMPORT, there are characters other than blanks after the closing parenthesis of the column list in the Action String (for example, "REPLACE into ...") parameter. For LOAD, there are characters other than blanks after the closing parenthesis of the column list and/or the exception tablename in the Action String parameter.

The command cannot be processed.

Resubmit the command with a valid Action String parameter.

SQL3039W

A lesser degree of parallelism, requiring less memory, will be used.

SQL3040N

One of the following reason codes may apply:

1

Either the file file-name is not a valid sqlu_media_list or the values provided are not valid. The media_type must be SQLU_CLIENT_LOCATION.

2

There are not enough file names provided. There are more documents to be exported than the number of file names provided multiplied by SQLU_MAX_SESSIONS.

3

The combination of a path name and a file name exceeds the maximum length of 255 bytes per file.

4

The file file-name cannot be accessed.

5

The file name file-name contains a path name but paths should not be included.

6

The sum of the starting position and the length of the input data exceeds the size of the file with file name file-name.

Determine which reason code applies, correct the problem, and resubmit your command.

SQL3041N

Sybase does not support date values prior to 1753.

Please give a valid date value and issue the command again.

SQL3042N

The value specified for LINKTYPE for a DATALINK column is invalid.

Check the LINKTYPE specified. Correct the value and resubmit the command.

SQL3043N

Correct the specification and resubmit the command.

SQL3044N

The DATALINK SPECIFICATION for a DATALINK column has duplicate specifications for DL_URL_REPLACE_PREFIX or DL_URL_DEFAULT_PREFIX.

Remove the duplicate specification and resubmit the command.

SQL3045N

The dcolumn position is less than 1 or greater than the maximum number of columns (1024) in a delimited file.

The command cannot be processed.

Resubmit the command with valid dcolumn positions.

SQL3046N

For METHOD methods other than Default, the number of columns specified must be a positive number (greater than 0).

The command cannot be processed.

Resubmit the command with a valid number of columns in the METHOD parameter.

SQL3047N

The only valid LOAD/IMPORT methods for Delimited ASCII files are P for Positions or D for Default.

The command cannot be processed.

Resubmit the command with a valid import method.

SQL3048N

When fewer columns are specified in the METHOD list than are specified for the target table, the values for the missing input columns are loaded as nulls. Because the columns in the target table that correspond to one or more of these input columns are not nullable, null cannot be inserted.

The file cannot be loaded.

Define a new table that has the same number of columns as the input file or that has nullable columns. Resubmit the command.

SQL3049N

The database column type is not valid for this format file. The database column is not nullable so the utility is ended.

The utility stops processing. No data is loaded.

Redefine the database table so the columns are compatible with the columns loaded from the file.

SQL3050W

If an IMPORT of an IXF data file has been issued and the code page of the character data in the IXF file is different from the code page of the application invoking the import operation, a conversion will be made from the code page of the data file to the code page of the application and the operation will continue.

If a LOAD of an IXF data file has been issued and the code page of the character data in the IXF file is different from the database code page, a conversion will be made from the code page of the data file to the code page of the database and the operation will continue.

If you do not want a conversion to be performed, invoke the utility using the FORCEIN option; otherwise no action is required.

SQL3051W

The data that was loaded into the CLOB or DBCLOB column is stored in a separate file and no conversions have been performed on it.

To properly load the data, call the utility from an application that has the same code page as the IXF file.

This is a warning only.

SQL3052N

Reason codes:

1

The input data files come from different paths, and there are type columns in the target table. The type path parameter must be specified.

2

The load is issued from a remotely connected client and there are files containing the "type" data. The "type" path parameter must be specified.

Specify the path and resubmit your command.

SQL3054N

The end of the file was reached before the expected end of the first record. The file may not be a PC/IXF file.

The LOAD/IMPORT utility stops processing. No data is imported.

Verify that the input file is correct.

SQL3055N

The value in the length field of the first record is not the ASCII representation of a number. The file may not be a PC/IXF file.

The utility stops processing. No data is loaded.

Verify that the input file is correct.

SQL3056N

The value in the length field of the H record is not large enough for a valid H record. The file may not be a PC/IXF file.

The utility stops processing. No data is loaded.

Verify that the input file is correct.

SQL3057N

The type field in the first record is not H. The first record is not a valid H record. The file may not be a PC/IXF file.

The utility stops processing. No data is loaded.

Verify that the input file is correct.

SQL3058N

The identifier field in the H record does not identify the file as a PC/IXF file.

The utility stops processing. No data is loaded.

Examine the identifier field in the H record.

SQL3059N

The version field in the H record contains a value that is not valid.

The utility stops processing. No data is loaded.

Examine the version field in the H record.

SQL3060N

The Heading-record-count field in the H record is not an ASCII representation of a number or is a number that is not valid for this field.

The utility stops processing. No data is loaded.

Examine the HCNT field in the H record.

SQL3061N

The single-byte and/or double-byte code page field in the H record is not an ASCII representation of a number or is a number that is not valid for this field.

The utility stops processing. No data is loaded.

Examine the single-byte and double-byte code page field in the H record, change them to appropriate values, and resubmit the command.

SQL3062N

The double-byte code page field in the H record is not an ASCII representation of a number or is a number that is not valid for this field.

The utility stops processing. No data is loaded.

Examine the double-byte code page field in the H record, change it to an appropriate value, and resubmit the command.

SQL3063N

The single-byte code page value in the H record is not compatible with the application code page value. When the FORCEIN option is not used, the data cannot be loaded unless conversion from value 1 to value 2 is supported.

The utility stops processing. No data is loaded.

To load this data, resubmit the command with the FORCEIN option.

SQL3064N

The double-byte code page value in the H record is not compatible with the application code page value. When the FORCEIN option is not used, the data cannot be loaded unless value 1 and value 2 are the same.

The utility stops processing. No data is loaded.

To load data where the double-byte code page values do not match, resubmit the command with the FORCEIN option.

SQL3065C

The system encountered an error while determining the code page of the application.

The utility stops processing. No data is loaded or unloaded.

Contact your technical service representative.

SQL3066N

The end of the file was reached while the system was looking for the T record or while it was reading the T record.

The utility stops processing. No data is loaded.

Examine the T record of the input file. If the PC/IXF file was copied from one medium to another, compare the copy with the original or repeat the copy process.

SQL3067N

The length field in the T record is not an ASCII representation of a number.

The utility stops processing. No data is loaded.

Examine the length field in the T record.

SQL3068N

The value in the length field of the T record is not large enough so the T record is not valid.

The utility stops processing. No data is loaded.

Examine the length field in the T record.

SQL3069N

After the H record, the first record not an A record is also not a T record. The H record must be immediately followed by a T record but A records may exist before the T record.

The utility stops processing. No data is loaded.

Examine the records following the H record.

SQL3070N

The length field in an A record is a number that is not valid for this field.

The utility stops processing. No data is loaded.

Examine the length field in the A records.

SQL3071N

The data-convention field in the T record is a value other than C.

The utility stops processing. No data is loaded.

Examine the data-convention field in the T record.

SQL3072N

The data-format field in the T record is a value other than M.

The utility stops processing. No data is loaded.

Examine the data-format field in the T record.

SQL3073N

The machine format field in the T record is a value other than PC bbb, where each b is a blank.

The utility stops processing. No data is loaded.

Examine the machine format field in the T record.

SQL3074N

The data-location field in the T record is a value other than I.

The utility stops processing. No data is loaded.

Examine the data-location field in the T record.

SQL3075N

The C-record count field in the T record is not an ASCII representation of a number or is a number that is not valid for this field.

The utility stops processing. No data is loaded.

Examine the CCNT field in the T record.

SQL3076N

The name length field in the T record is not an ASCII representation of a number or is a number that is not valid for this field.

The utility stops processing. No data is loaded.

Examine the name length field in the T record.

SQL3077N

The value in the CCNT field of the T record is larger than the maximum allowed for the indicated release.

The utility stops processing. No data is loaded.

Examine the CCNT field in the T record.

SQL3078N

The length field in an A record is not an ASCII representation of a number.

The utility stops processing. No data is loaded.

Examine the length fields in the A records.

SQL3079N

The length field in a C record is not an ASCII representation of a number.

The utility stops processing. No data is loaded.

Examine the length field in the C records.

SQL3080N

The value in the length field of a C record is not large enough so the C record is not valid.

The utility stops processing. No data is loaded.

Examine the length field in the C records.

SQL3081N

The number of C records found (in the correct position) is less than the number expected from the C-record-count (CCNT) in the T record.

The utility stops processing. No data is loaded.

Examine the T and C records.

SQL3082N

The end of the file was reached while the system was looking for a C record or while it was still reading a C record.

The utility stops processing. No data is loaded.

Examine the C records in the input file. If the PC/IXF file was copied from one medium to another, compare the copy with the original or repeat the copy process.

SQL3083N

The D-record-id field in the C record for the indicated column is not an ASCII representation of a number.

The utility stops processing. No data is loaded.

Examine the D-record-id field in the C record.

SQL3084N

The D-record-position field in the C record for the indicated column is not an ASCII representation of a number.

The utility stops processing. No data is loaded.

Examine the D-record-position field in the C record.

SQL3085N

The D-record-id or the D-record-position fields in the C record for the indicated column contain a value that is either out of the value range or is not correct relative to the previous C record.

The utility stops processing. No data is loaded.

Examine the D-record-id and D-record-position fields in the C record.

SQL3086N

Either there was not a PC/IXF column specified to be exported into the indicated column or the specified PC/IXF source column does not exist. Nulls cannot be inserted because the database column is not nullable.

The utility stops processing. No data is loaded.

Check the METHOD parameter for erroneous names or positions or for fewer entries in the METHOD parameter than the Action String (for example, "REPLACE into ...") parameter states or implies.

SQL3087N

The PC/IXF column cannot be loaded into the indicated database column and the reason was given in a previous message in the message log. Nulls cannot be inserted because the database column is not nullable.

The utility stops processing. No data is loaded.

Read the previous messages to understand why the column is not valid.

SQL3088N

The source PC/IXF column is not compatible with the target database column. The column types or lengths may be incompatible. Nulls cannot be inserted because the database column is not nullable.

The utility stops processing. No data is loaded.

Compare the columns in the source PC/IXF file with the columns in the database.

SQL3089N

Some record other than a D record was found where a D record was expected.

The utility stops processing. No data is loaded.

Examine the D records in the file.

SQL3090N

The length field in a D record is not an ASCII representation of a number.

The utility stops processing. No data is loaded.

Examine the length field in the D records.

SQL3091N

The length field in a D record is a number that is not valid for this field.

The utility stops processing. No data is loaded.

Examine the length field in the D records.

SQL3092N

The identifier field in a D record is not valid. One or more D records may have been written out of sequence.

The utility stops processing. No data is loaded.

Examine the identifier field in the D records.

SQL3094N

The specified column was not in the input file. Because the corresponding database column is not nullable, data cannot be loaded into the column.

The utility stops processing. No data is loaded. The column names processed before the error occurred are in the database

Verify that the input file contains the specified column names.

SQL3095N

A column position was specified that was not within the range of 1 to 256.

The utility stops processing. No data is loaded. The column names processed before the error occurred are in the database.

Verify that the specified column position is within the range 1 to 256.

SQL3100W

The length or maximum length of the specified output column is greater than 254 bytes. Columns larger than 254 are not supported by some other products.

The entire field is exported without truncation.

Prior to DB2 Version 9.5 only, this message is returned when data is exported in DEL file format and the length of one or more columns in the output file is longer than 254 bytes.

If the output file cannot be processed by another product, export only a substring of the incorrect column, redefine the table, or manually truncate the data in the DEL column.

SQL3101W

The system puts character string delimiters around the character strings being exported but it found a character string that already has the delimiter in the character string.

Delimiters will be placed around the character string. Future use of that string leads to an appearance of truncation. Processing can continue.

Review the data for the given column and row in the output table or file. To avoid loss of data, change the character delimiter to some character that is not in the data.

SQL3102W

The number of columns taken from the input file or table is greater than the number to be put in the output table or file.

Only data for the columns indicated in the output table or file will be processed. Data in the excess input columns is not processed.

Review the data in the output table or file.

SQL3103W

The number of columns taken from the input file or table is less than the number to be put in the output table or file.

Only data for the columns indicated in the input table or file will be processed. Data in the excess output columns is not processed.

Review the data in the output table or file.

SQL3104N

This is the normal beginning message.

No action is required.

SQL3105N

This is the summary message for the export utility which is printed at the end of the message file. This message will state how many rows resulting from the SELECT statement were processed before the export utility terminated.

If an sqlcode of 0 was returned from the utility, then no response is required. If an sqlcode of 3107 was returned, check the message file for warnings that occurred during the export and resubmit the command if desired. If a negative sqlcode was returned, an error occurred during the export and the data file may not contain all the data requested. The command should be resubmitted with the error corrected.

SQL3106N

The error message may be incomplete or formatted incorrectly.

No action is required.

SQL3107W

You can load data into a database from a file, tape, or named pipe using the LOAD command. You can specify that any warnings or errors from the LOAD processing be printed to a message file. If no message file is specified, the warnings or errors are printed to standard out (unless the database manager instance is configured as a partitioned-database environment.)

This message is returned when at least one warning was received during processing. If a message file is being used, the warnings and errors will be printed there.

This warning does not affect processing.

Review the message file warning.

SQL3108W

SQL3109N

This is the normal beginning message. The message may indicate the name of a temporary file created on the server instead of the source file.

No action is required.

SQL3110N

This is the normal ending message.

No action is required.

SQL3111C

A system I/O error occurred while closing the input data file. This error can refer to a problem on either the client or the server.

The file is not closed.

Examine the input file for an I/O error.

SQL3112W

There are fewer columns specified in the input file than in the output table. Because the extra columns in the table are defined as nullable, the values in those columns are filled with nulls.

No action is required.

SQL3113W

The database column type is not valid for this file. Because the column is nullable, nulls are inserted.

Null values are loaded for the indicated column.

SQL3114W

The text that was loaded is shown in the text token.

The contents of the field may be incomplete.

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

SQL3115W

The field value is longer than 32700 bytes.

The value was truncated after 32700 bytes.

Compare the value in the output table with the input file. If necessary, correct the input file and resubmit the command or edit the data in the table. Check for unmatched character string delimiters.

SQL3116W

A null field value was encountered in the input file. Because the target column in the table is not nullable, it cannot be loaded.

For files other than ASCII files, the value of the column number specifies the field within the row of the missing data. For ASCII files, the value of the column number specifies the byte position within the row of the missing data.

The row is not loaded.

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

SQL3117W

The value in the specified field cannot be converted to a SMALLINT value. There may be a data type mismatch. The value may be larger than a 2-byte integer.

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.

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

SQL3118W

The value in the specified field cannot be converted to a SMALLINT value. There may be a data type mismatch. The value may be larger than a 2-byte integer. 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.

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

SQL3119W

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

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

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

Examine the input data. If necessary, take one of the following actions:

• Correct the input data and resubmit the command.
• In the output table, manually replace the null with the correct value.

SQL3120W

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

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

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

Examine the input data. If necessary, take one of the following actions:

• Correct the input data and resubmit the command.
• In the output table, manually insert a row containing the correct values.

SQL3121W

The value in the specified field cannot be converted to a FLOAT value. 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.

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

SQL3122W

The value in the specified field cannot be converted to a FLOAT value. There may be a data type mismatch. 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.

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

SQL3123W

The value in the specified field cannot be converted to a PACKED DECIMAL value. 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.

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

SQL3124W

The value in the specified field cannot be converted to a PACKED DECIMAL value. There may be a data type mismatch. 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.

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

SQL3125W

The length of the field data in the input file was longer than the length of the database field where it is being loaded.

The character data was truncated.

Compare the value in the output table with the input file. If necessary, correct the input file and resubmit the command or edit the data in the table. The width of the database column cannot be increased. If necessary, define a new table with wider columns and repeat the process.

SQL3126N

Connecting to a database cataloged as remote and issuing a LOAD command requires absolute path for data files.

The pointers to lobpaths, copytarget, tempfiles and part_file_location must be either absolute paths or null.

Resubmit the statement with valid absolute file and pathnames.

SQL3128W

The date value in the specified field is longer than the length of the string representation of a date.

The date value is truncated to fit into the table.

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

SQL3129W

The field data in the input file was shorter than the database column.

The data on the right is padded with blanks.

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

SQL3130W

The time value in the specified field is longer than the length of the string representation of a time.

The time value is truncated to fit into the table.

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

SQL3131W

The timestamp value in the specified field is longer than the length of the string representation of a timestamp.

The timestamp value is truncated to fit into the table.

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

SQL3132W

The character data column has a defined size that is longer than the longest default character column which can be exported; each value will be truncated to the specified size.

For example, by default, only the first SQL_LONGMAX bytes of a LOB column will be exported. If the entire LOB column is desired, the LOBSINFILE keyword must be specified in the filetype modifier and each LOB column will be stored into a separate file.

This is a warning only. No action is required.

SQL3133W

The DATALINK value in the specified field is invalid. 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.

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

SQL3134W

The DATALINK value in the specified field is invalid. 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.

Examine the input value. If necessary, correct the input file and resubmit the command.

SQL3135N

The number of data columns in the METHOD parameter must be less than or equal to the number of data columns in the actual table.

Specify the correct number of input columns in the METHOD parameter and resubmit the command.

SQL3137W

If loading from a delimited ASCII file, the row contains too few fields. If loading from a non-delimited ASCII file, the row contains too few bytes of data. There is no input value for at least one non-nullable target column.

The row is not loaded.

Examine the input file and the contents of the target table. Correct the input file and resubmit the command, or edit the data in the table.

SQL3138W

The end of the input data file was reached before the terminating character string delimiter was found.

A closing character string delimiter is assumed at the end of the data.

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

SQL3139W

The IMPORT or EXPORT utility could not disconnect from the database.

The output data may be incomplete.

Use the error number in the message to determine the exact error.

SQL3140W

The value in the specified field cannot be converted to a decimal floating-point value. 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.

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

SQL3141W

The value in the specified field cannot be converted to a decimal floating-point value. There may be a data type mismatch. 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.

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

SQL3147W

The number of rows exported exceeds 2048. The first generation products cannot support more than 2048 rows.

Continue processing.

The rows beyond 2048 can be read only by second and third generation products.

SQL3148W

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

Processing continues with the next row of input data.

See the next message in the message file for the row number not inserted. Examine the input file and the database contents. If desired, modify the database or modify the input file and rerun the operation.

SQL3149N

This summary message tells how many rows of data were read from the input file, how many rows were successfully inserted into the database table, and how many rows were rejected. If using the INSERT_UPDATE option, the number of rows updated is the number of rows processed minus the number inserted and rejected.

None, because this is a summary message. The detail messages may suggest corrective action.

SQL3150N

Information is given about the product that created the PC/IXF file and when it was created.

No action is required.

SQL3151N

No data conversion will be performed from the IXF code page to the application code page because the FORCEIN option was specified.

No action is required. If the conversion from the IXF file code page to the application code page is supported by the database manager, the operation can be resubmitted without the FORCEIN option and the data will be converted.

SQL3152N

The double-byte code page values in the record and the application are not compatible. Because the FORCEIN option was used, the data is inserted.

No action is required.

SQL3153N

Optional information is given about the name of the table where data was extracted, the product that created the table, and the original source of the data.

No action is required.

SQL3154W

The HCNT value in the H record and the CCNT value in the T record do not agree.

The CCNT value in the T record is used.

Verify that the CCNT value is correct. If not, make the necessary changes to the HCNT or CCNT values and resubmit the command.

SQL3155W

The value in the name length field in the C record for the indicated column is not valid.

Data from the indicated column is not loaded.

Change the name length field in the C record and resubmit the command.

SQL3156W

The null field in the C record for the indicated column is not valid.

Data from the indicated column is not loaded.

Change the null field in the C record and resubmit the command.

SQL3157W

The type field in the C record for the indicated column is not valid. The code page values may not be compatible with the column type.

Data from the indicated column is not loaded.

Change the type field in the C record and resubmit the command.

SQL3158W

The single-byte code page field in the C record for the indicated column is not valid.

Data from the indicated column is not loaded.

Change the single-byte code page field in the C record and resubmit the command.

SQL3159W

The double-byte code page field in the C record for the indicated column is not valid.

Data from the indicated column is not loaded.

Change the double-byte code page field in the C record and resubmit the command.

SQL3160W

The column length field in the C record for the indicated column is not valid.

Data from the indicated column is not loaded.

Change the column length field in the C record and resubmit the command.

SQL3161W

The precision field in the C record for the indicated column is not valid.

Data from the indicated column is not loaded.

Change the precision field in the C record and resubmit the command.

SQL3162W

The scale field in the C record for the indicated column is not valid.

Data from the indicated column is not loaded.

Change the scale field in the C record and resubmit the command.

SQL3163W

The column length field in the C record for the indicated column is blank.

A column length of 00008 is used.

No action is required.

SQL3164W

The column length field in the C record for the indicated column is not valid. The indicated column is a floating point column.

Data from the indicated column is not loaded.

Change the column length field in the C record and resubmit the command.

SQL3165W

The column type in the C record for the indicated column is not valid.

Data from the indicated column is not loaded.

Change the column type field in the C record and resubmit the command.

SQL3166W

Either there was not a PC/IXF column specified to be loaded into the indicated column, or the specified PC/IXF source column does not exist.

Null values are loaded for the indicated column.

No action is required. If nulls are not acceptable for this column, check the METHOD parameter for erroneous names or positions or for fewer entries in the METHOD parameter than columns stated in or implied by the Action String (for example, "REPLACE into ...") parameter.

SQL3167W

Values in the PC/IXF column cannot be loaded into the indicated database column and the reason is given in a previous message in the log.

Null values are loaded for the indicated column.

Read the previous messages to understand why the column is not valid.

SQL3168W

The source PC/IXF and the target database column types or lengths may not be compatible.

Null values are loaded for the indicated column.

Compare the columns in the source PC/IXF file and the database.

SQL3169N

This is for information only about the optional use of the FORCEIN option.

No action required.

SQL3170W

The end of the file was reached before the end of the current row of data. The file may contain only part of the expected data.

The partial row of data is not loaded.

If the PC/IXF file was copied from one medium to another, compare the copy with the original or repeat the copy process.

SQL3172W

The specified input column was not found in the input spreadsheet file. The database column is nullable and contains null values.

Verify the specified input column name.

SQL3175W

The record in the spreadsheet file is not compatible with the data type of the database column. If the database column is a graphic data type, the input data may contain an odd number of bytes.

If the column is nullable, a null is inserted. If the column is not nullable, the row is not imported.

Either edit the data in the table or verify that the data in the spreadsheet file is valid for importing into a database manager database and resubmit the command.

SQL3179W

The row of data from the input file has missing or not valid data for a non-nullable column. The values in the remaining database columns in that row are not inserted.

Processing continues with the next row. The row is not inserted.

Either edit the data in the table or verify that the data in the spreadsheet file is valid for inserting into a database manager database.

SQL3180W

This is a request for the application to prompt the user to place the specified diskette in the specified drive.

The utility is waiting to be called again after the user puts the diskette in the drive.

Prompt the user for the diskette and then return to the utility with the callerac parameter indicating whether processing continues or ends.

SQL3181W

During the load of a PC/IXF file created by the database manager, the A record of subtype E that is expected as the last A record was not found.

The input file probably is damaged.

Continue processing.

Check for data that was not loaded. If data is missing, edit the table or change the input file and resubmit the command. If the PC/IXF file was copied from one medium to another, compare the copy with the original or repeat the copy process.

SQL3182W

During the load of a PC/IXF file that is contained on more than one diskette, a request to insert a diskette was sent to the application, a confirmation that the diskette is in the drive was returned but the continuation file is not there or is not valid. This action does not apply to the first diskette.

The utility waits for a response from the application to either continue processing or stop processing.

Have the user verify that the correct diskette is in the drive. If the correct diskette is in the drive, call the utility again with the callerac parameter set to stop processing.

SQL3183W

At least one COLDEL, CHARDEL or DECPT keyword in the filetmod parameter is not at the beginning of the filetmod parameter and does not follow a blank (space). This condition may arise during the LOAD/IMPORT or export of delimited ASCII (DEL) files.

The utility stops processing. The erroneous delimiter overrides are ignored.

Resubmit the command with a correct filetmod parameter.

SQL3184W

The table was created, however, it may be different than the original table.

Compare the table definition of the newly created table and the expected table. Make any necessary corrections using commands such as ALTER TABLE. Look at the SQLCODE indicated in the warning message for more information about what happened.

SQL3185W

This message provides the identification of the row where the error occurred for the previous message listed in the message file (for example, SQL3306).

No action is required.

SQL3186W

The utility could not insert a row of data into the database because either the database transaction log is full or the lock space available to the application is full.

The completed database transactions are committed and the insert is tried again. If the repeated insert continues to indicate the same failure, the utility stops processing.

Be aware that a subsequent failure of the utility causes the database to roll back to the state after the last commit, not to the state before the utility was initially called.

SQL3187W

The IMPORT utility was creating an index when an error occurred. An index may already exist for some table.

This error occurs only during the import of a PC/IXF file.

The utility continues processing. The file was imported, but the index was not created on the table.

Federated system users: in addition to the previously listed cause, this error can occur when a CREATE NICKNAME statement was issued at federated server and the table at the data source had an index or indexes with too many columns, or the total index row size could not be represented in the federated server catalog. The sqlcode in the message provides further information about the problem encountered.

Read the next message in the message log (SQL3189) for the name of the index that was not created. Create the index with the CREATE INDEX command.

Both of the previously listed options have potential performance implications.

SQL3188N

When running LOAD/IMPORT with the REPLACE option, the specified database table is truncated before inserting the data back into the table. An error occurred during the truncation processing. This error is returned for a system-period temporal table because it can not be truncated.

The utility ends with an error.

Resubmit the command. If the table is a system-period temporal table, resubmit the command without the REPLACE option.

SQL3189N

This message always follows message SQL3187 when an error occurs while creating an index. name is the name of the index where the create failed. column list is a string of index column names. Each column name in the string is preceded by a plus (+) or a minus (-) sign indicating ascending or descending order.

The utility continues processing.

Manually create the index with the CREATE INDEX command.

SQL3190N

The utility stops processing. No data is imported.

Resubmit the command either without the INDEXIXF option or with the other parameters that are valid with the INDEXIXF option.

SQL3191W

The data does not match the user specified format. This may be caused by missing fields, mismatched column separators, or a value out of range.

Examine the input value. Correct the input file or specify a DATEFORMAT, TIMEFORMAT, or TIMESTAMPFORMAT that matches the data and resubmit the command.

SQL3192N

The user specified format is not valid because it may be specified more than once, or it may contain an invalid character.

The formats must be enclosed in double-quotes.

Valid DATEFORMAT specifiers include “YYYY” and the “M”, and “D” characters.

Valid TIMEFORMAT specifiers include “AM”, “PM”, “TT”, and the “H”, “M”, and “D” characters.

Valid TIMESTAMPFORMAT specifiers include all of the specifiers for DATEFORMAT and TIMEFORMAT, as well as “UUUUUU”. However, “M” cannot be next to both a date format specifier and a time format specifier.

A field separator is necessary if the corresponding value in the data file can have a variable length.

The utility stops processing.

Examine the format specifier. Correct the format, and resubmit the command.

SQL3193N

There are restrictions on the types of tables that the load utility and the import utility support. Here are some examples of restrictions:

• You can load or import data into a view only if the view can be updated.
• You can load or import data into a materialized query table only if the materialized query table is not replicated.

This message is returned when an attempt is made to load or import data into an unsupported type of view or table.

Resubmit the command with the name of a table or a view that is supported by the utility.

SQL3194N

The utility cannot be run against a system table.

The utility stops processing. No data is loaded.

Resubmit the command with a valid table name.

SQL3195W

This warning code is a request for the application to prompt the user to place another diskette in the specified drive.

The utility is waiting to be called again after the user puts the diskette in the drive.

Prompt the user for the diskette and then return to the utility with the callerac parameter indicating whether processing continues or ends.

SQL3196N

The source file to be loaded into a database could not be found in the path indicated by the datafile parameter.

The command cannot be processed.

Verify that the input file does exist and that the path to it is correct.

SQL3197N

An attempt was made to execute more than one instance of the import or export utility on a system where this is not supported.

The command cannot be processed.

Resubmit the second operation when no other processes are attempting to execute the same utility.

SQL3201N

A table that is a parent in a relationship with another table cannot be replaced.

The command cannot be processed.

Select a different option, such as INSERT, or select a different target for the utility operation.

SQL3202N

The Load utility failed to acquire a partition lock. Another Load utility is currently loading into the same table and is connected to the same db-partition as the current load.

If you would like to execute multiple Loads into the same table concurrently (assuming a disjoint set of output db-partitions), then you must assure the Load Coordinator Agents reside on different db-partitions by executing each Load from a database connection connected to different db-partitions.

SQL3203N

The INSERT_UPDATE option is only valid when the target table has a primary key and the target columns include all columns of the primary key. In addition, the target column list and the target table should contain at least one column that is not part of the primary key.

The command cannot be processed.

Select a different option such as INSERT, or choose a different target for the utility operation.

SQL3204N

The INSERT_UPDATE option is not valid for views and a view has been selected as the target of the utility operation.

The command cannot be processed.

Select a different option such as INSERT, or choose a different target for the utility operation.

SQL3205N

A view whose base table is a parent table in a referential relationship with any table (including itself) cannot be replaced.

The command cannot be processed.

Select a different option such as INSERT, or choose a different target for the utility operation.

SQL3206N

A view whose definition involves a subquery cannot be replaced. If the view definition depends on the definition of other views, the other views cannot contain subqueries. The use of a subquery anywhere in the definition of any view on which the target view is based prohibits the REPLACE option.

The command cannot be processed.

Select a different option, such as INSERT, or choose a different target for the utility operation.

SQL3207N

SQL3208W

User specified to import data from typed tables into regular table. Please note, object_id column will not be cast while importing.

Please make sure such operation is intentional.

SQL3209N

When CREATE option is used, neither subtable name nor attribute names can be renamed.

Please check your IMPORT command and make sure no subtable-list is specified.

SQL3210N

option is not compatible with hierarchy in EXPORT, IMPORT, or LOAD.

Please check the command syntax for hierarchical support.

SQL3211N

LOAD does not support typed tables. Please consider IMPORT instead.

Please use IMPORT to bring hierarchical data into the database.

SQL3212N

An attempt was made to terminate a crashed, interrupted, or forced LOAD operation against a table which contains DATALINK column(s), or a table which resides in table space(s) in delete pending state. These are not currently supported.

Use the RESTART option of the LOAD command to recover a crashed, interrupted, or forced LOAD operation.

SQL3213I

No action is required.

SQL3214N

The table is incompatible with DEFERRED index mode because of the indicated reason code:

1

The table has unique indexes.

2

The table has expression-based indexes.

3

The table is a column-organized table.

4

The table has XML columns.

In all cases, specify an indexing mode of AUTOSELECT, REBUILD or INCREMENTAL, and reissue the command.

SQL3215W

INCREMENTAL indexing mode is not supported for this operation. REBUILD indexing mode is used instead.

The user can avoid this warning by defining the index in a table space that is not shared by other objects in the table to be loaded. Alternatively, avoid use of the COPY option. Please refer to the documentation for a full list of alternatives to the COPY option.

SQL3216W

INCREMENTAL indexing can only be used on tables that have a compatible index object at the time the load utility begins. Loading with indexing mode REBUILD causes the table index to be rebuilt in a consistent manner.

No action required.

SQL3217W

INCREMENTAL indexing can only be used when appending data to a table using the load INSERT action. This feature is not supported with when loading with REPLACE, RESTART, or TERMINATE actions.

No action necessary.

SQL3218C

The LOAD utility cannot proceed because one or more index on disk data structures for the target table are in an inconsistent state.

Terminate all applications and issue the RESTART DATABASE command for the affected database to rebuild the damaged index or indexes. Then resubmit the LOAD command.

SQL3219N

The LOAD utility encountered problems during its attempt to disable constraint checking for the target table.

SQL3220W

An attempt to LOAD/IMPORT a multiple IXF file was made, but one of the files is missing from the directory specified. LOAD/IMPORT tries to find the parts in the same directory as the first part.

The import will terminate.

SQL3221W

The import is about to attempt a COMMIT of the work performed.

If the SQL3222W message is not printed immediately after this message, then the COMMIT failed and you will need to check your table or view to see which records have been imported. You can then start the import again with a RESTARTCOUNT set to the number of records successfully imported to skip those rows and import the rest of the file. (If you had been doing a CREATE or REPLACE_CREATE or REPLACE, call the second import with INSERT option.)

SQL3222W

The COMMIT was successful.

None necessary if you get this message.

SQL3223N

The parameter of type parameter is not specified properly. The pointer should be either a NULL pointer or should point to an appropriate value.

The command cannot be processed.

Call the utility again with a proper parameter.

SQL3225N

The utility was called with a RESTARTCOUNT value or a SKIPCOUNT value which was greater than the number of rows in the input file resulting in no rows being loaded into the table/view.

Ensure that the RESTARTCOUNT value or the SKIPCOUNT value is correct and call the utility again.

SQL3227W

An error or warning was encountered during LOAD, IMPORT or EXPORT of a table. CPU parallelism was greater than 1 at the time the problem was encountered, and an SQL message was written which identified the user record with a special unique token. This message serves to map the unique record token to the record number of the source user data.

Refer to the original SQL message returned for appropriate action.

SQL3228N

The “indexing mode” option for the load utility was specified as “deferred”. This option is not supported with tables having DATALINK columns.

Reissue the load command specifying a different indexing mode.

SQL3229W

The row of data from the input file has invalid data.

The row was not inserted. Processing continues with the next row. This message can also be hit if a file path does not match any of the restricted paths in load, or in the IMPORT command using the ADMIN_CMD procedure. See DB2_LOAD_RESTRICTED_IO_PATH.

If necessary, correct the input file and resubmit the command.

SQL3230N

The datafile codepage indicated by the CODEPAGE file type modifier, or by the header information of the IXF file is incompatible with the database codepage for this data type.

Change the input data to be in a codepage compatible with the data type.

SQL3232W

An error occurred while writing LOB or XML documents to the specified file.A new file name has been used. Check the db2diag log file for a record detailing the failure.

Export wasn't able to write to the original file. It assumes that there is a problem with the file, for instance the file size limit being exceeded. It will write using the next filename into the same path. If Export fails again when it writes, Export will then assume there is an error with the path. For instance, the path's filesystem could be full or there is insufficient access for Export to write or create files in the path. It will then attempt to use the next available path specified in the XML TO / LOBS TO options.

No action is required.

SQL3233W

Reason codes:

1

The attribute attribute-name is not recognized.

2

The attribute attribute-name is not applicable to a specific column.

Check the attribute name and correct it if needed.

SQL3234N

An error was encountered attempting to parse an XDS string. char-number indicates the position where the error occurred. It is set to 0 if the position could not be determined.

The possible reason codes are as follows:

1

The XDS string is malformed.

2

A mandatory attribute is missing.

3

An attribute name is invalid.

4

An attribute value is invalid.

5

A duplicate attribute name was found.

Resubmit the command with a valid XML Data Specifier.

SQL3235N

One of the following reason codes may apply:

1

Either the path path-name is not a valid sqlu_media_list or the values provided are not valid. The media_type must be SQLU_LOCAL_MEDIA and all path names must be terminated with a valid path separator.

2

There is not enough space on the paths provided for the EXPORT utility to hold all the data of type type.

3

The path path-name cannot be accessed.

Determine which reason code applies, correct the problem, and resubmit your command.

SQL3236N

In the XMLVALIDATE option, If a schema is specified in the IGNORE clause, it cannot also be present in the left side of a schema pair in the MAP clause.

The command cannot be processed.

Resubmit the command with a valid XMLVALIDATE option.

SQL3237N

Reason codes:

1

The Action String is too long due to XML specific processing.

2

The Action String contains a "WITH" clause, which is incompatible with the XMLSAVESCHEMA option.

Resubmit the command without the XMLSAVESCHEMA option or modify the Action String.

SQL3239W

One or more XML schemas were used to validate inserted XML documents but these schemas no longer exist in the database. Therefore, schema information for these XML documents will not be written to the exported data file.

SQL3240N

To run the utility against a protected table, the authorization ID authorization-id must have LBAC credentials that allow inserting new rows into the table.

Have a user with SECADM authority grant the authorization ID authorization-id LBAC credentials that allow inserting new rows into the table. If the table has protected rows but no protected columns, then granting any security label that is part of the security policy policy-name is sufficient. If the table has protected columns, then the LBAC credentials must allow writing to all of the protected columns.

sqlcode: -3240

sqlstate: 5U014

SQL3241W

The value for the column of data type DB2SECURITYLABEL in the input source is not a valid security label for the security policy that is protecting the target table. Any security label inserted into a column of data type DB2SECURITYLABEL must be a part of the security policy that is protecting the table. The row is not loaded.

Check the input source column and make sure that the value is valid for the policy protecting the target table. If the values in the input source are in string form, you must specify a security label related file type modifier. If necessary, correct the input data source and resubmit the command.

sqlcode: +3241

sqlstate: 01H53

SQL3242W

The SECLABELCHAR file type modifier was specified, but the value for the DB2SECURITYLABEL column is not in the proper format for a security label string. The row is not loaded.

Check that the values in the input source for the DB2SECURITYLABEL column are in the correct format. If necessary, correct the input data source and resubmit the command.

sqlcode: +3242

sqlstate: 01H53

SQL3243W

The SECLABELCHAR file type modifier was specified, but the security label string contains an invalid element for the specified component. The row is not loaded.

Check the security label string carefully:

• Make sure that the elements are listed in the same order that their components are listed in the security policy protecting the target table.
• Check the spelling of the element.

If necessary, correct the input data source and resubmit the command.

sqlcode: +3243

sqlstate: 01H53

SQL3244W

The SECLABELNAME file type modifier was specified, but the security label named security-label-name cannot be found for the security policy policy-name. The row is not loaded.

Check the input source column and confirm that the value appears to be valid for the security policy protecting the target table. If necessary, correct the input data source and resubmit the command.

sqlcode: +3244

sqlstate: 01H53

SQL3245W

The user is not allowed to insert a row into a protected table if they do not have appropriate security label and/or exemption credentials The row is not loaded

Ask your database security administrator to grant the proper security label or exemptions required for this operation. If necessary, resubmit the command.

sqlcode: +3245

sqlstate: 01H53

SQL3250N

The COMPOUND=x option was specified for the import utility and cannot be processed due to the reason with reason code reason-code:

1

It is invalid when the INSERT_UPDATE option is used.

2

It is invalid with the following file type modifiers: IDENTITYIGNORE, IDENTITYMISSING, GENERATEDIGNORE, GENERATEDMISSING.

3

The database being imported to is accessed through a server or gateway of a previous release.

4

The value is not within the allowed range of 1 to 100 (On DOS or Windows, the maximum value is 7).

5

The table being imported is a hierarchy or typed table.

6

The table being imported has generated columns.

7

It is invalid when the XMLVALIDATE USING XDS option is used.

8

It is invalid when the USEDEFAULTS file type modifier is specified.

9

The table being imported is a random distribution table using the random by generation method.

The action corresponding to the reason code:

For reason code 1:

• Remove COMPOUND=x from the file type modifier option, or use INSERT option.

For reason codes 2, 3, 5, 6, 8, 9:

• Remove COMPOUND=x from the file type modifier option.

For reason code 4:

• Set x in COMPOUND=x to a correct value.

For reason code 7:

• Remove COMPOUND=x or remove XMLVALIDATE USING XDS option.

SQL3251N

The utility encountered more errors than can be relayed in the sqlca (maximum number is 7) while using the COMPOUND option. Messages for these errors will not be printed to the message file.

The utility continues processing.

If you desire all the error messages for each row inserted during an import, do not use the COMPOUND option or use a COMPOUND value less than or equal to 7.

SQL3252N

The Load utility was invoked with a METHOD option which is incompatible with the file format specified.

Review the documentation for restrictions and incompatibilities and reissue the Load command using a different METHOD option or file format to accommodate this restriction.

SQL3253N

This is an informational message indicating that a load from an SQL statement fetching from a cataloged database has begun.

No action is required.

SQL3254N

This is an informational message indicating that a load from an SQL statement fetching the contents of a table on a cataloged database has begun.

No action is required.

SQL3255N

The Load utility has encountered an error while executing or attempting to execute the source user exit. This is because of one of the following reasons:

1. Ensure that the source user exit exists, has correct permissions, and resides in the "bin" subdirectory of the "sqllib" path. Then reissue the Load.
2. Debug your source user exit application and ensure that it is working as designed. Then reissue the Load.

SQL3256N

The Load utility has encountered an error while processing data for the specified file type. The format of the data is invalid. The utility has stopped processing.

Ensure the data is in the correct file type format.

SQL3257N

The Load utility has encountered an error while processing data in the specified file type. The utility has stopped processing. This is because of one of the following reasons:

Reason Codes:

1. The data file header information is invalid or missing.
2. The record header information for the given record num is invalid or missing.
3. The column header information for the given record num is invalid or missing.
4. The column data for the given column number column num in record number record num is invalid or missing.

1-4. Ensure the data is in the correct file type format.

SQL3260N

An unexpected error occurred when accessing the LDAP directory. The command can not be processed.

Record the message number (SQLCODE) and the error code. Use the Independent Trace Facility to obtain the DB2 trace. Then contact your IBM service representative.

SQL3261N

The REGISTER LDAP command did not complete successfully because a required input parameter was not specified as indicated by the following reason codes:

1

The Network Id parameter was not specified.

2

The Partner LU parameter was not specified.

3

The Transaction Program (TP) name parameter was not specified.

4

The Mode parameter was not specified.

6

The TCP/IP hostname parameter was not specified.

7

The TCP/IP service name parameter was not specified.

8

The IPX Address was not specified.

9

The computer name was not specified.

10

The instance name was not specified.

Re-submit the command with the required input parameter

SQL3262N

The TCP/IP service name specified is not valid.

Ensure that the TCP/IP service name is configured and reserved in the local etc/services file, then re-submit the command. Alternatively, specify the port number that is assigned to the TCP/IP service name.

SQL3263N

The protocol type specified is not supported for the command.

Re-submit the command using a supported protocol type.

SQL3264N

The command did not complete successfully because the database server had not been registered in LDAP.

Register the database server in LDAP using the REGISTER LDAP command. Then re-submit the command.

SQL3265N

Unable to authenticate the LDAP user due to unexpected LDAP system error.

Use the Independent Trace Facility to obtain the DB2 trace. Then contact your IBM service representative.

SQL3266N

The specified password is not a correct password for the specified user Distinguished Name (DN).

Re-submit the command using the correct password.

SQL3267N

The command did not complete successfully because the LDAP user did not have sufficient authority to perform the required task. The LDAP user object also requires write access to the BaseDN under which DB2 LDAP objects are created.

• Configure the LDAP userID and password by using the db2ldcfg command.
• Grant the required access (ACL) to the LDAP user object so that the LDAP user can add, delete, read, and write to his own object.

SQL3268N

The LDAP schema defined at the server does not contain the definition for the DB2 object classes and/or attributes used in the current release of DB2.

Refer to the Administration Guide on how to extend the LDAP schema with DB2 object classes and attributes.

SQL3269N

The database manager was not able to access information in the LDAP directory because the LDAP server was not available.

Perform the following actions:

1. Ensure that the LDAP server is active.
2. Verify that TCP/IP is configured correctly on your machine
3. Verify that the DB2LDAPHOST registry variable is set to the TCP/IP hostname and port number of the LDAP server by running the "db2set DB2LDAPHOST" command. If the DB2LDAPHOST is not set, you can set it by using the "db2set DB2LDAPHOST=<host-name>[:<port-number>[:SSL]]" command, where <host-name> is the TCP/IP hostname of the LDAP server, and <port-number> is the TCP/IP port number of the LDAP server. The <port-number> value is optional. The default port number is 389. To use an encrypted connection, specify a port number and ":SSL", to point to the encrypted port of the LDAP server: "db2set DB2LDAPHOST=<host-name>:<port-number>:SSL".

SQL3270N

The LDAP user's Distinguished Name (DN) is not valid.

Re-submit the command using a valid LDAP user's DN.

SQL3271N

When setting user preferences such as CLI configuration or DB2 registry variable, the LDAP user's DN and password must be defined for the current logon user.

Refer to the IBM eNetwork LDAP documentation on how to configure the LDAP user's DN and password for the current logon user.

SQL3272N

The command did not complete successfully because the node node-name was not found in the LDAP directory.

Ensure the node name is correct and re-submit the command.

SQL3273N

The command did not complete successfully because the database database-alias was not found in the LDAP directory.

Ensure the database name is correct and re-submit the command.

SQL3274W

The database was created successfully. However, the database could not be cataloged in the LDAP directory because there was an error occurred during the operation.

Correct the error as indicated in the SQLCODE. Then catalog the database in the LDAP directory using the CATALOG LDAP DATABASE command.

SQL3275W

The database was dropped successfully. However, the database could not be uncataloged in the LDAP directory because there was an error occurred during the operation.

Correct the error as indicated in the SQLCODE. Then uncatalog the database in the LDAP directory using the UNCATALOG LDAP DATABASE command.

SQL3276N

Unable to query for the LDAP naming context for the LDAP server.

Contact your LDAP directory administrator to obtain the LDAP naming context for the LDAP server that you are using. If you are using IBM eNetwork Directory V2.1, this is the name of the LDAP suffix. Then set the naming context for the current machine using the "db2set DB2LDAP_BASEDN=<naming-context>" command.

SQL3277N

The command did not complete successfully because another database of the same name already exists in the LDAP directory.

Re-submit the command using a different alias name.

SQL3278N

The command did not complete successfully because another node of the same name already exists in the LDAP directory.

Re-submit the command using a different alias name.

SQL3279N

The command did not complete successfully because the LDAP support is disabled on the current machine.

If the LDAP support is installed, enable the LDAP support by running the command: "db2set DB2_ENABLE_LDAP=YES".

If the LDAP support is not installed, you need to run the setup program and select to install the LDAP support.

SQL3280N

The attempt to connect to a DRDA server failed because DB2 Connect is not installed on this IBM Data Server Client and the gateway-node was not specified when cataloging this LDAP database.

Either install DB2 Connect on this IBM Data Server Client or recatalog this LDAP database with a valid gateway-node.

SQL3281N

The database server was not registered in LDAP because the OSTYPE parameter specified was not valid. The OSTYPE parameter describes the operating system type of the server.

Resubmit the command specifying an operating system type (OSTYPE) that is supported by DB2.

SQL3282N

Either or both the distinguished name (DN) of the user and the password that were specified were not valid.

This error may occur when a user is running in a Windows 2000 domain environment , which supports LDAP, and logs into a local account which may not have sufficient authority.

Resubmit the command using valid values for both the distinguished name (DN) of the user and the password.

If you are working in a Windows 2000 domain environment, ensure that logon with an account that has sufficient authority.

SQL3283W

The database manager configuration was updated successfully. However, the protocol information could not be updated in the LDAP directory because an error occurred during the LDAP operation.

Correct the error as indicated in the SQLCODE. Then update the protocol information in the LDAP directory using the UPDATE LDAP NODE command.

SQL3284N

The database server was not registered in LDAP because the nodetype parameter specified was not valid.

Use a valid nodetype when registering the database server in LDAP. Valid values for the nodetype parameter are: SERVER, MPP, and DCS.

SQL3285N

The command did not complete successfully because LDAP is not supported on this platform.

If LDAP is not supported on this platform, issue the following command to disable LDAP support: db2set DB2_ENABLE_LDAP=NO

SQL3303N

File types other than IXF are not allowed with the CREATE or REPLACE_CREATE keywords in the Action String (e.g. "REPLACE into ...") parameter.

The IMPORT utility stops processing. No data is imported.

Change the file type to IXF, or use INSERT, INSERT_UPDATE or REPLACE.

SQL3304N

The parameters specified on the command require that the table exists.

The utility stops processing. No data is loaded.

SQL3305N

The CREATE keyword indicates that a new table must be created but a table with the specified name already exists.

The IMPORT utility stops processing. No data is imported.

Either erase the existing table or use a keyword other than CREATE and resubmit the command.

SQL3306N

An SQL error occurred while inserting a row into the table.

If the SQL error is not severe the row will be rejected and the utility continues processing; otherwise the utility stops processing.

Examine other messages in the message file for details about the actual error and resubmit the command, if necessary.

SQL3307N

The IMPORT utility stops processing. No table is created.

Either correct the columns specified in the METHOD and Action String parameters or correct the columns specified in the METHOD parameter.

SQL3308N

The code page values for the column and the application are not compatible. When the FORCEIN parameter is not specified, the data cannot be loaded if the conversion from the IXF file code pate to the application code page is not supported.

The utility stops processing. No data is loaded.

To load data with these code pages, resubmit the command with the FORCEIN option.

SQL3309N

During the load of a PC/IXF file, a graphic data column was encountered. Because the FORCEIN parameter was not used, the data cannot be loaded.

The utility stops processing. No data is loaded.

If you want to load the data with the graphic data, resubmit the command with the FORCEIN parameter.

SQL3310N

The CREATE or REPLACE_CREATE option was specified on the IMPORT command. A column with an invalid C record was found while importing the PC/IXF file.

The IMPORT utility stops processing. The table is not created.

Verify the column definition information in the input file.

SQL3311N

You can insert data from a properly formatted file into an existing table, hierarchy, view or nickname by using the IMPORT command. You can also create a new table, or replace an existing table from the data in an input file, by specifying the CREATE parameter or the CREATE_REPLACE parameter with the IMPORT command.

This message is returned when an attempt is made to run the IMPORT command specifying the CREATE parameter or the CREATE_REPLACE parameter with an Integration Exchange Format (IXF) input file that includes functionality that is not supported with the CREATE parameter or the CREATE_REPLACE parameter.

The reason code indicates more specifically the type of information that could not be imported:

1

Indexes that include column names that contain hexadecimal values of 0x2B or 0x2D

2

XML columns

3

Multidimensional clustered (MDC) tables

4

Table partitioning keys

5

An index name has been truncated due to code page conversion.

6

Protected tables

7

Action strings other than 'SELECT * FROM <TABLE-NAME>'

8

Column names that were specified with the METHOD N parameter during export

9

A column name that was too long for IXF format was truncated.

10

A user-defined type name that is too long for IXF format was truncated.

11

Typed table information has been truncated due to code page conversion.

12

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

13

Decimal floating-point columns

14

Hidden columns

15

Indexes with random ordering

16

Column-organized tables

17

Expression-based indexes

18

Indexes created with the BUSINESS_TIME WITHOUT OVERLAPS clause

19

Information about columns where STRINGUNITS has been specified as CODEUNITS32

20

BINARY or VARBINARY columns

21

Random distribution tables

22

Row modification tracking enabled tables

For reason codes 1, 3, 4, 5, 7, 8, 9, 11, 14, 17, and 18:

• To force the import utility to create the tables despite the fact that some information is missing, specify the FORCECREATE parameter when you issue the IMPORT command with the CREATE or REPLACE_CREATE parameter.

For reason codes 2, 6, 10, 12, 13, 15, 16, 19, 20, 21 and 22, perform the following steps:

1. Use the db2look command to extract table information and create the table.
2. Issue the IMPORT command with the INSERT or REPLACE parameter with the specified IXF file.

sqlcode: -3311

sqlstate: 5U058

SQL3313N

The disk or diskette is full. During the export to a PC/IXF file, either the PC/IXF data file is on a fixed disk, or the PC/IXF data file and the database are on the same drive, or the PC/IXF data file and the message file are on the same drive.

The EXPORT utility stops processing. The exported data is not complete.

Provide more space on the disk or diskette or specify that the data file be located on a different drive than the database or the message file and resubmit the command.

SQL3314N

During the load of a PC/IXF file, an A record was found in the PC/IXF file, that contained run identification information (in the date and time fields) that differs from the run identification information in the header (H) record. This action does not apply to an A record at the start of a continuation file.

The input file has probably been damaged.

The utility stops processing.

Re-create the damaged file, or repair the damaged file to recover as much data as possible. Resubmit the command.

SQL3315N

During the load of a PC/IXF file that was created by Database Services, an A record was found in the PC/IXF file, that contained volume information (in the volume fields) that is not valid.

The input file has probably been damaged.

The utility stops processing.

Re-create the damaged file, or repair the damaged file to recover as much data as possible. Resubmit the command.

SQL3316N

During the load of a multiple part PC/IXF file, an I/O error occurred while the system was closing one of the files that make up the input PC/IXF file. This action does not apply to the last file in the group of files that make up the PC/IXF file.

The utility stops processing.

Resubmit the command.

SQL3318N

A COLDEL, CHARDEL, or DECPT keyword appears more than once in the filetmod parameter. This condition may arise while using delimited ASCII (DEL) files.

The utility stops processing. No data is loaded or exported.

Resubmit the command with a correct filetmod parameter.

SQL3319N

An SQL error occurred while creating the table.

The IMPORT utility stops processing. The table was not created. No data was imported.

Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.

SQL3320N

A COLDEL, CHARDEL, or DECPT keyword is located at the very end of the filetmod parameter. There is no delimiter or decimal point character following the keyword. This condition may arise while using delimited ASCII (DEL) files.

The utility stops processing. No data is loaded or exported.

Resubmit the command with a correct filetmod parameter.

SQL3321C

The IMPORT utility could not insert a row of data into the database because the database transaction log was full or the lock space available to the application was exhausted. All work was committed, but the utility could not insert the row, because the database transaction log or the lock space remains full.

The utility stops processing. All previous changes were committed, but the current row was not imported.

Check the amount of space remaining on the filesystem containing your database files and the amount of lock space available to the application. Consider increasing the maximum log size, maximum storage for the lock list, or the percent of the locklists available to a single application in the database configuration file.

SQL3322N

An error occurred in the wait/post semaphores.

The utility stops processing. For the EXPORT utility, data may be incomplete on the media. For the IMPORT utility, data not already committed is rolled back.

Stop and restart the database manager and resubmit the utility.

SQL3324N

A column of data returned by the SQL statement is not supported.

Federated system users: The data type of the data that you want is not supported by either the federated server or the data source that you want to access.

Correct the error and retry the command.

Federated system users: Specify a supported data type and resubmit the program.

SQL3326N

The command cannot continue.

Change the Action String parameter with a valid column list and call the utility again.

SQL3327N

A system error occurred during processing.

The utility stops processing.

Record all error information from the SQLCA, if possible. Retain the message file. Terminate all applications using the database. Reboot the system. Restart the database. Try the command again.

If sufficient memory resources exist and the problem continues, invoke the Independent Trace Facility at the operating system command prompt.

SQL3330W

Only even length character fields can be loaded into graphic database columns.

The row is not loaded.

Either load the data to a new table using the CREATE option in the IMPORT command or do not load this column into this table.

SQL3331C

The command cannot be processed.

Retry the utility when the file is not in use, or retry the utility directing the output to a path and file that allows writing.

SQL3332C

This message may accompany another error message. It indicates that the maximum number of open files has been reached.

The command cannot be processed.

Terminate other applications to reduce the number of files open and retry the utility.

SQL3333C

This message may accompany another error message. It indicates that a file or directory to be accessed does not exist or cannot be found.

The command cannot be processed.

Resubmit the command with the correct file name, including a valid path.

SQL3334C

This message may accompany another error message. It indicates there is not enough storage available to open the file.

The command cannot be processed.

SQL3335C

This message may accompany another error message. It indicates there is no available space for writing on the device.

The command cannot be processed.

To make space available on the device, delete unneeded files or direct the output data to a device with space available.

SQL3337N

An I/O error has occurred while attempting to write data to a temporary file on the server (temporary files are created in the tmp directory under the sqllib directory for the instance of the database manager). The file system on the server may be full.

The utility stops processing. The database is unchanged.

Contact the System Administrator for the server to make space available on the server, and resubmit the command.

SQL3338N

A system I/O error has occurred while attempting to read the temporary message file on the server.

The IMPORT operation is complete; however, the message file on the database client system may be empty or incomplete.

Query the remote database to determine if the utility operation was successful.

SQL3340N

Resubmit the command using the ALLOW NO ACCESS option.

SQL3341N

Only system temporary table spaces can be used for rebuilding the indexes in a table space other than the index table space. The page size of the system temporary table space must match the page size of the index table space.

SQL3342N

The LOCK WITH FORCE option of the load utility requires SYSADM or SYSCTRL authority.

Reissue the load command from a user ID with sufficient authority.

SQL3343N

The load that failed prior to the point in time of the end of a rollforward cannot be restarted after the rollforward has completed.

Use the TERMINATE mode to terminate the load or drop the table.

SQL3346N

USE TablespaceName is only valid for ALLOW READ ACCESS loads with INDEXING MODE REBUILD. If INDEXING MODE AUTOSELECT is specified, load will use the alternate table space only if it chooses to rebuild the indexes.

SQL3400N

When loading from a non-delimited ASCII file, columns must be selected by locations in the file.

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the source file.

SQL3401N

Further restrictions are based on filetype.

The command cannot be processed.

Resubmit the command with a valid method indicator.

SQL3402N

A location pair with both the beginning and the ending location set to zero was specified for the indicated column, but the column is not nullable.

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the source file.

SQL3403N

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the source file.

SQL3404N

The field specification for locating the data for the indicated database column within the input non-delimited ASCII file is not valid. The location pair defines a field longer than 50 bytes.

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the source file.

SQL3405N

The field specification for locating data for the indicated database column within the non-delimited ASCII file is not valid. The location pair defines a field length that is not valid for an external representation of a date.

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the source file.

SQL3406N

The field specification for locating the data in the indicated database column within the input non-delimited ASCII file is not valid. The location pair defines a field length that is not valid for an external representation of a time.

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the source file.

SQL3407N

The field specification for locating the data for the indicated database column within the input non-delimited ASCII file is not valid. The location pair defines a field length that is not valid for an external representation of a timestamp.

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the file.

SQL3408W

The field specification for obtaining data from the input non-delimited ASCII file defines a field larger than the size (or maximum size) of the target database column.

The utility continues processing. Truncation occurs when necessary.

No action is required.

SQL3409W

The indicated database column is a fixed-length column. The field specification for obtaining data from the input non-delimited ASCII file defines a field smaller than the size of the target database column.

The utility continues processing. Values input to the indicated database column are padded with spaces as necessary, on the right.

No action is required.

SQL3410N

The field specification for locating the input data in the ASCII file that is to be inserted into the indicated database column defines a field with an odd number of bytes.

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the source file.

SQL3411W

The value in the field indicated is not an acceptable graphic column value. The value may contain an odd number of bytes. For DEL files, the value of the column number specifies a field in the indicated row. For ASCII files, the value of the column number specifies the byte location within the row where the value begins.

The row is not inserted.

If a null is not acceptable, correct the input file and resubmit the command, or edit the data in the table.

SQL3412W

The value in the field indicated is not an acceptable graphic column value. The value may contain an odd number of bytes. A null cannot be inserted because the target column is not nullable. For DEL files, the value of the column number specifies a field in the indicated row. For ASCII files, the value of the column number specifies the byte location within the row where the value begins.

The row is not inserted.

No action is required. If the row is necessary, correct the input file and resubmit the command, or edit the data in the table.

SQL3413W

The value in the specified field is not acceptable because it is too short for the target column. The value of the column number specifies the byte location within the row where the field begins.

A null value is inserted.

No action is required. If a null is not acceptable, correct the inner field and resubmit the command, or edit the data in the table.

SQL3414N

At the end of the load phase a temporary file is created with information necessary to restart the load. If the load is interrupted before this point, this file is not created.

This message indicates that this file could not be found during load restart.

The utility stops.

Depending on where the interrupt occurred, it may be possible to restart the load at the build phase.

SQL3415W

The value in the field indicated cannot be converted from the codepage of the input data file to the codepage of the database.

If a null value is not acceptable, correct the input data file and resubmit the command, or edit the data in the table.

SQL3416W

The value in the field indicated cannot be converted from the codepage of the input data file to the codepage of the database.

No action is required. If the row is necessary, correct the input data file and resubmit the command, or edit the data in the table.

SQL3417N

The location pair is invalid for the codepage because the codepage has a pure DBCS encoding. This means that every character in the codepage is 2 bytes long. An even number of bytes should be specified in the location pair.

The command cannot be processed.

Resubmit the command with a valid set of locations for the columns in the source file.

SQL3418W

The NOCHARDEL file type modifier is designed to support vendor data files that do not have character delimiters. It was not intended to be used when the data file was created by DB2 EXPORT. In the DEL file format, the character delimiters are used to avoid data loss or corruption and thus are part of the default behaviour.

Verify that NOCHARDEL is the required in the import or load command.

SQL3419W

The vendor sort library is activated by setting the DB2 registry variable DB2SORT. The current sort specification requires a feature that is not supported by this vendor sort library. The database manager will use the default sort to continue with the operation. Possible features not supported by vendor sort:

• Database created using IDENTITY_16BIT collation.
• Database configuration parameter ALT_COLLATE is set to IDENTITY_16BIT.
• Load target table has XML columns.
• Load target table has data partitioning and local indexes.
• Load target table has indexes with RANDOM ordering.

No action required.

SQL3500W

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.

No action is required.

SQL3501W

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.

No action is required.

SQL3502N

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.

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

SQL3503W

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.

No response required.

SQL3504W

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

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

Correct the length specified and resubmit the command.

SQL3506W

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.

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

SQL3507N

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.

Correct the parameter and resubmit the command.

SQL3508N

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

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.

8

The file or directory path is not valid.

A file or directory path required by the load does not match any of the restricted paths. Change the file or directory path to a valid path and rerun load. See DB2_LOAD_RESTRICTED_IO_PATH and/or DB2_LOAD_RESTRICTED_IO_ALLOW_SOURCEUSEREXIT.

9

SOURCEUSEREXIT is not allowed. See DB2_LOAD_RESTRICTED_IO_ALLOW_SOURCEUSEREXIT.

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

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.

No action is required.

SQL3510N

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

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

SQL3511W

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.

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

SQL3512W

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.

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

SQL3513N

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

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 system error occurred during database utility processing.

Different actions are required depending on the value of function.

SQL3515W

No action is required.

SQL3516N

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.

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

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.

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

SQL3518N

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

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

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

The Consistency Point performed by Load was successful.

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

SQL3521N

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.

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

SQL3522N

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.

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

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.

LOAD QUERY TABLE <tablename> 

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

SQL3524N

The utility stops processing.

Correct the value and resubmit the command.

SQL3525N

Incompatible options have been provided to the utility.

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

SQL3526N

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.

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

In the FILETMOD parameter, the CODEPAGE option was invalid.

Correct the codepage number and resubmit the command.

SQL3528W

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.

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

SQL3529N

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

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

SQL3530I

The Load Query utility was invoked in an MPP environment.

No action is necessary.

SQL3531I

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

No action is necessary.

SQL3532I

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

No action is necessary.

SQL3533I

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

No action is necessary.

SQL3534I

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

No action is necessary.

SQL3535W

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

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

SQL3536N

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

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

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

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

SQL3538N

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.

Use the TABLE parameter of LOAD QUERY instead.

SQL3539N

LOAD TERMINATE can only be followed by LOAD TERMINATE.

User can proceed with LOAD TERMINATE only.

SQL3550W

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.

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

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.

No action is required.

SQL3600N

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.

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

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.

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

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

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

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.

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

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.

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

Correct the table names and execute the command again.

sqlcode: -3605

sqlstate: 428A6

SQL3606N

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.

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

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.

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

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.

SQL3701W

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.

No action required.

SQL3702W

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.

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

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.

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.

This is an informational message. No action is required.

SQL3704N

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.

Resubmit the command using a valid num_buffers parameter.

SQL3705N

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.

Reissue the command with a valid buffer size.

SQL3706N

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

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

SQL3707N

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

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.

SQL3783N

During load recovery, an error was encountered while opening the copy location file. The operating system file open return code is returned.

Look at the error code in the message for more information. Correct the error, if possible, and resubmit the command.

SQL3784W

During load recovery, invalid data was encountered while reading from the copy location file. The line number and error type are returned. The utility waits for a response to continue.

Correct the data in the copy location file and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL3785N

A severe error occurred during load recovery. The utility stops processing.

(Note : if you are using a partitioned database server, the node number indicates which node the error occurred on. Otherwise, it is not pertinent and should be ignored.)

Examine the error code in the message for more information. Take corrective action and resubmit the command.

SQL3798W

Load recovery is in progress and one of the parameters passed in is not valid for the current state of load recovery.

Correct the value in error and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL3799W

A warning condition is encountered during load recovery. The utility waits for a response to continue.

(Note : if you are using a partitioned database server, the node number indicates which node the error occurred on. Otherwise, it is not pertinent and should be ignored.)

Examine the error code in the message for more information. Take corrective action and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL3802N

An invalid quiesce mode was passed to the quiesce API.

Resubmit the command with the correct parameters.

SQL3804N

An invalid index was encountered during the processing of a utility command.

Check in the Administration Guide to determine the appropriate way to revalidate the index and resubmit the command after the condition is corrected.

SQL3805N

The loadapi action (either quiescemode or callerac) passed to the load API is in conflict with either the state of the application or the state of one or more table spaces for the table.

The possible reason codes are as follows:

01

The state of one of the table spaces for the table specified prohibits the loadapi action or quiescemode.

02

The application is not at the start of its logical unit of work. This condition prohibits the load action specified.

03

The state of the application prohibits the load action specified.

04

One or more of the table spaces for the table is already quiesced by the maximum number of quiescers.

05

The system catalog table space cannot be quiesced.

06

A LOAD command with the COPY option is not allowed when a table space is in backup pending state.

07

Attempt to restart a load at an incorrect phase.

08

Attempt to restart a load into a table whose partitioning key depends on an identity column and where not all of the table partitions are restarting from the load phase. Such a load is not allowed as hashing of rows during the restarted load may be different from the hashing in the initial load due to the dependence on the identity column.

09

The QUIESCE TABLESPACES FOR TABLE command failed because the database is in WRITE SUSPEND state.

10

Attempt to restart a load against a random distribution table using the random by generation method.

The user response corresponding to the reason code is as follows:

01

Resubmit the command with the correct loadapi action or quiescemode, or correct the state of the table spaces for the table.

02

Resubmit the command with the correct load action or complete the current logical unit of work by issuing either a COMMIT or ROLLBACK.

03

Resubmit the command with the correct load action.

04

Determine which table spaces for the table have reached the maximum number of quiescers. QUIESCE RESET these table spaces.

05

Resubmit the command with a table which is not in the system catalog table space.

06

Resubmit the command omitting the copy parameter

07

Determine at which phase the load should be restarted and resubmit the command with the correct phase.

08

Terminate the load operation using the TERMINATE action then resubmit the original load command.

09

Resume I/O write operations for the database, and resubmit the QUIESCE TABLESPACES FOR TABLE command.

10

Terminate the load operation using the TERMINATE action then resubmit the original load command.

SQL3806N

One or more constraints for the table to be loaded are still on when the load API is invoked.

Resubmit the command after all table constraints are turned off.

SQL3807N

Another user has submitted the quiesce command and it has not yet completed.

Wait for the quiesce to complete.

SQL3808N

Another user has submitted the unquiesce command and it has not yet completed.

Wait for the unquiesce to complete.

SQL3901N

Processing ended because of a non-severe system error.

SQL3902C

A system error occurred.

SQL3910I

SQL3911I

SQL3912I

SQL3913I

SQL3914I

SQL3915I

SQL3916I

SQL3917I

SQL3918I

SQL3919I

SQL3920I

The application version reported by the satellite does not exist at the satellite control server.

Contact the help desk or your system administrator.

SQL3921I

When disabled, the satellite cannot synchronize.

Contact the help desk or your system administrator.

SQL3930W

No synchronization scripts were downloaded to the satellite for execution.

Contact the help desk or your system administrator to ensure that synchronization scripts are available on the satellite control database for this satellite.

SQL3931W

Either the satellite ID is not defined correctly on the satellite or this satellite has not been defined in the satellite control database.

If you use the DB2SATELLITEID registry variable, ensure that it is set to the unique ID for the satellite. If you are using the operating system logon ID as the satellite ID, ensure you log on using it.

SQL3932W

The application version on the satellite is different from any that are available for this satellite's group.

Ensure that the application version on the satellite is set to the correct value.

SQL3933W

The release level of the satellite must be within the range of one level above to two levels below that of the satellite control server.

Contact the help desk or your system administrator.

SQL3934W

The satellite has been placed in the disabled state at the satellite control server.

Contact the help desk or your system administrator.

SQL3935W

The satellite is in the failed state at the control server.

Contact the help desk or your system administrator.

SQL3936W

The synchronization session has not reached a stage where the progress information has been logged, or there is no active synchronization session for this satellite.

Ensure the synchronization session is active, or try querying for progress information later.

SQL3937W

A satellite can only synchronize with a particular application version for its group. The application version for this satellite is not available for the satellite's group at the control server.

Ensure that the application version on the satellite is set to the correct value.

SQL3938W

An interrupt was issued while the script execution phase of the synchronization process was being performed. The synchronization session was stopped but the satellite may be in an inconsistent state because a script may have been halted at an inappropriate place.

Contact the help desk or your system administrator.

SQL3942I

The session identifier was set successfully for the satellite.

No action is required.

SQL3943N

The specified synchronization session identifier is longer than the allowed length of length characters.

Ensure that the identifier is no more than nnn characters.

SQL3944I

The session identifier was reset successfully for the satellite.

No action is required.

SQL3945I

The session identifier for this satellite was found and returned successfully.

No action is required.

SQL3946N

The synchronization session identifier operation has failed for an unknown reason.

Ensure that the product is installed correctly. If the failure persists, contact DB2 service.

SQL3950N

Only one synchronization session can be active at a time.

Wait until the current synchronization session completes successfully before initiating another session.

SQL3951N

Either the operating system logon was bypassed or the DB2SATELLITEID registry variable was not set.

If you are using the operating system logon ID as the satellite ID, log on to the operating system. If you use the DB2SATELLITEID registry variable, ensure that it is set to the unique ID for the satellite.

SQL3952N

Either the satellite ID is not defined correctly on this satellite or this satellite has not been defined at the satellite control server.

If you use the DB2SATELLITEID registry variable, ensure that it is set to the unique ID for the satellite. If you are using the operating system logon ID as the satellite ID, ensure you log on using it. Otherwise, contact the help desk or your system administrator.

SQL3953N

The satellite ID has been disabled at the satellite control server.

Contact the help desk or your system administrator.

SQL3954N

The satellite is in the failed state because a previous synchronization session failed.

Contact the help desk or your system administrator.

SQL3955N

The satellite control database is not cataloged correctly.

Contact the help desk or you system administrator.

SQL3956N

The application version is not defined locally on this satellite or is not defined correctly.

Ensure that the application version is set to the correct value.

SQL3957N

An error has been detected by the communication subsystem. Refer to sqlcode for more details.

Contact the help desk or your system administrator.

SQL3958N

An unknown error has been detected by the communication subsystem. Refer to sqlcode for more details.

Contact the help desk or your system administrator.

SQL3959N

An error has been detected by the communication subsystem. Refer to sqlcode for more details.

Contact the help desk or your system administrator.

SQL3960N

An error has been detected by the communication subsystem. Refer to sqlcode for more details.

Contact the help desk or your system administrator.

SQL3961N

An authentication error was detected while trying to connect to the satellite control database.

Either the remote administrative user ID or the password required to connect to the satellite control database was not correct, or both. Either provide the correct user ID and password, or contact the help desk or your system administrator.

SQL3962N

An error preventing synchronization occurred at the satellite control server.

Attempt to synchronize again. If failure persists, contact the help desk or your system administrator.

SQL3963N

An error occurred while uploading results to the satellite control server.

Contact the help desk or your system administrator.

SQL3964N

The release level of the satellite must be within the range of one level above to two levels below that of the satellite control server.

Contact the help desk or your system administrator.

SQL3965N

The satellite cannot download the scripts that are required to synchronize the satellite. One possible reason for this failure is that the control server cannot instantiate parameterized scripts with the attributes of the satellite. Another reason is that the satellite control server was temporarily unable to complete the request because of resource constraints.

Try the request again. If the failure persists, contact the help desk or your system administrator.

SQL3966N

Try the request again. If failure persists, contact the help desk or your system administrator.

SQL3967N

Progress on this satellite's synchronization session cannot be retrieved. Either the data is corrupt, or it does not exist.

If a synchronization session is active and no progress information is available, contact the help desk or your system administrator.

SQL3968N

One of the synchronization scripts failed during execution. Either a return code was not in the defined success code set, or the script failed to execute.

Contact the help desk or your system administrator.

SQL3969N

Script execution fails when an interrupt is received. An abnormal termination of this type will cause the synchronization session to fail because the system may be in an inconsistent state.

Contact the help desk or your system administrator.

SQL3970N

Script execution failed because of an unknown error.

Contact the help desk or your system administrator.