Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

You can define the releases of DB2 database for which you want to verify installation prerequisites in an XML resource file. This message is returned when the db2prereqcheck utility cannot find the specified XML resource file or the default XML resource file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot open a file during normal processing. Because the db2prereqcheck utility runs with the same privileges as the user who ran the db2prereqcheck command, this message can be returned when the user who ran the db2prereqcheck command does not have read and write permission for the named file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

You can define the releases of DB2 database for which you want to verify installation prerequisites in an XML resource file. This message is returned when an invalid version is specified in the XML resource file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when an invalid parameter is specified with the db2prereqcheck command.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot determine the current level of the operating system.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot determine the distribution level of the current Linux operating system. There are several reasons why the utility might be unable to determine the distribution level. For example, the utility might be unable to determine the distribution level if the utility cannot find or read the system file called /etc/issue.

The db2prereqcheck utility cannot perform all of the the necessary prerequisite verification steps without knowing the distribution level of the current Linux operating system. In order for the db2prereqcheck utility to be used to verify installation prerequisites, the problem that prevented the utility from determining the distribution level must be resolved.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

While verifying installation prerequisites, the db2prereqcheck utility uses the Resource Package Manager utility. This message is returned when the db2prereqcheck utility call the rpm command and that rpm command fails.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot find the named package or file while the utility is verifying installation prerequisites.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility encounters an error that the utility cannot classify or resolve.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility needs to determine the version of a package to verify installation prerequisites, but the utility cannot determine the version of the package.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot find a library file that is required to verify installation prerequisites.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot find a map file that is required to verify installation prerequisites.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The current system might meet installation prerequisites even if the db2prereqcheck utility cannot determine the version of the C++ standard library that is installed.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility uses several different methods for determining the current version of the C++ standard library. This message is returned when the db2prereqcheck utility attempts to determine the version of the currently-install C++ standard library using the ldconfig utility.

The current system might meet installation prerequisites even if the db2prereqcheck utility cannot determine the version of the C++ standard library that is installed.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot find the 32-bit version of a required library file. If the named file is missing, 32-bit database applications might not function properly.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility attempts to execute a command to verify installation prerequisites, but the command fails.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot read a file during normal processing. Because the db2prereqcheck utility runs with the same privileges as the user who ran the db2prereqcheck command, this message can be returned when the user who ran the db2prereqcheck command does not have read and write permission for the named file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility determines that the version of the currently-install Windows operating system is not supported by one or more versions of DB2 database that were specified in the db2checkprereq XML resource file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

You can define the releases of DB2 database for which you want to verify installation prerequisites in an XML resource file. This message is returned when the db2prereqcheck utility cannot process the contents of the specified XML resource file or the default XML resource file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility produces an output, report file that contains a log of the prerequisites checked and the success of the verification. There is a default report file name, but you can also specify the name of the report file using the -o parameter with the db2prereqcheck command.

This message is returned when the value specified with the -o parameter is not valid for a file name. For example, this message can be returned when the value specified with the -o parameter is not in a format that is valid for a file name.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

You can specify a version using the -v parameter with the db2prereqcheck command.

This message is returned when a value is specified for the -v parameter with the db2prereqcheck command, but the specified value does not match any valid versions of DB2 database defined in the resource XML file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility reads information about which prerequisites to check from an input XML resource file. There is a default XML resource file name, but you can also specify the name of the XML resource file using the -f parameter with the db2prereqcheck command.

This message is returned when the file specified with the -f parameter is not in valid XML file or its content is not in the format recognized by db2prereqcheck tool.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

You can control what kinds of tests the db2prereqcheck utilty performs and the output format by specifying various parameters with the db2prereqheck command.

This message is returned when mutually exclusive parameters are specified with the db2prereqcheck command.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

You can specify a version using the -v parameter with the db2prereqcheck command.

If you use an XML resource file that lists one or more versions of DB2 database, you can cause the db2prereqcheck utility to verify the installation prerequisites for only the latest version that is specified in the XML resource file by specifying the -i parameter with the db2prereqcheck command.

This message is returned when the -i parameter is specified with the db2prereqcheck command, but the db2prereqcheck utility failed to determine what the latest version is that is specified in the XML resource file contents. There are multiple reasons for which the db2prereqcheck utility might be unable to retrieve the latest version from the XML resource file, including the following reasons:

• No DB2 database versions are specified in the XML resource file.
• The format of the XML resource file is not valid.
• The DB2 database versions that are specified in the XML resource file are not valid.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility produces a report file that contains information about the installation prerequisites that were verified on the current system.

This message is returned when an error occurs while db2prereqcheck is attempting to print information to the report file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

On Linux operating systems on an InfiniBand network or a 10 Gigabit Ethernet (10GE) RoCE network, specific InfiniBand Support packages are required. For a list of required packages, see the DB2 pureScale Feature installation prerequisites for Linux topic.

Explanation

