SQL3250N COMPOUND=value is invalid. Reason code: reason-code.

Explanation

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

1

It is invalid when the INSERT_UPDATE option is used.

2

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

3

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

4

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

5

The table being imported is a hierarchy or typed table.

6

The table being imported has generated columns.

7

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

8

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

9

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

User response

The action corresponding to the reason code:

For reason code 1:

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

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

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

For reason code 4:

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

For reason code 7:

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

SQL3251N error-count more errors occurred during the import.

Explanation

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

The utility continues processing.

User response

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

SQL3252N The Load METHOD method option is incompatible with the specified file format.

Explanation

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

User response

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

SQL3253N The utility is beginning to load data from the SQL statement statement in database database.

Explanation

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

User response

No action is required.

SQL3254N The utility is beginning to load data from the Table schema.tablename in database database.

Explanation

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

User response

No action is required.

SQL3255N The Load utility encountered an error while executing the SOURCEUSEREXIT source user exit. Reason Code reason.

Explanation

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

Reason Codes:
  1. The source user exit file specified could not be found.
  2. The source user exit ended prematurely or returned a non-zero return code.

User response

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

SQL3256N The Load utility encountered an error while processing data for the specified file type.

Explanation

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

User response

Ensure the data is in the correct file type format.

SQL3257N The Load utility encountered an error while processing data in the specified file type. Reason Code reason. If applicable, record number is record num and column number is column num.

Explanation

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

Reason Codes:

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

User response

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

SQL3260N An unexpected error occurred when accessing the LDAP directory. Error code = error-code.

Explanation

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

User response

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

SQL3261N The REGISTER LDAP command did not complete successfully because a required input parameter was not specified. Reason code = reason-code.

Explanation

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

1

The Network Id parameter was not specified.

2

The Partner LU parameter was not specified.

3

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

4

The Mode parameter was not specified.

6

The TCP/IP hostname parameter was not specified.

7

The TCP/IP service name parameter was not specified.

8

The IPX Address was not specified.

9

The computer name was not specified.

10

The instance name was not specified.

User response

Re-submit the command with the required input parameter

SQL3262N The TCP/IP service name name is not valid.

Explanation

The TCP/IP service name specified is not valid.

User response

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

SQL3263N The protocol type is not supported.

Explanation

The protocol type specified is not supported for the command.

User response

Re-submit the command using a supported protocol type.

SQL3264N The database server has not been registered in LDAP.

Explanation

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

User response

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

SQL3265N An unexpected error occurred during LDAP authentication.

Explanation

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

User response

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

SQL3266N The LDAP user password is incorrect.

Explanation

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

User response

Re-submit the command using the correct password.

SQL3267N The command failed because the user does not have sufficient authority to invoke the command. User ID: user-ID.

Explanation

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

User response

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

SQL3268N The LDAP schema is not compatible with the current release of DB2.

Explanation

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

User response

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

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

Explanation

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

User response

Perform the following actions:

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

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

Explanation

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

User response

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

SQL3271N The LDAP user's Distinguished Name (DN) and/or password is not defined for the current logon user.

Explanation

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

User response

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

SQL3272N The node node-name was not found in the LDAP directory.

Explanation

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

User response

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

SQL3273N The database database-alias was not found in the LDAP directory.

Explanation

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

User response

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

SQL3274W The database was created successfully. However, the database was not cataloged in the LDAP directory. SQLCODE = sqlcode.

Explanation

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

User response

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

SQL3275W The database was dropped successfully. However, the database was not uncataloged in the LDAP directory. SQLCODE = sqlcode.

Explanation

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

User response

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

SQL3276N Unable to obtain the LDAP naming context.

Explanation

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

User response

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

SQL3277N The database database-alias already exists in the LDAP directory.

Explanation

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

User response

Re-submit the command using a different alias name.

SQL3278N The node node already exists in the LDAP directory.

Explanation

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

User response

Re-submit the command using a different alias name.

