SQL2000-2999

SQL2000N

The input or output drive specified in the utility command does not exist.

The utility stops processing.

Resubmit the utility command with the correct drive specifier.

SQL2001N

The user may have pressed the interrupt key sequence, or had called the utility with a terminate caller action.

This message can also be returned during a backup or restore operation on a database node when the database catalog node is down.

The utility stops processing.

Restart the application or reissue the command, if needed. The output data from the interrupted command may be incomplete, and should not be used.

SQL2002N

The database utility command is only valid for local databases.

The utility stops processing.

Run the utility locally.

SQL2003C

An operating system error occurred. The return code can be found in the SQLERRD[0] field of the SQLCA.

The utility stops processing.

Look at the error return code in the SQLERRD[0] field of the SQLCA. Correct the error, if possible, and resubmit the command.

SQL2004N

The utility was using an SQL statement when an error occurred.

The utility stops processing.

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

SQL2005C

Incomplete data was read during an I/O operation.

The utility stops processing.

Determine if the I/O error can be corrected and resubmit the command.

SQL2006C

Incomplete data was written during an I/O operation.

The utility stops processing.

Determine if the I/O error can be corrected and resubmit the command.

SQL2007N

To backup a pagesize page size database object one needs a buffer larger than the page size. When backing up a database the data is first copied to an internal buffer. Data is then written from this buffer to the backup media when the buffer is full. The buffersize of buffersize 4K buffers that was specified is inadequate.

Use a larger buffersize.

SQL2008N

Each utility has its own list of valid callerac values.

This message can be returned for one of the following reasons:

• The callerac parameter value is not one of the acceptable values
• The requested action is out of sequence

Resubmit the command with a valid callerac parameter for the utility.

SQL2009C

This problem can occur in the following situations:

1. An attempt to backup or restore a database has failed due to insufficient space in the utility heap.
2. Utilities were left running during an online backup attempt.

To resolve all possible cases described in this message's Explanation, re-issue the command, invoking the autonomic mode by NOT specifying the following parameters:

  WITH num-buffers BUFFERS PARALLELISM n BUFFER buffer-size 

If you prefer to specify parameters explicitly, appropriate actions for each case are:

1. Increase the UTIL_HEAP_SZ database configuration parameter with the command: UPDATE DB CFG FOR <DBNAME> USING UTIL_HEAP_SZ <VALUE>. For backup and restore, this value must be at least as high as the number of buffers * buffer size.

   NOTE: If the database did not already exist when the RESTORE was attempted, create an empty database, increase its UTIL_HEAP_SZ as described above and retry the restore into the new database.

2. Retry the online backup after ensuring that utilities are not running.

SQL2010N

The utility could not connect to the database.

The utility stops processing.

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

SQL2011N

The utility could not disconnect from the database.

The utility stops processing.

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

SQL2012N

The utility could not enable interrupt handling. The actual return code can be found in the SQLERRD[0] field of the SQLCA.

The utility stops processing.

Look at the error return code in the SQLERRD[0] field of the SQLCA. Correct the error, if possible, and resubmit the command.

SQL2013N

An error occurred while the utility was accessing the database directory.

The utility stops processing.

If the path in the database parameter is not the database directory path, resubmit the command with the correct path. Otherwise, look at the error number in the message for more information. Make changes and resubmit the command.

SQL2014N

The utility received an error from a database environment command. The database manager configuration file and the database configuration file may contain incompatible values.

The utility stops processing.

Check the database manager configuration file and the database configuration file for inconsistent values. Resubmit the command.

SQL2015N

The database name is required. It must contain 1 to 8 characters and the characters must be chosen from the database manager base character set. The name must be located at a valid address for the application.

The utility stops processing.

Resubmit the command with a valid database name.

SQL2016C

The utility could not find the required program using the operating system Select Path.

The utility stops processing.

Update the PATH command to include the path to the indicated program name.

SQL2017N

The utility stops processing.

Wait until some of the current sessions stop processing and resubmit the command. Or, see the SQLERRD[0] field in the SQLCA for more information and resubmit the command.

SQL2018N

The utility stops processing.

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

SQL2019N

Because the current level of the utility being executed was not bound to the database, the system attempted to bind all utilities to the database, and this binding process failed. Possible causes for the error include the following situations:

• Insufficient disk space
• Too many open files, or a similar system resource problem
• A missing or invalid list of utility programs to be bound (db2ubind.lst)
• A missing or invalid bind file for one of the utilities (db2uxxxx.bnd)
• Insufficient authorization for binding utilities; the required privileges are BIND for the utility programs and SELECT for the system catalogs

For the RESTORE utility, the database is restored, but at least one utility is not bound to the database. The other utilities stop processing.

Complete all activities that might be competing for system resources, and resubmit the utility command. If the error continues, perform one of the following actions:

• Have a user with DBADM authority retry the command.
• Reinstall the database manager or reapply any recent updates or do both.
• Bind the utility programs (by binding the db2uxxxx.bnd files listed in the db2ubind.lst file) individually to the database (with no format option) to isolate the problem and possibly enable some utilities to operate successfully.

SQL2020N

All the utilities were rebound to the database because the utility was not bound to the database or the package of the utility that was bound to the database was not compatible with the installed version of the database manager, but there is still a timestamp conflict between the installed version of the database manager and the package so the utility and bind file are not compatible.

The utility stops processing.

Reinstall the database manager or reapply any recent updates or do both. Resubmit the utility command.

SQL2021N

The diskette to be used for Backup Database or for Restore Database is not in the drive or is not valid.

The command cannot be processed.

Verify that the correct diskette is in the drive or insert a new diskette.

SQL2023N

There are two log control files:

• Primary log control file SQLOGCTL1.LFH
• Secondary log control file SQLOGCTL2.LFH

  The secondary log control file is a mirror copy of the primary log control file for use in the event that there is a problem with the primary log control file.

The database manager received a read or write error while accessing the primary log control file.

The utility stops processing.

Record the error return code value. Determine whether the I/O error can be corrected.

SQL2024N

An I/O error occurred while accessing the specified file.

A file with the extension “.BRG” is used to determine whether a RESTORE operation has terminated abnormally. The file resides in the local database directory of the database for which the RESTORE operation was attempted.

A file with the extension “.BRI” stores information about the progress of an incremental RESTORE operation. The file resides in the local database directory of the database for which the RESTORE INCREMENTAL operation was attempted.

The file name consists of the database token concatenated with the file type extension. For example, if the database “SAMPLE” is assigned the database token “SQL00001”, the BRI file will have the name “instance/NODE0000/sqldbdir/SQL00001.BRI”.

The utility stops processing.

Record the error return code. Determine whether the I/O error can be corrected.

SQL2025N

An I/O error occurred while accessing a file on the specified media.

The utility or operation stopped processing.

If media is "TSM", there is a problem related to IBM Tivoli Storage Manager. A common TSM-related problem is time-out of a TSM session due to an inadequate COMMTIMEOUT setting.

1. Collect more information from the db2diag diagnostic log files by using the log analysis tool to search for the particular error code:

    db2diag -rc <RC> 

2. Respond to this error according to the type of media:
   • If media is TSM, refer to the full text of the IBM Tivoli Storage Manager API return code given in the error code, code.
   • For other media types, ensure that dir_or_devices is accessible and check for media errors. For example for media TAPE, ensure that the tape library is online. If you are attempting to backup to TAPE and you are using tape with variable block size, reduce the buffer size option to within the range that the tape device supports (the database manager automatically chooses an optimal value for this parameter if it is not specified).

SQL2026N

The internal disconnect command failed. The SQLCODE is returned in the message.

The utility stops processing.

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

SQL2027N

The internal connection failed. The SQLCODE is returned in the message. The database manager configuration file and the database configuration file may contain incompatible values.

The utility stops processing.

Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command. Check that the database manager configuration file values and the backup image's database configuration file values are compatible.

SQL2028N

The utility could not enable the interrupt handler. The SQLCODE is returned in the message.

The utility stops processing.

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

SQL2029N

An error was returned from either the specified command file, or from the operating system.

The user has either requested a Backup changes only of a database enabled for ROLLFORWARD recovery, or has requested a Backup changes only while requesting the use of the user exit.

SQL2030N

The specified drive does not have enough space for creating an internal subdirectory and information file.

The utility stops processing.

Free the indicated space on the specified drive and resubmit the command.

SQL2031W

A database utility process either writes data to or reads data from the media on the specified device. The utility returns so that the user may mount the correct media for the operation.

The utility waits for a response to continue.

Mount the media and return to the utility with the callerac parameter indicating if processing continues or ends.

SQL2032N

The parameter is incorrectly specified. Either the value is out of range or is incorrect.

Resubmit the command with a correct value for the parameter.

sqlcode: -2032

sqlstate: 22531

SQL2033N

Some common TSM reason codes are:

106

The specified file is being used by another process. You tried to read from or write to a file that is currently being used by another process.

137

TSM authentication failure.

168

Password file is needed, but user is not root. This message is often generated when the DSMI_DIR environment variable points to a directory that contains a 32-bit version of the dsmtca program, yet the database manager instance is 64-bit, or vice-versa.

400

An invalid option was specified on the OPTIONS parameter passed to TSM.

406

TSM Cannot find or read its options file.

The utility stops processing.

Responses for common TSM problems are:

106

Ensure that you specified the correct file or directory name, correct the permissions, or specify a new location.

137

If the TSM parameter PASSWORDACCESS is set to GENERATE, ensure that the system administrator has used the dsmapipw utility to set the password. If PASSWORDACCESS is set to PROMPT, ensure that the TSM_NODENAME and TSM_PASSWORD database configuration parameters have been set correctly.

168

Ensure that DSMI_DIR points to a directory containing the correct version of dsmtca, restart the instance, and execute the command again.

400

Ensure that the OPTIONS parameter specified on the BACKUP or RESTORE command is correct.

406

Ensure that the DSMI_CONFIG environment variable points to a valid TSM options file. Ensure that the instance owner has read access to the dsm.opt file. Ensure that the DSMI_CONFIG environment variable is set in the db2profile.

SQL2034N

The application program used an address that is not valid for this parameter. Either the address points to an unallocated buffer or the character string in the buffer does not have a null terminator.

Ensure that a valid address is used in the application program and the input string is null terminated.

SQL2035N

The calling application invoked the utility with no interrupt mode. During the operation a warning condition was encountered.

Resubmit the operation without specifying the no interrupt condition in the callerac parameter or take actions to prevent the warning and resubmit the operation.

SQL2036N

The application calling the utility has supplied a source or target path that is not valid. The path, file, named pipe, or device specified may not exist or is incorrectly specified.

Reissue the utility command with a path that represents a correct path or device.

SQL2037N

A call to a database utility specified TSM as the target or source of the backup. An attempt was made to load the TSM client. Either the TSM client is not available on the system or an error was encountered in the load procedure.

Ensure that the system has TSM available. Resubmit the command after TSM is made available, or resubmit the command without utilizing TSM.

SQL2038N

A database system error was encountered during the processing of one of the utilities.

1. Examine the error code in the message.
2. Review the diagnostic (db2diag) log files for more information.
3. Take corrective action.
4. If appropriate resubmit the command.

SQL2039N

The application calling the utility has terminated. The application side of the utility is in the same process as the calling application and terminates with the application. The agent side of the utility terminates as a result.

Reissue the command after determining why the application terminated.

SQL2040N

The application calling the Backup or Restore utility has supplied a database alias parameter that is not valid. The alias must be 1 to 8 bytes and the characters must be chosen from the database manager base character set.

Reissue the Backup or Restore command with a valid database alias.

SQL2041N

The application calling the utility has supplied a buffer size parameter that is not valid. The buffer size is used to determine the internal buffer size. The value is the number of 4K pages that are obtained for this buffer. The value must be specified as 0 or be between 8 and 16384 inclusive.

When running the backup or restore utility, if 0 is specified, the default buffer size defined in the database manager configuration is used.

If the target media is a diskette, the buffer size must be smaller than the diskette size.

SQL2042W

The application calling the utility has encountered an I/O error while trying to read or write to the tape device. The utility returns so that the user may correctly mount and position the tape.

The message may contain additional information to help diagnose the problem.

The utility waits for a response to continue.

Correctly mount and position the tape and return to the utility indicating if processing continues or ends.

The error, device and the additional information (if present) can be used to diagnose and correct the problem.

SQL2043N

Unable to start up the child processes or threads required during the processing of a database utility. There may not be enough available memory to create the new process or thread. The utility stops processing.

Ensure the system limit for number of processes or threads has not been reached (either increase the limit or reduce the number of processes or threads already running). Ensure that there is sufficient memory for the new process or thread. Resubmit the utility command.

SQL2044N

An unexpected error or bad message was received on one of the operating system message queues during the processing of a database utility.

The reason code indicates more specifically what the problem was:

1

Unable to create a message queue. This message can be returned with reason code 1 when the number of message queues allowed has been exceeded.

2

An error was encountered while reading from a message queue.

3

An error was encountered while writing to a message queue.

4

An invalid message was received from a message queue.

5

An error was encountered while opening a message queue.

6

An error was encountered while closing a message queue.

7

An error was encountered while querying a message queue.

8

An error was encountered while deleting a message queue.

Respond to this message in one or more of the following ways:

• Monitor message queue use by running the ipcs operating system command to see a list of message queues, their identifier, and their owner.
• Use fewer message queues. For example: use more, smaller IPX files with the EXPORT utility.
• Raise the message queue limits by setting operating system configuration parameters.

SQL2045W

A database utility process encountered error error returned by the operating system while writing to the media media. The utility returns so that the user may attempt to fix the problem or cancel the operation.

The utility waits for a response to continue.

Consult the troubleshooting documentation for your operating system and correct the error condition. Return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL2046N

The cluster caching facility (CF) is an instance-level designation that provides several services that are key to the operation of a DB2 pureScale environment. The CF structure contains information about elements of the DB2 pureScale instance, including information about each database in the DB2 pureScale instance.

The CF structure memory parameters are configurable online and accept resize requests during runtime. Resize requests for structure memory parameters such as CF_GBP_SZ, CF_SCA_SZ, and CF_LOCK_SZ are collectively bound by the memory limit set for CF_DB_MEM_SZ.

An update operation for a structure memory parameter must be completed within a time limit. This message is returned when the operation has exceeded that time limit. The operation has not completed.

View the total memory allocated for the CF structures using the GET DB CFG command with the SHOW DETAIL clause. Together, the structure memory parameters cannot exceed the value of the parameter CF_DB_MEM_SZ.

Set the value of parameter-name to a value that adheres to the relationships defined between all CF structure memory parameters, as recommended in the documentation.

sqlcode: -2046

sqlstate: 5U050

SQL2047N

The cluster caching facility (CF) is an instance-level designation that provides several services that are key to the operation of a DB2 pureScale environment. Structures within the CF contain elements that are critical to the operation of each database in a DB2 pureScale instance.

Overall CF memory is limited by the database manager configuration parameter named CF_MEM_SZ.

CF memory available for each database is limited by the database configuration parameter named CF_DB_MEM_SZ. Note CF_DB_MEM_SZ is an upper limit only and its memory is not reserved.

The available CF memory can be consumed by other active databases (if supported) or for internal CF purposes.

This message is returned when an attempt is made to set parameter-name to a value that exceeds the amount of memory that is available for CF_MEM_SZ or CF_DB_MEM_SZ.

View the total memory available for the CF structures using the GET DB CFG command with the SHOW DETAIL clause. The parameter that indicates the amount of memory available for the entire CF is named CF_MEM_SZ. The parameter that indicates the amount of memory available for all CF structures is named CF_DB_MEM_SZ.

Set the value of parameter-name to a smaller value.

sqlcode: -2047

sqlstate: 5U051

SQL2048N

An error occurred while accessing an object during the processing of a database utility. The following is a list of reason codes:

1

An invalid object type is encountered.

2

A lock object operation failed. The lock wait may have reached the lock timeout limit specified in the database configuration.

3

An unlock object operation failed during the processing of a database utility.

4

Access to an object failed.

5

An object in the database is corrupted.

6

This message is returned with reason code 6 when a table space cannot be accessed for one of multiple reasons, including the following reasons:

• The state of the table space does not support the type of access attempt. Some examples of database states that can prevent some types of database access include: quiesced, offline, and backup in progress.
• One or more of the table space containers are not available.

For example, this message can be returned with reason code 6 when an attempt is made to back up a table space that is already in the processes of being backed up.

7

A delete object operation failed.

8

Trying to load/quiesce into a table that is not defined on this partition.

9

The BACKUP utility encountered an end-of-file in an unexpected place while processing an object. This does not necessarily mean that the data is corrupt, but the BACKUP utility is not able to process the data in its current state.

The utility stops processing.

1

Ensure that object is of valid type.

2

Increase the locktimeout database configuration parameter.

3

Check that there are not any issues while locking object, then retry the operation.

4, 7

Check that object exists and is accessible. Ensure that you have correct privileges/permissions to access it.

5

If object is db2rhist.asc, make sure that the db2rhist file is accessible by the instance owner. If permissions are set correctly, the db2rhist file may be corrupt. Move the existing file from its existing location, or delete it. The database manager will create a new db2rhist file the next time it needs to access it. Note: deleting the db2rhist file will cause historical information in the db2rhist file to be lost.

If object is any other database control file, you may need to recover the database.

6

Determine the current state of the table space using the MON_GET_TABLESPACE table function and then perform the following troubleshooting steps:

• If the table space is offline, attempt to determine the underlying problem and correct it. For example:
  • If the file system is not mounted, mount the file system, and then bring the table space online.
  • If table space files have been deleted, perform a restore operation.
• If the table space is quiesced, make the table space available using the QUIESCE TABLESPACES FOR TABLE command with either the RESET clause or the EXCLUSIVE clause. Note that the userid holding the quiesce might be needed to perform the QUIESCE RESET or QUIESCE EXCLUSIVE operation.
• If the table space is in the process of being backed up, wait for the backup operation to complete.

8

Ensure that you specify an appropriate table.

9

Perform a REORG operation on the specified table, and resubmit the BACKUP command.

SQL2049N

During database activation, the database manager allocates memory for the structures inside the cluster caching facility (CF) as determined by database manager configuration parameters, database configuration parameters, and DB2 registry variables, including the following parameters and variables:

• CF_GBP_SZ
• CF_SCA_SZ
• CF_LOCK_SZ
• CF_DB_MEM_SZ
• NUMDB
• DB2_DATABASE_CF_MEMORY

Note that use of the DB2_DATABASE_CF_MEMORY registry variable must be coordinated with the CF_DB_MEM_SZ database configuration parameter and the NUMDB database manager configuration parameter.

Example

If there are four databases to be active at once, then the configuration parameters should be coordinated like this:

• The database manager configuration parameter NUMDB should be set to at least 4.
• If the database configuration parameter CF_DB_MEM_SZ is set to AUTOMATIC for each of the four databases, then the registry variable DB2_DATABASE_CF_MEMORY should be set to reflect the percentage of CF memory to be allocated to each database, which would be 25 in this example.

This message is returned when there is not enough memory allocated for the CF to accommodate the memory allocations for the structures inside the CF for one or more databases.

The reason code indicates which aspect of the CF memory allocation was the problem:

1

The Group Buffer Pool (GBP).

2

The Shared Communication Area (SCA).

3

The Global Lock Manager (LOCK).

4

The total CF memory required for this database.

5

The percentage of total CF memory assigned for this database.

Respond to this message in one or more of the following ways:

General:

• Increase the overall CF memory size by setting a larger value for CF_MEM_SZ
• Use the AUTOMATIC setting for each CF structure configuration parameter and have DB2 calculate appropriate values for these parameters

For reason codes 1 - 4:

• Reduce the individual CF structure configuration parameters depending on the reason code:

  1

  The CF_GBP_SZ database configuration parameter

  2

  The CF_SCA_SZ database configuration parameter

  3

  The CF_LOCK_SZ database configuration parameter

  4

  The CF_DB_MEM_SZ database configuration parameter

For reason codes 4 and 5:

• Determine the amount of CF memory used by other databases and see if any settings need to be changed in order to accommodate the CF memory requirements of this database.

SQL2051N

This message is returned when the database manager detects problems that interfere with communications between a DB2 member and cluster caching facility (CF).

The nature of the communication problem is indicated by the reason code:

1

The error occurred or was detected in RDMA Library.

2

The error occurred or was detected in the sockets layer.

3

The nature of the error could not be determined.

Refer to the troubleshooting documentation.

SQL2052N

In a DB2 pureScale environment, when you perform a backup operation from a DB2 member, the backup utility must collect recovery metadata for all other DB2 members in the instance. This message is returned when the backup utility cannot collect the metadata information for one or more members. The backup utility might be unable to carry out the serialization that is necessary to process the metadata.

1. Check the db2diag log files for any communication or I/O errors that are associated with the backup agent or the logger EDU. Correct the errors and run the backup operation again.
2. If the backup operation continues to fail, perform the following steps:
   1. Resolve the reason for which the backup utility was unable to collect metadata information.
   2. Run the backup operation again.

sqlcode: -2052

sqlstate: 5U055

SQL2054N

The backup or copy image in use is corrupted

This can also mean that the Restore utility determined that a compressed image was not decompressed correctly.

The utility stops processing.

Discard the image as it is not a valid image. Resubmit the utility command with a valid image.

SQL2055N

A database utility was unable to access memory during processing.

The utility stops processing.

Stop the database manager, then restart it and resubmit the utility command.

SQL2056N

An invalid media type was encountered during the processing of a database utility.

The utility stops processing.

Ensure the media used is among of the types supported by the utility. Resubmit the command with a valid media list.

SQL2057N

The source or target media specified during the processing of a database utility is already open by another process. The utility does not allow shared access for the operation.

The utility stops processing.

Ensure the media used is not in use currently. Resubmit the command with a valid media list.

SQL2058W

An end-of-media warning was encountered during the processing of a database utility. This error can also occur if an invalid tape device block size was specified.

The utility is waiting for a response to continue.

Correct the end-of-media condition and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

The tape device block size (or blocking factor) used at restore time must be the same as that used during the backup. If a variable block size is used, then the buffer size used must be less than or equal to the maximum block size of the tape device.

SQL2059W

An device full warning was encountered during the processing of a database utility.

The utility is waiting for a response to continue.

Correct the device full condition and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL2060W

An empty device was encountered during the processing of a database utility. The utility is waiting for a response to continue.

Mount the media and return to the utility with the caller action parameter to indicate if processing should continue or terminate.

SQL2061N

An attempt to access a device, file, named pipe, TSM or the vendor shared library is denied during the processing of a database utility. The utility stops processing.

Ensure the device, file, named pipe, TSM or vendor shared library used by the utility allows the access requested and resubmit the utility command.

SQL2062N

Other reason codes refer to vendor api codes.

The utility stops processing.

Ensure the device, file, or vendor shared library used by the utility is available and resubmit the utility command. If the command is still unsuccessful, contact your technical service representative.

For other reason codes, consult the appropriate vendor documentation for further details on the code.

SQL2065W

The caller action specified is not allowed because there is only one device left connected to the database utility.

Return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL2066N

The table space name specified is syntactically correct, but it does not exist in the database or cannot be used in the specified utility operation.

A table space might be disallowed for many reasons, including the following examples:

• If the utility in use is a backup operation, the table space might be disallowed because it is a system or user temporary table space or is in an inconsistent state.
• If the utility in use is a restore operation, the table space might be disallowed because another restore operation or a rollforward operation of the table space is already in progress.
• If the utility is a rollforward operation, the table space might be disallowed because a restore of the table space is already in progress.

Resubmit the utility command, specifying a valid table space.

SQL2068N

An invalid image was encountered during the processing of a database utility. The utility was not able to locate a valid media header. The utility stops processing.

Resubmit the command with correct backup or copy images.

SQL2069N

An invalid image was encountered during the processing of a database utility. The image provided was from a different database alias. The utility stops processing.

Resubmit the command with correct backup or copy images.

SQL2070N

An invalid image was encountered during the processing of a database utility. The image provided was from a backup or copy with a different timestamp. The utility stops processing.

Resubmit the command with correct backup or copy images.

SQL2071N

An unexpected error occurred while accessing a vendor shared library during the processing of a database utility.

The reason code indicates more specifically the nature of the problem:

1

An invalid shared library path was encountered.

2

