Explanation

The message indicates that the instance creation failed. Instance rollback happens on all involved hosts. Instance rollback is triggered if one of the following happens:

• Any operation (DB2 binary installation, GPFS cluster setting, RSCT peer domain setting, and instance file set creation, for example) fails on install-initiating host (IIH).
• Any operation fails on a CF host.
• Any operation fails on all member hosts.

Instance rollback does not roll back DB2 binaries.

Explanation

Instance creation rollback has been performed on all involved hosts. If DB2 binaries are successfully installed, they will not be rolled back. The DB2 pureScale instance that was partially created during the current installation has been removed.

Explanation

The message occurs when the instance is partially created on some of the hosts. Instance rollback happens on the hosts where the instance creation did not complete. Some immediate messages in the installation log after this line are rollback related. Rollback of the partial instance creation is triggered if any operation (DB2 binary installation, GPFS cluster setting, RSCT peer domain setting, instance file set creation, for example) fails on a member host, then rollback happens on the corresponding host.

Instance rollback does not roll back DB2 binaries.

Explanation

This error occurs when removing the GPFS_CLUSTER global registry or the PEER_DOMAIN global registry from specific hosts.

Explanation

On Windows operating systems, the IBM Data Server Driver Package simplifies application deployment. This driver, which has a small footprint, is designed to be redistributed by independent software vendors (ISVs) and to be used for application distribution in mass deployment scenarios typical of large enterprises.

You can install the IBM Data Server Driver Package or perform a maintenance install on an existing copy of the driver package using either the DB2 Setup wizard or the SETUP command. When you install the IBM Data Server Driver Package, the behavior of the installer depends on whether there are copies of the driver package already installed and whether a driver package copy name is specified to the install utility.

This message is returned when an attempt is made to install the IBM Data Server Driver Package and the installer cannot determine whether to create a new copy of the driver package or to perform a maintenance install on an existing copy of the driver package.

Explanation

You can install multiple copies of the IBM Data Server Driver for ODBC and CLI on the same machine. You might want to do this if you have two database applications on the same machine that require different versions of the driver. When multiple copies of the driver exist on this system, you can identify one of them as the "default" copy.

To upgrade a copy of the IBM Data Server Driver for ODBC and CLI when multiple copies of the driver are installed on the same system, the upgrade utility can determine which copy to upgrade in two ways: The name of the copy to upgrade can be specified with the upgrade command. If one of the copies is identified as the default and no name is specified with the upgrade command, the upgrade utility will upgrade the default copy.

This message is returned when an attempt is made to upgrade one of multiple copies of the IBM Data Server Driver for ODBC and CLI on a system and none of the existing copies is set as the default and no coy was specified by name with the upgrade command.

Explanation

When you install the IBM Data Server Driver Package, you can specify that the Data Server Driver Package should be the default database client interface.

When the Data Server Driver Package is set as the default database client interface during install, the Path and Classpath environment variables are automatically updated to include Data Server Driver Package details. However, if the Data Server Driver Package install detects that another IBM data server client or driver is already installed, the Path and Classpath environment variables will not be updated to include Data Server Driver Package details.

This message is returned when the Data Server Driver Package install detects that another IBM data server client or driver is already installed and as a result does not update the Path or Classpath environment variables.

Explanation

During instance creation, the database product installer creates IBM Tivoli System Automation for Multiplatforms (SA MP) resources by calling the following command as the instance user:

db2cluster -cm -resources -create

Error messages returned from the db2cluster command can be found in the following log file:

<instance_user>/sqllib/db2dump/db2diag.log

If there is a problem, the directory containing this log file is backed up as /tmp/db2dump.process_id during rollback.

This message is returned when the installer encounters a problem while creating the SA MP resources for the instance.

There are multiple reasons why this message might be returned. For example, this message can be returned if the db2nodes.cfg file incorrect or failed to be created. The file can be found at <instance_user>/sqllib/db2nodes.cfg. During rollback, the file is backed up as /tmp/db2nodes.cfg.process_id.

Explanation

You can use the copy of the Tivoli System Automation for Multiplatforms (SA MP) Base Component that is integrated with your database product to manage the high availability of your database system. You can install IBM Tivoli SA MP by using either the database product installer or the installSAM installation script that is included in the database product installation media.

The database product is intended to use the version of Tivoli SA MP that is included in the database product installation media. If an older version of Tivoli SA MP is already installed before the database product is installed, Tivoli SA MP must be updated or upgraded to the version that is included in the database product installation media..

This message is returned when the database product installer detects an older version of Tivoli SA MP is already installed.

Explanation

Deletion of the RSCT peer domain error can occur during a rollback or when running the db2idrop -g command.

Explanation

You can upgrade IBM Tivoli System Automation for Multiplatforms (SA MP) using either the database product installer or the installSAM install script that is included in the IBM Data Server install media.

Depending on which database product licenses you have purchased, there are conditions under which you can use IBM Tivoli System Automation for Multiplatforms (SA MP) that is integrated with IBM Data Server.

This message is returned when a fully licensed version of SA MP Base Component is upgrade to a version of SA MP that has only a trial license. It is possible that if the host machine on which the trial version of the SA MP product is installed is restarted, the SA MP product will not longer function.

Explanation

This message indicates that the given device path for tie-breaker device path, or instance shared device, is a symbolic link. The device path must be a storage device.

Explanation

Instance resource is the RSCT resource created for the DB2 pureScale instance during instance configuration. The instance is not in a usable state.

• This error might occur when a DB2 pureScale instance creation is rolled back or a DB2 pureScale instance is dropped.
• The command that the installer internally calls is db2cluster -cm -resources -delete running as the instance user. For more details, see the db2cluster command.
• During db2idrop -g, if instance resource deletion fails, no further instance dropping action will be performed. The log file for this command is <instance_user>/sqllib/db2dump/db2diag.log.
• Check if <instance_user>/sqllib/db2nodes.cfg is valid.
• During a rollback in instance creation, instance resource deletion will also be called. Since rollback rolls back <instance_user>/sqllib, the file is backed up as /tmp/db2diag.log.process_id.

Explanation

This error can occur during partial rollback or db2iupdt -drop. It occurs because shrinking of the RSCT peer domain has failed.

Explanation

This error occurs when the cluster interconnect netname for a host is not on the same subnet as the installation-initiating host.

All cluster interconnects need to be on the same subnet for performance reasons (all hosts within the same subnet can usually be reached in one routing hop). For example if the cluster interconnect network is configured with the network address 192.168.0.0/24, then all cluster interconnect netname addresses should start with 192.168.0 (for example, 192.168.0.1, 192.168.0.2, and so on).

Explanation

The database product installer cannot identify the cluster interconnect netname.