SQL3279N The command did not complete successfully because LDAP is disabled.

Explanation

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

User response

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

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

SQL3280N The attempt to connect to a DRDA server failed.

Explanation

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

User response

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

SQL3281N The OSTYPE parameter is not valid.

Explanation

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

User response

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

SQL3282N The supplied credentials are not valid.

Explanation

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

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

User response

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

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

SQL3283W The database manager configuration was updated successfully. However, the protocol information was not updated in the LDAP directory. SQLCODE = sqlcode-value.

Explanation

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

User response

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

SQL3284N The nodetype parameter is not valid.

Explanation

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

User response

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

SQL3285N The command did not complete successfully because LDAP is not supported.

Explanation

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

User response

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

db2set DB2_ENABLE_LDAP=NO

SQL3303N The file type must be IXF when using the CREATE or REPLACE_CREATE keywords in the Action String parameter.

Explanation

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

The IMPORT utility stops processing. No data is imported.

User response

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

SQL3304N The table does not exist.

Explanation

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

The utility stops processing. No data is loaded.

User response

Do one of the following:
  • Resubmit the command with a table name of an existing table.
  • If the input file is a PC/IXF file, resubmit the command with the CREATE option.

SQL3305N The table cannot be created because it already exists.

Explanation

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

The IMPORT utility stops processing. No data is imported.

User response

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

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

Explanation

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

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

User response

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

SQL3307N The number of columns in the METHOD parameter does not match the number of entries in the Action String parameter or a column specified in the METHOD parameter does not exist.

Explanation

The CREATE or REPLACE_CREATE option was specified on the IMPORT command. Either:
  • If the NAMES or POSITIONS method indicator was specified in the METHOD parameter, the number of columns explicitly specified in METHOD is not equal to the number of columns explicitly specified in the Action String (e.g. "REPLACE into ...") parameter.
  • If the DEFAULT method indicator was specified in the METHOD parameter, the number of columns in the PC/IXF file is less than the number of columns specified in the Action String parameter.
  • One column specified in the METHOD parameter does not exist in the PC/IXF file.

The IMPORT utility stops processing. No table is created.

User response

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

SQL3308N The code page values of the PC/IXF column name are not compatible with the code page values for the application. The FORCEIN parameter was not specified.

Explanation

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

The utility stops processing. No data is loaded.

User response

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

SQL3309N Column name in the PC/IXF file is defined as a graphic column. The FORCEIN parameter was not specified.

Explanation

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

The utility stops processing. No data is loaded.

User response

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

SQL3310N Column name in the PC/IXF file is not valid.

Explanation

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

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

User response

Verify the column definition information in the input file.

SQL3311N The import operation failed because some aspect of the data in the IXF input file is not supported with the CREATE parameter or the CREATE_REPLACE parameter. Reason code: reason-code.

Explanation

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

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

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

1

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

2

XML columns

3

Multidimensional clustered (MDC) tables

4

Table partitioning keys

5

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

6

Protected tables

7

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

8

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

9

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

10

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

11

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

12

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

13

Decimal floating-point columns

14

Hidden columns

15

Indexes with random ordering

16

Column-organized tables

17

Expression-based indexes

18

Indexes created with the BUSINESS_TIME WITHOUT OVERLAPS clause

19

Information about columns where STRINGUNITS has been specified as CODEUNITS32

20

BINARY or VARBINARY columns

21

Random distribution tables

User response

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

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

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

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

sqlcode: -3311

sqlstate: 5U058

SQL3313N The disk is full. Processing was ended.

Explanation

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

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

User response

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

SQL3314N The date and time fields in an A record do not match the date and time fields in the H record.

Explanation

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

The input file has probably been damaged.

The utility stops processing.

User response

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

SQL3315N The volume fields in an A record of subtype C are not valid.

Explanation

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

The input file has probably been damaged.

The utility stops processing.

User response

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

SQL3316N An I/O error occurred while closing part of the input file.

Explanation

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

The utility stops processing.

User response

