SQL3001C An I/O error (reason = reason) occurred while opening the output file.

Explanation

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

The command cannot be processed. No data is processed.

User response

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 An I/O error occurred while writing to the output data file.

Explanation

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.

User response

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

SQL3003C An I/O error occurred while closing the output data file.

Explanation

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

The file is not closed.

User response

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

SQL3004N The load, import, or export utility failed because the specified file type is not supported.

Explanation

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.

User response

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

SQL3005N Processing was interrupted.

Explanation

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.

User response

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 An I/O error occurred while opening the message file.

Explanation

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.

User response

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

SQL3007C An I/O error occurred while writing to the message file.

Explanation

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

Processing may not have finished.

User response

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

SQL3008N The utility encountered an error error while connecting to the database.

Explanation

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

No data is imported or exported.

User response

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

SQL3009N The Action String parameter is not valid or too long.

Explanation

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.

User response

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

SQL3010N The METHOD parameter is not valid.

Explanation

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.

User response

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

SQL3011C There is not enough storage to process the command.

Explanation

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.

User response

Stop the application. Possible solutions include:
  • Verify that your system has sufficient real and virtual memory.
  • Remove background processes.
  • Increase the util_heap_sz for the database.
  • Decrease the size of buffers to use for the LOAD.
  • The util_heap_sz is shared by the LOAD, BACKUP, RESTORE and REORG utilities, so have fewer concurrent instances of these utilities running.

SQL3012C A system error occurred.

Explanation

An operating system error occurred.

The command cannot be processed.

User response

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

SQL3013N The length of the filetmod is out of the acceptable range. It should be greater than or equal to zero and less than or equal to 8000.

Explanation

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.

User response

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

SQL3014C An I/O error occurred while closing the message file.

Explanation

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

The message file is not closed.

User response

If the message file is incomplete, resubmit the command.

SQL3015N An SQL error sqlcode occurred during processing.

Explanation

An SQL error occurred during the utility call.

The utility stops processing.

User response

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

SQL3016N An unexpected keyword keyword was found in the filetmod parameter for the filetype.

Explanation

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.

User response

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 A delimiter is not valid or is used more than once.

Explanation

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.

User response

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

SQL3018N The period was specified as a character string delimiter.

Explanation

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

The command cannot be processed.

User response

Resubmit the command with valid delimiter overrides.

SQL3019N No Action String parameter was specified in the command.

Explanation

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

The command cannot be processed.

User response

Resubmit the command with an Action String parameter.

SQL3020N The user does not have the authority to run the specified EXPORT command.

Explanation

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.

User response

Request appropriate authorization before exporting data from tables.

SQL3021N The user does not have the authority to run the specified IMPORT command on table name.

Explanation

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.

User response

Ensure that you are authorized to perform the import operation.

SQL3022N An SQL error sqlcode occurred while processing the SELECT string in the Action String parameter.

Explanation

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.

User response

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.

Explanation

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.

User response

Resubmit the statement with a valid database name parameter.

SQL3024N An I/O error occurred while opening the format file.

Explanation

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.

User response

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 A parameter specifying a filename or path is not valid.

Explanation

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.

User response

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

Resubmit the statement with a valid parameter.

SQL3026N The msgfile or tempfiles path parameter is not valid.

Explanation

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.

User response

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

SQL3027N An I/O error occurred while reading from the format file.

Explanation

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.

User response

Verify that the format file is readable.

SQL3028N The export method indicator is not valid. It must be either 'N' or 'D'.

Explanation

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

The command cannot be processed.

User response

Resubmit the statement with a valid method indicator.

SQL3029N No filetype parameter was specified.

Explanation

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.

User response

Resubmit the statement with a valid filetype.

SQL3030C An I/O error (reason = reason) occurred while opening the input file.

Explanation

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.

User response

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 An I/O error occurred while reading from the input file.

Explanation

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.

User response

Verify that the input file is readable.

SQL3032N The LOAD/IMPORT method indicator is not valid for the specified filetype. It must be either 'N', 'P', or 'default'.

Explanation

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.

User response

Resubmit the command with a valid method indicator.

SQL3033N A keyword such as INSERT, REPLACE, CREATE, INSERT_UPDATE, or REPLACE_CREATE is missing from the target specification or it is misspelled.

Explanation

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.

User response