Explanation

When adding a new host, validation checks to see if the new host can send a small data packet to the install-initiating host (IIH) and receive a reply. This send-reply test is commonly known as a ping. This message is the result of a failed ping.

Explanation

The DEFAULT_INSTPROF record in the Global Registry indicates the instance shared file system has already been set up by the database product installer. In this case, the following options or keywords are not needed:

• For response file installations:
  • INSTANCE_SHARED_DEVICE_PATH
  • INSTANCE_SHARED_DIR
• For the db2icrt or db2iupdt command:
  • instance_shared_dev
  • instance_shared_dir

If the value for INSTANCE_SHARED_DIR (or instance_shared_dir) does not match with the existing instance shared file system mount point, the installation fails.

Explanation

A GPFS cluster created by the DB2 software already exists. To create a DB2 pureScale instance by reusing this GPFS cluster, bring the cluster online on the specified host.

Explanation

This message occurs if the global registry variable record specified indicates that a shared file system already exists. The database product expects a shared file system exists for the instance shared file.

The directory name value is the mount point for the file system. The database product installer detects the mount point does not exist on the system. A possible reason is the specified global registry record is left over from a previous DB2 operation and the actual file system does not exist anymore, or, the filesystem was remounted somewhere else but the registry entry was not changed.

Explanation

The global registry variable record GPFS_CLUSTER indicates that there is a DB2-created GPFS cluster on the host. In this case, the installer detects there is no GPFS cluster on the host. The database product expects an existing GPFS cluster on this host.

Explanation

This error occurs when the database product installer fails to create an IBM Reliable Scalable Cluster Technology (RSCT) peer domain on a host because another, user-managed RSCT peer domain is active.

The peer domain that was not created by the database product installer must be stopped or removed prior to creating an RSCT peer domain by the database product installer.

Explanation

This message indicates that the given device path for tie-breaker device path, or instance shared device, is not a storage device. The device path must be a storage device. A device can be invalid for the following reasons:

• there are existing files or directories
• the device does not exist
• the device is not a storage device, such as pipe, fifo device, character device
• root has no searchable access authority to the given path
• the path name is too long.

Explanation

This error occurs when the database product installer detects that an RSCT peer domain was previously created on a host, but it is offline and the installation-initiating host is in a different RSCT peer domain. The remote host must be removed from the host list.

Explanation

This post installation message shows the hosts that have not been included in the instance due to an error. If DB2 binaries were successfully installed, they have not been removed. Look in the installation log for more information on the error that has caused this rollback.

Explanation

The GPFS cluster failed to be created during instance creation. This failure will trigger an instance creation rollback.

The db2cluster command log file can be found in /tmp/ibm.db2.cluster.*

Explanation

This message occurs when the GPFS cluster fails to be deleted during a rollback.

Explanation

This message occurs when the GPFS file system creation fails.

Explanation

This message occurs when the GPFS cluster extension to the host fails.

Explanation

This message occurs when the newly created GPFS file system fails to be deleted during a rollback.

Explanation

This error occurs because a validation process on the remote machine did not return within the required time out period.

Explanation

This message occurs when the GPFS cluster fails to remove the host.

Explanation

The db2cluster_prepare command did not detect a IBM General Parallel File System (GPFS). Running the db2cluster_prepare command is not required. When creating a DB2 pureScale instance, a GPFS file system will be created for you.

Explanation

This message occurs because there is no device path that can be found on the remote host with the same PVID as the given device path on the IIH. A matching PVID is required on the remote host.

Explanation

This error occurs when the database product installer detects that an RSCT peer domain was previously created by the DB2 pureScale Feature.

Explanation

This error occurs when the database product installer detects that an RSCT peer domain was previously created by the DB2 pureScale Feature but the installation-initiating host is in a different RSCT peer domain.

Explanation

The database product does not allow the joining of multiple GPFS clusters. The current host and the remote host indicated belongs to different GPFS clusters.

When the install-initiating host (IIH) is part of a GPFS cluster, the remote host should either not belong to a GPFS cluster, or, belong to the same GPFS cluster. When IIH is not part of a GPFS cluster, the remote host should not belong to a GPFS cluster.

Explanation

New copies must be installed to a path which does not contain an existing copy.

Explanation

The path and name pair provided in the response file by keywords FILE and DB2_COPY_NAME is invalid. The path specified contains an existing DB2 copy with a copy name that is different from the copy name provided. A path may only contain a single DB2 copy.

Explanation

The db2iupdt -drop command will not drop the last cluster caching facility or the last member, in the DB2 pureScale instance. You must run the db2iupdt -drop command from a host that will still belong to the instance after you've dropped the cluster caching facility or member.

Explanation

The DB2_COPY_NAME provided exists, but not on the path provided. When working with an existing copy of database product installed on Windows, the correct installation path must be specified.

Explanation

The temporary directory is used by the database manager to store files necessary for creating and managing instances and database objects. To install or update DB2 the temporary directory must be enabled for read, write and execute access to all users.

Explanation

The specified parameter is either missing, or invalid. Some parameters are mandatory in a response file for the specified command, however, certain combinations are not supported. For example, the PREFERRED_PRIMARY_CF parameter, or the PREFERRED_SECONDARY_CF parameter, can only be specified for a instance type of 'dsf'.

Explanation

The DB2 pureScale Feature for Linux is only supported on specific distributions.

User Action Consult the documentation for installing the DB2 pureScale Feature for information on software considerations in the installation prerequisites.

Explanation

The user Direct Access Programming Library (uDAPL) configuration file could not be accessed while attempting to create the DB2 pureScale instance. The DAPL configuration file is referenced by the DB2 pureScale Feature to verify the presence of a remote direct memory access (RDMA) capable network adapter. The file must be accessible on the path /etc/dat.conf.

Explanation

All software components of the DB2 pureScale Feature are installed and configured from a single host. If the installation of the feature fails on any one of the host machines, the database product installation process cannot complete.

There are several reasons why the installation process might have failed on a host machine:

• The host name cannot be found.
• The host is unreachable.
• Someone other than the root user is performing the installation.
• Your system does not meet all uDAPL or InfiniBand prerequisites.
• There is not enough disk space available in the /root or /tmp path to complete the installation.

Explanation

All hosts in a DB2 pureScale environment must be connected to a low latency, high-speed interconnect.

Explanation

The database product installer cannot detect which hosts require the fix pack to be applied.

Explanation

The installFixPack -p parameter does not automatically update instances. This must be performed manually.

Explanation

The fix pack was not installed successfully. The error log contains details.

Explanation

In environments that are not DB2 pureScale environments, a fix pack cannot be applied across hosts.