Resubmit the command.

SQL3318N There are duplicate keywords in the filetmod parameter.

Explanation

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

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

User response

Resubmit the command with a correct filetmod parameter.

SQL3319N An SQL error sqlcode occurred while creating the table.

Explanation

An SQL error occurred while creating the table.

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

User response

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

SQL3320N There is no delimiter or decimal point character after a keyword in the filetmod parameter.

Explanation

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

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

User response

Resubmit the command with a correct filetmod parameter.

SQL3321C Data was not imported into the database because the log was full or the lock space was exhaused. Recovery was not successful. SQLCODE sqlcode was returned.

Explanation

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

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

User response

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

SQL3322N An operating system semaphore error occurred.

Explanation

An error occurred in the wait/post semaphores.

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

User response

Stop and restart the database manager and resubmit the utility.

SQL3324N Column name has a type of type which is not recognized.

Explanation

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

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

User response

Correct the error and retry the command.

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

SQL3326N The column list following the table name in the Action String parameter is invalid.

Explanation

When you call IMPORT or LOAD with an Action String (e.g. "REPLACE into ...") parameter which contains a column list after the table name, this message will result if it is invalid. For example, the following Action String parameters will fail:
insert into tablea()
no columns within the parenthesis
insert into tablea(two words)
invalid column name
insert into tablea(grant.col1)
column name should not be qualified
insert into tablea(x1234567890123456789)
column name too long
insert into tablea(,col1,col2)
missing column name

The command cannot continue.

User response

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

SQL3327N A system error occurred (reason code1 = reason-code-1 and reason code2 = reason-code-2).

Explanation

A system error occurred during processing.

The utility stops processing.

User response

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

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

SQL3330W In row row-number a character field has an odd length but its target database column is a graphic column. The row was not loaded.

Explanation

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

The row is not loaded.

User response

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

SQL3331C The permission setting of a file (or directory) does not allow the specified access.

Explanation

This may accompany another error message. It indicates an attempt was made to get access to a file or directory in a way that is incompatible with the attributes of the file. One of the following may be the source of the difficulty:
  • Opening a file for writing on a read-only device
  • Opening a file for writing on a read-only file
  • Opening a directory instead of a file
  • Encountering a locking or sharing violation.

The command cannot be processed.

User response

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

SQL3332C The maximum number of open files has been reached.

Explanation

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

The command cannot be processed.

User response

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

SQL3333C The file or directory does not exist.

Explanation

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

The command cannot be processed.

User response

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

SQL3334C There is not enough storage available.

Explanation

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

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.

SQL3335C The file system is full.

Explanation

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

The command cannot be processed.

User response

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

SQL3337N An I/O error occurred while writing data to the server.

Explanation

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

The utility stops processing. The database is unchanged.

User response

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

SQL3338N An I/O error occurred reading a temporary message file on the server.

Explanation

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

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

User response

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

SQL3340N Unable to perform a load with concurrent read access to the table. Reason code = reason-code.

Explanation

The ALLOW READ ACCESS option of the LOAD command is not supported in the following cases as specified in the reason-code:
  1. When using LOAD REPLACE.
  2. When using INDEXING MODE DEFERRED.
  3. When the target table is in the Set Integrity Pending state and is not in the Read Access only state.
  4. When the indexes are marked invalid.
  5. When using LOAD TERMINATE or LOAD RESTART on a load that did not use the ALLOW READ ACCESS option, or when temporary files from the original load are missing.

User response

Resubmit the command using the ALLOW NO ACCESS option.

SQL3341N Invalid table space name provided with the USE option. Reason code = reason-code.

Explanation

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

User response

Resubmit the command with a table space name referring to a system temporary table space with the correct page size. The reason-code describes the failure as follows:
  1. Table space name in USE clause not found.
  2. Table space must be a system temporary table space.
  3. Page size in system temporary table space must match page size in index table space.

SQL3342N The user ID has insufficient authority to use the LOCK WITH FORCE option.