The library could not be loaded because it (or a library required by it) does not exist or does not have a valid format. This sometimes means that a 32-bit library is being loaded in a 64-bit instance, or a 64-bit library is being loaded in a 32-bit instance.

3

An error was encountered while unloading the shared library.

Responses by reason code:

1

Specify a correct path in the restore or backup command. Make sure the path is valid and contains the correct shared library.

2

Ensure that you are specifying the correct library. If your system can run 32-bit and 64-bit binaries, ensure that you are instructing the DB2 utility to load a library of the right format.

If the failure occurs while using TSM, verify that the TSM API Client is properly installed.

See the db2diag log file for more information.

3

Ensure that version of TSM client being used is compatible with your database manager instance.

SQL2072N

An error was encountered while binding the shared library during the processing of a database utility. The utility stops processing.

Note the reason code returned from the vendor utility in the message and take corrective action if possible. Resubmit the command with a valid shared library or using another supported media.

SQL2073N

An unexpected error occurred while processing DATALINK values.

Resubmit the command. If the problem still exists, resubmit the command after shutdown and restart of the database manager and the DB2 Data Links Managers.

The Restore utility can avoid DATALINK processing by specifying WITHOUT DATALINK.

SQL2074N

An unexpected error occurred while processing DATALINK values.

Resubmit the command. If the problem still exists, resubmit the command after shutdown and restart of DB2.

The Restore utility can avoid DATALINK processing by specifying WITHOUT DATALINK.

SQL2075N

An unexpected error occurred while processing DATALINK values.

Resubmit the command. If the problem still exists, resubmit the command after shutdown and restart of the DB2 Data Links Managers.

The Restore utility can avoid DATALINK processing by specifying WITHOUT DATALINK.

SQL2076W

The DB2 Data Links Manager server-name was not registered to the database with the ADD DATALINKS MANAGER command.

For details on why the ADD DATALINKS MANAGER command failed, check the administration notification log.

SQL2077W

Some or all of the Data Links Managers referred to in the table data were not available during reconcile processing. Reconcile processing completed successfully on Data Links Managers that were available. The table is placed in DataLink Reconcile Pending (DRP) state, because reconcile processing is pending on Data Links Managers that were not available.

The table will be taken out of DataLink Reconcile Pending state when reconcile is completed successfully on all Data Links Managers referred to in the table data. Bring up the Data Links Managers that were not available and run reconcile again.

SQL2078N

SQL2079N

An error was reported from a vendor shared library during the processing of a database utility. The return code displayed corresponds to one of the valid vendor API return codes. The utility stops processing.

Possible API return codes are:

3

The database product and vendor products are incompatible.

4

An invalid action was requested.

8

An invalid userid was specified.

9

An invalid password was provided.

10

Invalid options were specified.

12

An invalid device handle was provided.

13

An invalid buffer size was specified.

30

A severe error was experienced inside the vendor product.

other

A specific severe error returned by the vendor product.

Ensure the shared library provided is valid. Attempt to make the necessary corrective actions based on the vendor API return code and the corresponding db2diag log file entry and resubmit the utility command.

SQL2080N

A snapshot backup enables you to use fast copying technologies for the data copying and movement parts of backup and restore operations.

A snapshot backup was attempted on a database. However, the snapshot backup utilities were unable to uniquely identify all of the elements of the database that are required to be copied because there are one or more other databases cataloged in the same volume directory as the database being backed up.

If other databases are cataloged in the same volume directory as a database against which you are trying to run snapshot backup, the backup image might include files from databases other than the one you are trying to back up. If a backup image contains files from multiple databases, you can not successfully use that image to restore any of those databases.

You can only run a snapshot backup or restore on a database that is unique in its volume directory.

The snapshot backup failed.

To perform a snapshot backup on a database in a given volume directory that contains multiple databases:

• Drop or move any other databases in the target volume directory.
• Run the BACKUP command again.

SQL2081N

A snapshot backup enables you to use fast copying technologies for the data copying and movement parts of DB2 database backup and restore operations.

A restore of a database was attempted from a snapshot backup image. However, the snapshot restore utilities were unable to uniquely identify all of the elements of the database that are required to be copied for the reason indicated by the reason-code:

1

There are one or more other databases cataloged in the target volume directory.

If another database exists in the target volume directory, the restore will replace the volume directory, causing the existing database to become uncataloged.

2

The complete database directory in the backup image cannot be created on disk during restore because some portion of the database directory in the backup image is being used by another database.

For example, when you create a database, the database server creates a directory hierarchy to store metadata for that database: a directory is created with the name of the database manager instance; below this, there might be directories for database partitions; and below these are directories named using database tokens such as SQL00001 for the first database created, SQL00002 for the second database created, and so on.

You can not restore a snapshot backup image that contains directories named SQL00001, SQL00002, or similar if there exist directories on the target volume directory with the same names.

3

The log directories to be restored from the backup image already exist on disk and are not empty.

If the log directories to be restored from the backup image already exist on disk and contain data, the database manager will not restore these directories otherwise data could be unexpectedly overwritten.

The snapshot restore failed.

To restore a database from a snapshot backup image to a given target volume directory that contains multiple databases, drop or move any other databases in the target volume directory.

To ensure that log directories from a snapshot backup image can be restored, verify that the log directories either do not exist on disk or are empty. Run the RESTORE command again.

SQL2084N

There is already a work action set defined for the following specified database, workload, or service superclass: db-or-ssc-name. Only one work action set can be defined for any one database, workload, or service superclass at any given time.

1. Do one of the following:
   • Specify a different database, workload, or service superclass.
   • Drop the work action set currently defined for the database, workload, or service superclass.
2. Issue the request again.

sqlcode: -2084

sqlstate: 5U017

SQL2085N

The default service subclass cannot be specified when defining a work action to map activities.

Specify a different service subclass that is not the default service subclass and try the request again.

sqlcode: -2085

sqlstate: 5U018

SQL2086N

The value specified either for the FROM parameter or the TO parameter is not valid. The FROM value must be zero or a positive double-precision value and the TO value must either be a positive double-precision value or UNBOUNDED, to specify no upper bound. If the TO value is not UNBOUNDED, it must be greater than or equal to the FROM value.

Specify a valid value for both the FROM value and the TO value and try the request again.

SQL2089N

The ALTER WORKLOAD statement would have resulted in the last connection attribute being dropped from the workload workload-name, This operation is not allowed. There must be at least one connection attribute specified in the definition of the workload.

Ensure that the ALTER WORKLOAD statement leaves at least one connection attribute in the definition of the workload.

sqlcode: -2089

sqlstate: 5U022

SQL2090N

An attempt to drop workload workload-name has failed, for one of the following reasons.

• The workload has not been disabled.
• The workload has active workload occurrences.
• A threshold is associated with the workload.
• A work action set is associated with the workload.

Do one of the following:

• If the workload is not yet disabled, issue the ALTER WORKLOAD statement to disable the workload and keep new workload occurrences from becoming active.
• Wait until there are no more active workload occurrences running on the system and then issue the DROP statement to drop the workload.
• If a threshold is associated with the workload, issue the DROP THRESHOLD statement to drop the associated threshold.
• If a work action set is associated with the workload, issue the DROP WORK ACTION SET statement to drop the associated work action set.

sqlcode: -2090

sqlstate: 5U023

SQL2091N

A request has been made to rebalance a table space that has containers on one or more storage paths that are being dropped. The data server will drop these containers as part of the rebalance operation. However, the table space must have sufficient space on its remaining paths to accommodate the data moved from the dropped containers. The data server automatically extends existing containers and creates new containers on the remaining paths as necessary, but the remaining paths do not contain enough available storage to house the data to be moved.

For every table space that you intend to rebalance in this way, determine the number and size of containers that are to be dropped to obtain an estimate of the amount of data that is being moved to the remaining storage paths. At a minimum, the rebalance operation (or operations) requires this amount of free space to succeed. Either increase the amount of free space on the remaining storage paths, or add new storage paths to the database.

sqlcode: -2091

sqlstate: 57011

SQL2092N

One or more of the storage paths are already in the drop pending state.

Remove the storage paths that are in the drop pending state from the ALTER DATABASE statement or the ALTER STOGROUP statement. Then try the request again.

sqlcode: -2092

sqlstate: 55073

SQL2093N

A storage group must have at least one storage path associated with it. The ALTER STOGROUP statement is attempting to drop all of the storage paths for the storage group (or the remaining paths that are not already in the drop pending state).

Modify the ALTER STOGROUP statement so that at least one of the storage paths is not dropped. If all of the storage paths must be dropped, modify the ALTER STOGROUP statement to add one or more new storage paths at the same time. The new storage paths must have enough free space to accommodate the movement of containers and data from the paths being dropped.

sqlcode: -2093

sqlstate: 428HH

SQL2094W

A rebalance operation attempts to drop containers from storage paths in the "drop pending" state, and to create new containers on recently added storage paths. The operation also tries to create containers for stripe sets that do not already include all of the database storage paths. This warning occurred on one or more database partitions as a result of one of the following reason codes:

1

No containers need to be added or dropped.

2

No containers need to be dropped, but some stripe sets in the table space do not contain containers for every storage path. However, the storage paths do not have enough disk space for any of the new containers or the table space has reached its maximum size.

3

No containers need to be dropped, but some stripe sets in the table space do not contain containers for every storage path. Some containers could not be created because some storage paths do not have enough disk space, or the table space has reached its maximum size. The new containers will be added to the table space and the data will be rebalanced.

4

Some containers need to be dropped and some stripe sets in the table space do not contain containers for every storage path. However, the corresponding storage paths do not have enough disk space for any of the containers to be created. The containers on the "drop pending" storage paths will be dropped and the data will be rebalanced.

5

Some containers need to be dropped and some stripe sets in the table space do not contain containers for every storage path. Sufficient disk space exists to create some of these containers, but not all. Containers in the "dropped pending" storage paths will be dropped and new containers will be added as needed to stripe sets. The data will be rebalanced.

1

No rebalance is necessary.

2

Increase the amount of free space on the storage paths that are full or increase the maximum allowable size of the table space. Then try the request again.

3

Wait for the current rebalance to complete. Then, increase the amount of free space on the storage paths that are full or increase the maximum allowable size of the table space. Then try the request again.

4

Wait for the current rebalance to complete. Then increase the amount of free space on the storage paths that are full and try the request again.

5

Wait for the current rebalance to complete. Then increase the amount of free space on the storage paths that are full and try the request again.

To increase the amount of free space on a storage path either increase the size of the file system or delete non-database data.

sqlcode: +2094

sqlstate: 01690

SQL2095W

A request has been made to drop storage path storage-path from the database. Because one or more automatic storage table spaces have containers on this storage path, it cannot be removed immediately and is in the drop pending state. A storage path cannot be removed until all containers on it have been removed.

If more than one storage path is being dropped, this message might also apply to the other storage paths.

Perform one or more of the following tasks to remove containers from the storage path:

• Drop all automatic storage temporary table spaces. Then, recreate these table spaces. The newly created table spaces will not use the drop pending storage paths.
• Use the REBALANCE clause of the ALTER TABLESPACE statement to move data and containers from storage paths that are being dropped.
• Drop table spaces that you do not need.

sqlcode: +2095

sqlstate: 01691

SQL2096N

An attempt to drop threshold threshold-name failed. The threshold is not disabled, the threshold queue is not empty, or an activity is running under the control of the threshold.

If the threshold is not yet disabled, disable it. If the threshold is part of a work action set, you must use the ALTER WORK ACTION SET statement to disable it. If the threshold is not part of a work action set, use the ALTER THRESHOLD statement to disable it. Disabling the threshold prevents new requests from running under the control of the threshold. If the concurrency limit for a queueing threshold has been reached, the DISABLE action prevents new requests from joining the queue. Wait until the currently executing request completes or no more requests are in the queue, then issue the DROP THRESHOLD statement again.

sqlcode: -2096

sqlstate: 5U025

SQL2097N

The routine WLM_REMAP_ACTIVITY failed because one or more of the input parameters is not valid. The reason codes are as follows:

1

The activity can be remapped only to a service subclass under the service superclass of the activity. Specify the service superclass name of the activity in the service_superclass_name parameter or set it to null. Setting the service_superclass_name parameter to null defaults the input parameter to the current service superclass name of the activity.

2

A valid service subclass under the service superclass of the activity must be specified in the service_subclass_name parameter.

3

Specify Y in the log_evmon_record parameter to log an event monitor record to the THRESHOLD VIOLATIONS event monitor when the activity is remapped on a partition. Specify N in the log_evmon_record parameter to prevent logging an event monitor record to the THRESHOLD VIOLATION event monitor when the activity is remapped on a partition.

Ensure that the condition in the reason code is satisfied and reinvoke the WLM_REMAP_ACTIVITY routine.

sqlcode: -2097

sqlstate: 5U046

SQL2098N

The requested operation is not compatible with the transport operation. The following reason code indicates the error:

1

Storage paths cannot be altered when they are being accessed by the transport operation. This conflict can occur when the transport operation is adding or dropping storage paths on the staging database, or when dropping storage paths on the target database.

2

The requested operation cannot be performed on a table space that does not have containers and is unusable.

3

The table space name is reserved for the transport operation.

Based on the reason code, perform the following actions:

1

Wait until schema transport completes, then re-issue the ALTER STORAGE PATH command.

2

Drop the unusable table space. Do not perform the operation on the unusable table space.

3

Specify a different table space name.

SQL2101N

You can use the SYSPROC.ADMIN_MOVE_TABLE procedure to move data from one table space to a another table space. For example, you can migrate that data to a new table space using this procedure. The reason this error was returned is indicated by the reason code:

1

The DB2_SKIPDELETED registry variable is enabled. Prior to DB2 Version 9.7 Fix Pack 2, an online admin move table operation cannot be performed if the DB2_SKIPDELETED registry variable is enabled.

26

The protocol table SYSTOOLS.ADMIN_MOVE_TABLE was not created by this procedure and therefore cannot be used.

First, respond according to the given reason code:

1

Disable the DB2_SKIPDELETED registry variable.

26

Delete the table SYSTOOLS.ADMIN_MOVE_TABLE.

Then, call the ADMIN_MOVE_TABLE procedure again.

sqlcode: -2101

sqlstate: 5UA0M

SQL2102N

You can use the SYSPROC.ADMIN_MOVE_TABLE procedure to move data from one table space to a another table space. For example, you can migrate that data to a new table space using this procedure. The reason this error was returned is indicated by the reason code:

12

An unexpected internal error has occurred.

13

Load was used as the copy option, and the FORCE option was not set during the swap phase.

18

The procedure attempted to create an index on the table but could not do so because the table only contains columns that cannot be specified as part of an index.

19

Some rows in the staging table could not be processed during the replay phase because too many locks are active on the staging table.

22

An error occurred or rows were rejected when the target table was being loaded.

28

An error occurred while copying statistics from the source table to the target table.

31

The CLUSTER and NON_CLUSTER options are incompatible with each other.

32

The KEEP option is not supported for system-period temporal tables.

33

The maximum number of retries was exceeded when trying to acquire a semaphore.

Respond according to the given reason code:

12

To report this unexpected result, contact your DB2 service representative and provide the db2diag log file and the contents of the diagnostic directory path (as specified by the DIAGPATH database manager configuration parameter).

13

The load operation is non-recoverable. Use the FORCE option, along with COPY_USE_LOAD, so that you are aware of this fact and can create a backup image.

18

Create a column on the table that can be specified as part of an index before attempting to move this table.

19

Retry the operation when there is less insert, update, or delete activity occurring on the table.

22

See the db2load output file in the db2diag log directory and correct any errors or data that is causing the target table from being loaded successfully.

28

Statistics cannot be copied; retry the operation specifying the NO_STATS or NEW_STATS option.

31

The CLUSTER and NON_CLUSTER options cannot be specified at the same time. Choose only one to specify, or none if the default behavior is desired.

32

Retry the ADMIN_MOVE_TABLE SWAP operation without the KEEP option.

33

Wait until the conflicting move operation that is currently in progress releases the semaphore.

sqlcode: -2102

sqlstate: 5UA0M

SQL2103N

You can move data from one table space to a another table space by using the SYSPROC.ADMIN_MOVE_TABLE procedure.

This message is returned when the ADMIN_MOVE_TABLE procedure cannot operate on the source table or the target table for the reason indicated by the reason code:

6

The source table type is not supported or the table includes features that are not supported with the ADMIN_MOVE_TABLE procedure.

7

The verification operation has found differences between the tables. Either the number of rows or the values for the columns are not consistent between the two tables.

14

The source table is the target of an active event monitor and cannot be moved.

16

The alterable table flags or indexes in the source and target table are not in synchrony.

17

Column definitions or indexes differ when they should be the same.

20

The specified target table is not supported or referential constraints are defined on the table.

21

The specified target table is not empty.

33

A system-period temporal table or an application-period temporal table cannot be specified as a target table.

Respond according to the given reason code:

6

Change the type of the table to one that is supported. Remove any table features that are not supported with the ADMIN_MOVE_TABLE stored procedure.

7

Start the online move table operation again, which should fix the error in the protocol table.

14

Disable the event monitor before attempting to move the table.

16

Retry the swap phase in order to correct the differences with the alterable table flags or indexes between the source and target table.

17

Alter the column definition and index definition to be the same on the source table and target table.

20

Take one of the following actions:

• Change the target table so the table is supported.
• Specify a different, supported target table.
• Remove the reference constraints.

21

Specify a target table that is empty or delete all entries in the target table and retry the operation.

33

Specify a table that is not a system-period temporal table or an application-period temporal table as the target table.

sqlcode: -2103

sqlstate: 5UA0M

SQL2104N

You can use the SYSPROC.ADMIN_MOVE_TABLE procedure to move data from one table space to a another table space. For example, you can migrate that data to a new automatic storage table space using this procedure. The state of a database object or status of an operation conflicts with the attempted move table operation. The reason this error was returned is indicated by the reason code:

4

The status of the online move table operation does not allow the specified operation.

8

No online move table operation is in progress; therefore, the specified operation is not allowed.

9

An online move table operation is in progress; a parallel online table move operation on the same table is not allowed.

15

The table is the target table, staging table, or protocol table of an online table move operation and therefore cannot be moved.

29

An inplace reorganization operation is in progress which does not allow the copy phase of the online move table to take place.

Respond according to the given reason code:

4

Specify an appropriate operation for the current status of the online move table operation. The status of a move table operation can be checked using the following query:

 SELECT * FROM SYSTOOLS.ADMIN_MOVE_TABLE WHERE KEY='STATUS' AND TABNAME='<TABLE-NAME>'; 

8

Specify an operation that is allowed.

9

Wait until the conflicting online table move operation has completed.

15

Wait until the online table move operation is completed.

29

Wait until the inplace reorganization operation has completed.

sqlcode: -2104

sqlstate: 5UA0M

SQL2105N

You can use the SYSPROC.ADMIN_MOVE_TABLE procedure to move data from one table space to a another table space. For example, you can migrate that data to a new automatic storage table space using this procedure. The ADMIN_MOVE_TABLE procedure requires certain information or objects to exist before it can run successfully. The reason code indicates what was not satisfied:

10

Index information cannot be found in the protocol table.

11

Expected data cannot be found in the protocol table.

23

The column could not be dropped as specified because a unique index must exist before a column can be dropped. The column that is to be dropped cannot exist in that unique index.

24

A table space for regular data, large object (LOB) data, or indexes was specified but not all three of these table spaces were specified.

25

A table with a LONG, LOB, structured type, or XML column was specified to be moved but a unique index (excluding unique indexes that include an XML column) is not defined on that table.

30

The column could not be added as specified because any column that is being added and defined as NOT NULL must have a DEFAULT value specified.

Respond according to the given reason code:

10

Start the online move table operation again, which should fix the error in the protocol table.

11

Start the online move table operation again, which should fix the error in the protocol table.

23

Create a new unique index for the table, remove the column that is to be dropped from the unique index, or do not attempt to drop the column and retry the online move table operation.

24

Specify all three table space parameters (regular data, large object data, and index) or none of these parameters.

25

Create a unique index on the table, or do not attempt to move the table.

30

Specify a DEFAULT value for any added column that is defined as NOT NULL.

sqlcode: -2105

sqlstate: 5UA0M

SQL2150W

A RESTORE DATABASE command was issued. The user might have indicated that only a subset of the table spaces in the backup image were to be recovered.

No action is required.

SQL2154N

For table space restore, the backup must have been taken during the current log sequence of the database. The log file sequence is determined by the database that has been restored previously or the log files that have been processed. In addition, the backup must have been taken after the last time the database was enabled for roll forward recovery.

Table space restore has stopped.

Resubmit the command with a correct backup image.

SQL2155W

Changes have been made to the recovery history file since the file was open for a scan. The data read may not be consistent.

If it is essential to have consistent data from the scan, close the recovery history file and resubmit the command.

SQL2157N

Eight recovery history file scans in this process are already open. No more than eight open scans are allowed.

The command cannot be processed.

Issue one or more CLOSE RECOVERY HISTORY FILE SCAN commands and resubmit the command.

SQL2160W

An error was encountered during an access to the recovery history file. The utility is able to recover the file from an alternate copy. The utility continues processing.

The utility continues processing successfully. The user should take appropriate precautions to ensure the recovery history file is not damaged again.

SQL2161N

An error was encountered during an access to the recovery history file. The utility is not able to recover the file. The utility stops processing.

To continue processing, the user may remove the recovery history file and resubmit the command. The utility will regenerate a new file. Any data from the corrupted file are lost. The user may look at the corrupted file to see if any information can be saved. The user should take appropriate precautions to ensure the recovery history file is not damaged again.

SQL2162N

The database manager cannot access the specified log file because of the file permission settings. Recovery (rollforward or crash recovery) cannot continue.

Check the file system where the log files are stored. Ensure that sufficient permission has been given to the instance owner to access these log files, and attempt the recovery operation again.

SQL2163N

The database manager is unable to locate a backup image in the Recovery History File to recover the database to the given point in time. This error may occur when the History File has been pruned.

Try specifying a later point in time. If end of logs is specified, ensure that the History File includes a record of backup events.

SQL2164N

The recovery history file specified for the RECOVER command was not found.

Verify the file name and resubmit the command.

SQL2165W

The value of the iNumTablespaces field in db2HistoryData is less than the number of table spaces in the history file record being fetched. The table space data has been truncated to the value of iNumTablespaces.

Increase the memory allocation of poTablespace to allow for more table spaces, and update the value of iNumTablespaces to the corresponding higher number. The number of table spaces that is represented by the value of the oMaxTablespaces field in the db2HistoryOpenStruct data structure (returned by the db2HistoryOpenScan API) is guaranteed to be sufficient to read any entry in the history file.

SQL2166N

The RECOVER command relies on a recovery history file to determine which backup image and log files are needed to recover the database.

The database manager was unable to locate the recovery history file because the specified database does not exist.

Ensure that the specified database name is correct or use the USING HISTORY FILE clause of the RECOVER command to specify a recover history file for the database.

SQL2167W

The value of the ioLogRange.iNumLogStreams field in the db2HistoryData data structure is less than the number of log streams in the history file record being fetched. The log stream data has been truncated to the value of ioLogRange.iNumLogStreams.

Increase the memory allocation of ioLogRange.oStream to allow for more log streams, and update the value of ioLogRange.iNumLogStreams to the corresponding higher number. The number of log streams that is represented by the value of the oMaxLogStreams field in the db2HistoryOpenStruct data structure (returned by the db2HistoryOpenScan API) is guaranteed to be sufficient to read any entry in the history file.

SQL2170N

The utility has encountered an entry with the same identifier (timestamp to the second) in the recovery history file while writing to it. The write to the recovery history file terminates. Database manager ensures the uniqueness of the recovery history file identifiers and makes provisions for it even if there are more than one request per second. However, there may be cases where it will fail if numerous requests come in within a few seconds.

If the applications are running utilities (such as backup, quiesce, load) that generate numerous entries to the history file, try to pace the utility requests to prevent the problem.

SQL2171N

The entry specified to be updated in the recovery history file does not exist in the file. The utility stops processing.

Resubmit the command with a valid entry.

SQL2172W

The utility has encountered an error writing to the recovery history file. This warning does not affect processing.

Correct the error condition to prevent future warnings.

SQL2180N

The filtering specification provided uses one or both of incorrect syntax or an incorrect password key.