In DB2 pureScale environments, to apply fix pack update across multiple hosts, the DB2 copy must have the DB2 pureScale component installed on every host.

Explanation

All hosts must have the same service level to proceed.

Explanation

The IIH host must be listed in the host list file provided by the -H parameter.

Explanation

A database manager instance can be configured during product installation. TCP/IP port values are one of the settings that can be set during instance configuration. The TCP/IP port number is used by a database manager instance to listen for incoming DB2 connections. This message is displayed when an invalid invalid port number is entered. This message also appears in the log file created during a silent install operation

Explanation

The IBM Database Add-Ins for Visual Studio are included as a separately installable component. Once you are finished installing your database product, you will be presented with an option to install the IBM Database Add-Ins for Visual Studio.

This message is returned when the option to install the IBM Database Add-Ins for Visual Studio is selected and a supported version of Visual Studio and a .NET Framework are not installed.

Explanation

The IBM Database Add-Ins for Visual Studio are included as a separately installable component. Once you are finished installing your database product, you will be presented with an option to install the IBM Database Add-Ins for Visual Studio.

If you have Visual Studio 2008 and Visual Studio 2005 but your Visual Studio 2005 is not at the Service Pack 1 level, then VSAI will only be installed on Visual Studio 2008.

Explanation

The installer can create Windows user accounts during the install process, for example a user account can be create as the instance owner. During uninstall you have the option to delete any Windows user accounts created by the installer during the install process.

This message is displayed when, during a database product uninstall, the uninstall utility tried to delete a Windows user account but failed.

Explanation

The installer can create Windows group accounts during the install process. During uninstall you have the option to delete any Windows group accounts created by the installer during the install process. This message is displayed when, during a database product uninstall, the uninstall utility tried to delete a group account but failed.

Explanation

The installer can create Windows user and group accounts during the install process. This message is displayed when, during a database product uninstall, users and group accounts are found. These might be in use by another DB2 copy or by other applications. It is recommended keeping these accounts.

Explanation

The installer can create Windows user accounts during the install process. This message is displayed when, during a database product uninstall, user accounts were found. These might be in use by another DB2 copy or by other applications. It is recommended keeping these accounts.

Explanation

The installer can create Windows user group accounts during the install process. This message is displayed when, during a database product uninstall, user group accounts were found. These groups may be in use by another DB2 copy or by other applications. It is recommended keeping these accounts.

Explanation

You can securely run commands from remote machines by using a secure shell (SSH) server product such as IBM Secure Shell Server for Windows or Open Secure Shell (OpenSSH) on Linux and AIX operating systems.

This message is returned when the database product installer is configuring a SSH server in an environment with IBM General Parallel File System (GPFS) and the installer is unable to complete that SSH configuration on one or more host machines because GPFS is offline.

Explanation

A copy refers to one or more installations of the database product on the same computer. If you attempt to upgrade from an unsupported version, the copy upgrade will fail.

Explanation

Running the db2cluster_prepare command to takeover the cluster was unnecessary. DB2 cluster services are managing the cluster.

Explanation

While running the command, the GPFS cluster failed a verification test of the requirements for the DB2 pureScale Feature.

Explanation

The DB2 global registry file on the identified hosts could not be modified during the operation.

Explanation

The DB2 global registry file on the identified hosts could not be modified during the operation.

Explanation

All hosts in a DB2 pureScale instance must be able to communicate with all other hosts participating in the instance. The communication can be configured to use one of the following methods:

• db2locssh
• Passwordless SSH

This message is returned when the instance is configured to use passwordless SSH and the installer is unable to communicate between two host machines using passwordless SSH.

Explanation

The missing component is a prerequisite to running the command.

Explanation

The user-managed cluster is now managed by DB2 cluster services.

Explanation

The DB2 cluster services tiebreaker disk helps a subcluster obtain operational quorum in the event of a failure that leaves exactly half of the DB2 pureScale instance hosts able to communicate with each other. In this event, the subcluster will attempt to get an exclusive lock on the disk to achieve operational quorum. The DB2 pureScale instance can operate without a configured tiebreaker disk, however the instance is more resilient with one.

Explanation

All response file keywords must be applicable to the installation, and all keyword values must be valid. Some commands and keywords are only valid when run by the instance owner, or when the installation includes specific components, features, or configurations.

Explanation

Administrative or root authority is required to use the specified keyword when performing a response file installation.

Explanation

The installation cannot configure IBM Secure Shell Server to automatically start on this port.

Explanation

The IBM Secure Shell Server installation directory cannot be the same as a database product installation directory.

Explanation

The database product installer detected an error with the version of the IBM Secure Shell Server binaries. The fix pack installation cannot continue.

Explanation

An error occurred during the uninstallation of the IBM Secure Shell Server. IBM Secure Shell Server was not uninstalled.

Explanation

An error occurred during the uninstallation of the IBM Secure Shell Server. IBM Secure Shell Server was not uninstalled.

Explanation

A 32-bit and 64-bit version of a database product cannot coexist on a host machine.

Explanation

There is not enough free space available.

Explanation

In a pureScale environment, a shared disk path is required to hold shared instance and database files. When a database manager instance is created by using the db2icrt command, the shared disk path is specified by using the -instance_shared_dev parameter.

This message is returned when the database product installer does not have write permission for the specified shared disk path.

Explanation

The user Direct Access Programming Library (uDAPL) configuration file, dat.conf, is referenced by the DB2 pureScale Feature to verify the presence of a remote direct memory access (RDMA) capable network adapter. Exactly one copy of the file must be accessible under the appropriate subdirectory of /etc.

This message is returned when the database product installer found more than one of these uDAPL configuration files. If multiple uDAPL configuration files exist, the database product installer cannot determine which set of configurations to use.

Explanation

Two Windows groups are used by the database manager to enforce extended Windows security: the DB2 administrators group, which is named "DB2ADMINS" by default; and the DB2 users group, which is named "DB2USERS" by default. These groups are used by the database manager to provide protection at the operating system level.

The DB2 administrators group and the DB2 users group may both be local groups or they may both be domain groups. If the DB2 administrators group and the DB2 users group are domain groups, they must be in the same domain as each other.

Explanation

You can update a database manager instance to a higher level within a release, update an instance other than a DB2 pureScale instance to a DB2 pureScale instance, or scale a DB2 pureScale instance by using the db2iupdt command.

This message is returned when an an attempt is made to perform an instance update operation on a given instance, but the update operation cannot proceed because there is a conflict with resources that were not completely removed during a previous attempt to drop one or more instances.

Explanation

You can update a database manager instance to a higher level within a release, update an instance other than a DB2 pureScale instance to a DB2 pureScale instance, or scale a DB2 pureScale instance by using the db2iupdt command.

This message can be returned in two scenarios:

• The db2iupdt command is called with the -update parameter and a cluster caching facility (CF) that is not part of the DB2 cluster is specified with the -cf parameter
• The db2iupdt command is called with the -update parameter and a DB2 member that is not part of the DB2 cluster is specified with the -m parameter

Explanation

The db2dsdriver.cfg file was not moved to the destination directory. The following directory is not accessible:

• On Windows XP Professional and Windows Server 2003 the path is:

  
  C:\Documents and Settings\
  All Users\Application Data\IBM\DB2\
  <driver-copy-name>\cfg
  

• On Windows Vista, Windows 7, and Windows Server 2008 the path is:

  
  C:\ProgramData\IBM\DB2\<driver-copy-name>\cfg
  

Explanation

The DB2 pureScale Feature uses General Parallel File System (GPFS) as the shared-disk file system to provide data access across all members in a DB2 pureScale environment. GPFS requires certain commands to run as root on all hosts that are part of the GPFS domain. There are two ways to confgure your environment to meet this GPFS requirement:

• You can enable passwordless remote root login using standard SSH public key authentication.
• In DB2 Version 10.1 Fix Pack 2 and later fix packs, if you are using a DB2 managed GPFS file system for new DB2 pureScale installations, passwordless remote root login is no longer required. You can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts.

This message is returned when the database product installer fails to install the DB2 utilities that support using the db2sshid.

Explanation

The response file used during silent installation has detected an unknown keyword.

Explanation

In DB2 Version 10.1 Fix Pack 2 and later fix packs, if you are using a DB2 managed GPFS file system for new DB2 pureScale installations, you can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts instead of using passwordless remote root login. There are several DB2 SSH utilities located in the db2ssh directory to support using the db2sshid.

This message is returned when the database product installer detects that the db2ssh directory is w-writable. The permissions of the db2ssh directory should allow only root users write access to the directory.

Explanation

In DB2 Version 10.1 Fix Pack 2 and later fix packs, if you are using a DB2 managed GPFS file system for new DB2 pureScale installations, you can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts instead of using passwordless remote root login.

One of the DB2 utilities that supports using the db2sshid is the db2locssh script. During install, the database product installer attempts to use operating system commands to set the owner of the db2locssh script to the db2sshid. However, if the installer is unable to set the owner of the db2locssh script to the db2sshid the installer will set the owner of the db2locssh script to the current instance owner ID.

This message is returned when the database product installer sets the owner of the db2locssh script to the current instance owner ID because the installer failed to set the owner of the db2locssh script to the db2sshid.

Explanation

In DB2 Version 10.1 Fix Pack 2 and later fix packs, if you are using a DB2 managed GPFS file system for new DB2 pureScale installations, you can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts instead of using passwordless remote root login.

One of the DB2 utilities that supports using the db2sshid is the db2locssh script. During install, the database product installer verifies that the db2locssh script is functioning correctly.

This message is returned when the database product installer is unable to successfully verify the db2locssh functionality.

Explanation

In DB2 Version 10.1 Fix Pack 2 and later fix packs, if you are using a DB2 managed GPFS file system for new DB2 pureScale installations, you can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts instead of using passwordless remote root login. To use the db2sshid, you need to create a user id on all hosts in the DB2 cluster, including the installation-initiating host, and then pass that user id to the db2icrt command with the -i parameter.

This message is returned when an attempt is made to specify a user id as a db2sshid but the specified user id does not exist on all hosts in the cluster.

Explanation

In DB2 Version 10.1 Fix Pack 2 and later fix packs, if you are using a DB2 managed GPFS file system for new DB2 pureScale installations, you can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts instead of using passwordless remote root login. For the db2sshid to be used, a public key must be distributed to all hosts in the DB2 cluster.

This message is returned what the database product installer fails to distribute the public key to all of the hosts in the cluster during an upgrade or update operation.

Explanation

In DB2 Version 10.1 Fix Pack 2 and later fix packs, if you are using a DB2 managed GPFS file system for new DB2 pureScale installations, you can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts instead of using passwordless remote root login. For the db2sshid to be used, a public key must be distributed to all hosts in the DB2 cluster.

This message is returned what the database product installer fails to create the public key during instance creation or or update operation.

Explanation

In DB2 Version 10.1 Fix Pack 2 and later fix packs, if you are using a DB2 managed GPFS file system for new DB2 pureScale installations, you can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts instead of using passwordless remote root login. For the db2sshid to be used, a public key must be distributed to all hosts in the DB2 cluster.

This message is returned what the database product installer fails to create the public key during instance creation or or update operation.

Explanation

In an existing DB2 pureScale cluster, if the cluster caching facility (CF) is running, a member cannot be added to the CF host. Before a member can be added, the CF must be stopped using the db2stop command.

Explanation

You can uninstall one or more database products, features, or languages by using the db2unins utility.

You can run the db2unins command either from the installed copy of DB2 database or from the DB2 database installation media:

• Some db2unins parameters are only supported when the command is run from an installed copy of DB2 database.
• Some db2unins command parameters are only supported when the command is run from the installation media.

You can perform a forced uninstallation of all database products on the system by specifying the -f parameter with the db2unins command. The -f parameter is one of the parameters that can only be used when the db2unins command is run from the installation media.

This message is returned when the command is run from an installed copy of DB2 database and the -f parameter is specified. The command fails because the -f parameter cannot be specified when the command is run from an installed copy of DB2 database.

Explanation

The IBM Data Server Driver Package software simplifies application deployment. This driver, which has a small footprint, is designed to be used by independent software vendors (ISVs) for mass application deployment scenarios that are typical of large enterprises.

This message is returned when an attempt is made to upgrade the version of the IBM Data Server Driver Package software, and updating from the current version to the new version is not supported.

Explanation

The IBM Database Add-Ins for Visual Studio software is a collection of features that integrate seamlessly into your Visual Studio development environment so that you can work with database servers and develop procedures, functions, and objects.

This message is returned when an attempt is made to upgrade IBM Database Add-Ins for Visual Studio, and updating from the current version to the new version is not supported.

Explanation

The IBM Data Server Driver Package software simplifies application deployment. This driver, which has a small footprint, is designed to be used by independent software vendors (ISVs) for mass application deployment scenarios that are typical of large enterprises.

This message is returned when an attempt is made to upgrade the version of the IBM Data Server Driver Package software, and updating from the current version to the new version is not supported.

Explanation

The IBM Database Add-Ins for Visual Studio software is a collection of features that integrate seamlessly into your Visual Studio development environment so that you can work with database servers and develop database objects.

This message is returned when an attempt is made to upgrade IBM Database Add-Ins for Visual Studio, and updating from the current version to the new version is not supported.