On Linux operating systems on a 10 Gigabit Ethernet (10GE) RoCE network, specific High Performance Networking (HPN) packages are required. For a list of required packages, see the DB2 pureScale Feature installation prerequisites for Linux topic.

Explanation

On Linux operating, specific remote direct memory access (RDMA) packages are required.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

You can specify the type of network configuration for which the db2prereqcheck utility should verify prerequisites using the -t parameter. There are four valid values for the -t parameter:

• SINGLE_IB_PORT_CLUSTER
• MULTI_IB_PORT_CLUSTER
• SINGLE_ROCE_PORT_CLUSTER
• MULTI_ROCE_PORT_CLUSTER

This message is returned when an invalid value is specified for the -t parameter.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

You can verify installation prerequisites specifically for the DB2 pureScale environment by specifying the -p parameter. If you specify that the db2prereqcheck utility should verify the prerequisites for the DB2 pureScale environment, you can also specify the type of network configuration for which the db2prereqcheck utility should verify prerequisites using the -t parameter.

If you do not specify the -p parameter, the -t parameter must not be specified.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility requires the following minimum operating system levels:

• AIX 6.1
• HP-UX 11iv3
• Solaris 10

Explanation

The database manager performs a variety of system validation steps, including using the db2prereqcheck utility, before installing the database product and before creating or managing database manager instances.

This message is returned when an unhandled error is encountered by the db2prereqcheck utility as part of those larger install or instance management operations.

Explanation

The database manager performs a variety of system validation steps, including using the db2prereqcheck utility, before installing the database product and before creating or managing database manager instances.

The reason code indicates a specific reason for the error:

1

The database manager or the db2prereqcheck utility failed to open the file called "/etc/hosts".

2

The database manager or the db2prereqcheck utility failed to determine the IP address of the machine on which the cluster caching facility is located.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the utility encounters an error while printing a message in the current user language.

The failure to print one message might not affect the usefulness of the db2prereqcheck utility. However, if this error happens multiple times, this might indicate a problem with the installation of the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility uses the system command, "uname", to determine the level of the current operating system. There are multiple reasons that the db2prereqcheck utility might be unable to determine the operating system level by using the uname command, including the following examples:

• The call to the uname system command failed.
• The output of the uname system command is not what the db2prereqcheck utility was designed to expect.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility fails to open a temporary file while performing the prerequisite verification.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility is unable to perform the prerequisites validation because the utility cannot find the given file or package.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify whether a system meets the prerequisites for database product releases and fix packs that are defined in a resource XML file. You can cause the db2prereqcheck utility to read from a specified resource XML file by using the -f parameter with the db2prereqcheck command, or you can allow the db2prereqcheck utility to use a default resource XML file.

This message is returned when the db2prereqcheck utility fails to open the resource XML file, either a file specified with the -f parameter, or the default file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies system details by using system commands and examining various system configuration files. This message is returned when the db2prereqcheck utility is unable to extract necessary information from the output of a system command or the contents of a system configuration file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies system details by using system commands and examining the contents of system configuration files. This message is returned when the db2prereqcheck utility fails to extract the necessary package information from the output of the lslpp command.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies system details by using system commands and examining the contents of system configuration files. This message is returned when the db2prereqcheck utility fails to extract the necessary package information from the output of the lslpp command.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies system details using system commands and system configuration files. This message is returned when the db2prereqcheck utility successfully loads a system file.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The Input/Output Completion Port (IOCP) is required by the database server.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The -c, -u, -g, and -p parameters are mutually exclusive.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Because some requirements, such as General Parallel File System (GPFS), are not compatible with Security-Enhanced Linux (SELinux) enabled, the db2prereqcheck utility attempts to determine whether SELinux is enabled. This message is returned when the db2prereqcheck utility is unable to determine whether SELinux is enabled.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

DB2 database requires a General Parallel File System (GPFS.) However, GPFS is not supported with Security-Enhanced Linux (SELinux) enabled.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility is unable to perform the prerequisites validation because the utility cannot find the given file or package on the given host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

In versions of DB2 database earlier than DB2 Version 10.5, passwordless remote root login must be enabled to install DB2 database. This message is returned when passwordless remote root login needs to be enabled but the db2prereqcheck utility determined that passwordless remote root login is not currently enabled on the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility attempts to determine whether all system services that are required for successfully installing DB2 database are enabled. This message is returned when the db2prereqcheck utility detects that a required system service is not enabled.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

To install and configure DB2 pureScale, one of the following communication methods must be configured for all host machines in the DB2 cluster:

• db2locssh
• Passwordless SSH

This message is returned when the db2prereqcheck utility determines that neither db2locssh nor passwordless SSH is enabled between the named host machines.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The input/output Completion Port (IOCP) is required by the database server.

This message is returned when the db2prereqcheck utility detects that no input/output completion ports are installed on the given host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The input/output Completion Port (IOCP) is required by the database server.