Save the diagnostic information. Contact IBM service.

SQL2181N

An internal error occurred during filtered recovery. Recovery is terminated.

If the error was on an attempt to change the state for a table, try filtering out the full tablespace. Save the diagnostic information. Contact IBM service.

SQL2200N

The authid must be 1 to 128 bytes in length.

The utility stops processing.

Resubmit the command with the correct qualifier.

SQL2203N

The table name is required and it must be 1 to 128 characters in length (bytes in MBCS environments). The table name must be located at a valid application address.

The utility stops processing.

Resubmit the command with the correct table name.

SQL2204N

If an index is specified, the name must be 1 to 128 bytes in length. The index must be located at a valid application address.

The utility stops processing.

Resubmit the command with a valid index name.

SQL2205N

The specified index parameter is not valid for the requested operation. Following is a list of reason codes:

1

The specified index does not exist for the specified schema.table-name or schema.index-name.

2

The specified index is an extended index. The Reorganize Table utility does not support indexes based on index extensions.

3

All indexes defined on the table must be pseudo delete enabled for the following operations: Inplace Table REORG, Online LOAD, REORG INDEXES with the CLEANUP option.

4

An index other than the clustering index was specified on the table REORG command.

5

Inplace table REORG is not allowed if any indexes exist on the table that are based on index extensions.

6

An index cannot be specified for a REORG TABLE of a table that has one or more dimensions using the ORGANIZE BY clause of the CREATE TABLE command.

7

The specified index for REORG TABLE cannot be an XML regions index, XML column path index, or an index on an XML column.

8

REORG INDEXSCAN can only be used if an index is specified or if a clustering index exists on the table.

9

The specified index for REORG INDEX with the RECLAIM EXTENTS option must be in a database managed space (DMS) table space.

10

The specified index is an index with RANDOM ordering.

Federated system users: this situation can also be detected by the data source.

The utility or operation stops processing.

Resubmit the command with a valid index or without an index if applicable.

SQL2207N

The utility stops processing.

Resubmit the command with a valid datafile parameter.

SQL2208N

The utility stops processing.

Resubmit the command with a valid table space or long table space parameter or do not use these parameters. In the latter case, the Reorganize Table utility will use the table space(s) in which the table itself resides.

SQL2211N

The table does not exist in the database. Either the table name or the authorization ID is incorrect.

The command cannot be processed.

Resubmit the command with a valid table name.

SQL2212N

The Reorganize Table utility cannot be run against a view.

The utility stops processing.

Resubmit the command with a valid table name.

SQL2213N

The REORG utility requires that any table space specified is a system temporary table space. The table space name provided is not a table space defined to hold system temporary tables.

The utility stops processing.

Resubmit the command with the name of a system temporary table space or do not use the table space name parameter. In the latter case, the REORG utility will use the table space(s) in which the table itself resides.

SQL2214N

An attempt was made to reorganize the specified table or its indexes without the appropriate authorization. Appropriate authorization is the CONTROL privilege on the table or one of the following authorities: SYSADM, SYSCTRL, SYSMAINT, DBADM, or SQLADM.

The utility stops processing.

Log on as a user with the appropriate authority or privilege, and resubmit the REORG utility command.

SQL2215N

The user was already connected to the database specified in the Reorganize Table command. An error occurred while committing the previous work in progress for the database.

The utility stops processing with no attempt to roll back the work or break the database connection.

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

SQL2216N

An error occurred during the reorganization of a database table or its indexes.

The utility stops processing.

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

SQL2217N

If the system temporary table space or LONG temporary table space was not specified to the REORG utility then the utility was looking internally for a system temporary table space. A system temporary table space that uses the same page size as the table data either did not exist in the database or was not available at the time.

If a system temporary table space that uses the same page size as the table data does not exist in the database, please create a system temporary table space using a page size that matches the page size of the table data. If the page size of the table data differs from that of the LOB or LONG data, ensure a system temporary tablespace using that page size also exists.

If a system temporary table space that uses the same page size as the table data exists in the database but was not available at the time of your command, please reissue the command when the system temporary table space is available.

SQL2218N

SQL2219N

You can reclaim unused space and improve the performance of queries that have begun to run slowly as a result of a high volume of changes to table data by reorganizing tables. You can reorganize a table by issuing the REORG TABLE command.

You can perform an inplace (online) table reorganization, which allows users and applications full access to data in the table during reorganization, by specifying the INPLACE parameter with the REORG TABLE commmand.

This message is returned when an inplace table reorganization fails because of incompatible parameters, a function sequence error, or a restriction on inplace reorganization functionality. The reason code identifies the specific error:

1

Resuming a paused reorganization failed because the data or index object has changed since the reorganization was paused.

2

Resuming a reorganization failed because there is no paused reorganization to resume for the specified table.

3

An index cannot be specified to RESUME a non-clustering table reorganization.

4

Resuming a reorganization failed because the index that was specified when the reorganization was started has been dropped.

5

Resuming a reorganization failed because the index that was specified when the reorganization was resumed is not the same index that was specified when the table reorganization was paused.

6

Resuming a reorganization failed because the contents of the .OLR status file are invalid or because the .OLR status file is missing.

7

Resuming a reorganization failed because an I/O error occurred when the reorganization utility attempted to access the .OLR status file.

8

Starting or resuming a reorganization failed because a reorganization is already in progress for the specified table.

9

Starting a reorganization failed because there is already a paused reorganization for the specified table.

10

An attempt to pause or stop a reorganization failed because the command to pause or stop the reorganization has already been issued.

11

An attempt to pause or stop a reorganization failed because there is no table reorganization to pause or stop.

12

The table is in append mode.

13

The table is missing row change timestamp columns.

14

The table uses a type of data compression that is not supported with inplace table reorganization.

15

Resuming a reorganization failed because there is no paused reorganization to resume on the specified data partition.

16

An attempt was made to resume a reorganization by calling the REORG TABLE command, specifying the FULL parameter. However, the reorganization was not originally started with the FULL parameter specified.

17

An attempt was made to resume a reorganization by calling the REORG TABLE command, specifying the CLEANUP and OVERFLOWS parameters. However, the reorganization was not originally started with the CLEANUP and OVERFLOWS parameters specified.

18

The table has expression-based indexes.

19

An attempt to start, pause or resume a reorganization failed because multiple .OLR state files exist for the partitioned table.

20

A reorganization on a range partitioned table failed because a nonpartitioned index exists on the table.

Respond to this error according to the reason code:

1

Stop the running reorganization, and then start a new reorganization.

2

Start a new reorganization.

3

Respond to reason code 3 by taking one of the following actions:

• Continue the reorganization without specifying an index
• Stop the existing reorganization and then start a new reorganization, specifying an index name

4

Stop the paused table reorganization and then start a new reorganization.

5

Respond to reason code 5 by taking one of the following actions:

• Resume the reorganization, specifying the same index that was specified when the reorganization was originally started
• Resume the reorganization without specifying any index, which will cause the original index to be used by default

6, 7

Respond to reason codes 6 and 7 by performing the following troubleshooting steps:

1. Confirm that the file named "<tablespaceID>.<objectID>.OLR" exists under the database directory and is accessible, and then resubmit the command
2. If the error continues, stop the reorganization and then start a new reorganization.

8

No response is required because a reorganization is already in progress.

9

Respond to reason code 9 by taking one of the following actions:

• Resume the paused reorganization
• Stop the reorganization and then start a new reorganization

10

Wait for the reorganization to pause or stop.

11

No user response is required because no reorganization is running for the specified table.

12

Respond to reason code 12 by taking one of the following actions:

• Issue the ALTER TABLE statement, specifying the APPEND OFF clause and then perform the inplace reorganization
• Reorganize the table offline

13

Reorganize the table offline.

14

Reorganize the table offline.

15

Resume the reorganization specifying the correct data partition or without specifying the ON DATA PARTITION clause.

16

Resume the reorganization without specifying the FULL parameter.

17

Resume the reorganization without specifying the CLEANUP and OVERFLOWS parameters.

18

Reorganize the table offline.

19

Stop the reorganization on the table and then start a new reorganization.

20

Either drop the nonpartitioned indexes and reissue the reorganization command, or remove the INPLACE option from the reorganization command.

SQL2220W

A compression dictionary could not be built for one or more data object. The object(s) either contained no records, or contained no records larger than the minimum record length to be eligible for this page size. A new dictionary was not built. The operation continued to completion. If there was a dictionary prior to the operation, the dictionary is retained and the rows were subject to compression.

Refer to the Administration Log to determine which data object(s) caused the warning.

SQL2221N

If the REORG TABLE RECLAIM EXTENTS command was issued, the specified table name is only supported when the table is a multidimensional clustered (MDC) or insert time clustering (ITC) table and the MDC or ITC table is in a database managed space (DMS) table space.

If the REORG INDEXES ALL command with the RECLAIM EXTENTS option was issued, the indexes for the specified table name must be in a database managed space (DMS) table space.

Do one of the following:

• Use a table name that identifies an MDC or ITC table that is in a DMS table space in the REORG RECLAIM EXTENTS command.
• Use a table where the indexes are in a DMS table space for the REORG INDEXES ALL command.

sqlcode: -2221

sqlstate: 5U044

SQL2222N

The specified data partition name is not valid for the request as indicated by the following reason code:

1

The data partition name does not exist for the specified table.

2

The ON DATA PARTITION clause is not supported for the REORG INDEX command.

3

The operation cannot be performed because the data partition is in the attached or detached state.

Based on the reason code listed in the message, perform the following actions.

1

Resubmit the request with a valid data partition name or without a data partition name.

2

Resubmit the command without the ON DATA PARTITION clause.

3

Query the SYSCAT.DATAPARTITIONS catalog view to check the value of the STATUS column for the partition.

If the STATUS is 'A', the partition is newly attached, perform the following steps:

1. Issue the SET INTEGRITY statement to bring the attached partition into the normal status, the STATUS is an empty string.
2. Resubmit the request after SET INTEGRITY completes successfully.

If the STATUS value is 'D', 'L', or 'I', the partition is being detached, but the detach operation has not completed. Reorganization of the data or indexes of a detached partition is not permitted.

Once the detach operation completes the partition will no longer be part of the source table. You can reorganize the data or indexes of the newly created target table after detach completes.

SQL2223N

Rebuild synopsis table has failed. The base table can still be queried. But performance of queries referencing the base table might be suboptimal.

Check db2diag.log for error(s). Search for the SQLCODE of this message, and the SQLCODE mentioned in the message. If the SQLCODE mentioned in the message is -901 or -902, contact IBM Support. Otherwise correct the error(s) and re-issue the command.

sqlcode: -2223

sqlstate: 55019

SQL2224N

The synopsis table for the specified table does not exist in the database. A table might not have a synopsis table due to the table definition.

The command cannot be processed.

No further action is required.

sqlcode: -2224

sqlstate: 55019

SQL2300N

The table name must be fully qualified. The format is authid.tablename where authid contains 1 to 128 bytes and tablename contains 1 to 128 bytes in.

The utility stops processing.

Resubmit the command with the fully qualified table name, including the correct qualifier.

SQL2301N

The table name must be fully qualified and in the format authid.name where authid contains 1 to 128 bytes and name contains 1 to 128 bytes and must be located at a valid application address.

The utility stops processing.

Resubmit the command with the correct table name.

SQL2302N

The address for the list is not valid, the number of entries in the list is less than the number of indexes specified, or the address for an index in the list is not valid.

The utility stops processing.

Resubmit the command with a valid index list.

SQL2303N

The utility stops processing.

Resubmit the command with a valid statsopt parameter.

SQL2304N

The sharelev parameter in the RUN STATISTICS command must be R for reference or C for change.

The utility stops processing.

Resubmit the command with a valid sharelev parameter.

SQL2305N

The tname parameter specified a view or nickname rather than a table.

The utility stops processing.

Resubmit the command with a valid tname parameter.

SQL2306N

The table or index identified by name does not exist in the database, or the index identified by name is not defined on the specified table. The qualifier for the table or one of the indexes may be incorrect.

The utility stops processing.

Resubmit the command with valid table names and indexes.

SQL2307N

The Run Statistics utility command may not be run against a system table.

The utility stops processing.

Resubmit the command with a valid table name.

SQL2308N

The index name must be a fully qualified name. The format is authid.name where authid contains 1 to 128 bytes and name contains 1 to 128 bytes.

The utility stops processing.

Resubmit the command with a fully qualified name, including the correct qualifier.

SQL2309N

The index name must be a fully qualified name. The format is authid.name where authid contains 1 to 128 bytes and name contains 1 to 128 bytes.

The utility stops processing.

Resubmit the command with a valid index.

SQL2310N

An error occurred while the utility was gathering statistics.

The sqlcode number in the token sqlcode indicates more specifically what the underlying error was.

1. Review the SQL message for the given sqlcode.
2. Resolve the cause of the underlying error.
3. Resubmit the command.

SQL2311N

The user attempted to run statistics on the specified table without the appropriate authorization. If the table specified for the RUNSTATS command is the root table of a table hierarchy, the table name returned in the message might be a subtable of the specified root table.

For tables, CONTROL privilege on the table or one of the following authorities is required: SYSADM, SYSCTRL,SYSMAINT,DBADM,SQLADM, or LOAD.

For statistical views, both of the following authorizations are required:

• CONTROL privilege on the table or one of the following authorities: SYSADM, SYSCTRL,SYSMAINT,DBADM,SQLADM
• The appropriate privilege to access rows in the view. This means for each table, statistical view, or nickname referenced in the statistical view, you need one of the following privileges or authorities: SYSADM, DBADM, DATAACCESS, CONTROL or SELECT.

The utility stops processing.

Call the RUNSTATS utility command with appropriate authorization.

SQL2312N

The setting of the database configuration parameter stat_heap_sz is not big enough to collect non-uniform distribution statistics on the table.

Update the database configuration parameter stat_heap_sz to the suggested value and try again.

SQL2313W

The setting of the database configuration parameter stat_heap_sz is not big enough to collect non-uniform distribution statistics on the table. Only <n1> of <n2> rows could be processed.

Update the database configuration parameter stat_heap_sz by 20 percent and try again.

SQL2314W

The query optimizer uses statistics to determine the best access plan for a query. When inconsistent statistics are present, the optimizer performs access plan evaluation with information that is less accurate then if a consistent set of statistics was available. This might result in an access plan that is not optimal.

Possible causes of this warning include the following.

1. Issuing RUNSTATS on the table only may result in a situation where the table level statistics are inconsistent with the already existing index level statistics. Likewise, issuing RUNSTATS for indexes only or during index creation may leave table level statistics in an inconsistent state. For example, if index level statistics are collected on a particular table and later a significant number of rows is deleted from this table, issuing RUNSTATS on the table only may end up with the table cardinality less than FIRSTKEYCARD which is an inconsistent state.
2. If a RUNSTATS is issued with the ALLOW WRITE ACCESS option when many inserts, updates, or deletes are occurring concurrently, then inconsistencies may occur because of table changes between the time that table and index statistics are collected.
3. If a RUNSTATS is issued with the TABLESAMPLE option, then an excessively low sample size may cause statistics to be inaccurately extrapolated, resulting in inconsistencies. The chance of inaccurate extrapolation is higher for SYSTEM sampling than for BERNOULLI sampling.

Address the cause of the inconsistency and then collect statistics again to resolve the inconsistency.

1. Issue a RUNSTATS to collect both table level and index level statistics.
2. Collect statistics when inserts, updates, and deletes are minimal or not occurring at all. Or, if concurrent inserts, updates, and deletes are not essential, issue a RUNSTATS with the ALLOW READ ACCESS option.
3. Increase the sample size, or, if RUNSTATS was issued with TABLESAMPLE SYSTEM, use the TABLESAMPLE BERNOULLI option instead.

sqlcode: +2314

sqlstate: 01650

SQL2315N

The statistics profile for this table does not exist in the catalog table SYSIBM.SYSTABLES.

The utility stops processing.

To create a statistics profile for this table, use the SET PROFILE or SET PROFILE ONLY options. Refer to the RUNSTATS utility documentation for information about the utility options.

option-name is a token which can be "USE PROFILE", "UNSET PROFILE", or "UPDATE PROFILE".

SQL2316W

The maximum size of the STATISTICS_PROFILE column is 32768 bytes. If the size of the statistics profile is greater than this amount, the Runstats command strings is truncated to the maximum size.

The utility continues processing.

Refer to the STATISTICS_PROFILE column in the catalog table SYSIBM.SYSTABLES to review the statistics profile. If the existing statistics profile is not desired, reissue the RUNSTATS utility and specify the UPDATE PROFILE or the UPDATE PROFILE ONLY option to modify the profile. Refer to the RUNSTATS utility documentation for information about the utility options.

SQL2317W

Page-level sampling, or SYSTEM SAMPLING, could not be performed on the statistical view specified for RUNSTATS. For statistical views, SYSTEM sampling can only be applied to a single base table referenced in the view definition. If the view contains multiple tables, SYSTEM sampling is possible if a single table among all the tables in the statistical view can be identified as being joined with all primary keys or unique index columns of the other tables used in the view.

The referential integrity constraints can be informational. If the view meets the previously described criteria, page-level sampling will be done on the child table.

Because the statistical view specified did not satisfy these conditions, row-level sampling, or BERNOULLI SAMPLING, was done instead.

Specify BERNOULLI SAMPLING for the statistical view to avoid having this warning returned.

sqlcode: +2317

sqlstate: 0168V

SQL2406N

The backup failed because the database is in an inconsistent state.

The utility stops processing.

Use the ROLLFORWARD command to make the database usable. Then resubmit the BACKUP command.

SQL2412C

During the utility operation a corrupted database page was encountered. The database is in an unpredictable state and the utility cannot continue.

Record the message number (SQLCODE).

SQL2413N

Online backup cannot be performed while the database is not logging for forward recovery as forward recovery will be required at restore time. Forward recovery is placed into effect by setting either the database configuration LOGARCHMETH1 or LOGARCHMETH2 and then performing an offline backup of the database.

Execute an offline backup or reconfigure the database for roll-forward recovery and issue an offline backup so that subsequent online backups will be allowed.

SQL2416W

The tape which the utility is using has become full.

Mount another tape and continue the operation with the callerac parameter indicating if processing continues.

SQL2417N

The archive log command can only be used on databases that are in recoverable mode. A database is in recoverable mode if LOGARCHMETH1 is set to DISK, TSM, VENDOR, USEREXIT, or LOGRETAIN, or if LOGARCHMETH2 is set to DISK, TSM, or VENDOR.

Ensure that the specified database is in recoverable mode and reissue the command.

SQL2418N

The database specified in the dbase parameter of the Database Backup command could not be found.

Ensure that the correct database alias was specified for the Backup Database utility and that the database exists for this alias. Resubmit the command with the correct alias.

SQL2419N

During the processing of a database utility, the target disk became full. The utility has stopped and the target is deleted.

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

On unix-based systems, this disk full condition may be due to exceeding the maximum file size allowed for the current userid. Use the chuser command to update fsize. A reboot may be necessary.

On non unix-based systems, this disk full condition may be due to exceeding the maximum file size allowed for the operating system. Direct the target to other media, such as tape, or use multiple targets.

SQL2420N

During the Backup operation an initial backup header needs to be created at the start of the backup image. This header must fit on one tape when backing up to tape. There is insufficient space on the tape to contain this header.

Resubmit the Backup operation and either direct the output to a new tape, or reposition the current tape to provide enough space for this header.

SQL2421N

This message is returned when a table space level backup cannot be performed because the database is not recoverable or a backup pending condition is in effect. This can happen under the following conditions:

• The database is in an offline backup pending condition. This can be caused by a topology change, or when the database has been made recoverable.
• Table space level backup cannot be performed while the database is not logging for forward recovery as forward recovery will be required at restore time.

1. Do one of the following:
   • Execute a full database backup
   • Reconfigure the database for roll-forward recovery. Forward recovery is configured by setting either of the database configuration parameters, LOGARCHMETH1 or LOGARCHMETH2, and then performing an offline backup of the database.
2. Issue an offline backup so that subsequent table space level backups will be allowed.

SQL2423N

Some of the index files required by the backup are missing. These index files must be recreated prior to backing up the database.

Run the 'db2recri' program to recreate the missing index files and then resubmit the backup command.

SQL2424N

The TSM or vendor supplied archive server might not be in operational state.

Ensure TSM or the vendor supplied archive server is in an operational state and resubmit the backup command.

SQL2425W

During an online backup, all buffered log records are forced to disk and the last active log file is truncated. During the current backup, truncation of the last active log file has failed. As a result, new log records will continue to be written into the last log file used during the backup.

No user action is required. The last active log file used during the backup will eventually become inactive when it becomes full.

SQL2426N

Incremental backups are not enabled for a table space until after modification tracking has been activated for the database and a non-incremental backup has been performed on the table space.

Possible reason codes:

1. The configuration parameter TRACKMOD has not been set for the database.
2. The TRACKMOD configuration parameter has been set but at least one table space has not had a non-incremental backup taken since the TRACKMOD parameter was set.

The action is based on the reason code as follows:

1. Activate modification tracking for the database by setting the TRACKMOD database configuration parameter to on, then perform a full database backup.
2. Consult the db2diag log file to determine the name of the table space, then perform a full backup of that table space.

SQL2427N

A compressed backup image is being created with the plug-in library being included in the image. However, the library does not contain all the functions needed to decompress the backup image when it is restored.

The utility stops processing.

Resubmit the command, specifying the name of a library that has all the functions needed to decompress the backup image.

SQL2428N

You can include database log files in a backup image by specifying the INCLUDE LOGS parameter with the BACKUP command. When the INCLUDE LOGS parameter is specified with the BACKUP command, if any of the logs required for rollforward recovery cannot be retrieved and copied into the backup image the backup operation fails.

There are multiple reasons why the backup utility might encounter a problem while retrieving and copying the log files into the backup image, including these examples:

• An administrative action, such as unmounting the drive on which the log path resides or changing the permissions on the directory where the log path is located, has occurred which prevents the backup utility from access the log files.
• The contents of the log path have been moved or log files have been deleted.
• The archive log path contains log files from a previous database that has the same name as a current database.

1. Refer to the administration notification log for additional information about the cause of the failed log retrieval.
2. If the current log path was previously used for a database with the same name as the database being backed up, move old log files that were created for the previous database from both the archive log path and the current log path to another directory.
3. Correct the error and resubmit the command.

SQL2429N

The backup of a partitioned database failed on one or more database partitions.

When the database server backs up a partitioned database, a failure on any one of the partitions causes the whole backup to fail.

The backup operation terminated. No backup image was generated.

1. For each partition that returned an error, correct the problems that caused the error.
2. Rerun the BACKUP command.

SQL2430W

The database server successfully backed up the partitioned database containing this partition.

However, some of the table spaces that were specified in the BACKUP command do not exist on this partition. This might be because the table spaces specified are located on other partitions of this database; or because the list of table spaces specified contains an error.

The backup completed successfully.

1. Verify that the list of table spaces specified in the BACKUP command is correct.
2. • If the list of tables spaces that was specified is correct, no action is required.
   • If the list of tables spaces that was specified contains an error, correct the list and rerun the BACKUP command.

SQL2431W

The database server successfully backed up a partitioned database.

The backup image of each database partition contains only the log files that was were active at the time of the backup. It is not possible to rollforward the whole partitioned database using only the log files included in the backup images, if any of those log files does not span a period of time including the database minimum recovery time.

The minimum recovery time (MRT) for a database object is the earliest point in time to which it can be rolled forward.

In a partitioned database, the database MRT is the latest MRT of any one of its database partitions.

You can only roll forward a partitioned database if you have a set of log files on all database partitions that span a period of time that includes the database MRT.

The log files included with the backup image might not satisfy this requirement.

The backup completed successfully.

If your database recovery strategy relies on using only log files included in backup images to rollforward your partitioned database, rerun the backup command with the "ON ALL DBPARTITIONNUMS" parameter. This will ensure the log files included with the backup image will be sufficient to rollforward your database.

SQL2432N

A snapshot backup enables you to use fast copying technologies for the data copying and movement parts of DB2 database backup and restore operations.

The EXCLUDE LOGS parameter was specified for a snapshot backup, but the path for the given log directory or directories shares a path or storage device with other paths or storage devices used by the database being backed up.