Resubmit the command with a valid Action String parameter.

SQL3034N The keyword INTO is missing from the target specification or it is misspelled.

Explanation

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

The command cannot be processed.

User response

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

SQL3035N The tablename parameter in the target specification is not valid.

Explanation

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.

User response

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 in the target specification does not have a closed parenthesis.

Explanation

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

The command cannot be processed.

User response

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

SQL3037N An SQL error sqlcode occurred during Import processing.

Explanation

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

The command cannot be processed.

User response

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

SQL3038N The Action String parameter contains unexpected characters.

Explanation

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.

User response

Resubmit the command with a valid Action String parameter.

SQL3039W The memory available to LOAD for DATA BUFFER prohibits full LOAD parallelism. Load parallelism of value will be used

Explanation

The LOAD utility attempted to determine the optimal level of CPU parallelism for SMP exploitation based on the system configuration, or the user specified a value for LOAD parallelism when invoking the utility. However, one of the following limitation was encountered:
  1. The amount of free memory in the utility heap prohibits this degree of parallelism.
  2. The DATA BUFFER parameter was specified with a value too small to allow for the specified or available parallelism.

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

User response

  1. Ignore this message, and the LOAD will complete normally using the smaller value for LOAD parallelism. However, Load performance may be less than optimal.
  2. Specify a smaller value for LOAD parallelism when invoking the utility.
  3. Increase the size of the utility heap.
  4. Increase the size of the data buffer parameter, or leave the parameter blank and let the LOAD utility determine a default based on the freespace in the utility heap.

SQL3040N The utility cannot use the file name file-name specified in the option-name parameter. Reason code: reason-code.

Explanation

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.

User response

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

SQL3041N The date value specified is not supported in Sybase.

Explanation

Sybase does not support date values prior to 1753.

User response

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

SQL3042N The LINKTYPE specified for a DATALINK column is invalid.

Explanation

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

User response

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

SQL3043N The DATALINK SPECIFICATION for DATALINK column(s) is invalid.

Explanation

The DATALINK SPECIFICATION for DATALINK column(s) is invalid for one of the following reasons:
  • No value is specified for DL_URL_REPLACE_PREFIX.
  • No value is specified for DL_URL_DEFAULT_PREFIX.
  • No value is specified for DL_URL_SUFFIX.
  • Contains keywords other than DL_URL_REPLACE_PREFIX or DL_URL_DEFAULT_PREFIX or DL_URL_SUFFIX.

User response

Correct the specification and resubmit the command.

SQL3044N The DATALINK SPECIFICATION for a DATALINK column has duplicate prefix specification.

Explanation

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

User response

Remove the duplicate specification and resubmit the command.

SQL3045N A dcolumn position in the METHOD parameter is less than one or greater than the maximum number of columns (1024) in a Delimited ASCII file.

Explanation

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.

User response

Resubmit the command with valid dcolumn positions.

SQL3046N The number of columns in the METHOD parameter is less than one.

Explanation

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

The command cannot be processed.

User response

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

SQL3047N The LOAD/IMPORT method specified in METHOD is not valid for Delimited ASCII files. It must be either 'P' or 'default'.

Explanation

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

The command cannot be processed.

User response

Resubmit the command with a valid import method.

SQL3048N There are fewer columns specified from the input file than database columns, but one of the database columns is not nullable.

Explanation

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.

User response

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 data type type of the database column name is not compatible with this format file, but the database column is not nullable.

Explanation

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.

User response

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

SQL3050W Conversions on the data will be made between the IXF file code page file-code-page and the application code page application-code-page.

Explanation

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.

User response

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 to be loaded into column-name has been loaded, but conversion from the IXF file code page to the application code page has not been performed.

Explanation

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.

User response

This is a warning only.

SQL3052N The type path parameter is missing but is required. Reason code: reason-code.

Explanation

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.

User response

Specify the path and resubmit your command.

SQL3054N The input file is not a valid PC/IXF file. The file is too short to contain a valid H record.

Explanation

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.

User response

Verify that the input file is correct.

SQL3055N The input file is not a valid PC/IXF file. The length field in the first record cannot be converted to a numeric value.

Explanation

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.

User response

Verify that the input file is correct.

SQL3056N The input file is not a valid PC/IXF file. The value in the length field of the H record is too small.

Explanation

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.