This message is returned when the db2prereqcheck utility detects that no input/output completion ports are enabled on the given host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility cannot determine either the physical volume identifier (PVID) or the worldwide identifier (WWID) for the specified device path. This information is useful for verifying disk and network prerequisites.

If the db2prereqcheck utility is unable to determine the PVID or WWID, the db2prereqcheck can still successfully perform prerequisite checking. However, if the device path is used for install or instance management runtime operations in the future, the underlying problem that prevented the db2prereqcheck utility from determining the PVID or WWID might also cause errors with install or instance management utilities.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database.

This message is returned when the db2prereqcheck utility determined that there is insufficient space in the named directory on the given host machine for the installation of the database product to proceed successfully.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck is unable to successfully use the ping command to test connectivity and network response time from the given host machine to the given cluster interconnect netname.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck finds that TCP/IP has been configured incorrectly for the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the /etc/hosts file has not been configured correctly on the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the /etc/hosts file has not been configured correctly on the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the /etc/hosts file has not been configured correctly on the named host machines.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. For example, one of the tests that the db2prereqcheck utility performs is to run the simple command "ls <user-id>" to determine whether there is a home directory for the user.

This message is returned when the db2prereqcheck utility encounters a problem with a required user account on a host machine:

• An account for the user does not exist on the host machine
• The db2prereqcheck utility cannot find a home directory for the user on the host machine

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that a required user id does not exist on all required host machines.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that a required user id does not exist on all required host machines.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that a required user id does not exist on the host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility is unable to perform the prerequisites validation because the utility cannot find the given file or package.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility finds two packages are installed that are not supported together.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility determines details about the current operating environment and system components by using system commands and examining currently installed files. This message is returned when the db2prereqcheck utility is unable to perform the prerequisites validation.

Explanation

In DB2 pureScale environments, the Mellanox HCA driver mlx4_core parameter named log_mtts_per_seg must be configured in the modprobe configuration file, modprobe.conf, on host machines where any cluster caching facility (CF) resides. If this configuration parameter is not set appropriately, errors could occur when the database manager is started with the db2start command.

This message is returned when the db2prereqcheck utility is unable to validate the setting of log_mtts_per_seg on the given host machine for the reason indicated by the reason code:

1

The db2prereqcheck utility cannot find the file modprobe configuration file on the host machine.

2

The db2prereqcheck utility cannot find an entry for the log_mtts_per_seg parameter in the modprobe configuration file in the host machine.

Explanation

Configuring I/O completion ports (IOCPs) on AIX servers is not required for the installation of DB2 for Linux, UNIX, and Windows software. However, this configuration step is recommended for performance purposes.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

Part of the prerequisite verification that the db2prereqcheck utility performs includes verifying whether storage prerequisites have been met.

In DB2 pureScale environments, because the DB2 pureScale Feature requires the use of a storage area network (SAN), the db2prereqcheck utility attempts to determine whether a disk on a host machine is a member of a SAN.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility finds that the direct access transport file, dat.conf, has not been configured correctly on the named host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck finds that TCP/IP has been configured incorrectly for the named host machine.

Explanation

In pureScale environments, the Mellanox HCA driver mlx4_core parameter named log_mtts_per_seg must be configured in the modprobe configuration file, modprobe.conf, on host machines where any cluster caching facility (CF) resides.

This message is returned when the log_mtts_per_seg parameter is not configured to the recommended value of "7" on the host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database.

This message is returned when the db2prereqcheck utility determines that there is less than the recommended amount of space in the named directory on the given host machine, but that installing the database product could proceed successfully.

Note that although having less than the recommended amount of space on the directory named in the run time token directory-name might not prevent installing the database product from succeeding, having less than the recommended amount of space could cause run time performance problems or other errors in the future.

Explanation

One prerequisite for the DB2 pureScale Feature is that Intel TCO WatchDog Timer Driver modules must be blocklisted with modprobe.

Installing DB2 database might succeed if the Intel TCO WatchDog Timer Driver modules are not blocklisted. However, you will encounter runtime errors creating database manager instances if these modules are not blocklisted.

Explanation

You can verify that prerequisites for installing DB2 database by using the db2prereqcheck utility.

One requirement for installing the DB2 pureScale Feature is that all machines in the cluster are using the same operating system.

This message is returned when db2prereqcheck determines that not all machines in the cluster are running the same operating system.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

The db2prereqcheck utility verifies many prerequisites, including space requirements.

This message is returned when the db2prereqcheck tool determines that there is less than the recommended amount of free space available for one or both of the following paths:

• The default installation path (/opt)
• The instance home directory path (/home)

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility detects an Interface Adapter (IA) that is not configured in the /etc/hosts and direct access transport file, dat.conf, on the host machine.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