Explanation

You can update installed database products to apply a fix pack by using the installFixPack command.

This message is returned when there is a problem with one or more of the specified command parameters, including the following example problems:

• A parameter was specified that is not supported with the installFixPack command
• A parameter was specified that is not valid for the operating environment or for the type of database manager instance

Explanation

The database product installer installs files related to database functionality as well as files for software that is bundled with the database software.

This message is returned when the database product installer encounters a problem copying some files from the install media to the install location.

Explanation

On Windows operating systems, you can launch the setup wizard to install database products. You can perform a response file installation by specifying the -u parameter with the setup command.

This message is returned when an attempt is made to use one of the installation packages (such as DB2Serer.msi, for example) directly, which is not supported.

Explanation

You can remove database products or database product components by using the db2_deinstall command.

This message is returned when an attempt is made to uninstall a database product where the current host is part of an IBM General Parallel File System (GPFS) cluster that includes remote hosts.

Explanation

When a new DB2 member is being added to a DB2 pureScale instance, it is database product install and configuration utilities that add the new member. While the database product install utility processes an add member request, the utility validates the IBM Reliable Scalable Cluster Technology (RSCT) peer domain.

This warning message is printed when the database product install utility detects a problem with the RSCT peer domain while the utility is processing an add member request. (The problem with the RSCT peer domain configuration could have been caused by an error during a previous add member operation, for example.)

This warning message is printed when the RSCT peer domain validation failure does not cause the current add member operation to fail. This warning is printed for your information only.

Explanation

When a new DB2 member is being added to a DB2 pureScale instance, it is database product install and configuration utilities that add the new member. While the database product install utility processes an add member request, the utility validates several aspects of the environment and of the database manager instance itself.

This warning message is printed when the database product install utility detects a problem with the instance home directory while the utility is processing an add member request. (The problem with the instance home directory could have been caused by an error during a previous add member operation, for example.)

This warning message is printed when the directory structure validation failure does not cause the current add member operation to fail. This warning is printed for your information only.

Explanation

When a new DB2 member is being added to a DB2 pureScale instance, it is database product install and configuration utilities that add the new member. To accomplish the add member operation, the database product install utility performs many tasks.

This warning message is printed when the database product install utility encounters a recoverable error while processing an add member request. (The problem could have been caused by an error during a previous add member operation, for example.)

This warning message is printed when the failure does not cause the current add member operation to fail. This warning is printed for your information only.

Explanation

You can install database software without any user interaction by using a response file.

A response file is an English-only text file that contains setup and configuration information in the form of keywords and keyword-value pairs.

This message is returned when an attempt is made to perform an installation operation with a response file that includes an invalid keyword.

Explanation

You can create a database manager instance by running the db2icrt command. You specify the user name of the instance with the InstName parameter.

To create a DB2 pureScale instance, you must specify an instance name that can rlogin to host machines in the DB2 pureScale cluster. On AIX operating systems, you can enable a user name to rlogin to a host machine by setting the rlogin attribute to TRUE in the security file named /etc/security/user.

This message is returned when the database manager fails to create a DB2 pureScale instance because the rlogin attribute is not set to TRUE for the user name of the instance.

Explanation

You can create a database manager instance by using the db2icrt command.

On Windows operating systems only, and with multiple database partition instances only, you can override the default TCP/IP host name by using the -h parameter with the db2icrt command.

This message is returned when the -h parameter is specified, but no host name is specified with the -h parameter.

Explanation

If you are using a DB2 managed GPFS file system for new DB2 pureScale installations, you can use the non-root user ID (db2sshid) to use a secure shell (SSH) network protocol between hosts. To use the db2sshid, you need to create a user with the same user ID (UID) and group ID (GID) on all hosts in the DB2 cluster, and then pass that user id to the db2icrt command with the -i parameter.

This message is returned when an attempt is made to specify a user id as a db2sshid but the specified user id does not exist with the same UID and GID on every host machine in the DB2 cluster.

Explanation

To be able to create a DB2 pureScale instance, three users must exist:

1. A user for the instance owner
2. A non-root user to use a secure shell (SSH) network protocol between hosts
3. Another user to run fenced user-defined functions or procedures

These three users are required on all servers hosting a cluster caching facility (CF) or a DB2 member. For each of these three users, the user ID (UID) and group ID (GID) must be the same on all host machines in the DB2 cluster.

This message is returned when an attempt is made to invoke an install-related command or a configuration-related command, specifying an instance user that does not exist with the same UID and GID on every host machine in the DB2 cluster.

Explanation

You can add one or more interconnect netnames to a DB2 member or cluster caching facility (CF) in a DB2 pureScale instance by calling the db2iupdt command:

• To update the netname for a member, specify a comma-separated list of netnames with the the -mnet parameter
• To update the netname for a CF, specify a comma-separated list of netnames with the the -cfnet parameter

A prerequisite for updating the netname of a member or CF is that the target member or CF must be stopped before calling the db2iupdt command.

This message is returned when an attempt is made to update the netname of a member or CF while the target member or CF is active.

Explanation

You can update installed database products to apply a fix pack by using the installFixPack command.

This message is returned when there is a problem with the value that was specified for one or more of the command parameters, including the following example problems:

• An invalid value was specified for a parameter
• A value was specified that is not valid for the operating environment or for the type of database manager instance
• Conflicting values, values that are not supported together, were specified

Explanation

You can convert a database manager instance to a DB2 pureScale instance by using the DB2 Setup Wizard or the db2iupdt command. There are a number of prerequisites for converting an instance to a DB2 pureScale instance, including that all data and logs be on an IBM General Parallel File System (GPFS).

This message is returned when an attempt is made to convert an instance to a DB2 pureScale instance, but the attempt fails because all data and logs are not on a GPFS file system.

Explanation

You can upgrade the version of an installed database product by using a response file.

On Windows operating systems and on non-root installations on Linux and UNIX operating systems, to upgrade the version of an installed database product by using a response file, you must set the UPGRADE_PRIOR_VERSIONS response file keyword to TRUE.

This message is returned when an attempt is made to perform a response file upgrade on a Windows operating system or with a non-root installation on a Linux or UNIX operating system and the UPGRADE_PRIOR_VERSIONS response file keyword is not set to TRUE.

Explanation

When you are creating or updating a DB2 pureScale instance, you must specify the cluster interconnect netname for DB2 members and CFs. The cluster interconnect netname is the hostname of the interconnect used for high speed communication between members and cluster caching facilities (also referred to as CF.)

This message is returned when an attempt is made to create or update a DB2 pureScale instance, and a netname that does not exist is specified for a member or CF.

Explanation