User response

Verify that the input file is correct.

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

Explanation

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.

User response

Verify that the input file is correct.

SQL3058N The identifier field in the H record is not IXF.

Explanation

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.

User response

Examine the identifier field in the H record.

SQL3059N The version field in the H record is not valid.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the version field in the H record.

SQL3060N The HCNT field in the H record cannot be converted to a numeric value or the value is out of range.

Explanation

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.

User response

Examine the HCNT field in the H record.

SQL3061N The single-byte and/or double-byte code page field in the H record cannot be converted to a numeric value or the value is out of range.

Explanation

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.

User response

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 cannot be converted to a numeric value or the value is out of range.

Explanation

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.

User response

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 value-1 in the H record is not compatible with the single-byte code page value value-2 for the application. The FORCEIN option was not specified.

Explanation

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.

User response

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

SQL3064N The double-byte code page value value-1 in the H record is not compatible with the double-byte code page value value-2 for the application. The FORCEIN option was not specified.

Explanation

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.

User response

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

SQL3065C The value for the application codepage cannot be determined.

Explanation

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

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

User response

Contact your technical service representative.

SQL3066N While reading or looking for the T record, the end of the file was reached.

Explanation

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.

User response

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 cannot be converted to a numeric value.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the length field in the T record.

SQL3068N The value in the length field of the T record is too small.

Explanation

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.

User response

Examine the length field in the T record.

SQL3069N The first non-A record following the H record is not a T record.

Explanation

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.

User response

Examine the records following the H record.

SQL3070N The length field in an A record is out of range.

Explanation

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.

User response

Examine the length field in the A records.

SQL3071N The data-convention field in the T record is not C.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the data-convention field in the T record.

SQL3072N The data-format field in the T record is not M.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the data-format field in the T record.

SQL3073N The machine format field in the T record is not PCbbb (where b = blank).

Explanation

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.

User response

Examine the machine format field in the T record.

SQL3074N The data-location field in the T record is not I.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the data-location field in the T record.

SQL3075N The CCNT in the T record cannot be converted to a numeric value or the value is out of range.

Explanation

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.

User response

Examine the CCNT field in the T record.

SQL3076N The name length field in the T record cannot be converted to a numeric value or the value is out of range.

Explanation

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.

User response

Examine the name length field in the T record.

SQL3077N The number of C records specified in the CCNT field in the T record value exceeds the maximum allowed maximum.

Explanation

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.

User response

Examine the CCNT field in the T record.

SQL3078N The length field in an A record cannot be converted to a numeric value.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the length fields in the A records.

SQL3079N The length field in a C record cannot be converted to a numeric value.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the length field in the C records.

SQL3080N The value in the length field of the C record is too small.

Explanation

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.

User response

Examine the length field in the C records.

SQL3081N Not enough C records were found.

Explanation

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.

User response

Examine the T and C records.

SQL3082N While reading or looking for a C record, the end of the file was reached.

Explanation

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.

User response

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 column name cannot be converted to a numeric value.

Explanation

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.

User response

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

SQL3084N The D-record-position field in the C record for column name cannot be converted to a numeric value.

Explanation

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.

User response

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

SQL3085N The D-record-id and D-record-position fields in the C record for column name are out of range or inconsistent with the previous C record.

Explanation

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.

User response

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

SQL3086N There was no source column specified to be loaded into database column name or the specified source column does not exist, but the database column is not nullable.

Explanation

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.

User response

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 source column specified to be loaded into database column name is not valid, but the database column is not nullable.

Explanation

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.

User response

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

SQL3088N The source column specified to be loaded into database column name is not compatible with the database column, but the database column is not nullable.

Explanation

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.

User response

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

SQL3089N A non-D record was found where a D record was expected.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the D records in the file.

SQL3090N The length field in a D record cannot be converted to a numeric value.

Explanation

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

The utility stops processing. No data is loaded.

User response

Examine the length field in the D records.

SQL3091N The length field in a D record is out of range.

Explanation

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.

User response

Examine the length field in the D records.

SQL3092N The identifier field in a D record does not contain the expected value.

Explanation

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.

User response

Examine the identifier field in the D records.

SQL3094N The input column name was not found, but the corresponding database column is not nullable.

Explanation

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

User response

Verify that the input file contains the specified column names.