You can cause the db2prereqcheck utility to verify communication between all hosts in RDMA over Converged Ethernet (RoCE) and InfiniBand networks by specifying a list of netnames in the network. This message is returned when the the db2prereqcheck utility is unable to verify one of the specified netnames, because the netname is not listed in the etc/hosts file or is not configured in the direct access transport file, dat.conf.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility detects an invalid IP address for an Interface Adapter in an /etc/hosts file.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. The db2prereqcheck utility uses the libstdc++ and xlc libraries to perform some of the verification of Interface Adapters. This message is returned when the db2prereqcheck is unable to use one of these libraries.

Explanation

You can verify installation prerequisites by using the db2prereqcheck utility.

The db2prereqcheck utility verifies many hardware, software, and configuration prerequisites for successfully installing and running DB2 database. This message is returned when the db2prereqcheck utility detects an interface adapter that is not configured in the /etc/hosts and direct access transport file, dat.conf, on the host machine.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

On Windows operating systems, before verifying prerequisites, the db2prereqcheck utility copies some files from the database product install image directory to the temporary directory configured by the %TEMP% environment variable.

This message is returned when the db2prereqcheck utility fails to copy one of those files to the temporary directory.

Explanation

In a DB2 pureScale environment, the RDMA is supported through the User Direct Access Programming Library (uDAPL) interface.

This message is returned when the db2prereqcheck utility detects that the level of uDAPL that is currently installed is not supported with the current operating system level.

Explanation

You can verify installation prerequisites for the database product as well as feature-specific prerequisites, such as requirements for the DB2 pureScale Feature, by using the db2prereqcheck utility.

The DB2 pureScale Feature requires one or more raw devices to be configured for storing files that are shared by the DB2 members and cluster caching facilities (CFs). You can verify the shared devices that will be used by your DB2 pureScale instance by issuing the db2prereqcheck command, and specifying the devices with the -dl parameter.

This message is returned when the db2prereqcheck utility determines that one or more of the devices that were specified with the -dl parameter is not a raw device or is not configured with the same physical volume identifier (PVID) on all the host machines in the cluster.

Explanation

You can verify installation prerequisites for the database product as well as feature-specific prerequisites, such as requirements for the DB2 pureScale Feature, by using the db2prereqcheck utility.

When you are configuring network settings for a planned DB2 pureScale environment, entries in the /etc/hosts file on each host machine in the cluster must be formatted in the following way:

<IP-address> <full-domain-host-name> <alias>

When verifying DB2 pureScale requirements, the db2prereqcheck utility returns this error message if the /etc/hosts file is not formatted in the required way on all host machines in the cluster.

Explanation

You can verify installation prerequisites for DB2 database by using the db2prereqcheck utility.

You can use the db2prereqcheck utility to verify communication between all hosts in RDMA over Converged Ethernet (RoCE) and InfiniBand networks by specifying a list of netnames, hostnames and adapternames in the network.

This message is returned when the db2prereqcheck is unable to successfully ping all of the netname using RDMA to test connectivity between all the given host machine and cluster interconnect netnames. For more details refer the log file.

However, if these set of hostname and netname are for used for install or instance management runtime operations in the future, the underlying problem that prevented the db2prereqcheck utility from pinging netname might also cause errors with install or instance management utilities.

Explanation

You can verify installation prerequisites using the db2prereqcheck utility.

This message is returned when the db2prereqcheck utility found a software package that is not at the required minimum level for the operating system level.

Explanation

The "-db2ssh_test" option of the db2prereqcheck tool validates the setup of db2locssh and db2scp among hosts.

This message is returned when the execution of validation failed. You can find more detail and explanation in the detailed log and trace files displayed on the screen for further diagnostics

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

You must specify a value for the named option.

For an explanation of the syntax of the db2fedgentf command, use the following command: "db2fedgentf -h".

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

You must specify exactly one of the "-create" or "-drop" options with the db2fedgentf command.

For an explanation of the syntax of the db2fedgentf command, use the following command: "db2fedgentf -h".

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

The given option is not a valid option for the db2fedgentf command.

For an explanation of the syntax of the db2fedgentf command, use the following command: "db2fedgentf -h".

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

When you call the db2fedgentf command, you must specify a database name, a user name, and a password.

For an explanation of the syntax of the db2fedgentf command, use the following command: "db2fedgentf -h".

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

When you call the db2fedgentf command to create a new table function for a given federated stored procedure, you must specify both of the following:

• The name of the federated stored procedure using the "-stpn" option
• The column name and type pairs of the signature of the federated stored procedure

For an explanation of the syntax of the db2fedgentf command, use the following command: "db2fedgentf -h".

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

When you call the db2fedgentf command to create a new table function for a given federated stored procedure, you must specify the column name and type pairs of the signature of the federated stored procedure.

The format of that string should be:

"<name1> <type1>, <name2> <type2>, ..."

For example:

"PID CHAR(10), PRICE DOUBLE, QTY INT"

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

The db2fedgentdf utility creates JAVA table functions. To accomplish this, the utility performs the following tasks: creates a JAVA file that contains the source for the new table function; compiles that generated JAVA file; and registers the new table function.

