SQL2000 - SQL2249

SQL2000N The drive specified in the utility command is not a valid diskette drive or fixed disk.

Explanation

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

The utility stops processing.

User response

Resubmit the utility command with the correct drive specifier.

SQL2001N The utility was interrupted. The output data may be incomplete.

Explanation

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.

User response

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 specified database utility command is not valid for remote databases. The database specified in the command must reside on your local workstation.

Explanation

The database utility command is only valid for local databases.

The utility stops processing.

User response

Run the utility locally.

SQL2003C A system error occurred.

Explanation

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

The utility stops processing.

User response

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

SQL2004N An SQL error `sqlcode` occurred during processing.

Explanation

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

The utility stops processing.

User response

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

SQL2005C An I/O error occurred during a read operation. The data may be incomplete.

Explanation

Incomplete data was read during an I/O operation.

The utility stops processing.

User response

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

SQL2006C An I/O error occurred during a write operation. The data may be incomplete.

Explanation

Incomplete data was written during an I/O operation.

The utility stops processing.

User response

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

SQL2007N Specified buffersize of `buffersize` 4K buffers is too small for `pagesize` page size object.

Explanation

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.

User response

Use a larger buffersize.

SQL2008N The utility command could not be processed because the callerac parameter is not within valid range or the requested action is out of sequence.

Explanation

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

User response

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

SQL2009C A backup or restore failed due to inadequate memory resources.

Explanation

This problem can occur in the following situations:

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

User response

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:

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.
Retry the online backup after ensuring that utilities are not running.

SQL2010N The utility encountered an error `error` while connecting to the database.

Explanation

The utility could not connect to the database.

The utility stops processing.

User response

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

SQL2011N The utility encountered an error `error` while disconnecting from the database.

Explanation

The utility could not disconnect from the database.

The utility stops processing.

User response

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

SQL2012N Interrupt handling could not be enabled.

Explanation

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.

User response

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

SQL2013N The utility could not access the database directory. Error `error` was returned.

Explanation

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

The utility stops processing.

User response

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 A database environment error occurred.

Explanation

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.

User response

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

SQL2015N The database parameter is not valid. The database name is too long, it was not specified, or the address of the name is not valid.

Explanation

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.

User response

Resubmit the command with a valid database name.

SQL2016C The PATH command does not contain a path to `program-name`.

Explanation

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

The utility stops processing.

User response

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

SQL2017N Too many sessions are already started or OS/2 Start Session did not complete successfully.

Explanation

The BACKUP or RESTORE utility could not start the new session because:

The maximum number of sessions is already started.
The OS/2 Start Session program returned an error.

The utility stops processing.

User response

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 encountered an error `error` while attempting to verify the user's authorization ID or database authorizations.

Explanation

The user attempted to execute a utility and one of the following has occurred:

The user authorization ID is not valid.
An error occurred attempting to access the user's authorizations for the database.

The utility stops processing.

User response

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

SQL2019N An error occurred while utilities were being bound to the database.

Explanation

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.

User response

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 The utility is not bound to the database correctly.

Explanation

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.

User response

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

SQL2021N The correct diskette is not in the drive.

Explanation

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.

User response

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

SQL2023N The utility encountered an I/O error `code` while accessing the log control file.

Explanation

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.

User response

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

SQL2024N The utility encountered an I/O error `code` while accessing the file type `file-type`.

Explanation

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.

User response

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

SQL2025N An I/O error occurred. Error code: `code`. Media on which this error occurred: `dir_or_devices`.

Explanation

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.