SQL3095N The specified column position position is not in the valid range of 1 to 256.

Explanation

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.

User response

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

SQL3100W Column number column-number (identified as name) in the output DEL format file is longer than 254 bytes.

Explanation

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.

User response

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 There is a character string delimiter in column column-number in row row-number.

Explanation

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.

User response

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 in the METHOD parameter is greater than the number of columns in the Action String (e.g. "REPLACE into ...") parameter.

Explanation

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.

User response

Review the data in the output table or file.

SQL3103W The number of columns in the METHOD parameter is less than the number of columns in the Action String (e.g. "REPLACE into ...") parameter.

Explanation

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.

User response

Review the data in the output table or file.

SQL3104N The Export utility is beginning to export data to file name.

Explanation

This is the normal beginning message.

User response

No action is required.

SQL3105N The Export utility has finished exporting number rows.

Explanation

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.

User response

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 An error occurred while formatting a message for the message file.

Explanation

The error message may be incomplete or formatted incorrectly.

User response

No action is required.

SQL3107W At least one warning message was encountered during LOAD processing.

Explanation

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.

User response

Review the message file warning.

SQL3108W Unable to access file referenced by a DATALINK value in row row-number and column column-number. Reason code = reason-code.

Explanation

The possible causes of this message depend on the value of reason-code:
1
DATALINK value data location format is not valid.
2
DATALINK value DB2 Data Links Manager is not registered with the database.
3
DATALINK linktype value is not valid.
4
DATALINK value referenced file cannot be found by the DB2 Data Links Manager.
5
DATALINK value referenced file is already linked to the database.
6
DATALINK value referenced file cannot be accessed for linking. It may be a symbolic link or a file with permission bit for set user ID (SUID) on or set group ID (SGID) on.
7
DATALINK value URL or comment is too long.
8
DATALINK value referenced file cannot be linked to the database. The DB2 Data Links Manager does not authorize the DB2 user to link this file.

User response

The action is based on the reason-code as follows:
1
Correct the data location format. If hostname is not specified, DB2 can use the local hostname as default only if support for FILE LINK CONTROL is enabled. Refer to the Administration Guide for information on enabling this support.
2
Ensure that the correct DB2 Data Links Manager is specified and if so have it registered to the database. Registered DB2 Data Links Managers are ignored unless support for FILE LINK CONTROL is enabled. Refer to the Administration Guide for information on enabling this support.
3
Correct the linktype value.
4
Check that the correct file is specified and that the file exists
5
Either unlink the existing reference to the file or do not specify the file in this statement.
6
Linking of directories is not allowed. Use the actual file name, not the symbolic link. If SUID or SGID is on, this file cannot be linked using a DATALINK type.
7
Reduce the length of the data location value or the comment.
8
Contact the DB2 Data Links Manager administrator to get the necessary authorization

SQL3109N The utility is beginning to load data from file name.

Explanation

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.

User response

No action is required.

SQL3110N The utility has completed processing. number rows were read from the input file.

Explanation

This is the normal ending message.

User response

No action is required.

SQL3111C An I/O error occurred while closing the input data file.

Explanation

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.

User response

Examine the input file for an I/O error.

SQL3112W There are fewer input file columns specified than database columns.

Explanation

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.

User response

No action is required.

SQL3113W The data type type of the database column name is not compatible with this format file. Null values are inserted for the column.

Explanation

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.

User response

If nulls are not acceptable for the column, do one of the following:
  • Edit the data in the table.
  • If possible, use another compatible column in the database table as the target column and resubmit the command.
  • Redefine the database table so the columns are compatible with the columns being loaded and resubmit the command.

SQL3114W Some data following text in row row-number and column column-number was not loaded.

Explanation

Some data in the specified row and column is not loaded, probably because the column contains data as follows:
  • A closed string delimiter
  • An isolated carriage return or line feed control character
  • A non-delimited string value.

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

The contents of the field may be incomplete.

User response

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 beginning text in row row-number and column column-number is longer than the longest allowable table column. The value was truncated.

Explanation

The field value is longer than 32700 bytes.

The value was truncated after 32700 bytes.

User response

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 The field value in row row-number and column column-number is missing, but the target column is not nullable.

Explanation

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.

User response

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

SQL3117W The field value in row row-number and column column-number cannot be converted to a SMALLINT value. A null was loaded.