Because db2fedgentdf creates JAVA table functions, db2fedgentf must convert the SQL data types of the stored procedure result set columns to JAVA data types. In this case, there is no JAVA data type to which the named column can be converted.

No table function was created.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

The message was returned because db2fedgentf could not find an entry in the catalog for the federated stored procedure specified with the "-stpn" option on the command line.

No table function was created.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

The db2fedgentdf utility creates JAVA table functions. To accomplish this, the utility performs the following tasks: creates a JAVA file that contains the source for the new table function; compiles that generated JAVA file; and registers the new table function.

The reason this message was returned is indicated by the reason code:

1

db2fedgentf could not allocate a file handle for the JAVA source file.

2

db2fedgentf could not write the table function source to the JAVA source file.

3

db2fedgentf could not open a file handle for the JAVA source file. Refer to the error string for more information.

4

db2fedgentf could not write the table function source code to the JAVA source file. Refer to the error string for more information.

No table function was created.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

The db2fedgentdf utility creates JAVA table functions. To accomplish this, the utility performs the following tasks: creates a JAVA file that contains the source for the new table function; compiles that generated JAVA file; and registers the new table function.

The reason this message was returned is indicated by the reason code:

1

db2fedgentf could not determine the current path in which to create the JAVA source file.

2

db2fedgentf could not determine the database product install path.

3

db2fedgentf could not delete the existing version of the class file.

4

db2fedgentf could not copy the class file to the destination: <DB2-INSTALL-PATH>/function

No table function was created.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

This message is returned when db2fedgentf cannot uniquely identify the table function to drop. This can happen when there are multiple table functions with the same name.

No table function was dropped.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

While creating a new table function, db2fedgentf encountered the given SQL error.

No table function was created.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

To perform its tasks, the db2fedgentf utility executes multiple database commands and invokes the JAVA compiler 'javac' to compile the JAVA file for the table function. The db2fedgentf utility will get JDK path by reading DBM configuration parameter JDK_PATH. This message is returned when one of those tasks encountered an error.

No table function was dropped or created.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

When you call the db2fedgentf command to drop a table function for a given federated stored procedure, you must identify the table function using one of the following options:

• The table function name using the "-tfn" option
• The table function specific name using "-tfsn" option

For an explanation of the syntax of the db2fedgentf command, use the following command: "db2fedgentf -h".

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures. You can use the db2fedgentf utility to drop only those table functions that were created using the db2fedgentf utility.

This message was returned because the specified table function was not created using db2fedgentf.

No table function was dropped.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

This message is returned when db2fedgentf cannot uniquely identify the procedure. This can happen when there are multiple procedures with the same name.

No table function was created.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

When using db2fedgentf, you can create only one table function for each federated stored procedure.

No table function was created.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

This message is returned when the db2fedgentf utility successfully creates a table function.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

The db2fedgentdf utility creates Java table functions. To accomplish this, the utility must perform a variety of database tasks. This message is returned when the db2fedgentf utility encounters an internal DB2 database error while performing those tasks. Specifically, this message is returned when the db2fedgentf utility fails to allocate an environment handle.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

To perform its tasks, the db2fedgentf utility executes multiple database commands and invokes the Java compiler 'javac' to compile the Java file for the table function. The db2fedgentf utility determines where the Java SDK installed by reading the JDK_PATH configuration parameter.

This message is returned when the db2fedgentf utility cannot determine the location of the Java SDK from the JDK_PATH configuration parameter for some reason, such as because the configuration parameter is NULL.

Explanation

You can use the db2fedgentf utility to create or drop table functions that access result sets from federated stored procedures.

The db2fedgentdf utility creates Java table functions. To accomplish this, the utility performs the following tasks:

• Creates a Java file that contains the source for the new table function
• Compiles that generated Java file
• Registers the new table function
• Deletes the generated Java source file

This message is returned when the db2fedgentf utility was supposed to delete the generated Java source file, but the utility failed to delete the file.

Explanation

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility did not find any database objects or features in the specified database that are not supported in a DB2 pureScale environment.

Explanation

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility found some database objects or features in the specified database that are not supported in a DB2 pureScale environment which will be automatically converted or disabled when you convert the instance to a DB2 pureScale instance type.

Explanation

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility found some database objects or features in the specified database that are not supported in a DB2 pureScale environment and which cannot be automatically converted or disabled when you convert the instance to a DB2 pureScale instance type.

Explanation

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when an invalid parameter was passed to the db2checkSD command.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

You can pass the name of a specific database to be checked, or you can use the -e parameter to specify that the db2checkSD utility should check all databases in the current database manager instance. This message is returned when no database or databases were specified to be examined by the db2checkSD utility.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD creates an output log file that contains detailed information about the investigation of the database structure, metadata, objects, and features that the db2checkSD utility performed. You must specify the name of the output log file using the -l parameter.