When you are creating or updating a DB2 pureScale instance, you must specify the cluster interconnect netname for DB2 members and CFs. The cluster interconnect netname is the hostname of the interconnect used for high speed communication between members and cluster caching facilities (also referred to as CF.)

All members and CFs must be on the same subnet for performance reasons. This message is returned when an attempt is made to create or update a DB2 pureScale instance, and a member or CF netname is specified that is not on the same subnet as the netnames for the other members and CFs.

Explanation

You can upgrade a DB2 pureScale instance to a new release by using the db2iupgrade command. You can upgrade all hosts in the DB2 cluster simultaneously by specifying the -g parameter with the db2iupgrade command.

This message is returned when the db2iupgrade command is issued to upgrade a DB2 pureScale instance, but the db2iupgrade utility is unable to reach a host machine in the DB2 cluster.

Explanation

Software such as Reliable Scalable Cluster Technology (RSCT), IBM Tivoli System Automation for Multiplatforms (SA MP), and IBM General Parallel File System (GPFS) is bundled with the database product and installed by the database product installer when you install the database product.

This message is returned when the database product installer detects that software that is bundled with the database product is already on the system and was installed or maintained by some mechanism other than the database product installer.

By default, the database product installer will not replace or update software that was not installed or maintained by the database product installer. You can force the database product installer to replace or update bundled software by specifying the appropriate software keyword with the -f parameter.

Explanation

Some operations cannot be performed while a fix pack update is in progress. This message is returned when an attempt is made to perform one of these restricted operations while a fix pack update is in progress.

Explanation

During an offline or online fix pack update of a DB2 pureScale instance, there will be times when DB2 members and cluster caching facilities (CFs) have a different code level from the current effective code level (CECL). The instance is said to be in a heterogeneous state when there are members or CFs at the CECL and at least one member or CF has a code level different from the CECL.

Some operations cannot be performed while an instance is in a heterogeneous state. This message is returned when an attempt is made to perform one of these restricted operations while instance is in a heterogeneous state.

Explanation

You can update the version to a higher code level within a release without having to bring your database offline by using an online fix pack update.

An online fix pack update is accomplished by updating each DB2 member and cluster caching facility (CF) individually: taking the member or CF offline, updating the code level, and bringing that member or CF online again. Because a DB2 pureScale instance is designed to be available even when one member or CF is offline, this is how the instance can remain online throughout the update.

This message is returned during an online fix pack update when the installFixPack utility discovers that the secondary CF is not in a suitable state to keep the instance available if the primary CF is taken offline to perform the update.

Explanation

You can update the version to a higher code level within a release without having to bring your database offline by using an online fix pack update.

An online fix pack update is accomplished by updating each DB2 member and cluster caching facility (CF) individually: taking the member or CF offline, updating the code level, and bringing that member or CF online again. Because a DB2 pureScale instance is designed to be available even when a members or CF is offline, this is how the instance can remain online throughout the update.

This message is returned when an attempt is made to perform an online fix pack update on a DB2 pureScale instance that has only one active member. Because there is only one member active, taking that member offline to update it would cause the whole instance to be unavailable.

Explanation

You can update the version to a higher code level within a release without having to bring your database offline by using an online fix pack update. To perform an online fix pack update, you call the installFixPack command.

There are some restrictions related to performing an online fix pack update. For example, an online fix pack update cannot be performed if a DB2 member or cluster caching facility (CF) is in restart light mode. This message is returned when an attempt is made to perform an online fix pack update while a member or CF is in restart light mode.

Explanation

For many database manager commands, some parameter are mandatory in certain conditions.

This message is returned when a command is invoked in a DB2 pureScale environment, but some parameters that are mandatory for DB2 pureScale instances are not specified.

Explanation

You can update the version to a higher code level within a release without having to bring your database offline by using an online fix pack update. To perform an online fix pack update, you call the installFixPack command specifying the -online parameter.

This message is returned when the installFixPack command is called with the -online parameter specified, but the instance being updated is currently stopped. It is impossible to perform an online fix pack update of an instance that is stopped.

Explanation

The fenced user is used to run user defined functions (UDFs) and stored procedures outside of the address space used by the DB2 database.

This message is returned when an attempt is made to create an instance, but the database product installer could not determine the fenced user ID.

Explanation

When installing the database product, you can specify the install path. For example, you can specify the install path with the -b parameter of the db2_install command. If you do not specify an install path, the default install path will be used: $HOME/sqllib.

This message is returned when an attempt is made to create an instance, but the database product installer could not determine the install path.

Explanation

This message is returned when the database product installer encounters an internal error while creating a database manager instance.

Explanation

You can update installed database products to apply a fix pack by using the installFixPack command.

When you run the installFixPack command in non-interactive mode, you must specify the path where the database product is currently installed with the -b parameter.

This message is returned when the installFixPack command is called with an invalid base path specified with the -b parameter. The path might be invalid for different reasons, including that the path does not exist.

Explanation

You can update installed database products to apply a fix pack by using the installFixPack command.

You can specify the name of the instance to update with the -I parameter. And you can specify the base install path of the instance with the -b parameter.

This message is returned when the installFixPack command is called with incompatible values for the -I parameter and the -b parameter: the instance that is specified with the -I parameter is not installed in the path that is specified with the -b parameter.

Explanation

You can create a database manager instance by calling the db2icrt command.

You can control the type of instance that is created by specifying the -s parameter with the db2icrt command. If the -s parameter is not specified, the db2icrt utility will create the default type of instance. The default instance type is the first instance in the following list that the DB2 copy is licensed to create:

1. dsf
2. ese
3. wse
4. standalone
5. client

This message is returned when the db2icrt utility attempts to create a DB2 pureScale instance, either because a value of 'dsf' was specified with the -s parameter or because the -s parameter was not specified and the default type is 'dsf', but one or more parameters that are required to create a DB2 pureScale instance were not specified. The runtime token parameter-list lists all of the parameters that are required but were not specified.

Explanation

You can create a database manager instance by calling the db2icrt command.

This message is returned when one or more invalid parameters are specified with the db2icrt command. The parameter-list runtime token lists the parameter or parameters that are invalid.

Explanation

You can change or reconfigure the topology of a DB2 pureScale instance by calling the db2iupdt command with parameters such as: -add, -drop, -update, and -fixtopology.

This message is returned when the db2iupdt command is called with one of these topology configuring parameters specified, but the instance being updated is not a DB2 pureScale instance.

Explanation

You can convert an instance to a DB2 pureScale type of instance by calling the db2iupdt command, specifying conversion parameters such as: -instance_shared_dev or -instance_shared_dir parameter.

This message is returned when the db2iupdt command is called with some parameters that are related to the DB2 pureScale Feature, but the instance is not a DB2 pureScale instance and conversion parameters were not specified.