Explanation

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.

User response

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

SQL3118W The field value in row row-number and column column-number cannot be converted to a SMALLINT value, but the target column is not nullable. The row was not loaded.

Explanation

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.

User response

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

SQL3119W The value in row row-number and column column-number could not be converted to an integer value, so a null value was loaded instead.

Explanation

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

User response

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 value in row row-number and column column-number could not be converted to an integer value, and the target column is not nullable, so the row was not loaded.

Explanation

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

User response

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 field value in row row-number and column column-number cannot be converted to a FLOAT value. A null was loaded.

Explanation

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.

User response

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

SQL3122W The field value in row row-number and column column-number cannot be converted to a FLOAT value, but the target column is not nullable. The row was not loaded.

Explanation

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.

User response

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

SQL3123W The field value in row row-number and column column-number cannot be converted to a PACKED DECIMAL value. A null was loaded.

Explanation

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.

User response

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

SQL3124W The field value in row row-number and column column-number cannot be converted to a PACKED DECIMAL value, but the target column is not nullable. The row was not loaded.

Explanation

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.

User response

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

SQL3125W The character data in row row-number and column column-number was truncated because the data is longer than the target database column.

Explanation

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.

User response

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 Remote client requires absolute path for files and directories.

Explanation

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.

User response

Resubmit the statement with valid absolute file and pathnames.

SQL3128W The field containing data in row row-number and column column-number was truncated into a DATE field because the data is longer than the database column.

Explanation

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.

User response

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 A date, time, or timestamp field was padded with blanks. Row number: row-number. Column number: column-number. Text in the field: text.

Explanation

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

The data on the right is padded with blanks.

User response

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 field containing text in row row-number and column column-number was truncated into a TIME field because the data is longer than the database column.

Explanation

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.

User response

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 field containing text in row row-number and column column-number was truncated into a TIMESTAMP field because the data is longer than the database column.

Explanation

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.

User response

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 in column column will be truncated to size size.

Explanation

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.

User response

This is a warning only. No action is required.

SQL3133W The field in row row-number and column column-number contains invalid DATALINK value. A null was loaded.

Explanation

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.

User response

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

SQL3134W The field in row row-number and column column-number contains invalid DATALINK value, but the target column is not nullable. The row was not loaded.

Explanation

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.

User response

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

SQL3135N The number of columns in the METHOD parameter is greater than the number of columns in the target table.

Explanation

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.

User response

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

SQL3137W Row row-number is too short. At least one input value being loaded to a non-nullable column is missing. The row was not loaded.

Explanation

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.

User response

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 ending character string delimiter was not found before the end of the input data file was reached.

Explanation

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.

User response

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 An error error occurred while the utility was disconnecting from the database.

Explanation

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

The output data may be incomplete.

User response

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

SQL3140W The field value in row row-number and column column-number cannot be converted to a decimal floating-point value. A null was loaded.

Explanation

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.

User response

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

SQL3141W The field value in row row-number and column column-number cannot be converted to a decimal floating-point value, but the target column is not nullable. The row was not loaded.

Explanation

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.

User response

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

SQL3147W More than 2048 rows were exported into a worksheet formatted file.

Explanation

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

Continue processing.

User response

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

SQL3148W A row from the input file was not inserted into the table. SQLCODE sqlcode was returned.

Explanation

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.

User response

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 number-1 rows were processed from the input file. number-2 rows were successfully inserted into the table. number-3 rows were rejected.

Explanation

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.

User response

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

SQL3150N The H record in the PC/IXF file has product product, date date, and time time.

Explanation

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

User response

No action is required.

SQL3151N No data conversion will be done from the single-byte code page value code-page in the H record to the application single-byte code page value code-page because the FORCEIN option was specified.

Explanation

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

User response

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 value value in the H record is not compatible with the double-byte code page value value for the application. Data will be inserted because the FORCEIN option was specified.

Explanation

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.

User response

No action is required.

SQL3153N The T record in the PC/IXF file has name name, qualifier qualifier, and source source.

Explanation

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.

User response

No action is required.

SQL3154W The HCNT value in the H record and the CCNT value in the T record are not compatible. The CCNT value in the T record will be used.

Explanation

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.

User response

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 name length field in the C record for column name is not valid. Data from the column will not be loaded.

Explanation

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.

User response

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