This message is returned when no name for the db2checkSD output log file was specified using the -l parameter with the db2checkSD command.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when a parameter is passed to the db2checkSD command without a value.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when a parameter is passed to the db2checkSD command more than once.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD creates an output log file that contains detailed information about the investigation of the database structure, metadata, objects, and features that the db2checkSD utility performed. You must specify the name of the output log file name using the -l parameter. The log file name cannot be longer than 256 characters.

This message is returned when an output log file name was specified using the -l parameter with the db2checkSD command that is longer than 256 characters.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility. The db2checkSD utility is supported with DB2 Version 9.7 for Linux, UNIX, and Windows and later.

This message is returned when an attempt is made to use the db2checkSD utility to examine a database that is older than DB2 Version 9.7.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The following authority is required to run the db2checkSD command: SYSADM or higher. This message is returned when a user without SYSADM authority or higher attempts to run the db2checkSD command.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility performs the following tasks:

1. The db2checkSD utility identifies database objects and features that are not supported in a DB2 pureScale environment by examining database structures and metadata, as well as running queries against the database.
2. The db2checkSD utility generates a user script that you can run to prepare the database to be upgraded to a DB2 pureScale environment.

This message is returned when the db2checkSD utility found some table spaces that are in a state other than 'NORMAL', which would prevent the database from being upgraded successfully to a DB2 pureScale environment.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

You can pass the name of a specific database to be checked, or you can use the -e parameter to specify that the db2checkSD utility should check all databases in the current database manager instance.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility. The db2checkSD utility identifies these unsupported database objects and features by examining database structures and metadata, and running queries against the database.

This message is returned in the following situations, among others:

• An attempt was made to run the db2checkSD command from a computer that is configured to run only a cluster caching facility (CF).
• The db2checkSD utility was unable to connect to one or more of the databases.
• The db2checkSD utility encountered an unexpected error condition while running queries against the database.

Explanation

Before converting your instance to a DB2 pureScale instance type, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned after the db2checkSD utility has finished checking each database, when it is invoked with the -e option to check all databases in the instance.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility identifies these unsupported database objects and features by examining database structures and metadata, as well as running queries against the database. This message is returned when the db2checkSD utility found an empty database directory or when the db2checkSD utility could not find a local database directory.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

The db2checkSD utility generates the following files:

• An output log file that you can review for details about the db2checkSD utility's investigations
• A user script that you can use to identify database objects or features that must be removed or disabled before upgrading the database or databases to a DB2 pureScale environment

This message is returned when the db2checkSD utility was unable to create the output log file or the generated user script.

Explanation

Before upgrading a database to a DB2 pureScale environment, you can identify any database objects or features in the database that are not supported in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility found some database objects or features in the specified database that are not supported in a DB2 pureScale environment which will be automatically converted or disabled when you upgrade the database to a DB2 pureScale environment.

Explanation

The db2checkSD utility has already been run for the database and all checks were successful. The checks were not performed again.

Explanation

You can verify that a given database can be used in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility is not able to open the database manager configuration file.

Explanation

You can verify that a given database can be used in a DB2 pureScale environment using the db2checkSD utility.

This message is returned when the db2checkSD utility is not able to open the database configuration file.

Explanation

The db2checkSD utility verifies that a database can be used in a DB2 pureScale environment. An HADR standby database must be dropped before the instance is converted to a DB2 pureScale instance and reinitialized in the DB2 pureScale environment.

Explanation

The db2checkSD utility verifies that a database can be used in a DB2 pureScale environment. The database configuration parameter HADR_SSL_LABEL is not supported in DB2 pureScale environment.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

The following authority is required to run the db2ckupgrade command: SYSADM or higher. This message is returned when a user with insufficient authority attempts to run the db2ckupgrade command.

The command failed.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

The db2ckupgrade utility generates an output log file that you can review for details about the processing done by the utility.

This message is returned when the db2ckupgrade utility was unable to open or write to the output log file.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the number of parameters specified is incorrect.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when an invalid parameter was passed to the db2ckupgrade command.

The command failed.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

You can pass the name of a specific database to be checked, or you can use the -e parameter to specify that the db2ckupgrade utility should check all databases in the current database manager instance. This message is returned when no database or databases were specified to be examined.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

The db2ckupgrade creates an output log file that contains detailed information about the investigation that the db2ckupgrade utility performed. You must specify the name of the output log file name using the -l parameter.

This message is returned when no name for the db2ckupgrade output log file was specified.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when a parameter is passed to the db2kupgrade command without a value.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when a parameter is passed to the db2ckupgrade command more than once.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility verifies that all upgrade conditions are met. You can now upgrade the database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility is unable to connect to the specified database.

The command failed.

Explanation

You can verify that a given database can successfully be upgraded to a later version using the db2ckupgrade utility.

This message is returned when the db2ckupgrade utility finds database objects which are not supported in the version to which you are upgrading. Specifically, this message is returned when the following database objects are in a database being checked:

• Global variables of type XML
• Compiled SQL functions that use parameters of type XML or that return XML types