When the log directory shares a path or storage device with other paths or storage devices used by the database being backed up, it is not possible for the snapshot backup to include the shared path or storage device without including the log directory.

For example: when you create a database, the log directory is created under the main database directory by default. Because a snapshot backup will include everything under the main database directory, the log directory will be included in the resulting backup image too. If you use the default log path when you create a database, you will not be able to exclude the logs from the backup image when you perform a snapshot backup on that database.

The mechanism for grouping database directories varies among the snapshot backup support provided by different storage management software.

You can do one of:

• Choose not to exclude the logs from the snapshot backup image.
• Resubmit the BACKUP command without the EXCLUDE LOGS parameter.
• Reconfigure the log directory to enable excluding the logs from the snapshot backup image.
• Use the newlogpath database configuration parameter to specify a path for the log directory that is independent of any other database path.
• Reissue the BACKUP command using EXCLUDE LOGS.
• You can use the DBPATHS administrative view to determine the current database paths.

SQL2433N

You can include extraction log files in a backup image by specifying the INCLUDE LOGS parameter with the BACKUP DATABASE command. INCLUDE LOGS is the default with most online backups. If extraction log files exist they will be copied into the backup image.

In default environments, failing to include an extraction log file into a backup image is not a cause for the BACKUP DATABASE command to fail. The backup utility can tolerate such errors and will proceed to include the corresponding active log file instead to ensure the backup image is recoverable at restore time.

If the user has specified in the environment to fail the backup utility when an error is encountered trying to copy an extraction log file into the backup image, this error will be returned.

There are multiple reasons why the backup utility might encounter a problem while processing and copying the extraction log files into the backup image, including these examples:

• The contents of the log path have been moved or one or more of the extraction log files have been deleted.
• The file permissions for one or more of the extraction log files have been modified.
• One or more of the extraction log files are corrupted.

1. Refer to the DB2 diagnostic (db2diag) log for additional information about the cause of the failure.
2. Correct the error and resubmit the command.

Related information: BACKUP DATABASE command

SQL2434N

A redirected restore is a restore in which the set of table space containers for the restored database is different from the set of containers for the original database at the time the backup was done.

When you define new table space containers that are to be used by the restored database, you can define an architecture for the new table space containers that is not the same as the architecture of the original table space containers. For example, you can use a redirected restore operation to change a database that currently uses two table space containers to use a single table space container.

If the architecture of the table spaces to be used by the restored database is different from the architecture of the original database, it is possible that there are table space altering operations in the database log files that will have to be replayed during rollforward that are not valid in the new table space architecture.

This message is returned during a redirected restore operation when the rollforward utility attempts to replay a table space operation that is invalid for the target table space container architecture. Specifically, this message is returned when the rollforward utility attempts to perform a table space operation on a REGULAR or USER TEMPORARY DMS table space that causes the size of the table space to increase beyond the defined maximum allowed size, as determined by the PAGESIZE database configuration parameter.

1. Begin the redirected restore again using the RESTORE command with the REDIRECT parameter.
2. Define the new table space containers to be used by the restored database using the SET TABLESPACE CONTAINERS command, forcing the rollforward operation to omit replaying table space operations by specifying the IGNORE ROLLFORWARD CONTAINER OPERATION parameter.
3. Complete the restore operation using the RESTORE command with the CONTINUE parameter.

sqlcode: -2434

sqlstate: 58004

SQL2435N

This message is returned when an attempt is made to have multiple active databases in a DB2 pureScale environment, but the activation of one database fails because there is not enough memory in the cluster caching facility, also known as CF, for that database.

You can configure the total amount of memory that is available for the CF using the cf_mem_sz database manager configuration parameter. You can configure the percentage of the total CF memory that is assigned to each database that has the cf_db_mem_sz database configuration parameter set to AUTOMATIC using the DB2_DATABASE_CF_MEMORY registry variable. (Any database that has cf_db_mem_sz set to a specific value will ignore the DB2_DATABASE_CF_MEMORY registry variable.)

Use of the DB2_DATABASE_CF_MEMORY registry variable must be coordinated with the cf_db_mem_sz database configuration paremter and the numdb database manager configuration parameter.

Example

If there are four databases to be active at once, then the configuration parameters should be coordinated like this:

• The database manager configuration parameter numdb should be set to 4
• If the database configuration parameter cf_dm_mem_sz is set to AUTOMATIC for each of the four database, then the registry variable DB2_DATABASE_CF_MEMORY should be set to 25

One reason this error can occur is because the DB2_DATABASE_CF_MEMORY registry variable is set to 100 when numdb is greater than 1.

Respond to this error in one of the following ways:

• Determine the amount of CF memory used by other databases and see if any settings need to be changed in order to accommodate the CF memory requirements of this database.
• If the cf_db_mem_sz database configuration parameter is set to automatic for this database, increase the amount of memory available in the CF for this database by modifying the value of the DB2_DATABASE_CF_MEMORY registry variable.

SQL2436N

You can use the redistribute utility to rebalance the distribution of data across database partitions after adding or removing database partitions, or to achieve a desired data distribution across partitions. This message is returned when an attempt is made to redistribute data in a database, using the REDISTRIBUTE DATABASE PARTITION GROUP command for example, but the redistribute utility determines that there are one or more tables that are not in an appropriate state to be redistributed.

If the PRECHECK YES OR PRECHECK ONLY command parameter was specified in the REDISTRIBUTE DATABASE PARTITION GROUP command, this error message describes the first check that failed; data redistribution does not commence. In all other cases, the data redistribution was attempted and failed; tables that were partially processed are put in "redistribute pending" state.

The reason that the table failed to meet data redistribution prerequisites is indicated by the reason code:

1

The table is in "set integrity pending" state.

2

The table is in "load in progress" state. The LOAD utility is currently operating on this table, no access is allowed until the LOAD is finished.

3

The table is in "load pending" state. A previous LOAD attempt on this table resulted in failure. No access to the table is allowed until the LOAD operation is restarted or terminated.

4

The table is in "read access only" state. This state can occur during on-line LOAD processing (LOAD INSERT with the READ ACCESS option), or after an on-line LOAD operation, but before all constraints have been validated in the newly appended portion of the table using the SET INTEGRITY statement. No update activity is allowed on this table.

5

The table is in "reorg pending" state. This can occur after an ALTER TABLE statement containing a REORG-recommended operation.

6

The table is unavailable.

7

The table is an MDC table with a deferred index cleanup rollout operation in progress.

8

The table is a target table for an active event monitor of type "WRITE TO TABLE".

9

The table is in "not load restartable" state, which is a partially loaded state that will not allow a load restart operation.

10

The table is not in FULL access mode (ACCESS_MODE='F' in SYSCAT.TABLES).

11

The table has data partitions that are currently being attached (SYSCAT.DATAPARTITIONS.STATUS = 'A').

12

The table has detached data partitions and there are dependent tables that need to be incrementally maintained with respect to these detached data partitions (SYSCAT.DATAPARTITIONS.STATUS = 'D').

13

The table has detached data partitions that are involved with an index cleanup operation that is currently running (SYSCAT.DATAPARTITIONS.STATUS = 'I').

Take corrective action on table-name, but be aware that it might not be the only problematic table in the database partition group. By checking all of the tables in the database partition group, you can avoid multiple unsuccessful redistribution attempts. For more information, refer to the documentation about troubleshooting table states during data redistribution.

1

Execute the SET INTEGRITY statement with the IMMEDIATE CHECKED option on table table-name and then issue the REDISTRIBUTE DATABASE PARTITION GROUP command again. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

2

Wait until the load operation has finished, then issue the REDISTRIBUTE DATABASE PARTITION GROUP command again. You can use the LOAD QUERY command to monitor the progress the load operation. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

3

Restart or terminate the previously failed LOAD operation on this table by issuing the LOAD command with RESTART or TERMINATE command parameters, respectively. When the load operation completes, issue the REDISTRIBUTE DATABASE PARTITION GROUP command again. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

4

Issue the LOAD QUERY command to check whether the table is in the process of being loaded. If yes, wait until the LOAD utility has completed, or if necessary, restart or terminate the previously failed LOAD operation. If LOAD is currently not in progress, issue the SET INTEGRITY statement with the IMMEDIATE CHECKED option, to validate constraints in the newly loaded portion of the table. When the table is no longer in "read access only" state, issue the REDISTRIBUTE DATABASE PARTITION GROUP command again. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

5

Perform a REORG operation to make the table accessible, then issue the REDISTRIBUTE DATABASE PARTITION GROUP command again. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

6

Drop the table or restore it from a backup, then issue the REDISTRIBUTE DATABASE PARTITION GROUP command again. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

7

Issue the REDISTRIBUTE DATABASE PARTITION GROUP command again once the index cleanup of the rolled out blocks is complete. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

8

Either wait for the event monitor activity to complete or deactivate the event monitor using the SET EVENT MONITOR STATE statement. Re-submit the REDISTRIBUTE DATABASE PARTITION GROUP command, specifying the CONTINUE parameter or the ABORT parameter. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

9

Issue a LOAD TERMINATE or a LOAD REPLACE command to bring the table out of the "not load restartable" state. Re-submit the REDISTRIBUTE DATABASE PARTITION GROUP command using either the CONTINUE or ABORT option. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

10

Execute the SET INTEGRITY statement with the IMMEDIATE CHECKED option on the dependent immediate materialized query tables and staging tables for table-name. Re-submit the REDISTRIBUTE DATABASE PARTITION GROUP command using either the CONTINUE or ABORT option. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

11

Execute the SET INTEGRITY statement with the IMMEDIATE CHECKED option on table table-name and then issue the REDISTRIBUTE DATABASE PARTITION GROUP command again. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

12

Execute the SET INTEGRITY statement with the IMMEDIATE CHECKED option on the dependent immediate materialized query and staging tables of the tables that still need to be incrementally maintained with respect to the detached data partitions. Query the SYSCAT.TABDETACHEDDEP catalog view to locate these detached dependent tables. Then issue the REDISTRIBUTE DATABASE PARTITION GROUP command again using either the CONTINUE or ABORT option. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

13

Wait for the completion of the index cleanup for the detached partition. Re-submit the REDISTRIBUTE DATABASE PARTITION GROUP command using either the CONTINUE or ABORT option. Alternatively, omit the table by specifying the EXCLUDE parameter in the REDISTRIBUTE DATABASE PARTITION GROUP command.

sqlcode: -2436

sqlstate: 55019

SQL2437N

You can move data into and out of databases, using utilities such as LOAD, IMPORT, INGEST, and EXPORT.

There are several ways to specify how data movement utilities should handle implicitly hidden columns:

• Explicitly specify the list of columns to include in the data movement operation.
• Specify the hidden column-related parameter in the data movement command.
• Set the hidden column-related registry variable to indicate how all data movement utilities should handle hidden columns.

This message is returned when an attempt is made to move data into or out of one or more tables that contain implicitly hidden columns, and the data movement utility cannot determine whether the implicitly hidden columns should be included in the data movement operation because none of the methods described have been used to specify how hidden columns should be handled.

Run the utility again, specifying how implicitly hidden columns should be handled using appropriate command parameters or registry variables.

SQL2438W

You can move data into and out of databases, using utilities such as LOAD, IMPORT, INGEST, and EXPORT.

There are several ways to specify how data movement utilities should handle implicitly hidden columns:

• Explicitly specify the list of columns to include in the data movement operation.
• Specify the hidden column-related parameter in the data movement command.
• Set the hidden column-related registry variable to indicate how all data-movement utilities should handle hidden columns.

This message is returned when data is being moved into or out of one or more tables that contain implicitly hidden columns, and the data movement utility cannot determine whether the implicitly hidden columns should be included in the data movement operation because none of the methods described have been used to specify how hidden columns should be handled.

Data has been moved, but data in any implicitly hidden columns was not moved.

If the data in the implicitly hidden columns should have been moved, rerun the data movement operation specifying how implicitly hidden columns should be handled using appropriate command parameters or registry variables.

To avoid this warning in the future: When moving data into or out of tables that contain implicitly hidden columns, specify how implicitly hidden columns should be handled using appropriate command parameters or registry variables.

SQL2439N

This message is returned when a new level has been applied but the db2updvXX utility for that version (for example, db2updv97, or db2updv10) has not be used to update the system routine definitions.

Run the appropriate db2updvXX command.

SQL2440W

When the DB2_BCKP_INCLUDE_LOGS_WARNING registry variable is set to ON, online backups that include logs can succeed even if some of the logs required for the successful rollforward recovery of the image cannot be retrieved and copied into the backup image.

If this backup image is restored, it will not be able to complete rollforward recovery unless all of the required logs are made available.

Respond to this warning in one of the following ways:

• Refer to the administration notification log for additional information about the cause of the failed log retrieval attempt. Correct the error and resubmit the command.
• Ensure that a copy of the required logs is retained. As well, you should ensure that the log archiving device is made available for use as soon as possible.

To revert to the previous behavior in which online backups with missing logs failed, set the DB2_BCKP_INCLUDE_LOGS_WARNING registry variable to OFF.

SQL2441N

You can convert row-organized tables into column-organized tables by using the db2convert utility.

This message is returned when the db2convert command is called and one or more tables to be converted are either already in the process of being converted or are involved in a table move operation.

1. Resolve the in-progress conversion or table move operation by performing one of the following actions:
   • Monitor the table and wait for the in-progress conversion or move operation to complete.
   • Cancel the in-progress conversion or move operation by running the ADMIN_MOVE_TABLE stored procedure, specifying the CANCEL parameter.
2. Run the db2convert command again.

SQL2442N

You can convert row-organized tables into column-organized tables by using the db2convert utility.

This message is returned when either an invalid parameter is specified with the db2convert command, or when an invalid combination of parameters is specified.

Run the db2convert command again, specifying valid parameters.

SQL2443N

You can convert row-organized tables into column-organized tables by using the db2convert utility.

When you run the db2convert command, you must use the -d parameter to specify the name of the database in which the tables to convert are located.

This message is returned when the db2convert command is called but no database is specified with the -d parameter.

Call the db2convert command again, specifying a database name with the -d parameter.

SQL2444N

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can perform the conversion operation all in one step. However, you can also choose to perform the conversion operation in two steps:

1. Perform only the INIT, COPY, and REPLAY phases of the conversion by calling the db2convert command specifying the -stopBeforeSwap parameter.
2. Complete the conversion operation by calling the db2convert command specifying the -continue parameter.

If you choose to perform the conversion in two steps, the table specification in the first db2convert call and in the second db2convert call must match, and the first step must be completed before you can perform the second step.

This message is returned when the db2convert command is run with the -continue parameter, but no matching call to the db2convert command with the -stopBeforeSwap parameter has completed.

• Before running the db2convert command with the -continue parameter, run the db2convert command with the -stopBeforeSwap parameter.
• If a call to the db2convert command with the -stopBeforeSwap parameter is still running, wait for that operation to complete. Then call the db2convert command with the -continue parameter.

SQL2445N

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

For example, the following command converts all row-organized tables in database db1 that satisfy the matching criteria "owned by user1 and in schemaA":

 db2convert -d db1 -u user1 -z schemaA 

This message is returned when no tables satisfy the matching criteria that were specified with the db2convert command.

To convert row-organized tables into column-organized tables, call the db2convert command specifying criteria that match one or more tables in the database.

SQL2446I

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

This message is returned when the db2convert utility has completed the conversion process successfully for all tables that match the specified criteria.

No response is required.

SQL2447W

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when the db2convert fails to convert one or more tables.

There are multiple reasons that a table might have failed to be converted, including the following examples:

• The table includes functionality that is not supported with column-organized tables.
• The table includes functionality that cannot be converted by the db2convert utility due to a restriction.
• An error occurred while the table was being converted.

The db2convert utility prints summary information to stdout upon completion. That summary information includes a list of tables that were converted and tables that were not converted, including details about what errors occurred.

Review the summary information that the db2convert utility printed to stdout for more information about what succeeded and what failed.

SQL2448N

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when the db2convert fails to convert any tables.

There are multiple reasons that a table might have failed to be converted, including the following examples:

• The table includes functionality that is not supported with column-organized tables.
• The table includes functionality that cannot be converted by the db2convert utility due to a restriction.
• An error occurred while the table was being converted.

The db2convert utility prints summary information to stdout upon completion. That summary information includes a list of tables that were converted and tables that were not converted, including details about what errors occurred.

Review the summary information that the db2convert utility printed to stdout for more information about what what failed.

SQL2449W

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when none of the tables that match the specified criteria are row-organized tables.

To convert row-organized tables to column-organized tables, call the db2convert command specifying table criteria that match existing row-organized tables.

SQL2450I

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

You can perform the conversion operation in one step. However, you can also choose to perform the conversion operation in two steps:

1. Perform only the INIT, COPY, and REPLAY phases of the conversion by calling the db2convert command specifying the -stopBeforeSwap parameter.
2. Complete the conversion operation by calling the db2convert command specifying the -continue parameter.

Performing the operation in two steps allows you to back up the database before completing the conversion.

This message is returned when the db2convert utility has successfully completed the first step of the two-step conversion process for all tables that match the specified criteria.

To complete the conversion of the tables to column-organized tables, call the db2convert command specifying the same table criteria and the -continue parameter.

SQL2451W

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

You can perform the conversion operation in one step. However, you can also choose to perform the conversion operation in two steps:

1. Perform only the INIT, COPY, and REPLAY phases of the conversion by calling the db2convert command specifying the -stopBeforeSwap parameter.
2. Complete the conversion operation by calling the db2convert command specifying the -continue parameter.

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when the db2convert fails to convert one or more tables.

There are multiple reasons that a table might have failed to be converted, including the following examples:

• The table includes functionality that is not supported with column-organized tables.
• The table includes functionality that cannot be converted by the db2convert utility due to a restriction.
• An error occurred while the table was being converted.

The db2convert utility prints summary information to stdout upon completion. That summary information includes a list of tables that were converted and tables that were not converted, including details about what errors occurred.

To complete the conversion of the tables for which the INIT, COPY, and REPLAY phases of the conversion process were successful, call the db2convert command specifying the -continue parameter.

SQL2452N

You can convert row-organized tables into column-organized tables by using the db2convert command.

You can control which tables to convert by specifying matching criteria with db2convert parameters:

• All tables in the database
• Tables created by a specific user (-u parameter)
• Tables in a specified schema (-z parameter)
• One specified table (-t parameter)

You can perform the conversion operation in one step. However, you can also choose to perform the conversion operation in two steps:

1. Perform only the INIT, COPY, and REPLAY phases of the conversion by calling the db2convert command specifying the -stopBeforeSwap parameter.
2. Complete the conversion operation by calling the db2convert command specifying the -continue parameter.

The db2convert utility will attempt to convert all row-organized tables that match the specified criteria. This message is returned when the db2convert is unable to convert any tables.

There are multiple reasons that a table might have failed to be converted, including the following examples:

• The table includes functionality that is not supported with column-organized tables.
• The table includes functionality that cannot be converted by the db2convert utility due to a restriction.
• An error occurred while the table was being converted.

The db2convert utility prints summary information to stdout upon completion. That summary information includes a list of tables that were converted and tables that were not converted, including details about what errors occurred.

Review the summary information that the db2convert utility printed to stdout for more information about what failed.

SQL2453N

Rebinding is the process of recreating a package for an application program that was previously bound. You can rebind a package by using the REBIND command.

This message is returned when an attempt is made to rebind a package that is generated for an SQL object (such as an SQL procedure or a compiled function, among others) that is invalid. The SQL object might have become invalid for one of multiple reasons, such as because something in the body of the SQL object has changed since the SQL object and the associated package was created.

1. Revalidate the SQL object that generated the package by using one of the following methods:
   • Enable automatic revalidation and then execute and SQL statement that uses the SQL object.
   • Call the ADMIN_REVALIDATE_DB_OBJECTS procedure
   • Replace the SQL object using a CREATE OR REPLACE statement or by dropping the SQL object and creating it again.
2. Call the REBIND command again.

sqlcode: -2453

sqlstate: 560D6

SQL2454N

You can convert row-organized tables into column-organized tables by using the db2convert utility. You can cause all message text output from the db2convert utility to be printed to a file by specifying an output file name with the -o option. If the specified file does not exist, the db2convert utility will create the file. If the specified file exists, the db2convert utility will overwrite the existing file.

This message is returned when a file name is specified with the -o option, but the db2convert utility cannot write output to the specified file. There are different reasons why the db2convert utility might be unable to print to the specified output file, including the following examples:

• The user who called the db2convert command does not have write permission for the specified file or the directory in which the file is located.
• A full path was specified with the file name, and the specified path does not exist.

Call the db2convert command again, specifying an output file for which you have write permission.

SQL2455W

You can enable self-tuning for sort memory by setting the database configuration parameters SORTHEAP and SHEAPTHRES_SHR to "AUTOMATIC".

Self-tuning for sort memory is not supported with column-organized tables.

This message is returned when either the configuration parameter SORTHEAP or the configuration parameter SHEAPTHRES_SHR is updated to "AUTOMATIC" while there is a column-organized table in the database.

To use self-tuning for sort memory, use only row-organized tables instead of colum-organized tables.

SQL2456I

If database configuration parameter CF_DB_MEM_SZ is set to AUTOMATIC, these memory consumer parameters are also automatically set to AUTOMATIC: CF_GBP_SZ, CF_LOCK_SZ and CF_SCA_SZ.

If any of the memory consumer parameters is set to a fixed value, the other two memory consumer parameters and database configuration parameter CF_DB_MEM_SZ are also automatically set to a fixed value. If CF self-tuning memory was set on, CF self-tuning memory is turned off for this database.

If any of the memory consumer parameters is set to AUTOMATIC, the other two memory consumer parameters are also set to AUTOMATIC. The value of database configuration parameter CF_DB_MEM_SZ remains unchanged.

No action required.

SQL2457W

For CF self-tuning memory to be enabled, when registry variable DB2_DATABASE_CF_MEMORY is set to AUTO, these database configuration parameters must be set to AUTOMATIC: CF_GBP_SZ, and CF_LOCK_SZ, CF_SCA_SZ.

One of the database configuration parameters is not set to AUTOMATIC.

To enable CF self-tuning memory, set the specified parameter to AUTOMATIC using the UPDATE DATABASE CONFIGURATION command.

SQL2458W

Changing the setting of registry variable DB2_DATABASE_CF_MEMORY requires a database manager restart for the new value to take effect. Until the database manager is restarted, the databases are not aware of the new value and will not have their CF memory configurations adjusted according to the new value.

Restart the database manager using the DB2STOP and DB2START commands.

SQL2459N

Encryption-related or compressions-related configuration settings can be specified for backup operations in two ways:

• In BACKUP DATABASE command parameters
• In database configuration parameters

The reason code indicates more specifically why this message was returned:

1

Compression-related or encryption-related parameters were specified with the BACKUP DATABASE command while one of the database configuration parameters ENCRLIB and ENCROPTS was also set.

2

The BACKUP DATABASE command specified one of the parameters ENCRLIB or ENCROPTS as well as one of the parameters COMPRLIB or COMPROPTS.

Respond according to the reason code:

1

Configure compression or encryption using either database configuration parameters or BACKUP DATABASE command parameters:

• Option 1: Set the database configuration parameters ENCRLIB and ENCROPTS, and then issue the BACKUP DATABASE command without specifying compression-related or encryption-related command parameters.
• Option 2: Clear the database configuration parameters ENCRLIB and ENCROPTS, and then reissue the BACKUP DATABASE command specifying encryption and compression options using command parameters.

2

Issue the BACKUP DATABASE command specifying either ENCRLIB and ENCROPTS or COMPRLIB and COMPROPTS.

SQL2460W

In a multiple database environment, when one of the databases was activated, the database could not get as much memory as it wanted. This will affect how large that database can grow in the future. This message can be returned when the CF self-tuning memory is enabled and database memory configuration parameter CF_DB_MEM_SZ is set to AUTOMATIC. If the instance is hosting more than one database, either:

• Too many database were activated at the same time, or
• The instance is hosting databases with both fixed and automatic CF_DB_MEM_SZ setting. The databases with fixed CF_DB_MEM_SZ are not leaving enough CF memory for the databases with AUTOMATIC CF_DB_MEM_SZ.

Perform one of the following actions:

• Rerun the ACTIVATE DATABASE command,
• Manually configure database parameter CF_DB_MEM_SZ using the UPDATE DATABASE CONFIGURATION command, or
• Configure a fixed CF_DB_MEM_SZ setting for all databases.

SQL2461W

An online fix pack update applies a new fix pack level to members and cluster caching facilities (CFs) while the instance remains available. However, the ability to set registry variable DB2_DATABASE_CF_MEMORY to AUTO is blocked until after the instance is committed.

After the online update is committed, set registry variable DB2_DATABASE_CF_MEMORY to AUTO using the db2set command.

SQL2462N

You can convert row-organized tables into column-organized tables by using the db2convert command.

If an attempt to convert tables fails, you can cancel pending conversion changes by calling the db2convert command with the -cancel parameter.

This message is returned when the db2convert command is called with the -cancel parameter, but no matching conversion operation has failed.

To convert row-organized tables into column-organized tables, call the db2convert command again without specifying the -cancel parameter.

SQL2463N

To rollforward (or recover) through an upgrade operation requires multiple steps. This message is returned when the rollforward utility has reached an upgrade operation in the logs, which means additional actions are required to complete the rollforward operation.

Issue the rollforward (or recover) command from the later version of the product to complete the operation.

SQL2464N

When the rollforward utility encounters an upgrade or update operation in the database logs, the utility performs verification tests before replay of the operation can continue.

This message is returned when the rollforward utility detects an upgrade or update operation in the database logs and verification tests fail for one of the following reasons:

1

Not all transactions before the upgrade or update have been successfully replayed. (For example, a transaction that is in doubt cannot be replayed.)

2

A table space is in a state that is not supported with rollforward operations.

1. Identify the problem that is blocking the rollforward operation by reading related messages in the diagnostic (db2diag) log files. Look for this sqlcode and use the timestamps to verify that you are looking at the correct messages.
2. Resolve the error that is blocking the rollforward operation.
3. Re-issue the rollforward command from the same product version.

SQL2501C

The RESTORE utility either could not read data from the restored database or only a portion of the database was restored. Both cases indicate that the restored database is not usable.

The database is unusable and the RESTORE utility stops processing.

Resubmit the RESTORE command.

SQL2502C

An operating system error occurred when the RESTORE utility was reading the diskette or disk, or the diskette or disk does not contain a backup of the database directory or does not contain the results of any previous backup.

The utility stops processing.

If the input drive specified is a diskette drive, check the diskette being used. If the input drive is a hard file, verify that it is the correct hard file. Resubmit the command with the correct input drive and the correct diskettes, if applicable.

SQL2503N

The name of the database contained on the backup disk does not match the database name specified on the RESTORE command. The RESTORE utility cannot determine the name until after the database has been restored because a previous release backup image was restored.

The utility stops processing.

If the wrong database name was used in the command, resubmit the command with the correct database name. If the input drive specified is a diskette drive, check the diskette being used. If the input drive is a hard file, verify that it is the correct hard file. Resubmit the command with the correct input drive and the correct diskettes, if applicable.

SQL2504W

The RESTORE utility reads the first backup diskette to determine the path of the database directory that was backed up. If the backup media is a diskette and the diskette is not found in the specified input drive, the utility returns to the caller with this prompt. The calling program is expected to query the user and return to the utility with the user response.

The utility waits for a response from the caller.

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

SQL2505W

If the database being restored already exists, its files will be deleted before the restore process starts. The utility returns to the caller with this warning. The caller is expected to query the user and return to the utility with the user response. Once the database is dropped, it cannot be accessed again.

The utility waits for response from the caller.

Warn the user that the database files will be deleted and return to the utility with the callerac parameter indicating if processing continues or ends.

SQL2506W

If changes-only backups were performed and database files were deleted between backups, the RESTORE utility adds these deleted files back into the database. The restore process could not delete the extra files either because of an I/O error or by the failure of an internal connection to an internally stopped database.

The utility ends successfully.

Either use the database as it is or attempt to restore it again. Ensure that the DB2 configuration is compatible with the restored database configuration before rerunning the RESTORE utility.

SQL2507W

Because the RESTORE utility was not bound to the database or the package of the utility that was bound to the database is not compatible with the installed version of DB2, all the utilities have been rebound to the database. But there is a timestamp conflict between the installed version of the database product and the package so the utility and bind file are not compatible.

The database is restored, but the utility is not correctly bound.

Reinstall DB2 or reapply recent updates and resubmit the utility command.

SQL2508N

The timestamp parameter must contain either NULL or a portion of a valid timestamp, the portion consisting of complete components of a timestamp.

Resubmit the Restore operation with a valid timestamp value.

SQL2509N

The drive specified does not exist, or the database does not exist on this drive or is not cataloged on this drive. RESTORE should use the db2uexit command to perform the database restore.

The utility stops processing.

Resubmit the utility command with a valid drive.

SQL2510N

An error occurred in the wait or post semaphore.

The utility stops processing.

Stop the database manager, then restart it and resubmit the utility command.

SQL2511N

The utility could not drop the database.

The utility stops processing.

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

SQL2512N

The utility could not create the database.

The utility stops processing.

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

SQL2513N

The utility could not rename the database.

The utility stops processing.

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

SQL2514N

The restore was not successful as the release number in the database configuration of the restored database did not meet the minimum level of compatibility required by the installed database manager.

If you are restoring a database from an older version of Db2, the release number is not one supported for upgrade.

If you are restoring a database from the same version of Db2, the release number is not one supported by this level of Db2.

The utility stops processing.

Resubmit the command with a level of the database manager that is compatible with level of the backup. For information on compatibility, consult the Db2 documentation.

SQL2515N

The user attempted to execute the RESTORE DATABASE utility without SYSADM authority.

The utility stops processing.

Ensure that you have the appropriate authorization to run the RESTORE DATABASE command.

SQL2516N

In some situations, the RESTORE utility can attempt to move a database to a directory by renaming the directory associated with the database. This cannot be done if any databases are in use in any process on the workstation.

The utility stops processing.

Wait until no databases on the workstation are in use and resubmit the command.

SQL2517W

You can upgrade a database from one version to a newer version using the restore utility. You can upgrade by recreating your old database manager instance in the new version and then restoring a backup image from the the old instance into the new instance. In this scenario, after restoring the database in the new database instance, the restore utility automatically performs the upgrade operation. This message is returned when the upgrade operation that the restore utility automatically runs returns a warning or error.

Respond to this message by performing the following troubleshooting steps:

1. Review the text of the warning or error code listed in the runtime token warn-err-code.
2. Respond to the warning or error code listed in the runtime token warn-err-code before accessing the upgraded database.

The user who issued the RESTORE DATABASE command is given DBADM authority to the database. If other users had DBADM authority prior to the restore, work with a user who has SECADM authority, to grant DBADM authorization to these users.

SQL2518N

The database configuration file could not be restored due to an I/O error.

The utility stops processing.

Determine whether the I/O error can be corrected. Resubmit the command.

SQL2519N

The database backup that you restored is from a previous database product release. After the database files were restored, an attempt was made to upgrade the database to the current release. The database upgrade failed.

The database restore was completed but the database was not upgraded.

Review the SQLCODE (message number) returned for more information. Make any corrections and issue the UPGRADE DATABASE command before accessing the database.

SQL2520W

When a database is restored, the current database configuration file is not always replaced with the backup version. The current database configuration file was not usable. It has been replaced by the backup version.

The utility completed successfully.

Some values in the database configuration file may be different after the restore process. Check that the configuration parameters are set to the desired values.

SQL2521W

The restore process ran successfully. The specified file was not deleted due to an I/O error.

A file with the extension “.BRG” is used to determine whether a RESTORE operation has terminated abnormally. The file resides in the local database directory of the database for which the RESTORE operation was attempted.

A file with the extension “.BRI” stores information about the progress of an incremental RESTORE operation. The file resides in the local database directory of the database for which the RESTORE INCREMENTAL operation was attempted.

The file name consists of the database token concatenated with the file type extension. For example, if the database “SAMPLE” is assigned the database token “SQL00001”, the BRI file will have the name “instance/NODE0000/sqldbdir/SQL00001.BRI”.

The utility completed successfully.

Delete the .BRG or .BRI file manually. If the file cannot be deleted, contact your technical service representative.

SQL2522N

The backup image file file name consists of a database alias and a time stamp component. A file name is constructed from the source database alias and time stamp parameters provided in the Database Restore call. A portion of a time stamp may have been specified so that a match with more than one backup image file name was found. If no time stamp was provided restore implicitly matches any backup image; implying if there are more than one backup images a unique match cannot be made.

Resubmit the operation by specifying a time stamp with sufficient time stamp components to result in a match to a unique backup file.

SQL2523W

The database alias and name of the target database are the same as the backup image database alias and name. The database seeds are not the same indicating that the databases are not the same. The target database will be overwritten by the backup version. The Roll-forward recovery logs associated with the target database will be deleted. The current configuration file will be overwritten with the backup version.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2524W

The database seeds of the target database and the database image are the same, indicating these are the same databases, the database names are the same, but the database aliases are not the same. The target database will be overwritten by the backup version.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2525W

The database aliases of the target database and database image are not the same, the database names are the same, and the database seeds are not the same, indicating these are different databases. The target database will be overwritten by the backup version. The Roll-forward recovery logs associated with the target database will be deleted. The current configuration file will be overwritten with the backup version.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2526W

The database aliases of the target database and database image are the same, and the database seeds are the same, however the database names are different. These are the same databases. The target database will be overwritten by the backup version.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2527W

The database aliases of the target database and database image are the same, the database names are not the same, and the database seeds are not the same, indicating these are different databases. The target database will be overwritten by the backup version. The Roll-forward recovery logs associated with the target database will be deleted. The current configuration file will be overwritten with the backup version.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2528W

The database aliases of the target database and database image are not the same, the database names are not the same, and the database seeds are the same, indicating these are the same databases. The current database will be overwritten by the backup version.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2529W

The database aliases of the target and database image are not the same, the database names are not the same, and the database seeds are not the same, indicating these are different databases. The current database will be overwritten by the backup version. The Roll-forward recovery logs associated with the target database will be deleted. The current configuration file will be overwritten with the backup version.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2530N

The backup image being restored is corrupted making the database image non-restorable.

Discard the backup image as it is unusable. Restore from a previous backup if possible.

SQL2531N

The file selected for restore is not a valid backup image. Either the file selected has become corrupted or a backup tape is not at the correct position.

Determine the location of the correct backup image file, and resubmit the Restore command.

SQL2532N

The file selected for restore does not contain the requested backup image. The image is for a different database than that requested.

If using tape, ensure that the correct tape is mounted. If a restore or load is being done from disk, then the file must have been renamed. Rename the file to the correct filename with a match on database name and timestamp. Resubmit the command after taking the appropriate action.

SQL2533W

The backup image read from the tape position contains a media header that does not match the header of the image of the first file of the backup file sequence.

Ensure that the tape is positioned at the correct backup, then return to the utility with the callerac parameter indicating if processing continues.

SQL2534W

The data read from the tape position does not contain a valid backup media header.

Ensure that the tape is positioned at the correct position, then return to the utility with the callerac parameter indicating if processing continues.

SQL2535W

The end of tape has been reached and there is still more data to be processed. The remainder of the backup or load source exists on another tape or on several more tapes.

Mount the next tape in sequence that contains the source image and resubmit the Restore or Load command with the callerac parameter set to continue or end.

SQL2536W

The tape is positioned on a backup image file that is out of sequence. The tape containing the backup image must be positioned to the file of sequence number sequence of the backup image.

Position the tape containing the backup image to the correct file and resubmit the Restore command with the callerac parameter set to continue or end.

SQL2537N

SQLUD_NOROLLFWD was specified for the rst_type parameter of the Database Restore utility, indicating that a roll-forward is not required to make the restored database usable. If the database to be restored was backed up in online mode or the restore issued was a tablespace level restore, then a roll-forward operation is necessary to make the database usable.

Resubmit the Database Restore command without specifying SQLUD_NOROLLFWD for the rst_type parameter.

SQL2538N

While reading and restoring from the Backup Image file, an end of file condition was reached unexpectedly. The backup image is unusable and the restore operation terminates.

Resubmit the Database Restore command with a usable backup image file.

SQL2539W

This message is returned when the database aliases, names and seeds of the target database and database image are the same, indicating these are the same databases. The current database will be overwritten by the backup version.

This message can also be returned when the RESTORE command is called with the GENERATE SCRIPT parameter. When the RESTORE command is used to generate a restore script, the restore utility performs some of the same error checking that is performed when a restore operation is being performed. When this message is returned when the RESTORE command is called with the GENERATE SCRIPT parameter, the message can be ignored.

• If this message is being returned when the RESTORE command is called with the GENERATE SCRIPT parameter no response is required.
• Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2540W

The Database Restore utility was invoked in No Interrupt mode, i.e. WITHOUT PROMPTING. During the processing, one or more warnings were encountered but not returned at the time they were encountered. The Restore has completed successfully and the warning messages found are shown at the completion in this message.

Ensure that the action that caused this warning to be generated has not resulted in a condition not wanted.

SQL2541W

The utility was successful, but the file containing the backup image could not be closed.

Attempt to close the file containing the backup image.

SQL2542N

The backup image file filename consists of a database alias and a timestamp component. A filename is constructed from the source database alias and timestamp parameters provided in the Database Restore call. No filename existed in the source directory that matched based on the source database alias and timestamp provided.

The following situations might apply:

1. The path to the backup was incorrectly specified in the restore command.
2. You do not have permission to access the backup image or the directory within which the backup image resides.
3. You are performing an automatic incremental restore and a required image was not found based on the timestamp and location in the database history.
4. You are restoring a database in a partitioned database environment, the database does not already exist, and the first database partition being restored is not the catalog partition.
5. You are restoring from TSM media, and the TSM API client configuration used by the current instance is not able to access the backup image.

Appropriate responses corresponding to the situations described previously are:

1. Ensure that the database backup image resides on the media source. Resubmit the operation by specifying a correct path to the backup image and correct timestamp to result in a match.
2. Ensure that you have permission to access the backup image and the directory in which it resides.
3. Check the database history for the corresponding backup entry and verify that the location listed matches the actual location of the backup image. Either update the database history and retry the operation to result in a match or issue a RESTORE INCREMENTAL ABORT command to cleanup any resources that may have been created during processing.
4. Always restore the catalog partition first when restoring a partitioned database.
5. Use db2adutl utility with QUERY option to check if the image could be retrieved from TSM. If you are restoring a backup image taken from a different instance on a different server, make sure to use the options NODENAME, OWNER, and optionally PASSWORD corresponding to the TSM settings of the TSM node on which the backup image was originally taken. Once you have verified that the image could be retrieved, you could pass the same options in the options string of the RESTORE command.

SQL2543N

The application calling the Restore utility has supplied a target directory for the new database to be created. Either this directory does not exist, or is not a valid directory for database creation. An invalid directory for database creation would be a directory of greater than 215 characters in length.

Reissue the Backup or Restore command with a valid target directory.

SQL2544N

While the database was being restored the directory to which it was being restored had become full. The database being restored is unusable. The Restore terminates and if the database being restored is a new database, then it is deleted.

Free up sufficient space on the directory for the database, and reissue the Restore, or if restoring to a new database supply a directory with sufficient space to contain the database.

SQL2545W

The backup image is not immediately accessible by the TSM server. The restore process can continue and make the request to the server to retrieve the data. The time required is unknown.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2546N

During restore or load recovery, the first image from the backup or copy must be processed first. The image found on the media is not the first in sequence.

The utility waits for a response to continue.

Mount the media with the correct backup or copy image and return to the utility with the correct caller action parameter to indicate if processing should continue or terminate.

SQL2547N

The physical log file formats have changed between these releases, making rollforward impossible.

Restore the database using the version of DB2 used to create the database and rollforward to the end of logs. Take an off-line full database backup at this time. This new backup image will be restorable on the new release of DB2.

SQL2548N

If attempting to restore an image from a server with a newer FixPak level to a server with a lesser FixPak level, then ensure that the code page is supported by both servers. Alternatively, consider applying the newer FixPak to the server you are restoring to.

SQL2549N

The containers which were used by the table spaces in the backup image are not available, are already in use, or one or more table space names specified in the list on the restore command do not exist in the backup image.

Use redirected restore to redefine the containers for the table spaces in this backup image, or specify a list of valid table space names to restore. If this error occurs during the transport operation, it might be caused by containers already in use by a staging database from a failed transport operation. This will cause subsequent transport operations to fail when restoring to their staging databases. Drop any transport staging databases and re-issue the RESTORE DATABASE command.

SQL2550N

The backup image used for the restore is a backup of a database from a different node. You can only restore a backup to the same node.

Ensure that you have the correct backup image for the node then issue the request again.

SQL2551N

In an environment that is not a DB2 pureScale environment, the catalog node can exist on only one node. This message is returned when there is a discrepancy between the backup image and the node being restored to. This can occur in the following cases:

1. The backup image specified catalog node node1 and the restore was attempted to an existing database whose catalog node is node node2
2. The restore was attempted to a new database and the catalog node has not been restored first.

Verify that the correct backup image is being restored.

If you are restoring to an existing database and want to change the catalog node to node2, the existing database must be dropped first.

If you are restoring to a new database, restore the catalog node node1 first.

SQL2552N

The length of the report file name exceeded the allowed limit of 255.

Specify a report file name whose length is within the allowed limit and resubmit the restore command.

SQL2553I

The utility completed successfully.

No action necessary.

SQL2554N

SQL2555I

The backup that you used to restore the database is from a previous DB2 release. After you restored the database, it was upgraded to the DB2 release where you issued the RESTORE DATABASE command.

The user who issued the RESTORE DATABASE command is given DBADM authority to the database. If other users had DBADM authority prior to restore, the security administrator, who has SECADM authority, must grant DBADM authorization to these users.

The RESTORE DATABASE command was completed successfully. The UPGRADE DATABASE command issued automatically after the database restore was also completed successfully.

Perform post-upgrade tasks.

SQL2556W

A RESTORE DATABASE command was issued with the optional LOGTARGET path specified but the backup image did not contain all of the logs required for a successful rollforward recovery.

To successfully complete rollforward recovery, supply all of the required log extents from a log archive or other location.

SQL2560N

You can restore a database or restore one or more table spaces in a database from a backup image into a target database using the RESTORE DATABASE command or the db2Restore API.

There are some conditions that must be met to run a restore operation from a table space level backup. For example, the target database that is specified for the restore operation must meet one of the following conditions:

• The specified target database is the original database from which the backup image was taken.
• The specified target database. does not exist, and the rebuild option is specified in the restore command or API call.

This message is returned when an attempt is made to perform a database restore operation or a table space-level restore operation to a target database that is neither the original database from which the backup image was created nor a newly-created database.

Respond to this error in one of the following ways:

• Run the restore operation again, specifying a target database that is the original database from which the backup image was taken.
• Run the restore operation again, using the rebuild options and specifying a target database that does not exist.

SQL2561W

The RESTORE utility was issued with the REBUILD option and either specified a table space image to restore or specified a list of table spaces to restore from a backup image. If the database does not already exist, it will be created using the table spaces available for restore and the same database attributes as those in the image. If the database already exists, the database will be overwritten using the table spaces available for restore and based on the sqlcode returned with this warning.

If a subset of table spaces is restored from a non-recoverable database, the table spaces that were not part of the restore can never be recovered unless you do a complete database restore.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2563W

This message can be returned for different reasons, including the following examples:

• An error was encountered while accessing the containers of the table spaces.
• The restore command was invoked with a list of table spaces so that only a subset of the table spaces in the backup were restored.
• An attempt was made to restore table spaces that have file system caching enabled into containers on disks that do not support file system caching.

• If a disk-full error occured, increase the disk space and reattempt the restore. The db2diag.log contains details on which table space failed due to insufficient disk space. The db2diag.log also contains the path to which Db2 attempted to restore the table space. Use the db2ckbkp tool with the -T option to determine the size and target location of each table space.
• If the table spaces have been dropped since the backup was taken, no further action is necessary.
• If this message is not due to a subset restore, verify the status of the table spaces by running the LIST TABLESPACES command.
• If a table space is in the "storage definition pending" state, the storage definition for the table space must be corrected for restore to complete successfully.

SQL2565N

The database contained in the backup image is an existing database and does not match the database to be restored. The option you have specified for restore requires that the database being restored to is new or the same as in the backup image.

The utility stops processing.

Resubmit the command with the correct database name.

SQL2566W

One or more table spaces have tables in DATALINK Reconcile Pending (DRP) or DATALINK Reconcile Not Possible (DRNP) because of one of the following reasons:

• Restoring to a database that has a different database name, alias, hostname, or instance than the backup image. If no rollforward follows the restore, any tables with DATALINK columns are placed in DRNP state.
• Restore is done specifying the WITHOUT DATALINK option and no rollforward follows the restore. Any tables with DATALINK columns are placed in DRP state.
• Restoring from a backup image that has become unusable. If no rollforward follows the restore, any tables with DATALINK columns are placed in DRNP state.
• DATALINK column information does not exist at the DB2 Data Links Manager(s). Affected tables are placed in DRNP state.
• Restore involving fast reconciliation failed while trying to relink files at the DB2 Data Links Manager(s). Affected tables are placed in DRNP state.

Look in the administration notification log to find out what tables are put in DRP/DRNP state. See the Administration Guide for information on reconciling tables that are in DRP/DRNP state.

SQL2570N

Possible reason codes are:

1

target-OS and source-OS are not compatible systems.

2

A cross-platform restore of a compressed backup was attempted and no decompression library was specified. By default the library in the backup image from source-OS is used. This library is not suitable for a restore on target-OS.

3

A compression library-only restore was attempted on target-OS, a different operating system from the one on which the backup was taken (source-OS).

Responses for each reason code are:

1

To use this particular backup image, restore it on a system that is restore-compatible with the operating system on which the backup was taken. To move a database from one type of operating system to another, use the db2move utility.

2

Retry the Restore operation, specifying a decompression library that was compiled for target-os. For example, db2 restore db sample comprlib libdb2compr.a.

3

Do not attempt to restore a compression library on an operating system where it cannot be used.

SQL2571N

An error was encountered during the automatic restore process. This error occurred during an incremental restore or during a rebuild of a database from table space images or from a subset of table spaces in a database image. The utility was unable to complete as intended. The utility stops processing.

In the case of an incremental restore, this error is returned after the initial definitions have been restored and the processing of the required incremental restore set cannot be completed successfully.

In the case of a rebuild, this error is returned after the initial target image has been restored and the processing of the remaining required restore set cannot be completed successfully.

The error is a result of one of the following reason codes:

1

The backup image corresponding to the specified timestamp could not be found in the database history.

2

An error occurred trying to determine which table spaces to restore.

3

A required backup image could not be found in the database history.

4

The wrong rebuild type was specified for the incremental rebuild intended.

5

Cannot automatically restore only temporary table spaces.

If this is an incremental restore or an incremental rebuild, issue a RESTORE INCREMENTAL ABORT command to clean up any resources that may have been created during processing. Perform a manual incremental restore to restore the database from this backup image.

If this is a non-incremental rebuild then complete the rebuild, if necessary, by issuing table space restores against the remaining images required to rebuild the database as intended. See the diagnostic (db2diag) log files for additional information.

SQL2572N

Each tablespace in the backup image is aware of the backup image that must be restored before the backup image that failed can be successfully restored. You must restore the image with the timestamp reported in this message before you can successfully restore the image that invoked this message. There might be additional images to restore before the indicated image, but this was the first tablespace to encounter an error.

Ensure the order of the set of incremental backup images is correct and continue the incremental restore process.

SQL2573N

A RESTORE operation was attempted using an incremental backup image. An incremental backup cannot be restored on its own; it can be restored only as part of an incremental RESTORE operation.

The utility stops processing.

To restore this backup image, reissue the RESTORE command using the INCREMENTAL modifier. To perform a non-incremental RESTORE operation, specify a non-incremental backup image.

SQL2574N

The target image is the first image to be restored as part of an incremental RESTORE operation. This image contains the tablespace definitions and other control structures for the database that is being restored. The RESTORE utility cannot restore an image that is newer than the target image during an incremental RESTORE operation, because it could corrupt the database.

The incremental RESTORE operation failed because it attempted to restore a backup image with a timestamp that is more recent than the timestamp of the target image.

The utility stops processing.