SQL3156W The null field in the C record for column name is not valid. Data from the column will not be loaded.

Explanation

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

Data from the indicated column is not loaded.

User response

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

SQL3157W The type field in the C record for column name is not valid. Data from the column will not be loaded.

Explanation

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.

User response

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

SQL3158W The single-byte code page field in the C record for column name is not valid. Data from the column will not be loaded.

Explanation

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.

User response

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 column name is not valid. Data from the column will not be loaded.

Explanation

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.

User response

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 column name is not valid. Data from the column will not be loaded.

Explanation

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

Data from the indicated column is not loaded.

User response

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

SQL3161W The precision field in the C record for column name is not valid. Data from the column will not be loaded.

Explanation

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

Data from the indicated column is not loaded.

User response

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

SQL3162W The scale field in the C record for column name is not valid. Data from the column will not be loaded.

Explanation

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

Data from the indicated column is not loaded.

User response

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

SQL3163W The column length field in the C record for floating point column name is blank. A value of 00008 will be used.

Explanation

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

A column length of 00008 is used.

User response

No action is required.

SQL3164W The column length field in the C record for floating point column name is not valid. Data from the column will not be loaded.

Explanation

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.

User response

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

SQL3165W The column type field type in the C record for column name is not valid. Data from the column will not be loaded.

Explanation

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

Data from the indicated column is not loaded.

User response

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

SQL3166W No PC/IXF column was specified to be loaded into database column name or the specified PC/IXF column does not exist. Nulls will be inserted.

Explanation

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.

User response

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 The PC/IXF column specified to be loaded into database column name is not valid. Nulls will be inserted.

Explanation

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.

User response

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

SQL3168W The PC/IXF column specified to be loaded into database column name is not compatible with the database column. Nulls will be inserted.

Explanation

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

Null values are loaded for the indicated column.

User response

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

SQL3169N The FORCEIN option may be used to make the PC/IXF column name acceptable for loading into database column name.

Explanation

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

User response

No action required.

SQL3170W The end of the file was reached within a row of data. The partial row of data was not loaded.

Explanation

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.

User response

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 name was not found. The corresponding database column will contain null values.

Explanation

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

User response

Verify the specified input column name.

SQL3175W The input record for database row row, column column is not valid.

Explanation

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.

User response

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 Row row in the input file is missing data for inserting into a non-nullable column in the database. The row was not inserted.

Explanation

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.

User response

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 Insert diskette number into drive drive.

Explanation

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.

User response

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

SQL3181W The end of the file was reached before the expected ending record was found.

Explanation

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.

User response

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 Insert diskette number into drive drive. The diskette that is currently inserted is not the right diskette or the continuation diskette is not valid.

Explanation

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.

User response

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 Multiple delimiter overrides in the filetmod parameter are not separated by blanks.

Explanation

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.

User response

Resubmit the command with a correct filetmod parameter.

SQL3184W An SQL warning SQLCODE occurred while creating the table.

Explanation

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

User response

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 The previous error occurred while processing data from row row-number of the input file.

Explanation

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

User response

No action is required.

SQL3186W Data was not loaded into the database, because the log was full or the lock space was exhausted. SQLCODE sqlcode was returned. A commit will be attempted and the operation will continue if the commit is successful.

Explanation

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.

User response

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 An error occurred while creating an index. SQLCODE sqlcode was returned.

Explanation

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.

User response

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.

Federated system users: select from the data source catalog and the federated server catalog to determine which index or indexes were not created in thefederated server catalog. Either:
  • Create the indexes using the CREATE INDEX command. Remember to truncate columns as appropriate in order to not violate limits which caused the index to not be created in the first place.
  • Do nothing and allow federated server to function without knowledge about the index.

Both of the previously listed options have potential performance implications.

SQL3188N An error occurred while erasing the contents of the table.

Explanation

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.

User response

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

SQL3189N The previous message refers to index name with columns column-list.

Explanation

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.

User response

Manually create the index with the CREATE INDEX command.

SQL3190N The indexixf option is not valid for this Import operation.

Explanation

If INDEXIXF is used in the filetmod parameter of the IMPORT command, each of the following is also required:
  • The IMPORT must be replacing the contents of a table.
  • The METHOD parameter must be null.
  • Each IXF column must be targeted to a database column with the same name.