If you proceed to upgrade the database to the target version, these objects will be invalidated during database upgrade. You will be unable to use these database objects until you upgrade to a version that supports those database objects.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when one of the parameters passed to the db2ckupgrade utility is longer than the maximum allowed length for that parameter.

Explanation

Some workload management objects are assigned default, system-reserved identifiers (ID).

This message is returned when the db2ckupgrade utility determines that an existing workload management object has an ID that happens to fall in the range of default, system-reserved IDs. The database cannot be upgraded while the workload management object with the conflicting ID exists in the database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

Typically, amount of free space defined by SYSCATSPACE should be at least the same as the current amount of used space.

This message is returned when SYSCATSPACE has less than 50% free pages left.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the database being checked is found to be in a restore pending state.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the database being checked is in the process of having a backup taken to provide a starting point for roll-forward recovery, but is still in a backup pending state.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the database being checked is enabled for roll-forward recovery and it has been restored but not rolled forward.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the database being checked is found to be in an inconsistent state.

The possible causes of this inconsistent state include

• The database is online and SQL has been issued which modified data in the database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility completes with one or more warnings but the database can still be upgraded

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

The db2ckupgrade command attempts to deactivate the specified database and stop all necessary database services. This message is returned when the db2ckupgrade utility failed to deactivate the database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility attempted to set the DB2_QP_BYPASS_COST variable but failed.

Explanation

While upgrading your database product to a higher version, you can verify whether the databases are ready to be upgraded by using the db2ckupgrade utility.

The db2ckupgrade command must be invoked from the higher version product install media or installation path.

This message is returned when the version of the db2ckupgrade utility is not higher than the database being tested, which could happen in different scenarios:

• The db2ckupgrade command was invoked from the same product as the database being tested, instead of being invoked from the higher version product.
• The database was upgraded to the higher version, and then db2ckupgrade was run against the already-upgraded database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when a previous LOAD attempt on one or more tables in the database did not complete successfully. The upgrade cannot proceed until the LOAD operation is restarted or terminated.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This messages is returned when the REDISTRIBUTE utility has not completed for one or more tables in the database. The upgrade cannot proceed until the REDISTRIBUTE is finished.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility determines that the database to be upgraded is enabled for VARCHAR2 support. Upgrading from DB2 Version 9.5 with VARCHAR2 is not supported.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned in the following situations, among others:

• An attempt was made to run the db2ckupgrade command from a computer that is configured to run only a cluster caching facility (CF).
• The db2ckupgrade utility encountered an unhandled error condition while examining database structures and metadata, and running queries against the database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility finds an empty database directory or when the db2ckupgrade utility could not find a local database directory.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

The db2ckupgrade command must start the database manager in order to perform the verifications. This message is returned when db2ckupgrade is unable to start the database manager.

The token sqlcode contains the sqlcode that was returned from the underlying start database manager call.

The command failed.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility cannot operate because I/O writes are suspended for the database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility has completed but not all upgrade conditions were met. The database cannot be upgraded.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned then the db2ckupgrade utility attempted to access a table space which is in an invalid state, for which the intended access is not allowed.

The possible causes of the inconsistent state include:

• The database is online and SQL has been issued which modified data in the database.
• The database is online and HADR has been enabled.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the -e parameter is specified but the db2ckupgrade utility is unable to find any local databases.

The command failed.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This messages is returned when the db2ckupgrade utility finds MQTs that depend on system views. During database upgrade all system views will be recreated, so any MQTs that depend on the system views will be automatically dropped.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the db2ckupgrade utility could not perform the verification because it failed to activate the database.

Explanation

Some system built-in routines such as table functions, views, or stored procedures, are discontinued in the target version of the database upgrade due to the introduction of new functionality or changes to the existing functionality.

The database upgrade to that target version drops any system built-in routines that are discontinued. To continue to use database objects that have a dependency on these system built-in routines, you have to alter these database objects and remove the dependency before the database upgrade.

This message is returned when the db2ckupgrade command detects a database object such as a view, trigger, or a user-defined stored procedure, that has a dependency on system built-in routines that are discontinued in the target version of the database upgrade.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when the HADR primary's log shipping position does not match some HADR standby's log replay position.

Before the upgrade process can begin all data produced on the primary database must be shipped and replayed by each standby database configured in the cluster.

Explanation

You can verify whether a database can be upgraded by using the db2ckupgrade utility. Before upgrading to a new version, you can identify any database objects or features in the database that are not supported in the new version using the db2ckupgrade utility.

The security administrator uses audit policies to configure the audit facility to gather information about a database. This message is returned when the db2ckupgrade utility finds audit policies that are associated with a database (entries in the SYSCAT.AUDITUSE catalog view with a blank OBJECTTYPE), but none of the entries is associated with the current database. There is no entry that has an OBJECTNAME that matches the current database name.