Reissue the command, specifying a backup image with a timestamp that is older than the timestamp of the target image.

SQL2575N

To perform an incremental RESTORE operation, the backup images must be restored in chronological order of oldest to newest for each tablespace. An incremental RESTORE operation specified a backup image with a timestamp older than the timestamp of the previous image that was restored for the specified tablespace.

The utility stops processing.

Reissue the command, specifying a backup image with a timestamp that is newer than the timestamp of the last image that was restored for the tablespace.

SQL2576N

To perform a manual, cumulative restore operation you must issue the RESTORE command, specifying the INCREMENTAL clause, for each image involved in the restore operation.

This message is returned when the RESTORE command is issued without the INCREMENTAL clause, but the utility detects that a previous incremental restore operation has not completed.

To perform a manual, cumulative restore operation, issue the RESTORE command, specifying the INCREMENTAL clause, for each image involved in the restore operation.

To abort the current manual incremental restore operation, issue the RESTORE command, specifying the INCREMENTAL ABORT clause.

SQL2577N

The image being restored is a compressed backup, but no decompression library was specified and no library was found in the image.

The RESTORE utility requires a plug-in library to decompress the backup. This library is typically stored in the backup image itself, but in this case the creator of the backup chose to exclude the library. The library name can also be specified as a parameter to the RESTORE utility.

The utility stops processing.

Resubmit the command, specifying the name of a library that can decompress the data in the image.

SQL2578N

The specific object that was asked to be restored does not exist in the backup image.

The RESTORE utility attempted to restore a single object from the backup image. No object of this type exists in the backup image.

The backup history file and the decompression library are the objects that can be restored individually.

The utility stops processing.

Resubmit the command, specifying a backup image that does contain the object in question.

SQL2580W

The specified log target path contains at least one file with a name which matches the log filename format. If the restore operation later attempts to extract a log file of the same name, this will cause the restore to fail.

Either remove the existing log files from the log target path, or otherwise ensure that the files which exist in the log target will not match the filenames of any logs to be extracted from this backup image. Then return the utility with a callerac parameter indicating that restore processing should either continue or terminate.

SQL2581N

An error occurred while attempting to extract a log file from the backup image. This could be because one of the following reasons:

1

The backup image does not include logs.

2

The log target path specified could be full or invalid.

3

A log file name in the backup image matches a log file which already exists in the log target path.

4

There was an I/O error while trying to write the file.

5

The primary log directory on disk contains log files that will be destroyed by restore.

6

The mirror log directory on disk contains log files that will be destroyed by restore.

7

The default log directory of the existing database has logs that will be destroyed by the restore.

1

Check that the backup image contains log files to be restored. If it does not, resubmit the command without specifying the LOGTARGET parameter.

2

Check that the specified LOGTARGET path is valid and that there is enough space available for all log files in the backup image to be extracted. Resubmit the command.

3

Check that there are no existing log files in the log target path with the same name as log files in the backup image being restored. Resubmit the command.

4

See the diagnostic (db2diag) log files for additional information. Try to resolve the problem and resubmit the command.

5, 6, or 7

Do one of the following:

• Manually copy or move the log files from the primary log directory so you can archive those log files; and then call the RESTORE DATABASE command again.
• Call the RESTORE DATABASE command again with the LOGTARGET parameter and either the INCLUDE FORCE parameter or the EXCLUDE FORCE parameter.

SQL2582W

The RESTORE utility was issued with the REBUILD option but it has detected that a rebuild of the database is already in progress. If this operation were to take place then it would abort the current rebuild in progress and start a new one using this backup image as the target. The database will be overwritten.

Subsequent restore commands during the rebuild phase of the database should not be issued with the REBUILD option.

Return to the utility with the callerac parameter indicating processing to continue or end.

SQL2583N

The RESTORE utility has detected that a previous incremental restore operation has not completed. The intended restore command is not part of the previous incremental restore and cannot be processed unless the previous incremental restore is aborted.

The utility stops processing.

Issue a restore with the INCREMENTAL ABORT option and then reissue the intended restore command.

SQL2584N

Snapshot backup enables you to use fast copying technologies for the data copying and movement parts of DB2 database backup and restore operations.

The snapshot backup image must be restored as a whole. For this reason, when there are database logs in the snapshot backup image, they must be restored with the rest of the image.

There are database logs in the snapshot backup image you are restoring, so they must be restored with the rest of the image. However, the path for the given log directory shares a path or storage device with other paths or storage devices used by the database being restored.

It is not unusual for the path of the log directory to share a path or storage device with other database paths or storage devices. For example: when you create a database, the log directory is created under the main database directory by default. When a log path shares a path or storage device with other database paths or storage devices, a snapshot restore can not restore the log directory unless you specify the target location for the log directory using the LOGTARGET parameter.

The snaphot restore failed because you did not specify a LOGTARGET, or because you specified an invalid LOGTARGET.

Resubmit the RESTORE command using the LOGTARGET parameter.

SQL2585N

The backup image selected for restore is from an instance that does not match the current instance.

Snapshot backup images can only be restored to the same instance name they were taken from.

To find snapshot backup images that are available for the current instance, use the db2acsutil utility.

To restore a given snapshot backup image:

1. Move to the instance from which this snapshot backup image was taken.
2. Resubmit the command.

SQL2590N

An error occurred while using the RESTORE DATABASE command with the TRANSPORT option to transport table spaces and schemas from a database backup image to a target database. The following reason code indicates the error:

1

The list of table spaces and schemas being transported is not a valid transportable set.

2

The table spaces and schemas being transported contain tables with columns that are of a data type that is not supported with schema transport.

3

Table spaces or schemas already exists on the target database.

4

The list of table spaces and schemas being transported contains system catalogs. The system catalogs can not be transported.

5

All default staging databases are already in use.

6

Rollforward requires user interaction to resolve load copy recovery.

7

The backup image must contain the SYSCATSPACE table space.

8

Transport is not supported in partitioned database environments or in DB2 pureScale environments.

9

Transport is not supported when the source instance is an ESE instance and the target instance is a DB2 pureScale instance.

10

Attempting to increase LSN on target database failed.

12

Table space ID for schema transport cannot be reserved because another session of transport is already in progress.

13

Storage paths are dropped as table spaces are being reserved for schema transport.

14

A warning occurred when creating the staging database.

15

An error occurred on target database while transporting table spaces.

16

An error occurred on staging database while transporting table spaces.

17

Schema transport stopped because table space ID mapping is not resolved or validated. An error occurred in one of the following situations:

• Mapping table space IDs between the staging database and the target database.
• Validating table space IDs provided by the client against the server memory.
• The mapped table space is not valid.

18

Reason code 18 can be returned for two reasons:

• An attempt was made to perform a schema transport operation into a database that is configured to disallow non-logged operations.
• An attempt was made to specify the TRANSPORT INTO clause with the RESTORE command when restoring to a target database that is encrypted with DB2 native encryption.

19

Not all DDL objects in the transportable set can be created on the target database.

20

The specified backup image was created using an online backup operation, and the LOGTARGET parameter was not specified with the RESTORE command.

21

The table spaces and schemas being transported contain partitioned tables, which are not supported with schema transport.

Based on the reason code, perform the following actions:

1

Ensure that the table space list contains all objects that exist in the schema list and vice versa. See the db2diag log file for the failing object.

2

Respond to reason code 2 by performing the following steps:

1. Identify the columns that are defined as a data type that is not supported with schema transport by reviewing diagnostic details in the db2diag log files.
2. Remove the columns that are unsupported with schema transport by performing one of the following actions:
   • Drop the columns that are of an unsupported data type.
   • Drop the tables containing the columns that are of an unsupported data type.
   • Remove the table spaces and schemas containing the unsupported columns from the list of schemas to be transported.
3. Run the restore operation again.

3

You can perform one of the following actions to resolve the conflict with the table spaces or schemas and re-issue the RESTORE DATABASE command.

• Drop or rename the conflicting table spaces on the target database.
• Drop or rename the table spaces from the source database and create another backup image.
• Exclude the offending table spaces and schemas from the transportable set. When removing table spaces and schemas, you must ensure the remaining table spaces and schemas define a valid transportable set.

4

Remove the system table spaces from the table space list and re-issue the RESTORE DATABASE command again.

5

When re-issuing the RESTORE DATABASE command, you can either specify a non-default staging database name with the STAGE IN option, or wait for other transports to complete to free up a default staging database name.

6

Ensure that the rollforward logs do not include a load copy recovery operation.

7

Add the SYSCATSPACE tablespace to the backup image.

8

Ensure that the database is single node database that is not configured as a partitioned database environment or a DB2 pureScale environment.

9

Select a compatible backup image and re-issue the RESTORE DATABASE command.

10

Check db2diag.log for errors during attempt to increase LSN on target database.

12

Concurrent transport operations against any target database is not supported. Wait until the existing schema transport completes, then re-issue RESTORE DATABASE command.

13

Wait until schema transport completes, then re-issue operations that alter storage paths. Cleanup connections to the target database and drop the staging database. Re-issue the RESTORE DATABASE command.

14

Check db2diag.log for errors during creation of the staging database. Resolve errors, drop the staging database, then re-issue the RESTORE DATABASE command.

15

Check db2diag.log for errors on the target database. Resolve errors, drop the staging database, then re-issue the RESTORE DATABASE command.

16

Check db2diag.log for errors on the staging database. Resolve errors, drop the staging database, then re-issue the RESTORE DATABASE command.

17

Ensure that the transportable set does not contain any objects that have dependency on table spaces outside of the transportable set. For example, an object in the transportable set cannot have an index defined in another table space that is not included in the transportable set. Check db2diag.log for details on the cause of error. Resolve errors, drop the staging database, then re-issue the RESTORE DATABASE command.

18

Specify a target database that allows non-logged operations and that is not encrypted.

19

Some objects might be invalid or some dependencies might not exist. Check db2diag.log for details on the cause of error. Resolve errors, then re-issue the RESTORE DATABASE command.

20

Call the RESTORE command again, specifying the LOGTARGET parameter.

21

Respond to reason code 21 by performing the following steps:

1. Identify the partitioned tables by reviewing diagnostic details in the db2diag log files.
2. Remove the partitioned tables by performing one of the following actions:
   • Drop the partitioned tables.
   • Remove the table spaces that contain the partitioned tables from the list of table spaces to be transported.
3. Run the restore operation again.

SQL2600W

The pointer to the authorization structure parameter is NULL, the pointer to the authorization structure points to an area that is smaller than the length indicated in the structure length field, or the authorization structure length field is not set to the correct value.

The command cannot be processed.

Correct the value of the input parameter and resubmit the command.

SQL2650N

An invalid parameter was passed to a read log API. The possible reason codes are as follows:

01

Invalid action specified.

02

The starting log record identifier is greater than the current database active log record identifier.

03

The log record identifier range bounded by the starting and ending log record identifiers is not large enough to span a log record.

04

The starting log record identifier does not represent the start of an actual log record.

05

The starting log record identifier's location could not be determined.

06

The ending log record identifier is less than or equal to the starting log record identifier.

07

The buffer is not valid for the indicated size.

08

The buffer is not of sufficient size to store a log record.

09

A pointer is not valid.

10

The filter option is not valid.

11

The logfile path is not valid.

12

The overflow logfile path is not valid.

13

The retrieve logs option is not valid.

14

The specified number of bytes for memory allocation is too small.

15

The log sequence number is larger than can be contained by its respective API field.

16

The log record identifier type for piStartLRI is invalid.

17

The log record identifier types for piStartLRI and piEndLRI are not the same.

18

piStartTime is not supported for iCallerAction.

19

An invalid time stamp is specified for piStartTime.

20

The connected Db2 server version does not support a start time stamp.

21

The start time stamp could not be mapped to a LRI.

Based on the reason code, follow the instructions given:

01

Ensure that the action is either DB2READLOG_QUERY, DB2READLOG_READ, or DB2READLOG_READ_SINGLE.

02

Reduce the value of the starting log record identifier.

03

Ensure that the ending log record identifier is sufficiently larger than the starting log record identifier.

04

Ensure that the starting log record identifier is either the initial log record identifier or the next start log record identifier that is returned in the read log information structure.

05

Ensure that the starting log record identifier resides in a log extent in the database log path.

06

Ensure that the ending log record identifier is greater than the starting log record identifier.

07

Ensure that the buffer has been allocated and is of the size indicated by the log buffer size parameter.

08

Increase the size of the allocated buffer.

09

Ensure that memory has been correctly allocated and the pointers properly initialized.

10

Ensure that the filter option is either DB2READLOG_FILTER_OFF or DB2READLOG_FILTER_ON.

11

Ensure that the log path field is defined and points to a valid directory.

12

Ensure that the overflow log path field is defined and points to a valid directory.

13

Ensure that the retrieve option is either DB2READLOG_RETRIEVE_OFF, DB2READLOG_RETRIEVE_LOGPATH, or DB2READLOG_RETRIEVE_OVERFLOW.

14

Increase the number of bytes that can be allocated internally.

15

Use the latest version or level of the read log API, because the version in use possesses data type limitations for containing the log sequence number.

16

Ensure that the log record identifier type for piStartLRI is either DB2_READLOG_LRI_1 or DB2_READLOG_LRI_2.

17

Ensure that the log record identifier type for piStartLRI matches the log record identifier type for piEndLRI.

18

piStartTime is only supported with DB2READLOG_QUERY.

19

Provide a valid start time stamp for piStartTime and ensure that the Db2 server level supports the piStartTime parameter.

20

Ensure that the Db2 server version supports the piStartTime parameter, or update your application to not set the piStartTime field.

21

Provide a valid start time stamp for piStartTime and ensure the time stamp is recent. See the Db2 diagnostic log for further details.

SQL2651N

The asynchronous read log API was used against a connected database which does not have LOG RETAIN or USER EXITS ON. Only databases which are forward recoverable may have their associated logs read.

Update the database configuration for the database, identified to the asynchronous read log API, turning LOG RETAIN and/or USER EXITS ON.

SQL2652N

The allocation of internal structures and buffers that are used by the db2ReadLog or db2ReadLogNoConn API has failed.

Increase the amount of available memory that is available to the process (increase real or virtual memory, or remove unnecessary background processes).

SQL2653W

A Restore, Rollforward or Crash Recovery might have reused log sequence number ranges. The possible reason codes are as follows:

1

Restore has taken place.

2

Rollforward has taken place.

3

Crash Recovery has taken place.

No action is required.

SQL2654W

All log records in the database active log have been read by the asynchronous log reader.

No action is required.

SQL2655N

The Asynchronous Log Reader attempted to read log records from the specified log file. The specified log file is not associated with the database being asynchronously read.

Remove this log file from the database log directory. Move the correct log file into the database log directory and resubmit the call to the Asynchronous Read Log API.

SQL2656N

The Asynchronous Log Reader attempted to read log records from the specified log file. The specified log file has been corrupted and cannot be read.

Increase the start read log sequence and resubmit the call to the Asynchronous Read Log API to start reading after the specified log file.

SQL2657N

You can read log records from the DB2 database logs, or query the log manager for information about the current state of logs using the db2ReadLog API.

This message is returned when the db2ReadLog API is called, but the log reader cannot access log records from the indicated log file on the indicated log stream. One reason this can happen is because the log path was recently changed, using the newlogpath database configuration parameter, and the required log file is located in the old log path.

1. If log archiving is enabled, perform the following troubleshooting steps:
   1. Confirm whether database log files are successfully being archived and retrieved by looking for related errors in the db2diag log files.
   2. If there are error in the db2diag log files that indicate that log archiving is not functioning properly, troubleshoot and resolve the problems with log archiving.
2. Perform the following general troubleshooting steps:
   1. Determine the location of the log file for which the db2ReadLog API was searching, indicated in the run-time token log-file-name.
   2. Manually copy the required log file into the database log path (indicated by the logpath database configuration parameter.)
3. Resubmit the call to the db2ReadLog API.

SQL2701N

SQL2702N

The utility cannot read the configuration file config-file.

Please ensure the configuration file exists and is readable.

SQL2703N

The utility cannot open the log file log-file for writing or appending.

Please ensure the log file exists and is writable.

SQL2704N

The utility cannot read the input data file input-data-file.

Please ensure the input data file exists and is readable.

SQL2705N

The utility cannot read the input partitioning map file in-map-file.

Please ensure the input partitioning map file exists and is readable.

SQL2706N

The utility cannot open the output partitioning map file out-map-file for writing.

Please ensure the output partitioning map file is writable.

SQL2707N

The utility cannot open the distribution file dist-file for writing.

Please ensure the distribution file is writable.

SQL2708N

The utility cannot open the output data file out-data-file for writing.

Please ensure the output data file is writable.

SQL2709N

There is a syntax error in the specification of a keyword and its argument.

A keyword and its argument must be delimited by an '=' sign.

SQL2710N

There is an undefined keyword in the configuration file.

SQL2711N

The column delimiter (CDELIMITER) specified in the configuration file is not valid.

Make sure the column delimiter (CDELIMITER) is a single byte character.

SQL2712N

The string delimiter (SDELIMITER) specified in the configuration file is not valid.

The string delimiter (SDELIMITER) cannot be a period.

SQL2713N

The value for run type (RUNTYPE) specified in the configuration file is not valid.

Valid run type (RUNTYPE) can be either PARTITION or ANALYZE (case insensitive).

SQL2714N

The value for message level (MSG_LEVEL) specified in the configuration file is not valid.

Valid message level (MSG_LEVEL) can be either CHECK or NOCHECK (case insensitive).

SQL2715N

The value for check level (CHECK_LEVEL) specified in the configuration file is not valid.

Valid check level (CHECK_LEVEL) can be either CHECK or NOCHECK (case insensitive).

SQL2716N

The value for record length (RECLEN) reclen specified in the configuration file is not valid.

The record length (RECLEN) must be between 1 and 32767.

SQL2717N

The node specification (NODES) in the configuration file is not valid.

SQL2718N

The output node specification (OUTPUTNODES) in the configuration file is not valid.

SQL2719N

The output type (OUTPUTTYPE) in the configuration file is not valid.

Valid output types (OUTPUTTYPE) are W (write) or S (stdin), case insensitive.

SQL2720N

The number of partitioning keys defined cannot exceed the maximum limit: 256.

Remove one or more partitioning keys defined in the configuration file.

SQL2721N

 PARTITION=<key name>,
           <position>,
           <offset>,
           <len>,
           <nullable>,
           <datatype>

If a delimited-data file, <position> must be defined; otherwise, <offset> and <len> must be defined.

SQL2722N

The log file specification (LOGFILE) in the configuration file is not valid.

<log type> can only be W (write) or A (append), case insensitive.

SQL2723N

The trace specification (TRACE) in the configuration file is not valid.

The trace specification (TRACE) must be a positive integer between 0 and 65536 (exclusive).

SQL2724N

The node list specification is not valid.

One and only one of the two parameters: NODES and MAPFILI (input partition map) must be specified in the configuration file.

SQL2725N

If run type is ANALYZE, a filename for the output partition map must be defined.

Specify a filename for the output partition map.

SQL2726N

At least one partitioning key must be defined.

Specify one or more partitioning keys.

Altering the distribution key can only be done to a table whose table space is associated with a single-partition database partition group.

You can add or drop distribution keys, using the ALTER TABLE statement.

SQL2727N

For non-delimited data, starting position for a key must be less than the record length.

Make sure starting position for a key is less than the record length.

SQL2728N

Output node list must be a subset of the node list, which is derived from NODES or the input partition map file.

Make sure all output nodes are defined in the node list.

SQL2729N

There is at least one error in the partitioning map file.

The specific error is indicated by the reason code:

1

The partitioning map file cannot be read.

2

The number of values in the partitioning map file is not 1 or 32768.

3

The node number in the partitioning map file is not between 0 and 999.

4

The data in the partitioning map file is not in a valid format.

1

Check file permissions for the partitioning map file. Also, check that another program has not deleted or altered the partitioning map file.

2

Ensure that the partitioning map file contains only a single value (if the resultant database partition group is a single-partition database partition group) or exactly 32768 values (if the resultant database partition group is a multipartition database partition group).

3

Ensure that the node numbers are in the range of greater than or equal to 0 and less than or equal to 999.

4

Ensure that the values in the partitioning map file are integers greater than or equal to 0.

SQL2730N

An I/O error occurred while writing the header to an output data file.

Check your operating system documentation for file I/O errors and ensure that there is sufficient space on the output device.

SQL2731N

An I/O error occurred while reading from input data file.

Check your operating system documentation for file I/O errors.

SQL2732N

Binary data is not permitted on the host versions of this utility program.

Check your input data file.

SQL2733N

The run type (RUNTYPE) must be defined as either PARTITION or ANALYZE.

Please specify run type (RUNTYPE) in the configuration file.

SQL2734N

The specification for parameter 32KLIMIT in the configuration file is not valid.

Parameter 32KLIMIT can be either YES or NO, case insensitive.

SQL2735W

The record rec-no of the input data is discarded because it contains nothing but spaces.

Check record rec-no in the input data file.

SQL2736N

Partitioning key fields contain invalid data.

Check the input data file at line line.

SQL2737N

An I/O error occurred while writing a record to the output data file for node out-node.

Check your operating system documentation for file I/O errors and ensure that there is sufficient space on the output device.

SQL2738W

Expected writing length (RECLEN) does not match the actual writing length.

Adjust record length value defined in the configuration file.

SQL2739N

If a binary numerical input data file, the record length has to be defined.

Please specify the record length in your configuration file.

SQL2740N

Float data type is only supported when the file type is BIN (binary).

Make sure data types and the type of input data file match.

SQL2741N

The file type specification (FILETYPE) in the configuration file is not valid.

All the values are case insensitive.

SQL2742N

In a binary input data file, the length of a partition key with decimal data type must conform to the equation: LENGTH=(PRECISION+2)/2 (integer division), because it is a packed decimal.

Match the length of a decimal-typed partition key with its precision if the input data file is a binary data file.

SQL2743N

In a binary input data file, the length of a partition key with integer, small integer, float, and double data type must be a predefined constant, i.e. 4 for integer, 2 for small integer, 4 for float, and 8 for double.

Check partition key definitions in the configuration file.

SQL2744N

The maximum length for a file name is 80 bytes.

Check the configuration file.

SQL2745N

The NEWLINE flag must be either YES or NO, and if not given, it is NO.

Check the specification of NEWLINE flag in the configuration file.

SQL2746N

If a fixed-length positional ASC file or a binary numerical data file, each record has to be exactly the same length as the value of the RECLEN parameter in the configuration file.

Make sure the input data file is complete.

SQL2747N

For a positional ASC input data file or a delimited data file with parameter 32KLIMIT on, the maximum record length can not exceed the 32k (bytes) limit.

Check your input data file and make sure the record length is less than 32k bytes.

SQL2748N

For a positional ASC input data file or a binary numerical data file, each record has to be long enough to hold all partitioning keys.

Check the record length of your input data file.

SQL2749N

If a record is greater than 32k bytes long in a delimited data file, all partitioning keys of each record have to be within the first 32k bytes of the record.

Check record rec-no in the input data file.

SQL2750N

The maximum length of a line in the configuration file must be less than 255 bytes.

Check your configuration file and make sure all lines are less than 255 bytes.

SQL2751N

If new line checking is required for a fixed length ASC data file (NEWLINE parameter is YES and RECLEN parameter is not zero), the actual length of each record has to match the expected record.

Check record rec-no in the input data file.

SQL2752N

The codepage specification is not valid. It must be a positive integer.

Correct the codepage specification in the configuration file.

SQL2753N

The program failed to get the territory code and codepage of its environment.

Check with your database system administrator.

SQL2754N

The database does not support codepage conversion between those two codepages.

Please ensure your data is in a convertible codepage.

SQL2755N

Valid format of decimal data is SQL_PACKEDDECIMAL_FORMAT, SQL_CHARSTRING_FORMAT, or SQL_IMPLIEDDECIMAL_FORMAT, mutually exclusive.

Verify the format of your decimal data, correct the format value, and resubmit the command.

SQL2756N

A cluster caching facility (CF) structure is a memory resource for a database in a DB2 pureScale environment. The CF structures include Group Buffer Pool (GBP), Shared Communication Area (SCA), and Lock (LOCK). The corresponding configuration parameters for CF structures are CF_GBP_SZ, CF_SCA_SZ, and CF_LOCK_SZ, respectively.