The utility stops processing. No data is imported.

User response

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

SQL3191W The field in row row-number, column column-number which begins with string does not match the user specified DATEFORMAT, TIMEFORMAT, or TIMESTAMPFORMAT. The row will be rejected.

Explanation

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.

User response

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

SQL3192N In the filetmod a user specified format keyword beginning with the string string is not valid.

Explanation

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.

User response

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

SQL3193N No data was inserted because it is not supported to either load or import data into the specified view or table.

Explanation

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.

User response

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

SQL3194N The specified table is a system table. You cannot load a system table.

Explanation

The utility cannot be run against a system table.

The utility stops processing. No data is loaded.

User response

Resubmit the command with a valid table name.

SQL3195W The diskette number in drive drive cannot be used for the output file. Insert a formatted diskette with writable free space.

Explanation

The EXPORT utility cannot use the current diskette for exporting to a PC/IXF file for one of the following reasons:
  • The output file cannot be opened on the diskette. The diskette may be unformatted.
  • Not enough free space is available on the diskette.

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.

User response

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

SQL3196N The input file was not found.

Explanation

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.

User response

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

SQL3197N An attempt was made to execute multiple copies of import or export.

Explanation

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.

User response

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

SQL3201N The specified table cannot be replaced because another table is dependent on it.

Explanation

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

The command cannot be processed.

User response

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.

Explanation

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.

User response

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 not permitted for the specified target because it has no primary key or all columns are in the primary key.

Explanation

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.

User response

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

SQL3204N The INSERT_UPDATE option may not be applied to a view.

Explanation

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.

User response

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

SQL3205N The specified view cannot be replaced because the base table has a dependent.

Explanation

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.

User response

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

SQL3206N The specified view cannot be replaced because its definition involves a subquery.

Explanation

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.

User response

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

SQL3207N Invalid table-list provided. Reason code reason-code.

Explanation

The traversal-order-list/subtable-list provided is invalid. The explanation for the reason code is:
  1. Tables specified in the traversal-order-list are not in PRE-ORDER fashion.
  2. Tables specified in the traversal-order-list are not connected.
  3. Mismatch of schema name found in traversal-order-list/subtable-list.
  4. With REPLACE option, some subtables are missing in the traversal-order-list.
  5. Subtable-list is not equal to or a subset of the traversal-order-list.

User response

The user action, based on the reason code, is:
  1. Make sure the traversal-order-list is in PRE-ORDER fashion.
  2. Make sure all tables in the traversal-order-list are connected.
  3. Make sure schema names are consistent.
  4. When REPLACE option is used, make sure all subtables in the hierarchy are included.
  5. Make sure subtable-list is equal to or is a subset of the traversal-order-list.

SQL3208W Importing data from typed tables into regular table.

Explanation

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

User response

Please make sure such operation is intentional.

SQL3209N Import with CREATE option does not allow renaming subtable name nor attribute names.

Explanation

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

User response

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

SQL3210N Option option is not compatible with hierarchy in command-name.

Explanation

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

User response

Please check the command syntax for hierarchical support.

SQL3211N LOAD does not support typed tables.

Explanation

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

User response

Please use IMPORT to bring hierarchical data into the database.

SQL3212N The TERMINATE option of the LOAD command is not currently supported for tables with DATALINK column(s), or table spaces in delete pending state.

Explanation

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.

User response

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

SQL3213I The indexing mode is mode.

Explanation

The indexing mode values are a follows:
REBUILD
indexes will be completely rebuilt
INCREMENTAL
indexes will be extended
DEFERRED
indexes will not be updated, but will be marked as requiring refresh prior to next access.

User response

No action is required.

SQL3214N The load operation failed because the table is incompatible with the DEFERRED index mode. Reason code: reason-code.

Explanation

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.

User response

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

SQL3215W The Load utility currently does not support INCREMENTAL indexing when loading into a DMS table space on tables where the table's index object resides in the same table space as any of the other target table's objects, and the COPY option is also specified. The REBUILD indexing mode will be used instead.

Explanation

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

User response

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 The table's index object was not compatible with INCREMENTAL index maintenance at the time the load utility began. INCREMENTAL indexing cannot be performed during this load utility operation. The REBUILD indexing mode will be used instead.

Explanation

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.

User response

No action required.