Explanation

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

User response

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

SQL3343N Load restart not allowed after a rollforward through a failed load.

Explanation

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

User response

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

SQL3346N USE TablespaceName option ignored. Reason code = reason-code.

Explanation

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

User response

Refer to the reason code for an explanation.
  1. Indexing mode incompatible with USE TablespaceName option.
  2. Table has no indexes.
  3. LOAD TERMINATE does not need to use a separate table space.
  4. USE TablespaceName is only supported for ALLOW READ ACCESS loads.

SQL3400N The method specified in METHOD is not valid for Non-Delimited ASCII files. It must be 'L' for locations.

Explanation

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

The command cannot be processed.

User response

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

SQL3401N The method specified in METHOD is not valid for any filetype.

Explanation

The method for selecting columns in the file is not a value allowed for any filetype. Choose one of the following method indicators:
  • P for positions
  • N for names
  • L for locations
  • D for default

Further restrictions are based on filetype.

The command cannot be processed.

User response

Resubmit the command with a valid method indicator.

SQL3402N A beginning-ending location pair with both values zero was specified for non-nullable column name.

Explanation

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

The command cannot be processed.

User response

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

SQL3403N The beginning-ending location pair for inserting into column name is not valid. (begin end)

Explanation

The field specification for locating the input data for the indicated database column within the input non-delimited ASCII file is not valid. The field specification has one of the following errors:
  • The beginning location is less than zero.
  • The ending location is less than zero.
  • The ending location is less than the beginning location.

The command cannot be processed.

User response

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

SQL3404N The beginning-ending location pair for inserting into column name is not valid for a number.

Explanation

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

The command cannot be processed.

User response

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

SQL3405N The beginning-ending location pair for inserting into column name is not valid for a date.

Explanation

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

The command cannot be processed.

User response

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

SQL3406N The beginning-ending location pair for inserting into column name is not valid for a time.

Explanation

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

The command cannot be processed.

User response

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

SQL3407N The beginning-ending location pair for inserting into column name is not valid for a timestamp.

Explanation

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

The command cannot be processed.

User response

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

SQL3408W The beginning-ending location pair for inserting into column name defines a field larger than the target column. Data may be truncated.

Explanation

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

The utility continues processing. Truncation occurs when necessary.

User response

No action is required.

SQL3409W The beginning-ending location pair for inserting into column name defines a field shorter than the target fixed length column. Data will be padded.

Explanation

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

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

User response

No action is required.

SQL3410N The beginning-ending location pair for insert into column name is not valid for a graphic column.

Explanation

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

The command cannot be processed.

User response

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

SQL3411W The field value in row row-number and column column-number is not valid for a graphic column. A null was inserted.

Explanation

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

The row is not inserted.

User response

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

SQL3412W The field value in row row-number and column column-number is not valid for a graphic column but the target column is not nullable. The row was not inserted.

Explanation

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

The row is not inserted.

User response

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

SQL3413W The field value in row row-number and column column-number is too short for the target column. A null was inserted.

Explanation

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

A null value is inserted.

User response

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

SQL3414N The temporary file filename could not be found.

Explanation

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

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

The utility stops.

User response

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

SQL3415W Failed to convert the field value in row row-number and column column-number from the codepage of the input data file to the codepage of the database. A null value was loaded.

Explanation

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

User response

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

SQL3416W Failed to convert the field value in row row-number and column column-number from the codepage of the input data file to the codepage of the database. The row was not loaded.

Explanation

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

User response

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

SQL3417N A beginning-ending location pair pair-number is invalid for the codepage codepage.

Explanation

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

The command cannot be processed.

User response

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

SQL3418W The NOCHARDEL file type modifier should not be specified if the data was exported using DB2. It is provided to support vendor data files that do not have character delimiters.

Explanation

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

User response

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

SQL3419W The specified sort option is not supported by the vendor sort. The default DB2 sort will be used to continue with the operation.

Explanation

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

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

User response

No action required.