The database configuration parameter named CF_DB_MEM_SZ controls the total CF memory limit for this database. All CF structure memory is included within this limit.

If the value of the database configuration parameter named parameter-name exceeds the parameter value of CF_DB_MEM_SZ, the request cannot be completed and the operation will time-out.

This message is returned when an update to CF structure memory has not completed and another request is made to update the memory for the same CF structure.

View the update request that is pending for the CF structure using the GET DB CFG command with the SHOW DETAIL clause.

Ensure the values for memory of all CF structures are lower than the value of CF_DB_MEM_SZ.

Wait for the update request that is pending to complete or time-out.

sqlcode: -2756

sqlstate: 5U052

SQL2761N

Specify either the table name or the database partition group name, but not both.

Check your command line options.

SQL2762N

The utility needs to know where the database manager is installed, then it can find its bind file.

Make sure your database manager is properly installed.

SQL2763N

The table tbl-name cannot be located in sysibm.systables.

Make sure the table exists in the database.

SQL2764N

The database partition group db-partition-group cannot be located in SYSCAT.DBPARTITIONGROUPDEF.

Make sure the database partition group exists in the database.

SQL2765W

The utility cannot open the output partition map file for writing. It will write the output to stdout.

Check your file access permissions.

SQL2766N

The size of the partition map is not correct. Data is corrupted in the database.

Contact the Database Administrator to resolve the problem.

SQL2767N

There is an invalid command line option.

Make sure to specify the correct command line options.

SQL2768N

The distribution map has been expanded from 4096 entries to 32768 entries, and cannot be returned by the deprecated API.

Use the replacement API instead of the deprecated API.

SQL2796N

While running the load utility in the LOAD_ONLY partitioning mode, data file records were found that do not match the database partition that the records were being loaded into.

Verify the records in the data file for each database partition and ensure that each record is being loaded in the intended database partition. You can accomplish this task by placing the records in a separate file and invoking the load utility against it using the PARTITION_ONLY partitioning mode. By doing this, records will be grouped by their destination database partition.

SQL2800N

The utility failed to add, drop, or change the database partition because the input parameters specified are invalid as indicated by the reason code:

1

The database partition number is not specified

2

The TCP/IP host name is not specified

3

The computer name is not specified

4

The database partition number is invalid.

5

The port number is invalid.

6

The TCP/IP host name is invalid.

7

The port value is not defined for your instance in the services file.

8

The port value is not in the valid range defined for your instance in the services file.

9

The database partition number is not unique.

10

The host name/port couple is not unique.

11

The host name value has no corresponding port 0.

The action corresponding to the reason code is:

1

Ensure that the database partition number is specified

2

Ensure that the TCP/IP host name is specified

3

Ensure that the computer name is specified

4

Ensure that the database partition number is between 0 and 999.

5

Ensure that the port number is between 0 and 999.

6

Ensure that the host name specified is both defined on the system and is operational

7

Ensure that the TCP/IP services on your system contains an entry for your instance

8

Ensure that you only use port values that are specified in the services file on your system

9

Ensure that the database partition number specified is unique.

10

Ensure that the new host name/port is not already defined in the db2nodes.cfg file.

11

Ensure that the port value 0 has been defined for host name specified.

SQL2801N

Enter the command again using valid parameters.

SQL2802N

Issue the DB2NCHG command with one of the valid command options.

SQL2803N

Issue the DB2NDROP command with one of the valid command options.

SQL2804N

Issue the DB2NLIST command with one of the valid command options.

SQL2805N

An error has occurred during an attempt to create, drop, or add a database partition. The reason code indicates the reason for the error:

1

Unable to register the service

2

Unable to set the required User Rights Policy

3

Unable to set the Logon Account for the service

4

Unable to delete the service

The action corresponding to the reason code is:

1

If the workstation name is specified during DB2NCRT, ensure that the workstation name is correct.

2

Ensure that the user name specified is valid.

3

Ensure that the user name and the password specified are valid.

4

If the database partition resides on another machine, ensure that the machine is running.

SQL2806N

DB2NDROP failed because the node does not exist.

Ensure the node number is correct and reissue the command.

SQL2807N

DB2NCRT failed because the node already exists.

Ensure the node number is correct and reissue the command.

SQL2808W

The DB2NDROP processing has completed successfully.

No further action is required.

SQL2809W

The DB2NCRT processing has completed successfully.

No further action is required.

SQL2810W

The DB2NCHG processing has completed successfully.

No further action is required.

SQL2811N

The command is only valid if the instance is a partitioned database instance.

Ensure that the specified instance name is valid. If the instance name is not specified on the command line, ensure that the DB2INSTANCE environment is set to a valid partitioned database instance.

SQL2812N

Enter the command again using valid arguments.

SQL2813I

The drive mapping was added successfully.

No action necessary.

SQL2814I

The drive mapping was deleted successfully.

No action necessary.

SQL2815I

Informational message.

No action necessary

SQL2900W

The ingest utility uses the distribution key to determine the partition number and routes input records to one of that partition's flushers. Because of the condition that the reason code specifies, the ingest utility will route records to a random flusher. The reason codes are:

1

The NUM_FLUSHERS_PER_PARTITION configuration parameter was set to 0, so there is only 1 flusher for all partitions.

2

The target table is a type that does not have a distribution key.

3

At least one of the distribution key columns has a type that is a user-defined type (UDT) or a DB2SECURITYLABEL.

4

If the SQL statement is INSERT or REPLACE, the column list does not specify all the distribution key columns. If the SQL statement is UPDATE, DELETE, or MERGE, the WHERE or ON clause does not specify all the distribution key columns.

5

If the SQL statement is INSERT or REPLACE, a value in the VALUES list is not a field name or constant. If the SQL statement is UPDATE, DELETE, or MERGE, one or more of the following is true:

• The comparison to a distribution key column is not an equality comparison.
• The value compared to a distribution key column is not a field name or constant.
• The distribution key column corresponds to more than one field name or constant.

6

The SQL statement is UPDATE, DELETE, or MERGE and the WHERE or ON clause is not of the form:

(dist-key-col1 = value1) AND (dist-key-col2 = value2) AND ... (dist-key-colN = valueN)

where dist-key-col1 to dist-key-colN includes all the distribution key columns and each value is a field name or constant.

7

There is at least one distribution key column that has a numeric type, but its corresponding field does not have the exact same numeric type, including the same precision and scale.

If this has a negative performance impact, modify the configuration parameter or INGEST command, depending on the reason code:

1

Set the NUM_FLUSHERS_PER_PARTITION configuration parameter to 1 or greater.

2

Specify a target table that has a distribution key.

3

Specify a table whose distribution key does not contain a column whose type is a user-defined type (UDT) or a DB2SECURITYLABEL.

4

Ensure that all distribution keys are specified on the SQL statement and that each distribution key corresponds to exactly one field.

5

Ensure that all of the following are true:

• For INSERT or REPLACE statements, all value in the VALUES list are field names or constants.
• For UPDATE, DELETE, or MERGE statements:
  • Any comparison to a distribution key column is an equality comparison.
  • Any value compared to a distribution key column is a field name or constant.
  • Any distribution key column corresponds to one field name or constant.

6

Change the WHERE predicate or the ON predicate that it specifies all distribution key columns and it is of the form:

(dist-key-col1 = value1) AND (dist-key-col2 = value2) AND ... (dist-key-colN = valueN)

where dist-key-col1 to dist-key-colN includes all the distribution key columns and each value is a field name or constant.

7

Change the field definitions so that each field that corresponds to a numeric distribution key column has the exact same type as the distribution key column, including the same precision and scale.

SQL2901I

The ingest utility completed successfully, but returned some errors or warnings. Refer to the specified messages file to determine what those errors or warnings are.

The number of errors includes errors from which the utility could not recover, but does not include errors from which the utility recovered.

If you do not want to receive this message in the future, correct the cause of the errors or warnings.

SQL2902I

The ingest utility completed successfully, but returned some errors or warnings.

The number of errors includes errors from which the utility could not recover, but does not include errors from which the utility recovered.

If you do not want to receive this message in the future, correct the cause of the errors or warnings.

SQL2903W

The INGEST SET or INGEST command completed successfully, but a user-specified configuration parameter was overridden. If this message is issued for an INGEST SET command, the overriding value remains in effect for the remainder of the CLP session. If this message is issued for an INGEST command, the overriding value remains in effect only for the INGEST DATA command.

The explanation corresponding to the reason code is:

1

The commit_count and commit_period configuration parameters cannot be set to 0 on the same INGEST command. commit_period has been set to 1.

2

The commit_count configuration parameter must be set to a multiple of 1000, so it has been rounded to the nearest multiple of 1000.

3

The commit_count configuration parameter has been reduced because either the lock list or the transaction log ran out of space. The new value is the number of rows that had been committed right before the lock list or transaction log ran out of space.

4

The commit_period configuration parameter has been has been reduced because either the lock list or the transaction log ran out of space. The new value is the number of seconds between the time of the last commit and the time when the lock list or transaction log ran out of space.

10

The num_flushers_per_partition configuration parameter has been adjusted to 0 because one of the following is true:

• For an UPDATE operation, there are no appropriate columns in the search key, or all columns in the search key are also in the update key (specified on the SET clause).
• For a DELETE operation, there are no appropriate columns in the search key.

The search key is the set of all columns c1, c2, ... specified on a WHERE or ON clause of the form:

(c1 = $field_1) AND (c2 = $field_2)
    AND ... (cn = $field_n)
   [AND (<any other conditions<)]

(The last AND condition enclosed in square brackets is optional.)

11

The num_flushers_per_partition configuration parameter has been adjusted to 0 in a partitioned database environment because at least one column in the table's distribution key is also in the update key (specified on the SET clause).

12

The num_flushers_per_partition configuration parameter has been adjusted to 1 because there is no index that contains at least one column that is in the search key (specified on the WHERE clause) but not in the update key (specified on the SET clause).

14

The num_flushers_per_partition configuration parameter has been adjusted to the value of the max_connections database manager configuration parameter because it cannot be greater than max_connections.

15

The num_flushers_per_partition configuration parameter has been adjusted to floor(128/(number of members)) because the target table is a column-organized table. Column-organized tables are structured such that the maximum ingest performance is achieved when a total of 128 parallel insert threads are employed over all members.

16

The num_flushers_per_partition configuration parameter has been adjusted to 50 because the target table is a column-organized table. Column-organized tables are structured such that the maximum ingest performance is achieved when 50 parallel insert threads are employed.

The user response corresponding to the reason code is:

1

To avoid receiving this message, do not set commit_period to 0 if you are leaving commit_count at its default value of 0.

2

To avoid receiving this message, set commit_count to a multiple of 1000.

3

To avoid receiving this message, do one or more of the following:

• If the warning occurred because the lock list ran out of space, increase the locklist or maxlocks database configuration parameters.
• If the warning occurred because the transaction log ran out of space, increase the logfilsiz, logprimary, or logsecond database configuration parameters.
• Reduce the commit_count configuration parameter to the new value or a lower value

4

To avoid receiving this message, do one or more of the following:

• If the warning occurred because the lock list ran out of space, increase the locklist or maxlocks database configuration parameters.
• If the warning occurred because the transaction log ran out of space, increase the logfilsiz, logprimary, or logsecond database configuration parameters.
• Reduce the commit_period configuration parameter to the new value or a lower value

10

To avoid receiving this message, do one of the following:

• Before issuing the INGEST command, set the ingest configuration parameter num_flushers_per_partition to 0.
• If there are no appropriate columns in the search key, change the SQL statement on the INGEST command to specify a search key of the form:

  
  (c1 = $field_1) AND (c2 = $field_2)
       AND ... (cn = $field_n)
  

• If all columns in the search key are also in the update key, change the search key or the update key so that the search key does not contain all the columns in the update key.

11

To avoid receiving this message, do one of the following:

• Before issuing the INGEST command, set the ingest configuration parameter num_flushers_per_partition to 0.
• Change the SQL statement on the INGEST command so that it does not update any of the columns in the table's distribution key.

12

To avoid receiving this message, do one of the following:

• Before issuing the INGEST command, set the ingest configuration parameter num_flushers_per_partition to 1.
• Define an index that includes at least one column that is in the search key but not in the update key.

14

To avoid receiving this message, do one of the following:

• Before issuing the INGEST command, issue the INGEST SET command to set the num_flushers_per_partition configuration parameter to a value that is less than or equal to the max_connections database manager configuration parameter.
• Set the max_connections database manager configuration parameter to AUTOMATIC or a value that is greater than or equal to the num_flushers_per_partition configuration parameter.

15

To avoid receiving this message, do one of the following:

• Before issuing the INGEST command, issue the INGEST SET command to set the num_flushers_per_partition configuration parameter to a value that is less than or equal to the max_coordagents database manager configuration parameter.
• Set the max_coordagents database manager configuration parameter to AUTOMATIC or a value that is greater than or equal to the num_flushers_per_partition configuration parameter.

16

To avoid receiving this message, before issuing the INGEST command, issue the INGEST SET command to set the num_flushers_per_partition configuration parameter to floor(128/(number of members)) or lower.

SQL2904W

The specified field has a value that is longer than the field's length. The value has been truncated. For example, if the field is defined as CHAR(3) but the value is "ABCDEF", the value is truncated to "ABC".

If the truncation is acceptable, no further action is required. To avoid this message, specify a longer field length on the INGEST command or edit the input data so that the length of the field value is less than or equal to the length of the field.

SQL2905I

This message provides the identification of the line and input file where the error occurred for the following message listed.

The table is either the one specified on the SQL statement of the INGEST command or the exception table. If the table is the one specified on the SQL statement, and the SQL statement is INSERT or REPLACE, and the INGEST command specified an exception table, the ingest utility attempts to insert the record into the exception table. Otherwise, the ingest utility discards the record.

If the error occurred issuing the SQL statement on the target table of the INGEST command and the ingest utility successfully inserted the row into the exception table, correct the data in the exception table and copy it from the exception table to the target table. Otherwise, verify that the data on the specified line in the input file is correct. If needed, correct the data in the input file and re-run the ingest utility using an input file with only the corrected lines.

SQL2906I

This message provides the identification of the line and input pipe where the error occurred for the following message listed.

The table is either the one specified on the SQL statement of the INGEST command or the exception table. If the table is the one specified on the SQL statement, and the SQL statement is INSERT or REPLACE, and the INGEST command specified an exception table, the ingest utility will attempt to insert the record into the exception table. Otherwise, the ingest utility will discard the record.

No action is required.

SQL2907I

This message provides the identification of the line and input TCP/IP port where the error occurred for the following message listed.

The table is either the one specified on the SQL statement of the INGEST command or the exception table. If the table is the one specified on the SQL statement, and the SQL statement is INSERT or REPLACE, and the INGEST command specified an exception table, the ingest utility will attempt to insert the record into the exception table. Otherwise, the ingest utility will discard the record.

No action is required.

SQL2908I

This message provides the identification of the input pipe where the error occurred for the following message listed.

No action is required.

SQL2909I

This message provides the identification of the input TCP/IP port where the error occurred for the following message listed.

No action is required.

SQL2910N

When modifiers are specified on a field, they must be specified on all fields that have a similar type. For example: If a decimal field specifies RADIX POINT, the same RADIX POINT character must be specified on all other INTEGER, DECIMAL, DECLFOAT, and FLOAT fields. If a format string is specified on a DATE field, the same format string must be specified on all other DATE fields. If an INTEGER field specifies EXTERNAL, then EXTERNAL must be specified on all other INTEGER, DECFLOAT, and FLOAT fields. (Fields of type DECIMAL, however, can specify PACKED or ZONED. But all fields of type DECIMAL must specify the same EXTERNAL, PACKED, or ZONED modifier as all other DECIMAL fields.)

Reissue the INGEST command, specifying the modifiers on all fields of a similar type.

SQL2911N

The INGEST command specified a binary field type, but the input file format is not POSITIONAL. The command failed.

One of the following:

• If the input data is in delimited format, change the field type to one that specifies character data. For example, if the field type is INTEGER, change it to INTEGER EXTERNAL. If the field type is DB2SECURITYLABEL, change it to DB2SECURITYLABEL NAME or DB2SECURITYLABEL STRING.
• If the input data is in positional format, change the INGEST command to specify FORMAT POSITIONAL. If needed, add the POSITION clause to each field definition.

SQL2912N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. If any input fields are a binary data type, the length of those binary fields must be specified with the INGEST command or db2Ingest API call.

This message is returned when an attempt is made to ingest data that contains binary fields and the length of those binary fields is not specified.

Perform the ingest operation again, specifying the length of any binary fields.

SQL2913N

INGEST commands that specify FORMAT POSITIONAL must specify or imply the field length, or the POSITION parameter must specify the end position. The command failed.

Reissue the INGEST command and specify either the end position of the field or the field length.

SQL2914I

The ingest utility is starting. The job ID is the one specified on the RESTART parameter or if none was specified, a default job ID that the utility generated. The job ID can be used on the INGEST GET STATS command while the INGEST command is running. If the INGEST command fails, the job ID can be used on a later INGEST command with the RESTART CONTINUE or RESTART TERMINATE parameter.

Save the job ID in case it is needed for a later command.

SQL2915N

The length specified by RECORDLEN on the INGEST command must be greater than or equal to the sum of the field lengths specified on each field definition. The command failed.

Correct the field lengths or the RECORDLEN parameter.

SQL2916N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. How the ingest utility modifies the target table is controlled by specifying an SQL statement with the INGEST command or db2Ingest API call.

This message is returned when an attempt is made to perform an ingest operation with an SQL statement that references no fields.

Modify the SQL statement to include at least one field, and then perform the ingest operation again.

SQL2917N

You can specify the maximum size of Inter Process Communication (IPC) shared memory by setting the SHM_MAX_SIZE ingest utility configuration parameter.

This message is returned when the ingest operation fails because the SHM_MAX_SIZE configuration parameter is not large enough.

1. Set the SHM_MAX_SIZE configuration parameter to a larger value (by issuing the INGEST SET command, for example.)
2. Run the ingest operation again.

SQL2918N

The INGEST command failed because of an invalid combination of keywords.

Remove the conflicting keywords and reissue the command.

SQL2919N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can stream data into multiple types of tables, including the following examples:

• Multidimentional clustering tables
• Materialized query tables
• Partitioned tables
• Others

This message is returned when an attempt is made to ingest data into a type of table that the ingest utility does not support.

Perform the ingest operation again, specifying a supported table type.

SQL2920N

An INGEST command that specifies an SQL statement that uses a WHERE or ON clause must include a search condition that specifies at least one field. The command failed.

Reissue the INGEST command specifying a search condition.

SQL2921N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify to the ingest utility how the data is defined in the input stream by describing the fields into which the data is separated.

This message is returned when an attempt is made to perform an ingest operation with an SQL statement that references a data field that does not exist in the input source data.

Perform the ingest operation again, specifying fields that correspond to the fields in the input data stream.

SQL2922I

This message provides the identification of the input file where the error occurred for the following message listed.

No action is required.

SQL2923N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify the data type of input fields when you invoke the ingest operation.

This message is returned when an invalid field type is specified.

Perform the ingest operation again, specifying a supported field type.

SQL2924N

Fields that specify the DEFAULTIF parameter cannot be used in a predicate or in an expression. The command failed.

Change how the field is used in the SQL statement or remove the DEFAULTIF parameter, and reissue the command.

SQL2925N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can cause the ingest utility to insert a default value into the target table whenever a certain character appears in the input data by using the DEFAULTIF parameter.

If the DEFAULTIF parameter is specified with a field definition, the column that corresponds to that field must have a default value.

This message is returned when the DEFAULTIF parameter is specified but the corresponding target table column does not have a default value.

Respond to this message in one of the following ways:

• If inserting a default value is not required, remove the DEFAULTIF parameter from the field definition and then perform the ingest operation again.
• If inserting a default value is required, change the SQL statement so that the field corresponds to a column that has a default value, and then perform the ingest operation again.

SQL2926N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can cause the ingest utility to insert a default value into the target table whenever a certain character appears in the input data by using the DEFAULTIF parameter.

If the DEFAULTIF parameter is specified with the ingest utility, the default value of the corresponding target table column must be a constant or NULL.

This message is returned when the DEFAULTIF parameter is specified but the default value of the corresponding target table column is neither constant nor NULL.

Change how the field is used in the SQL statement or remove the DEFAULTIF parameter, and resubmit the ingest operation.

SQL2927N

There might be a data type mismatch because the value in the specified field cannot be converted to the field's data type.

Correct the input file or change the field's type, and reissue the command.

SQL2928N

You can stream data from files and pipes into DB2 database tables by using the ingest utility.

This message is returned when an attempt is made to invoke the ingest utility, but the specified input source is not a file or named pipe.

Perform the ingest operation again, specifying a valid input source.

SQL2931N

You can stream data from files and pipes into DB2 database tables by using the ingest utility.

This message is returned when the ingest utility could not open, read from, or close the specified input file or named pipe.

Verify the input source and then perform the ingest operation again, specifying a valid input source.

SQL2932N

The ingest utility failed to allocate an interprocess IPC resource after the specified number of attempts. The resource type can be one of the following:

1. Shared memory
2. Listener queue
3. Semaphore

This message normally follows earlier messages that indicate the error or errors that occurred when trying to allocate the resource.

Examine previous error messages to determine the errors that occurred. Correct the errors and re-run the INGEST command. On Linux and UNIX, if there are not enough system resources to allocate the IPC resource, use the ipcrm command to remove existing IPC resources.

SQL2933N

The INGEST command failed.

If the parameter is PIPE_TIMEOUT, the INGEST command did not receive any data from the pipe for at least the specified number of seconds after the command opened the pipe.

Verify there is not a problem with the data source that is preventing it from sending data within the specified time. If the data source needs more time to send data, increase the value of the relevant configuration parameter, or set it to 0 so there is no timeout.

SQL2934N

The port number specified (or resolved to) in the INGEST command must be within the allowable range. The INGEST command failed.

Reissue the INGEST command, specifying a port within the allowable range or a service name that maps to a port number that is within the range.

SQL2935W

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify the properties such as data type or length of input fields when you invoke the ingest operation.

When a field has a value that is longer than the defined length of the field, the value will be truncated. For example, if the field is defined as CHAR(3) but the value is "ABCDEF", the value is truncated to "ABC".

This message is returned when an input field has a value that is longer than the defined length of the field.

If the truncation is acceptable, no further action is required.

To avoid this message, take one of the following actions:

• Specify a longer field length with the INGEST command or the db2Ingest API call.
• Edit the input data so that the length of the field value is less than or equal to the length of the field.

SQL2936N

The INGEST command cannot use that port because it is being used by another running application. The INGEST command failed.

Reissue the INGEST command, specifying a port that is not in use.

SQL2937N

The INGEST command specified the DEFAULTIF clause, but the input file format is not POSITIONAL. The command failed.

One of the following:

• If the input data is in delimited format, remove the position specification from the DEFAULTIF clause.
• If the input data is in positional format, change the INGEST command to specify FORMAT POSITIONAL. If needed, add the POSITION clause to each field definition

SQL2938N

The field specification for locating the input data for the indicated database column within the input non-delimited ASCII file is not valid for the reason indicated by the following reason codes:

1

The start position is 0.

2

The end position is less than the start position.

3

The end position is greater than 32 767.

4

Fields of type SMALLINT, INTEGER, BIGINT, DECIMAL, REAL, FLOAT, and DECFLOAT with the EXTERNAL modifier have a maximum length of 50.

5

If a format string is specified for fields of type DATE, TIME, and TIMESTAMP(p), the field length must be greater than or equal to length of the shortest value that matches the format string.

6

If a format string is not specified:

• For DATE fields, the field length must be between 8 and 10, inclusive.
• For TIME fields, the field length must be between 4 and 8, inclusive.
• For TIMESTAMP fields, the field length must be between 19 and 32, inclusive.

The INGEST command failed.

Follow the action indicated by the reason code and resubmit the command:

1

Specify a start position that is greater than 0.

2

Specify an end position that is greater than the start position.

3

Specify an end position that is less than or equal to 32 767.

4

Change the field length to a value less than or equal to 50.

5

Shorten the format string so that the length of shortest value that matches the format string is less than or equal the field length, or change the field length to a value greater than or equal to the the length of shortest value that matches the format string.