User response

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>
```
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 An error `sqlcode` occurred while trying to internally disconnect from the database.

Explanation

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

The utility stops processing.

User response

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

SQL2027N An error `sqlcode` occurred while trying to internally connect to the database.

Explanation

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.

User response

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 Error `sqlcode` occurred while installing the interrupt handler.

Explanation

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

The utility stops processing.

User response

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

SQL2029N An error `error` occurred while `command-file-name` was processing.

Explanation

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

User response

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 `name` drive is full. At least `number` free bytes are needed on this drive.

Explanation

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

The utility stops processing.

User response

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

SQL2031W Warning! Please mount the target or source media on device `device`.

Explanation

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.

User response

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

SQL2032N The `parameter` parameter is not valid.

Explanation

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

User response

Resubmit the command with a correct value for the parameter.

sqlcode: -2032

sqlstate: 22531

SQL2033N An error occurred while accessing TSM during the processing of a database utility. TSM reason code: `reason-code`.

Explanation

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.

User response

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 address of the `parm` parameter is not valid.

Explanation

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.

User response

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

SQL2035N The warning condition `warn` was encountered while executing the utility in non-interrupt mode.

Explanation

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

User response

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 path for the file, named pipe, or device `path/device` is not valid.

Explanation

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.

User response

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

SQL2037N TSM could not be loaded.

Explanation

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.

User response

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 `errcode` occurred during processing.

Explanation

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

User response

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

SQL2039N The application calling the utility has terminated.

Explanation

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.

User response

Reissue the command after determining why the application terminated.

SQL2040N The database alias parameter `dbalias` is not valid or not specified.

Explanation

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.

User response

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

SQL2041N The buffer size parameter specified is not valid. The buffer size must be specified as 0 or be between 8 and 16384 inclusive.

Explanation

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 Warning! I/O error `error` accessing device `device`. Additional information (if available): `additional-information`. Please ensure media is mounted and positioned correctly.

Explanation

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.

User response

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 a child process or thread.

Explanation

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.

User response

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 error occurred while accessing a message queue. Reason code: `reason-code`.

Explanation

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.

User response

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 Warning! Error `error` occurred while writing to media `media`.

Explanation

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.

User response

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 configuration parameter named `parameter-name` could not be updated because the operation timed out.

Explanation

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.

User response

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 There is not enough available memory in the CF to satisfy the request to increase the database configuration parameter named `parameter-name` to the specified value.

Explanation

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.

User response

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 object `object`. Reason code: `reason-code`.

Explanation

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.

User response

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 Database activation failed because there is insufficient CF memory. Reason code = `reason-code`.

Explanation

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.

User response

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 There was a communication failure between a DB2 member and a CF. Reason code = `reason-code`. CF identifier: `CF-id`. Host name: `host-name`.

Explanation

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 the User-Level Direct Access Programming Library (uDAPL.)
2: The error occurred or was detected in the sockets layer.
3: The nature of the error could not be determined.

User response

Refer to the troubleshooting documentation.

SQL2052N The backup operation failed because the backup utility was unable to collect the required information and metadata for one or more DB2 members.

Explanation

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.

User response

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.
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 is corrupted.

Explanation

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.

User response

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

SQL2055N Unable to access memory from memory set `memory-heap`.

Explanation

A database utility was unable to access memory during processing.

The utility stops processing.

User response

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

SQL2056N An invalid media type was encountered on media `media`.

Explanation

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

The utility stops processing.

User response

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

SQL2057N The media `media` is already opened by another process.

Explanation

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.

User response

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 on media `media`.

Explanation

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.

User response

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 A device full warning was encountered on device `device`.

Explanation

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

The utility is waiting for a response to continue.

User response

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 The device `device` is empty.

Explanation

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

User response

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 media `media` is denied.

Explanation

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.

User response

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 An error occurred while accessing media `media`. Reason code: `reason-code`.

Explanation

An unexpected error occurred while accessing a device, file, or the vendor shared library during the processing of a database utility. The following is a list of reason codes:

1: An attempt to initialize a device, file, or the vendor shared library failed.

Other reason codes refer to vendor api codes.

The utility stops processing.

User response

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 Caller action `caller-action` specified is not allowed when the media `media` specified is the only one left connected to the utility.

Explanation

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

User response

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

SQL2066N The command failed because the specified table space either does not exist or is not supported with the specified command. Specified table space name: `name`.

Explanation

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.

User response

Resubmit the utility command, specifying a valid table space.

SQL2068N An invalid image was encountered on media `media`. There was no media header.

Explanation

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.

User response

Resubmit the command with correct backup or copy images.

SQL2069N An invalid image was encountered on media `media`. The image was created for database alias `dbalias`.

Explanation

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.

User response

Resubmit the command with correct backup or copy images.

SQL2070N An invalid image was encountered on media `media`. The image contained timestamp `timestamp`.

Explanation

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.

User response

Resubmit the command with correct backup or copy images.

SQL2071N An error occurred while accessing the shared library `shared-library-name`. Reason code: `reason-code`.

Explanation

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.

User response

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 Unable to bind the shared library `shr-lib-name`. Reason code: `reason-code`.

Explanation

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

User response

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 DATALINK processing failed because of internal problems at the database server or DB2 Data Links Manager.

Explanation

An unexpected error occurred while processing DATALINK values.

User response

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 DATALINK processing failed because of internal problems at the database server.

Explanation

An unexpected error occurred while processing DATALINK values.

User response

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 DATALINK processing failed because of internal problems at the DB2 Data Links Manager.

Explanation

An unexpected error occurred while processing DATALINK values.

User response

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.

Explanation

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

User response

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

SQL2077W Reconcile processing completed successfully on Data Links Managers that were available. Reconcile processing is pending on Data Links Managers that were not available. Examine the administration notification log for more information.

Explanation

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.

User response

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 The DB2 Data Links Manager could not be added or dropped successfully. Reason code = `reason-code`.

Explanation

The DB2 Data Links Manager could not be added or dropped, as indicated by the one of the following reason codes:

01: The DB2 Data Links Manager being added is already registered to the database.
02: The DB2 Data Links Manager being dropped is not registered to the database.
03: The database manager configuration parameter DATALINKS is set to NO.
04: The database already has the maximum allowed number of DB2 Data Links Managers registered to it.

User response

The action depends on the reason code as follows:

01: Do not attempt to add the DB2 Data Links Manager more than once.
02: Do not attempt to drop a DB2 Data Links Manager which is not registered.
03: Set the database manager configuration parameter DATALINKS to YES using the UPDATE DATABASE MANAGER CONFIGURATION command and attempt the operation again.
04: Do not attempt to add more than the maximum allowed number of DB2 Data Links Managers.

SQL2079N An error was reported by the shared library `shr-lib-name`. Return code: `return-code`.

Explanation

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.

User response

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 failed. The database being backed up is not unique within its volume directory.

Explanation

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.

User response

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 restore failed because some element or elements of the database to be restored have the same name as some element or elements of existing databases. Reason code = `reason-code`.

Explanation

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.

User response

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 Only one work action set can be defined for the following database, workload, or service superclass: `db-or-ssc-name`.

Explanation

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.

User response

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.
Issue the request again.

sqlcode: -2084

sqlstate: 5U017

SQL2085N The service subclass specified in the mapping work action `work-action-name` cannot be the default service subclass.

Explanation

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

User response

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

sqlcode: -2085

sqlstate: 5U018

SQL2086N Invalid range specified for work class `work-class-name`.

Explanation

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.

User response

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

SQL2089N The last connection attribute cannot be dropped from the definition of workload `workload-name`.

Explanation

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.

User response

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

sqlcode: -2089

sqlstate: 5U022

SQL2090N The workload `workload-name` cannot be dropped because it is not disabled, it has active workload occurrences, or it has a threshold or a work action set associated with it.

Explanation

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.

User response

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 The remaining storage paths do not contain enough storage space to rebalance the data in table space `tablespace-name`.

Explanation

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.

User response

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 Storage path `storage-path` is in the drop pending state. The current request cannot be processed.

Explanation

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

User response

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 The specified storage paths cannot be dropped. At least one storage path must be associated with the storage group.

Explanation

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).

User response

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 The rebalance of table space `tablespace-name` either did not add or drop containers, or there was insufficient disk space to create all of the containers. Reason code: `reason-code`.

Explanation

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.

User response

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 Storage path `storage-path` is in the drop pending state because one or more automatic storage table spaces reside on the path.

Explanation

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.

User response

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 The threshold `threshold-name` cannot be dropped. The threshold is not disabled, the threshold queue is not empty, or an activity is running under the control of the threshold.

Explanation

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.

User response

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 activity cannot be mapped to the service subclass you specified because at least one of the input parameters to the routine WLM_REMAP_ACTIVITY is not valid. Reason code = `reason-code`.

Explanation

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.

User response

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

sqlcode: -2097

sqlstate: 5U046

SQL2098N Cannot perform requested operation because the requested operation conflicts with objects currently used by or previously produced by schema transport operation. Reason Code: `rc`

Explanation

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.

User response

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 The ADMIN_MOVE_TABLE procedure could not be completed because of an incompatibility with a related database object or configuration. Reason code: `reason-code`.

Explanation

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.

User response

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 The ADMIN_MOVE_TABLE procedure could not be completed because of an internal failure during the execution of the procedure. Reason code: `reason-code`.

Explanation

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.
35: The maximum index key length was exceeded for the table.

User response

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.
35: Ensure that the tablespace you are moving your table to has the same or larger page size.

sqlcode: -2102

sqlstate: 5UA0M

SQL2103N The ADMIN_MOVE_TABLE procedure could not be completed because some aspect of either the source table or target table is not supported by the ADMIN_MOVE_TABLE procedure. Reason code: `reason-code`.

Explanation

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.

User response

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 The ADMIN_MOVE_TABLE procedure could not be completed at this time by this user. Reason code: `reason-code`.

Explanation

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.

User response

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 The ADMIN_MOVE_TABLE procedure could not be completed because a prerequisite for running the procedure was not satisfied. Reason code: `reason-code`.

Explanation

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.

User response

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 The table spaces contained in the backup image were restored. Depending on the request of the caller, one or more of these table spaces might have been skipped.

Explanation

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.

User response

No action is required.

SQL2154N The RESTORE was not successful. The backup used to restore the table space(s) is not associated with the current log sequence for the database.

Explanation

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.

User response

Resubmit the command with a correct backup image.

SQL2155W Changes have been made to the recovery history file since the open scan was issued.

Explanation

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

User response

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

SQL2157N There are already eight recovery history file scans open.

Explanation

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

The command cannot be processed.

User response

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

SQL2160W A damaged recovery history file has been replaced. Processing continued.

Explanation

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.

User response

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

SQL2161N A damaged recovery history file could not be fixed. The specified action failed.

Explanation

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.

User response

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 A recovery operation failed because the database manager does not have permission to access log file `log-file-number` for database `database-name` on database partition `dbpartitionnum` and log stream `log-stream-ID`.

Explanation

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

User response

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 on database partition number `partition_number`.

Explanation

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.

User response

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 RECOVER utility was unable to find the specified recovery history file `filename` on database partition number `partition_number`.

Explanation

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

User response

Verify the file name and resubmit the command.

SQL2165W The number of table spaces that are stored in a history file record exceeds the number of allocated table spaces in the poTablespace field of the db2HistoryData data structure.

Explanation

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.

User response

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 RECOVER command failed because the database `database` does not exist.

Explanation

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.

User response

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 number of log streams that are stored in a history file record exceeds the number of allocated log streams that were passed into the function.

Explanation

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.

User response

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 encountered entries with the same identifier in the recovery history file. Write fails.

Explanation

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.

User response

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 update of the recovery history file failed because the specified object part does not exist in the file.

Explanation

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

User response

Resubmit the command with a valid entry.

SQL2172W The utility has completed but it is not able to log the event in the recovery history file due to error `error`.

Explanation

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

User response

Correct the error condition to prevent future warnings.

SQL2180N Incorrect syntax or incorrect password key used in filtering specification.

Explanation

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

User response

Save the diagnostic information. Contact IBM service.

SQL2181N An internal error occurred during filtered recovery.

Explanation

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

User response

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 qualifier for the table or index name is too long.

Explanation

The authid must be 1 to 128 bytes in length.

The utility stops processing.

User response

Resubmit the command with the correct qualifier.

SQL2203N The tablename parameter is not valid. Either the table name is too long, only an authorization ID was specified, the table name was not specified, or the address of the name is not valid.

Explanation

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.

User response

Resubmit the command with the correct table name.

SQL2204N The iname parameter is not valid. The name of the index is too long, only an authorization ID was specified, or the address of the index is not valid.

Explanation

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.

User response

Resubmit the command with a valid index name.

SQL2205N The requested operation failed because the specified index is not valid. Reason code: `reason-code`.

Explanation

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.

User response

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

SQL2207N The filepath specified by the datafile parameter is not valid.

Explanation

The datafile parameter is not any of the values that indicate the default filepath. Also the datafile parameter is not a valid non-default value. One of the following may apply:

The pointer is not valid.
The pointer points to a string that is too long for a filepath designation.
The specified path value is not valid (on the server machine).
The file path does not end with an appropriate separator for the server machine.

The utility stops processing.

User response

Resubmit the command with a valid datafile parameter.

SQL2208N The table space `tablespace-name` specified by the table space or long table space parameter is not valid.

Explanation

The table space or long table space parameter does not contain a valid value. One of the following conditions may exist:

The pointer is not valid
The pointer points to a string that is too long for a table space name
The specified table space does not exist.

The utility stops processing.

User response

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 specified table does not exist.

Explanation

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

The command cannot be processed.

User response

Resubmit the command with a valid table name.

SQL2212N The specified table is a view. The Reorganize Table utility cannot be run against a view.

Explanation

The Reorganize Table utility cannot be run against a view.

The utility stops processing.

User response

Resubmit the command with a valid table name.

SQL2213N The specified table space is not a system temporary table space.

Explanation

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.

User response

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 This user ID does not have the authority to run the REORG utility on table `name`.

Explanation

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.

User response

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

SQL2215N SQL error `sqlcode` occurred while committing previous work for the database.

Explanation

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.

User response

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

SQL2216N SQL error `sqlcode` occurred while reorganizing a database table or its indexes.

Explanation

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

The utility stops processing.

User response

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

SQL2217N The page size of the system temporary table space used by the REORG utility must match the page size of the table space(s) in which the table data resides (including the LONG or LOB column data). The cause is based on the following reason codes `reason-code`.

Explanation

Following is a list of reason codes:

1: The cause relates to selection of a temporary tablespace for the table's data.
2: The cause relates to selection of a temporary tablesace for the table's LONG or LOB data.

If the system temporary table was explicitly specified to the REORG utility then the page size of the system temporary table space used by the REORG utility must match the page size of the table space or table spaces in which the table data, including LONG or LOB column data, resides, or else an appropriate container for long data must be specified. One of the following has violated this restriction:

The table's data resides in a table space that has a different page size than that of the specified system temporary table space.
The table contains LONG or LOB columns whose data resides in a table space with a page size that is different than that of the system temporary table space and the table's regular data but no tablespace with the correct page size could be found for the LONG or LOB data objects.

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.

User response

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 One or more parameters specified for the REORG utility is incompatible.

SQL2219N The inplace table reorganization failed on one or more members. Table name: `table-name`. Reason code: `reason-code`.

Explanation

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.

User response

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:

Confirm that the file named "<tablespaceID>.<objectID>.OLR" exists under the database directory and is accessible, and then resubmit the command
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 The compression dictionary was not built for one or more data objects.

Explanation

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.

User response

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

SQL2221N The REORG command failed because the specified table `table-name` is incompatible with the request to reclaim extents.

Explanation

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.

User response

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 `data-partition-name` is not valid. Reason code: `reason-code`

Explanation

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.

User response

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:

Issue the SET INTEGRITY statement to bring the attached partition into the normal status, the STATUS is an empty string.
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.

SQL2000 - SQL2249

SQL2000N The drive specified in the utility command is not a valid diskette drive or fixed disk.

Explanation

User response

SQL2001N The utility was interrupted. The output data may be incomplete.

Explanation

User response

SQL2002N The specified database utility command is not valid for remote databases. The database specified in the command must reside on your local workstation.

Explanation

User response

SQL2003C A system error occurred.

Explanation

User response

SQL2004N An SQL error sqlcode occurred during processing.

Explanation

User response

SQL2005C An I/O error occurred during a read operation. The data may be incomplete.

Explanation

User response

SQL2006C An I/O error occurred during a write operation. The data may be incomplete.

Explanation

User response

SQL2007N Specified buffersize of buffersize 4K buffers is too small for pagesize page size object.

Explanation

User response

SQL2008N The utility command could not be processed because the callerac parameter is not within valid range or the requested action is out of sequence.

Explanation

User response

SQL2009C A backup or restore failed due to inadequate memory resources.

Explanation

User response

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

Explanation

User response

SQL2011N The utility encountered an error error while disconnecting from the database.

Explanation

User response

SQL2012N Interrupt handling could not be enabled.

Explanation

User response

SQL2013N The utility could not access the database directory. Error error was returned.

Explanation

User response

SQL2014N A database environment error occurred.

Explanation

User response

SQL2015N The database parameter is not valid. The database name is too long, it was not specified, or the address of the name is not valid.

Explanation

User response

SQL2016C The PATH command does not contain a path to program-name.

Explanation

User response

SQL2017N Too many sessions are already started or OS/2 Start Session did not complete successfully.

Explanation

User response

SQL2018N The utility encountered an error error while attempting to verify the user's authorization ID or database authorizations.

Explanation

User response

SQL2019N An error occurred while utilities were being bound to the database.

Explanation

User response

SQL2020N The utility is not bound to the database correctly.

Explanation

User response

SQL2021N The correct diskette is not in the drive.

Explanation

User response

SQL2023N The utility encountered an I/O error code while accessing the log control file.

Explanation

User response

SQL2024N The utility encountered an I/O error code while accessing the file type file-type.

Explanation

User response

SQL2025N An I/O error occurred. Error code: code. Media on which this error occurred: dir_or_devices.

Explanation

User response

SQL2026N An error sqlcode occurred while trying to internally disconnect from the database.

Explanation

User response

SQL2027N An error sqlcode occurred while trying to internally connect to the database.

SQL2004N An SQL error `sqlcode` occurred during processing.

SQL2007N Specified buffersize of `buffersize` 4K buffers is too small for `pagesize` page size object.

SQL2010N The utility encountered an error `error` while connecting to the database.

SQL2011N The utility encountered an error `error` while disconnecting from the database.

SQL2013N The utility could not access the database directory. Error `error` was returned.

SQL2016C The PATH command does not contain a path to `program-name`.

SQL2018N The utility encountered an error `error` while attempting to verify the user's authorization ID or database authorizations.

SQL2023N The utility encountered an I/O error `code` while accessing the log control file.

SQL2024N The utility encountered an I/O error `code` while accessing the file type `file-type`.

SQL2025N An I/O error occurred. Error code: `code`. Media on which this error occurred: `dir_or_devices`.

SQL2026N An error `sqlcode` occurred while trying to internally disconnect from the database.

SQL2027N An error `sqlcode` occurred while trying to internally connect to the database.

SQL2028N Error `sqlcode` occurred while installing the interrupt handler.

SQL2029N An error `error` occurred while `command-file-name` was processing.

SQL2030N The `name` drive is full. At least `number` free bytes are needed on this drive.

SQL2031W Warning! Please mount the target or source media on device `device`.

SQL2032N The `parameter` parameter is not valid.

SQL2033N An error occurred while accessing TSM during the processing of a database utility. TSM reason code: `reason-code`.

SQL2034N The address of the `parm` parameter is not valid.

SQL2035N The warning condition `warn` was encountered while executing the utility in non-interrupt mode.

SQL2036N The path for the file, named pipe, or device `path/device` is not valid.

SQL2038N A database system error `errcode` occurred during processing.

SQL2040N The database alias parameter `dbalias` is not valid or not specified.

SQL2042W Warning! I/O error `error` accessing device `device`. Additional information (if available): `additional-information`. Please ensure media is mounted and positioned correctly.

SQL2044N An error occurred while accessing a message queue. Reason code: `reason-code`.

SQL2045W Warning! Error `error` occurred while writing to media `media`.

SQL2046N The configuration parameter named `parameter-name` could not be updated because the operation timed out.

SQL2047N There is not enough available memory in the CF to satisfy the request to increase the database configuration parameter named `parameter-name` to the specified value.

SQL2048N An error occurred while accessing object `object`. Reason code: `reason-code`.

SQL2049N Database activation failed because there is insufficient CF memory. Reason code = `reason-code`.

SQL2051N There was a communication failure between a DB2 member and a CF. Reason code = `reason-code`. CF identifier: `CF-id`. Host name: `host-name`.