An audit policy is not required to upgrade the database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned after the db2ckupgrade utility has finished checking each database, when it is invoked with the -e option to check all databases in the instance.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded. When upgrading from DB2 V9.8 the database upgrade moves certain table space files to a new location. If the table space containers use an unexpected mount point configuration the table space data cannot be moved by the upgrade processing.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded. When upgrading from DB2 9.8 the files under /MEMBERnnnn/sqldbdir are consolidated to a single location. If the files in /sqldbdir are not identical on all members the upgrade processing cannot consolidate them.

Explanation

You can verify whether a database is ready to be upgraded by issuing the db2ckupgrade command. If the database is ready to be upgraded, the db2ckupgrade utility puts the database in "upgrade pending" state. When a database is in upgrade pending state, all connections are blocked.

There are two ways to bring a database out of upgrade pending state:

• Upgrade the database
• Issue the db2ckupgrade command with the -resetUpgradePending parameter

This message is returned when the db2ckupgrade utility has successfully reset the upgrade pending state of the database. No upgrade conditions were checked. Applications may connect to the database.

Explanation

You can verify whether a database is ready to be upgraded by issuing the db2ckupgrade command. If the database is ready to be upgraded, the db2ckupgrade utility puts the database in "upgrade pending" state. When a database is in upgrade pending state, all connections are blocked.

There are two ways to bring a database out of upgrade pending state:

• Upgrade the database
• Issue the db2ckupgrade command with the -resetUpgradePending parameter

This message is returned when the db2ckupgrade utility fails to reset the upgrade pending state of the database because of the error given in the runtime token sqlcode.

Explanation

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility.

The db2iupgrade utility internally calls db2ckupgrade. If the database is ready to be upgraded, the database is put into upgrade pending state. When a database is in upgrade pending state, attempts to connect to the database are blocked.

This message is returned when the db2ckupgrade command is issued internally by the db2iupgrade utility and the database has been put in upgrade pending state. The database can be upgraded.

Explanation

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility. The db2iupgrade utility internally calls db2ckupgrade.

If the db2ckupgrade utility determines that the database is ready to be upgraded, the db2ckupgrade utility puts the database into upgrade pending state.

This message is returned when the db2ckupgrade utility is called internally by the db2iupgrade utility, and an error occurs when the db2ckupgrade utility attempts to put the database into upgrade pending state. The database cannot be upgraded.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when incompatible input parameters were passed to the db2ckupgrade command.

Explanation

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility. The db2iupgrade utility calls the db2ckupgrade command internally.

If the db2ckupgrade utility determines that the database is ready to be upgraded, the db2ckupgrade utility puts the database in upgrade pending state.

This message is returned when the db2ckupgrade command is issued to verify a database that is already in upgrade pending state.

You can upgrade the database.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded. The db2ckupgrade utility requires an exclusive database connection to run all upgrade condition checks.

It tries to get exclusive database connection, but if it fails, it gets shared database connection. Under such a circumstance, it does not check all upgrade conditions.

This message is returned when the db2ckupgrade utility verifies the upgrade condition under shared database connection.

Explanation

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility.

The db2ckupgrade utility can also be used to perform some operations other than verifying whether a database is ready to be upgraded. For example: -resetUpgradePending parameter.

This message is returned when the db2ckupgrade utility successfully ran one of those operations and no upgrade conditions were checked.

Explanation

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility.

The db2ckupgrade utility can also be used to perform some operations other than verifying if a database can be upgraded. For example: resetting upgrade pending state.

This message is returned when the db2ckupgrade utility successfully run those operations, which does no upgrade condition checks.

Explanation

You can verify whether or not a database is ready to be upgraded by using the db2ckupgrade utility.

You can control which verification tests the db2ckupgrade utility performs by specifying different command parameters with the db2ckupgrade command. For example, specifying the -allChecks parameter causes the db2ckupgrade utility to perform all tests.

When the -allChecks parameter is specified with the db2ckupgrade command, the db2ckupgrade utility requires an exclusive database connection.

This message is returned when the -allChecks parameter is specified with the db2ckupgrade command but the db2ckupgrade utility failed to get an exclusive database connection.

Explanation

You can verify whether a database is ready to be upgraded by using the db2ckupgrade utility. The db2ckupgrade utility requires an exclusive database connection to run all upgrade condition checks.

If the db2ckupgrade utility fails to get an exclusive connection, the utility will fall back to using a shared connection. When the db2ckupgrade utility uses a shared connection, it does not test all upgrade conditions.

This message is returned when the db2ckupgrade utility tests only some upgrade conditions because it could only use a shared database connection.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when database upgrade on an HADR primary database is not supported. In order to proceed with the upgrade procedure, the db2ckupgrade command must stop HADR services and change the HADR role back to STANDARD.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

This message is returned when on the HADR standby database a table space is in an invalid or error state. This can be a result of a container or disk problem. A decision must be made how this impacts the upgrade procedure.

Explanation

The db2ckupgrade command is used to verify if a database can be upgraded.

Typically, amount of free space defined by SYSTEMP should be at least the same as the current amount of used space.

This message is returned when SYSTEMP has less than 50% free pages left.