Explanation

You can change or reconfigure the topology of a DB2 pureScale instance by calling the db2iupdt command with parameters such as: -add, -drop, -update, and -fixtopology.

This message is returned when the db2iupdt command is called with some DB2 pureScale Feature parameters, but topology configuration parameters were not specified.

Explanation

You can change or reconfigure the topology of a DB2 pureScale instance by calling the db2iupdt command with parameters such as: -add, -drop, -update, and -fixtopology.

You can convert an instance to a DB2 pureScale type of instance by calling the db2iupdt command, specifying conversion parameters such as: -instance_shared_dev and -instance_shared_dir parameter.

This message is returned when the db2iupdt command is called with conversion parameters specified against an instance that is already a DB2 pureScale instance.

Explanation

You can create a database manager instance by calling the db2icrt command. You specify the name of the instance to be created when you call the command:

db2icrt <new-instance-name>

There is a length restriction on instance names: instance names must have 8 characters or less. This message is returned is returned when the db2icrt command is called, with an instance name specified that is longer than 8 characters.

Explanation

You can install a new version of DB2 software and upgrade existing database manager instances by using a response file installation. Response files contain values that are used to answer questions during the installation process that you would normally answer if you were using an interactive tool such as the DB2 Setup wizard.

When you are installing a database product in the same location as an existing database product using a response file installation, you must use the UPGRADE_PRIOR_VERSIONS keyword in the response file to specify whether the existing database product should be upgraded or overwritten.

This message is returned when, during a response file installation, the installer detects that an older version of the database product is installed in the specified install directory but the UPGRADE_PRIOR_VERSIONS keyword is not specified in the response file.

Explanation

You can add a DB2 member or a cluster caching facility (CF) to a DB2 pureScale instance by invoking the db2iupdt command with the -add parameter. You can drop a DB2 member or a CF from a DB2 pureScale instance by invoking the db2iupdt command with the -drop parameter.

You can specify the details for a member to add or drop by using the -m and -mnet parameters. You can specify the details for a CF to add or drop by using the -cf and -cfnet parameters. However, it is not supported to add or drop both a member and a CF in one invocation of the db2iupdt command. In other words, it is not supported to specify both the -m parameter and the -cf parameter together.

This message is returned when the -m parameter is specified and the -cf parameter is also specified.

Explanation

This message is returned when a command is invoked with parameters that are invalid for one the following reasons:

• The parameter is not part of the command syntax
• The parameter is not supported in the current environment
• The parameter is not supported with the current product edition

Explanation

You can install DB2 database by using the db2_install utility as a root user or as a non-root user:

• When you install DB2 database as a root user by invoking the db2_install command, you can specify the install path with the -b parameter.
• When you install DB2 database as a non-root user by invoking the db2_install command, the only supported install path is /home/<user>.

This message is returned when the db2_install command is invoked by a non-root user and a path other than /home/<user> is specified with the -b parameter. When a non-root user specifies a path other than /home/<user> with the -b parameter, the db2_install utility ignores the -b parameter and installs the database product in /home/<user>.

Explanation

This message is returned when an install utility or an instance configuration utility fails to perform required tasks because the utility cannot write to the instance home directory.

The install and instance configuration utilities perform tasks as the user who invoked the command, so this error could be phrased as: the operation failed because the user who invoked the command does not have write access to the instance home directory.

Explanation

You can create a database manager instance by calling the db2icrt command. Not all db2icrt command parameters are applicable to every instance creation scenario. For example, parameters such as -m and -tbdev are applicable only to creating a DB2 pureScale instance.

This message is returned when the db2icrt command is invoked with parameters that are related to the DB2 pureScale Feature, but the DB2 pureScale Feature is not installed.

Explanation

You can install most database products as a non-root user. Non-root installations have most of the function of root installations, but there are some differences. For example, in non-root installations, the database product may only be installed in a subdirectory called "sqllib" in the home directory of the user who invokes the db2_install command ($HOME/sqllib).

This message is returned when the db2_install command is invoked by a non-root user and a path other than $HOME/sqllib is specified with the -b parameter.

Explanation

You can update the version of a database manager instance, configure the topology of a DB2 pureScale instance, or convert an instance to a DB2 pureScale instance by invoking the db2iupdt command.

You can upgrade an instance from one product release to another by invoking the db2iupgrade command.

This message is returned when mutually exclusive parameters are specified with either the db2iupdt command or the db2iupgrade command.

Explanation

You can update the version of a database manager instance, configure the topology of a DB2 pureScale instance, or convert an instance to a DB2 pureScale instance by invoking the db2iupdt command.

You can control the actions of the db2iupdt utility by specifying various parameters with the db2iupdt command.

Some collections of parameters must be specified altogether or not at all. This message is returned when parameters that must all be specified together are not all specified with the db2iupt command.

Explanation

You can list the installed database products by issuing the db2ls command. Some parameters, such as -f, require values to be specified with the parameter.

This message is returned when the db2ls command is called and a parameter that required a value is specified without a value.

Explanation

You can list the installed database products by issuing the db2ls command. Some parameters, such as -q and -b, must be specified together, if they are specified at all.

This message is returned when the db2ls command is called and only one parameter is specified from a pair of parameters that must be specified together.

Explanation

After installing a new release of a database product, you can upgrade your existing database manager instances to the new release by issuing the db2iupgrade command.

This message is returned when the db2iupgrade command is issued from the path given in the runtime token path, and there is a problem with the database product that is installed on the host machine given in the runtime token host-name.

The reason code identifies the the problem more specifically:

Reason code 1

The database product is not installed on the host machine.

Reason code 2

There is a problem with the database product installation on the host machine. For example, some product files might be missing.

Reason code 3

The release of the database product that is installed on the host machine does not match the release of the database product that is installed in the path from which the db2iupgrade command was issued.

Explanation

To access a database through Open Database Connectivity (ODBC) APIs, you must register (or catalog) the database as a data source with the ODBC diver manager.

When you upgrade your database manager instance to a new release, the db2iupgrade utility ensures that any databases that were registered as ODBC data sources before the instance upgrade are still registered as ODBC data sources after the instance upgrade.

This message is returned for your information only.

Explanation

To access a database through Open Database Connectivity (ODBC) APIs, you must register (or catalog) the database as a data source with the ODBC diver manager.

When you upgrade your database manager instance to a new release, the db2iupgrade utility attempts to ensure that any databases that were registered as ODBC data sources before the instance upgrade are still registered as ODBC data sources after the instance upgrade.

This message is returned when the db2iupgrade utility encountered an error while preserving the list of databases that are registered as data sources with the ODBC driver manager.

Explanation

You can run a DB2 pureScale environment using different network protocols:

• Remote direct memory access (RDMA) protocol over an InfiniBand (IB) network
• RDMA protocol over a Converged Ethernet (RoCE) network
• Transmission Control Protocol/Internet Protocol (TCP/IP) over an Ethernet network

This message is returned when a DB2 pureScale instance is created or updated, and the instance will use the TCP/IP protocol because the database manager instance configuration utilities did not detect a network configured to use RDMA.

Explanation

The database product installer uses temporary directories to store files necessary for creating and managing instances and database objects. For database products to be installed or database manager instances to be updated, the temporary directories must have enough memory available to meet memory requirements.

Explanation

When you apply a fix pack to your database product by issuing the installFixPack command, the installFixPack utility will also update IBM General Parallel File System (GPFS) by default.

This message is returned when an attempt is made to apply a fix pack in a DB2 pureScale environment where GPFS is installed, and the installFixPack utility encounters an error starting GPFS.

More detailed diagnostic information is recorded in log files named installGPFS* in the /tmp directory.

Explanation

You can upgrade a non-root database manager instance by issuing the db2nrupgrade command. When you issue the db2nrupgrade command, you must use the -b parameter to specify the directory where the configuration files from the old DB2 version are stored.

This message is returned when the db2nrupgrade command is issued without the backup directory being specified with the -b parameter.

Explanation

By default, the database product installer installs IBM General Parallel File System (GPFS) and creates a GPFS cluster when you install the DB2 pureScale Feature. Similarly, when you apply a DB2 fix pack, the installFixPack utility automatically updates GPFS software, when required, by default. However, if you manually install or update GPFS, the database product installer and the installFixPack utility might be unable to subsequently maintain GPFS automatically.

This message is returned when the installFixPack utility detects that the GPFS software that is on the system was installed or updated by some mechanism other than the database product installer or the installFixPack utility.

Explanation

You can use the SSL protocol to protect database client-server communications over the network by installing the IBM Global Security Kit (GSKit). In some configurations, the database product installer installs and updates the GSKit package automatically.

This message is printed in those configurations where the GSKit package is not installed, and consequently was not updated as part of a DB2 fix pack operation.

Explanation

You can update installed database products to apply a fix pack by using the installFixPack command.

In a DB2 pureScale environment, the installFixPack utility performs the fix pack installation by installing the fix pack, including performing cluster maintenance operations, on each host machine in the DB2 cluster in sequence.

This message is returned when the installFixPack utility encounters an error while performing cluster maintenance operations for a host machine in the cluster.

Explanation

To configure network settings in a DB2 pureScale environment, you must install required uDAPL software, associate interconnect netnames with pseudo IP addresses, and add required entries to the Direct Access Transport (DAT) configuration file.

This message is returned when an attempt is made to create a DB2 pureScale instance, but a host machines in the DB2 network has not been properly configured for uDAPL.

Explanation

You can upgrade a database manager instance from one product release to another by invoking the db2iupgrade command.

To minimize the amount of time for which an instance must be stopped for an upgrade operation, you can perform the upgrade in two phases:

• Phase 1: Prepare the instance for upgrade while the instance is active by issuing the db2iupgrade command with the -prepare parameter.
• Phase 2: Commit the upgrade operation by stopping the instance and then issuing the db2iupgrade command with the -commit parameter.

You must perform both phases by issuing the db2upgrade command from the same install location. This message is returned when phase 1 is initiated from one install location, directory A, and then phase 2 is initiated from a different install location, directory B.

Explanation

You can upgrade a database manager instance from one product release to another by invoking the db2iupgrade command.

To minimize the amount of time for which an instance must be stopped for an upgrade operation, you can perform the upgrade in two phases:

• Phase 1: Prepare the instance for upgrade while the instance is active by issuing the db2iupgrade command with the -prepare parameter.
• Phase 2: Commit the upgrade operation by stopping the instance and then issuing the db2iupgrade command with the -commit parameter.

This message is returned when the db2iupgrade command is issued with the -commit parameter, but the instance has not yet been prepared for the upgrade operation.

Explanation

You can upgrade a database manager instance from one product release to another by invoking the db2iupgrade command.

To minimize the amount of time for which an instance must be stopped for an upgrade operation, you can perform the upgrade in two phases:

• Phase 1: Prepare the instance for upgrade while the instance is active by issuing the db2iupgrade command with the -prepare parameter.
• Phase 2: Commit the upgrade operation by stopping the instance and then issuing the db2iupgrade command with the -commit parameter.

Once you prepare the instance for upgrade by issuing the db2iupgrade command with the -prepare parameter, you must either cancel the upgrade operation or complete it by issuing the db2upgrade command with the -commit parameter. This message is returned when the db2iupgrade command is issued with the -prepare parameter, and then the db2iupgrade command is issued without the -commit parameter.

Explanation

You can upgrade a database manager instance from one product release to another by invoking the db2iupgrade command.

To minimize the amount of time for which an instance must be stopped for an upgrade operation, you can perform the upgrade in two phases:

• Phase 1: Prepare the instance for upgrade while the instance is active by issuing the db2iupgrade command with the -prepare parameter.
• Phase 2: Commit the upgrade operation by stopping the instance and then issuing the db2iupgrade command with the -commit parameter.

This message is returned when an error occurs while the instance is being prepared for upgrade.

Explanation

You can upgrade a database manager instance from one product release to another by invoking the db2iupgrade command.

To minimize the amount of time for which an instance must be stopped for an upgrade operation, you can perform the upgrade in two phases:

• Phase 1: Prepare the instance for upgrade while the instance is active by issuing the db2iupgrade command with the -prepare parameter.
• Phase 2: Commit the upgrade operation by stopping the instance and then issuing the db2iupgrade command with the -commit parameter.

This message is returned when an error occurs while the instance upgrade operation is being committed.

Explanation

In a DB2 pureScale environment, the Fast Communications Manager (FCM) handles communications between DB2 members and cluster caching facilities (CFs).

When you install the DB2 pureScale Feature, a range of ports must be reserved for the FCM to use. The installer attempts to configure a range of ports in the /etc/services file.

This message is returned when the installer detects entries in the /etc/services file for a service with the same name as the new FCM service name.

Explanation

In a DB2 pureScale environment, the Fast Communications Manager (FCM) handles communications between DB2 members and cluster caching facilities (CFs).

When you install the DB2 pureScale Feature, a range of ports must be reserved for the FCM to use. The installer attempts to configure a range of ports in the /etc/services file.

This message is returned when the installer detects entries in the /etc/services file for a service with the same name as the new FCM service name.

Explanation

This program completed successfully but with one or more warnings.

Explanation

Execution completed with one or more warnings. Refer to installation log file for more information.