6

Change the field length to a value within the ranges given in the explanation of reason code 6.

SQL2939N

The current value for the indicated command parameter is not valid because it is outside the allowable range.

The command failed.

Reissue the command, specifying a value for the command parameter that is within the allowable range.

SQL2940N

The ingest utility does not support ingesting data into tables that are on versions of the database server earlier than the version shown in the message.

Connect to a database server whose version is the same as or later than the version shown in the message and re-run the utility.

SQL2941N

The field type on the field definition specifies a length, precision, or scale that is not valid. Examples of this error are:

• A field definition that specifies CHAR(70000) is not valid because the maximum length of a field is 32767.

Correct the length, precision, or scale on the field definition.

SQL2942N

When a field definition specifies DEFAULTIF, the field must be assigned to one and only one column and cannot be part of an expression that is assigned to that column. For example, consider the following INGEST command:

INGEST FROM FILE my_file.txt FORMAT DELIMITED
  ...
  UPDATE my_table
  SET (c1, c2, c3, c4, c5) =
      ($field1, $field2, $field2,
          $field3, $field4+$field5)
  WHERE $field3 = 1;

Only $field1 can specify DEFAULTIF. $field2 cannot because it is assigned to multiple columns. $field3 cannot because it is also used in a predicate. $field4 and $field5 cannot because they are used in an expression.

Remove the DEFAULTIF modifier or change the SQL statement so that the field is assigned to one and only one column and is not part of an expression assigned to that column.

SQL2943N

When either of the following is true, the ingest utility cannot insert into or update the table:

• The SQL statement on the INGEST command is INSERT (including as part of a MERGE statement) and one of the following is true:
  • All the columns specified after the table name are defined as GENERATED ALWAYS.
  • No columns are specified after the table name, but all the table's non-hidden columns are defined as GENERATED ALWAYS.
• The SQL statement on the INGEST command is UPDATE (including as part of a MERGE statement) and all the columns specified on the SET clause are defined as GENERATED ALWAYS.

Change the command to specify at least column that is not defined as GENERATED ALWAYS.

SQL2944N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. How the ingest utility modifies the target table is controlled by specifying an SQL statement with the INGEST command or db2Ingest API call.

When the ingest utility is used with an INSERT statement that does not have a VALUES clause, the number of fields must be the same as the number of specified or implied table columns. (The number of implied columns is the number of non-hidden columns in the table.)

For example, the following INGEST command is not valid because two fields are specified but there are three columns:

INGEST FROM FILE my_file.del FORMAT DELIMITED
  ($field1 INTEGER EXTERNAL, $field2 CHAR(32))
  INSERT INTO my_table(col1, col2, col3);

Perform the insert operation again, specifying the same number of fields as the number of specified or implied table columns, or add the VALUES clause to the INSERT statement.

SQL2945N

When the INGEST command specifies FORMAT DELIMITED, every field of type DB2SECURITYLABEL must specify the NAME or STRING modifier.

Add the NAME or STRING modifier to every field of type DB2SECURITYLABEL.

SQL2946N

The INGEST command can omit the field list only when the format is delimited. If the format is positional, you must specify the field list.

Add the field list to the INGEST command.

SQL2947N

The command failed because the ingest job with the specified identifier was not found.

• If you are issuing the INGEST GET STATS command, specify the identifier of an ingest job that is still running. To display these identifiers, issue the INGEST LIST command.
• If you are issuing the INGEST command with the RESTART parameter, specify the identifier of an ingest job whose restart data is still in the ingest restart table. To display these identifiers, issue the following query:

  SELECT jobid FROM systools.ingestrestart

SQL2948N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. There are some restrictions on the data types that are supported with the ingest utility.

This message is returned when an attempt is made to ingest data into a column that is an unsupported data type.

Alter the INGEST command or db2Ingest API call so that the unsupported column is not included in the ingest operation, and then perform the ingest operation again.

SQL2949N

This message is preceded by a message that identifies the input source name and line number. One of the fields in the specified input record is too long or out of range for the table column.

Specify a different table or edit the input data so that:

• All field values that correspond to a numeric table column are within the range of the column's data type.
• All field values that correspond to a character table column have a length that is less than or equal to the column's length.

SQL2950N

When you ingest into an updateable view and the view has multiple base tables, all the base tables that are protected by a security policy must be protected by the same security policy.

One of the following:

• Specify a different table or view.
• Alter the base tables so that all the base tables that are protected by a security policy are protected by the same security policy.

SQL2951N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. A security administrator can use security policies to define criteria that determine who has write access and who has read access to individual rows and individual columns of tables.

This message is returned when an attempt is made to ingest data into a table that is protected by a security policy but catalog view SYSCAT.SECURITYPOLICIES has no security policy with that ID.

Alter the table so that it is protected by a valid security policy and then run the ingest operation again.

SQL2952N

The INPUT CODEPAGE parameter on the INGEST command specifies a code page number that is not valid for one of the following reasons:

• The number is not a valid code page.
• DB2 or the INGEST command does not support the code page.
• The code page is not compatible with the client code page.

Correct the code page number on the INPUT CODEPAGE parameter and reissue the command.

SQL2953N

There might be a data type mismatch because the field value at the specified byte position cannot be converted to the field's data type.

Correct the input file or change the field's type and reissue the command.

SQL2954N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify a list of field definitions for the ingested data, but there is an upper limit to the number of field definitions that you can specify. The maximum allowable number of field definitions is given in the runtime token maximum-number.

This message is returned when an attempt is made to specify more field definitions than the ingest utility can support.

Perform the ingest operation again, specifying no more than the given maximum allowable number of field definitions.

SQL2955N

A file that the ingest utility requires could not be found. The installation of the DB2 Data Server Client or DB2 Data Server Runtime client might be incomplete or damaged.

Reinstall the DB2 Data Server client or the DB2 Data Server Runtime client.

SQL2956N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify to the ingest utility how the data is defined in the input stream by passing data structures such as db2IngestStruct, db2IngestCfgList, and db2IngestFormat to the db2Ingest API call.

This message is returned when an invalid value is specified for a field in one of the input data structures.

Call the db2Ingest API again, specifying valid values for the input data structures.

SQL2957N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. If the ingest utility fails before completing, you can restart the ingest operation from the last commit point. To make an ingest operation restartable, a restart log table must be created before the ingest operation is initiated.

This message is returned when an attempt is made to restart the ingest utility but the ingest utility could not find the restart log table.

• To run the ingest operation as not restartable, reissue the command specifying RESTART OFF.
• To perform a restartable ingest operation, create the restart log table and then run the ingest utility again

SQL2958N

The INGEST command specified RESTART CONTINUE. In order to restart a failed INGEST command, the restarted command must meet the following requirements:

• The NUM_FLUSHERS_PER_PARTITION configuration parameter must be the same as on the original command.
• If the input is from files or pipes, the number of input files or pipes must be the same as on the original command.

One of the following:

• Set the NUM_FLUSHERS_PER_PARTITION configuration parameter to the value it had when the original INGEST command was run.
• Modify the restarted INGEST command to specify the same number of files or pipes as on the original command.
• Remove the RESTART CONTINUE parameter. In this case, the command starts from the beginning instead of resuming from where the failed command left off.

SQL2959W

The ingest utility received the error that followed this message, but recovered from the error by issuing a COMMIT or issuing a ROLLBACK and reissuing the SQL statements. The utility reissued the statements the number of times specified in the message. The reason code indicates how the utility recovered from the error:

1

The utility recovered by issuing a commit earlier than requested by ingest configuration parameters COMMIT_PERIOD or COMMIT_COUNT. For this reason code, the number of reconnects and number of retires is "0".

2

The utility recovered by issuing a ROLLBACK and reconnecting or retrying the specified number of times.

To avoid receiving this message, refer to the explanation of the error message that follows this message and take any corrective action that is needed.

If the error message is SQL0911N, you can also do one of the following depending on the reason code:

• Reason code 2: Reduce the COMMIT_COUNT, COMMIT_PERIOD, or NUM_FLUSHERS_PER_PARTITION ingest configuration parameters.
• Reason code 68: Reduce the COMMIT_COUNT or COMMIT_PERIOD ingest configuration parameters, or increase the locklist or maxlocks database configuration parameters.

SQL2960N

A field definition specifies DB2SECURITYLABEL STRING, but the value of the corresponding field in the input source is not a valid security label string. The row is not loaded.

One of the following:

• If the field definition is correct, modify the field values in the input source to specify a valid security label string.
• If the field values in the input source are security labels in binary, remove the STRING keyword from the field definition.
• If the field values in the input source are security label names, modify the field definition to specify DB2SECURITYLABEL NAME.

.

SQL2961N

The INGEST command failed because it has more than the allowable number of input file names or pipe names.

Remove input file names or pipe names from the command so the number is less than or equal to than the maximum number specified in the message.

SQL2962N

The ingest utility issues this message when all of the following are true:

• The INGEST command omits the RESTART parameter or specifies RESTART NEW or RESTART CONTINUE.
• The target table is a nickname.
• When trying to insert into or update the nickname, the utility receives message SQL30090N with reason code 18.

The SQL30090N error occurs because the utility needs to update both the remote table that the nickname refers to and the restart log table, which is local. This requires the two-phase commit protocol, but the server definition that contains the nickname is not defined with server option DB2_TWO_PHASE_COMMIT set to 'Y'.

Any one of the following:

• Alter the the server definition that contains the nickname so it specifies server option DB2_TWO_PHASE_COMMIT 'Y'.

  Note that you cannot use command SET SERVER OPTION to set the DB2_TWO_PHASE_COMMIT option for the ingest utility because the SET SERVER OPTION command affects only the CLP connection, whereas the ingest utility establishes its own connection. You must set the server option in the server definition in the catalog.

• Specify a nickname that has server option DB2_TWO_PHASE_COMMIT set to 'Y'.
• Specify RESTART OFF so that the ingest utility does not maintain restart information in the restart log table.
• Specify a target table that is not a nickname.

SQL2963N

You can ingest data to a database table from an input file or pipe by using the INGEST command. You can specify that each input record is a sequence of text or binary fields by using the POSITIONAL parameter with the INGEST command. You can specify the starting position and ending position of each field within a record by using the POSITION clause in the field definition.

This message is returned when an invalid starting or ending position is specified with the POSITION clause.

• For a numeric field, correct the field length or the end position.
• For a DATE, TIME, or TIMESTAMP field, correct the format string or the end position.

SQL2964N

The INGEST command specifies a job ID that is currently in use, as indicated by the reason code:

1

The command specifies RESTART NEW, RESTART CONTINUE, or RESTART TERMINATE, but an INGEST command with the specified job ID is already running.

2

The command specifies RESTART NEW, but the restart table (SYSTOOLS.INGESTRESTART) already contains an INGEST command with the specified job ID.

The user response corresponding to the reason code is:

1

If the intention was to start a new INGEST job, do one of the following:

• Specify a different job ID.
• Wait until the job that is already running completes.
• Cancel the job that is already running.

If the intention was to restart the ingest job with the specified job ID, no action is needed because that job is still running. If the job fails, it can be restarted using the specified job ID. If the intention was to restart an ingest job with a different job ID, specify the ID of that job.

If the intention was to start a new INGEST job, do one of the following:

• Wait until the job that is already running ends.
• Cancel the job that is already running.

2

If you do not plan to restart the job with the specified job ID, run the INGEST command with RESTART TERMINATE to clean up the restart table for the specified job. Then re-run the INGEST command with RESTART NEW. If you plan to restart the failed job, specify a different ID for the new job.

SQL2965I

This message identifies the table being operated on when the error in the following message occurred. If the table is the restart table (systools.ingestrestart), the restart table might be corrupted, damaged, or missing.

If the table is the restart table (systools.ingestrestart):

• If the INGEST command gets no other errors and completes successfully, no action is needed. If you do not want to receive this message in the future, correct the error that caused the SQL operation to fail.
• If the INGEST command fails due to additional errors, do the following:
  1. Correct the error that caused the SQL operation to fail.
  2. Run the INGEST command with RESTART TERMINATE 'jobID' to remove the entries for this job from the restart table. ('jobID' is the job ID for the failing INGEST command. This is either the ID that you specified on the RESTART NEW parameter of the INGEST command or the job ID that the INGEST command generated.)
  3. Run the original INGEST command from the beginning. (Do not specify RESTART CONTINUE.)
  4. If the problem still occurs and the restart table does not contain any information about other ingest jobs, run the SYSPROC.SYSINSTALLOBJECTS procedure to drop and re-create the restart table. After you have created the restart table, repeat step 3.
  5. If the problem still occurs, contact IBM Technical Support.

If the table is not the restart table, contact IBM Technical Support.

SQL2966I

When the ingest utility connects to the database and gets a warning or error, the utility issues this message followed by the warning or error message. If you connected without explicitly specifying the user ID, the user-ID field is empty.

Refer to the user response for the message that follows this message. If the problem still occurs, verify the following:

• The database or alias exists and is cataloged correctly on the machine where INGEST is running. If the database directory entry specifies a node name, verify that the node is cataloged correctly:
  • If the node definition specifies a service name, verify:
    • The service name maps to the correct port number on the machine where INGEST is running.
    • The database server is listening on that port number.
  • If the node definition specifies a port number, verify that the database server is listening on the specified port number.
• Verify that the specified user ID and its corresponding DB2 authorization ID have authority to connect to the database server.

In order to determine whether the problem is with the ingest utility or somewhere else, try connecting directly to the database server using the parameters indicated in the message, as follows:

 db2 "CONNECT TO <db> USER <ID> USING <pwd>" 

SQL2967I

When the ingest utility runs in a DPF environment and it can determine values for each of the target table's distribution keys, it connects directly to each database partition. When the utility connects to the database partition and gets a warning or error, the utility issues this message followed by the warning or error message.

Refer to the user response for the message that follows this message. If the problem still occurs, verify the following:

• The database to which you are connected in the CLP is cataloged correctly on the machine where INGEST is running. If the database directory entry specifies a node name, verify that the node is cataloged correctly.
• The specified host is accessible from the machine where INGEST is running.
• If the message specifies a service name, verify:
  • The service name maps to the correct port number on the machine where INGEST is running.
  • The database server is listening on that port number.
• If the message specifies a port number, verify that the database server partition is listening on the specified port number.
• Verify that the specified user ID and its corresponding DB2 authorization ID have authority to connect to the database server partition.

In order to determine whether the problem is with the ingest utility or somewhere else, try connecting directly to the database server partition using the parameters shown in the message, for example:

 db2 "SET CLIENT CONNECT_DBPARTITIONNUM <num>" db2 "CONNECT TO <db> USER <ID> USING <pwd>" 

SQL2968N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify to the ingest utility how the data is defined in the input stream by describing the fields into which the data is separated.

This message is returned when one of the fields in the specified input record has a non-numeric value, but is used where a numeric value is expected.

Respond to this message by performing one of the following actions:

• Modify the SQL statement that is specified with the INGEST command or the db2Ingest API call so that fields which can be non-numeric are not used where a numeric value is required.
• Modify the input data so that all fields that are used where a numeric value is expected have a numeric value.

SQL2969N

In a partitioned database environment, the utility examines the values of fields that map to distribution key columns and uses those values to determine the partition to send the record to. The utility issues this message when the field value is invalid or out of range for the corresponding distribution key column type. For example, the utility issues this message if the distribution key column type is INTEGER, but the field contains "ABC". The column type is the type of the distribution key column that corresponds to the field. The column length is the length of the column in bytes.

The utility will not send the record to DB2. If the DUMPFILE parameter is specified, the utility will write the record to the dump file.

To avoid receiving this message, correct the field value in the input data.

SQL2970N

The database directory contains an entry for the specified database and the entry specifies a node that does not exist.

Define the node or modify the entry in the database directory to specify an existing node.

SQL2971N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. You can specify to the ingest utility how the data is defined in the input stream by passing data structures such as db2IngestStruct, db2IngestCfgList, and db2IngestFormat to the db2Ingest API call.

The fields of some db2Ingest input structures contain an array of objects:

• The first field of the db2IngestFormat structure is an array of db2IngestFieldDefn objects.
• The first field of the db2IngestCfgList structure is an array of db2IngestCfgParam objects.

This message is returned when one object in an array of objects contains an invalid field value. The runtime token index-number indicates which element in the array of objects has a problem. The index starts at zero.

Call the db2Ingest API again, specifying valid values for the input data structures.

SQL2972N

This message is returned when an attempt is made to restart an ingest operation, but one or more of the following is true:

Scenario 1: The target table and the restart log table (SYSTOOLS.INGESTRESTART) are in different table spaces, but the two table spaces are at different product code levels.

Scenario 2: The records in the restart log table that belong to the specified ingest job ID have been modified outside of the ingest utility.

Scenario 3: The input files or pipes for the restarted ingest operation do not provide the same records in the same order as the input files or pipes for the original command.

Scenario 4: One of more of the following parameters are different from the original ingest operation:

• The SQL statement.
• The field definition list, including the number of fields and all field attributes.

Scenario 5: One or more of the target table columns that the SQL command updates have a different definition than they had at the time of the original ingest operation.

Scenario 6: In a multiple database partition environment:

• Database partitions were added or removed since the original ingest operation was run.
• Data was redistributed across the partitions since the original ingest operation was run.

The user response depends on which restriction was violated: Respond to this message according to the scenario in which this message was returned:

Scenario 1: If the target table and the restart log table are in table spaces at different product code levels, restore the table spaces containing the target table and the restart table so they are at the same level.

Scenario 2: If the records in the restart log table have been modified, restore the contents of the restart table.

Scenario 3: If the format of the input files or pipes is not the same as the format of the input files or pipes specified for the original ingest operation, specify input files or pipes that provide the same records and in the same order as on the original ingest operation.

Scenario 4: If the parameters that were specified when the ingest operation was being restarted are not the same as the parameters that were specified with the original ingest operation, modify the SQL statement and the field definition list to match the original ingest operation.

Scenario 5: If the target table has been altered since the original ingest operation, restart the ingest operation from the beginning.

Scenario 6: If database partitions have been added or removed, or if data has been redistributed since the original ingest operation, restart the ingest operation from the beginning.

SQL2973N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. When a field in the input stream is a date, time, or timestamp, you can specify the format of the field by providing a format string.

This message is returned when a field definition specifies a date, time, or timestamp format string that is not valid.

Perform the ingest operation again, specifying a valid format string, surrounded by single quotes, for the given field.

SQL2974N

You can stream data from files and pipes into DB2 database tables by using the ingest utility. If the ingest utility fails before completing, you can restart the ingest operation from the last commit point.

This message is returned when the primary database connection was lost during the initialization of the ingest operation.

1. Review the db2diag diagnostic log files for additional diagnostic details.
2. Resolve the problem that caused the lost connection.
3. Re-establish the connection and perform the ingest operation again.

SQL2975N

The RECONNECT_COUNT ingest configuration parameter is set to a value greater than 0 and the INGEST command omits the RESTART parameter (so it defaults to NEW) or specifies RESTART NEW or RESTART CONTINUE.

Set the RECONNECT_COUNT ingest configuration parameterto 0 or specify RESTART OFF on the INGEST command.

SQL2976W

There is a conflict between the field length and the field end position. The indicated reason code describes the conflict and how the utility resolves it:

1

The field type is SMALLINT, INTEGER, or BIGINT in binary. The length specified by (end position) - (start position) + 1 is 2, 4, or 8, but does not match the length of the field type. The utility will use the specified end position.

For example, if the field definition is SMALLINT POSITION(1:4), the utility will read 4 bytes even though a SMALLINT is 2 bytes. If the field contains a value outside the range of a SMALLINT, the utility will issue an error when it tries to convert the field value to a SMALLINT.

2

The field type is SMALLINT, INTEGER, or BIGINT in binary, but the length specified by (end position) - (start position) + 1 is not 2, 4, or 8. The utility will adjust the end position to match the length of the field type.

For example, if the field definition is SMALLINT POSITION(1:3), the utility will adjust the end position to 2 (because a SMALLINT is 2 bytes).

3

The field type is DECIMAL, REAL, FLOAT, or DECFLOAT in binary, but the length specified by (end position) - (start position) + 1 conflicts with the length of the field type. The utility will adjust the end position to match the length of the field type.

For example, if the field definition is REAL POSITION(1:5), the utility will adjust the end position to 4 (because a REAL is 4 bytes).

4

The field length specified on the field type conflicts with (end position) - (start position) + 1. If the specified length exceeds (end position) - (start position) + 1, the utility will adjust the length to (end position) - (start position) + 1. If the specified length is less than (end position) - (start position) + 1, the utility will adjust the end position to (start position) + length - 1.

For example, if the field definition is CHAR(10) POSITION(1:8), the utility will adjust the length to 8. If the field definition is CHAR(8) POSITION(1:10), the utility will adjust the end position to 8.

To avoid receiving this message, do one of the following, depending on the reason code and the format of the data in the input source:

1

Change the field type or end position.

2

Change the field type or end position.

3

Change the field type, precision, scale, or end position.

4

Change the field end position or length.

SQL2977I

The utility received an error that prevents it from continuing. The utility will exit.

Rows that were committed prior to the error remain in the table.

Refer to the explanation and user response of the previous error message.

If the INGEST command specified RESTART NEW or omitted the RESTART option (in which case it defaults to NEW), correct the error and re-run the same INGEST command, specifying RESTART CONTINUE.

SQL2978I

Ingest configuration parameter RECONNECT_COUNT or RETRY_COUNT has a value greater than 0 and the utility received a recoverable error. The utility attempted to recover from the error but could not for the reason indicated by the reason code:

1

The number of reconnect attempts reached the value of the RECONNECT_COUNT ingest configuration parameter.

2

The number of retries reached the value of the RETRY_COUNT ingest configuration parameter.

3

The utility was interrupted or a terminating error occurred.

Refer to the explanation of the error message that follows this message and take any needed corrective action.

If the error message is SQL0911N, you can also do one of the following depending on the SQL0911N reason code:

• Reason code 2: Reduce the value for the COMMIT_COUNT, COMMIT_PERIOD, or NUM_FLUSHERS_PER_PARTITION ingest configuration parameters.
• Reason code 68: Reduce the value for the COMMIT_COUNT or COMMIT_PERIOD ingest configuration parameters, or increase the locklist or maxlocks database configuration parameters.

If the error cannot be easily avoided and you want the utility to recover, increase the setting of one or more of the following ingest configuration parameters, depending on the reason code you received for the current message (SQL2978I):

• For reason code 1:
  • RECONNECT_COUNT
  • RECONNECT_PERIOD
• For reason code 2:
  • RETRY_COUNT
  • RETRY_PERIOD

SQL2979I

The ingest utility is starting at the indicated timestamp. The utility will also issue a message indicating the job ID.

No user response is required.

SQL2980I

The ingest utility completed with no warnings or errors.

No user response required.

SQL2981N

An unexpected error occurred calling an operating system function or command. The reason codes are:

1

The command was not found in /usr/bin or /bin. For this reason code, the "Additional tokens" field in the message is blank.

2

The function or command failed with the system error code shown in the "Additional tokens" field of the message. On UNIX, error codes are defined in system header file errno.h. For information on Windows error codes, consult Microsoft documentation.

3

The function or command did not return output in the expected format. The "Additional tokens" field of the message shows the last line of output.

The user response depends on the reason code:

1

Verify that the specified command is installed in /usr/bin or /bin and is executable. If this is not the problem, contact IBM Technical Support.

2

If you cannot resolve the problem using the system error code, contact IBM Technical Support.

3

Verify that the command or function is the version that shipped with the operating system and not a version tailored to your installation. If this is not the problem, contact IBM Technical Support.

SQL2982W

You can monitor the progress of ingest operations being run by the authorization ID that is connected to the database by using the INGEST LIST command or the INGEST GET STATS command.

This message is returned when either the INGEST LIST command or the INGEST GET STATS command was issued, but the authorization ID that is currently connected to the database is not running any ingest operations on the current machine. If the authorization ID recently started an ingest operation from another session, the command might not have completed initialization or might have already finished.

Ensure that you are running the INGEST LIST or INGEST GET STATS command on the same machine where you issued the INGEST command. If the authorization ID recently started an ingest operation from another session and the command has not yet completed, wait a few seconds for the command to complete initialization. Then run the INGEST LIST command or the INGEST GET STATS command again.