SQL3217W The INCREMENTAL indexing mode is supported only when using LOAD to append data using the INSERT INTO action. The current LOAD action is action. The utility will use indexing mode of mode instead.

Explanation

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.

User response

No action necessary.

SQL3218C The LOAD utility cannot proceed because it has encountered one or more damaged index files. Restart the database and resubmit the LOAD command.

Explanation

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

User response

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 LOAD utility failed to disable constraint checking for the target table.

Explanation

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

User response

  • Issue the SET INTEGRITY OFF command on the target table prior to running the LOAD utility.
  • If attempting a LOAD in the REPLACE mode after a previously failed LOAD operation, use the LOAD TERMINATE command to put the tablespace into an accessible state prior to issuing a LOAD REPLACE command.

SQL3220W Volume volume-name was not found in the directory-name directory. Copy the volume into this directory and continue the LOAD/IMPORT.

Explanation

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.

User response

  • Find the part and put it in the same directory as the first part. Then call LOAD/IMPORT again with callerac of SQLU_CONTINUE. The LOAD/IMPORT will continue processing the file.
  • Terminate the LOAD/IMPORT by calling LOAD/IMPORT with a callerac of SQLU_TERMINATE.

SQL3221W ...Begin COMMIT WORK. Input Record Count = count.

Explanation

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

User response

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 ...COMMIT of any database changes was successful.

Explanation

The COMMIT was successful.

User response

None necessary if you get this message.

SQL3223N The parameter of type pointer to parameter is not specified properly.

Explanation

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.

User response

Call the utility again with a proper parameter.

SQL3225N The RESTARTCOUNT value or the SKIPCOUNT value value is greater than the number of rows (rows) in the file. No rows were loaded.

Explanation

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.

User response

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

SQL3227W Record token token1 refers to user record number token2.

Explanation

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.

User response

Refer to the original SQL message returned for appropriate action.

SQL3228N DEFERRED INDEXING is not supported for tables with DATALINK columns.

Explanation

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

User response

Reissue the load command specifying a different indexing mode.

SQL3229W The field value in row row-number and column column-number is invalid. The row was rejected. Reason code: reason-code.

Explanation

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

Reason codes:
1
The file named in the row and column cannot be found.
2
The file named in the row and column cannot be accessed.
3
Data is too long for the column.

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

User response

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

SQL3230N Codepage conversion from data file codepage datafile-codepage to database codepage database-codepage for data type data-type is not supported.

Explanation

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.

User response

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

SQL3232W An error occurred while writing to file file-name. file-name has been used instead.

Explanation

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.

User response

No action is required.

SQL3233W The attribute attribute-name in an XML Data Specifier (XDS) was ignored. Reason code: reason-code

Explanation

Reason codes:

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

User response

Check the attribute name and correct it if needed.

SQL3234N The XML Data Specifier (XDS) for column col-number is invalid. attribute name: attribute-name, character number: char-number, reason code: reason-code

Explanation

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.

User response

Resubmit the command with a valid XML Data Specifier.

SQL3235N The utility cannot use the type path path-name parameter as specified. Reason code: reason-code.

Explanation

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.

User response

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

SQL3236N A schema schema-name is specified in the IGNORE clause of XMLVALIDATE option, but it is also present in the left side of a schema pair in the MAP clause.

Explanation

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.

User response

Resubmit the command with a valid XMLVALIDATE option.

SQL3237N The supplied EXPORT Action String cannot be used with the XMLSAVESCHEMA option. Reason code: reason-code

Explanation

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.

User response

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

SQL3239W Schema information will not be included in the XDS for some XML documents.

Explanation

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 Authorization ID authorization-id does not have the LBAC credentials necessary to run the utility against a table that is protected with security policy policy-name.

Explanation

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.

User response

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 Row row and column column in the input source contains an invalid security label for the target table.

Explanation

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.

User response

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 Row row and column column in the input source contains an invalid security label string for the target table.

Explanation

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.

User response

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 security label string in row row and column column of the input source contains the element element, which is an invalid element for the security label component component.

Explanation

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.

User response

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 Row row and column column in the input source contains the security label named security-label-name, which cannot be found for the security policy policy-name protecting the target table.

Explanation

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.

User response

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 Row row and column column in the input source cannot be inserted into the target table because the user does not have the necessary LBAC credentials.

Explanation

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

User response

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