Explanation

You can create a database manager instance, including a DB2 pureScale instance by using the db2icrt command. You can also create an initial DB2 member and cluster caching facility (CF) as part of the creation of the DB2 pureScale instance by using the db2icrt command.

This message is returned when the db2icrt command is invoked with incorrect or missing parameters.

Explanation

An invalid argument was entered for the db2uit command. Valid arguments for this command are:

-d

turn debug mode on

-q

query a field given the search parameters. Without -q, this becomes an update (if -i ID is already present) or insert. Valid fields: i, r, a, p

-i

ID of the entry

-r

run levels

-a

action to perform

-p

process to launch

-Q

Quiet: no output

-D

Delete record

FileName

file to modify

RETURN CODES:

-q

If no field matches, non-zero, zero otherwise

update/insert

If file could not be updated, non-zero, zero otherwise

Explanation

Explanation

The db2ln command was run from another DB2 copy which creates symlinks in /usr/lib. These symlinks interfere with multiple DB2 copies running on the same system, whether those copies are the same version at different fixpacks, or different versions.

Explanation

The syntax for the db2idrop command is:

db2idrop [-h|-?]
         [-d]
         [-g]
         [-f]
         InstName

Valid arguments for this command are:

-h|-?

Display the usage information.

-d

Turn debug mode on.

-g

This parameter is required when db2idrop is used with a DB2 pureScale instance. Specifies that you want to drop the DB2 pureScale instance on all hosts. This parameter requires all DB2 members and all cluster caching facilities (CFs) are stopped on all the hosts in the DB2 pureScale instance.

-f

This parameter is deprecated. This parameter flags applications. If this flag is specified all applications using the instance will be forced to terminate. This parameter is not supported on a DB2 pureScale environment.

InstName

Specifies the name of the instance.

Explanation

Explanation

Installing DB2 64-bit on AIX requires different CDs for AIX version 4 and AIX version 5.

db2setup has detected that your system is running AIX version 5, but you are installing from the DB2 for AIX version 4 CD.

Explanation

Installing DB2 64-bit on AIX requires different CDs for AIX version 4 and AIX version 5.

db2setup has detected that your system is running AIX version 4, but you are installing from the DB2 for AIX version 5 CD.

Explanation

The host is still active in the GPFS cluster. Prior to updating the GPFS level, the host must be offline.

Explanation

You can use the db2iupdt command to update a database manager instance to a higher level within a release, convert a database manager instance to a DB2 pureScale instance, or manage DB2 members or cluster caching facilities (CFs) of a DB2 pureScale instance.

This message is returned when the db2iupdt command is invoked with incorrect or missing parameters.

Explanation

Explanation

Upgrading from 64-bit to 32-bit is not supported in this version.

Explanation

You can upgrade a database manager instance to a new release by using the db2iupgrade command.

This message is returned when the db2iupgrade command is called and invalid parameters or arguments are specified.

Explanation

An attempt to update the DB2 Administration Server DAS has failed because:

• This version of the dasupdt command cannot be used to update the DB2 Administration Server.
• To use this level of code for the DB2 Administration Server, an upgrade is required (instead of an update).

Explanation

The syntax for the db2setup command is:

db2setup  [-h|-?]
          [-t <TrcFile>]
          [-r <RspFile>]
          [-c]
          [-l <LogFile>]
          [-i <Lang>]
          [-f <nobackup>]   

Valid arguments for this command are:

-h|-?

Displays help information.

-t

Turns on the debug mode. The debug information is written to the file name specified.

-r

Performs a response file install using the file name specified. This parameter is mandatory when -c is specified.

-c

Validates the contents of the response file specified in the -r parameter. When specified, you must also specify the -r parameter.

-l

Writes the log to the file name specified. For root installations, the default log file is /tmp/db2setup.log. For non-root installations, the default log file is /tmp/db2setup_<userID>.log, where <userID> represents the user ID that owns the non-root installation. If the IBM Tivoli System Automation for Multiplatforms (SA MP) is being installed with db2setup, the install log file for the SA MP will be located in the same directory as database log files.

-i

Displays the db2setup utility in the language specified.

-f

This applies to the non-root upgrade only. Force db2setup to not backup installation files when the components are updated. If you choose not to backup the files, the space requirement of the installation directory is reduced. However, choosing not to backup the files also means that if any errors occur, the database product installer will not be able to perform a rollback operation. In this case, you will need to manually clean up the files and reinstall the product.

Explanation

Explanation

Explanation

Explanation

Explanation

An invalid argument was entered for the dascrt command. Valid arguments for this command are:

-d

enters debug mode, for use with DB2 Service

-u ASUser

is the user the DAS will run under

Explanation

Explanation

An invalid argument was entered for the command. Valid arguments for this command are:

-d

enters debug mode, for use with DB2 Service

Explanation

An invalid argument was entered for the dasupdt command. Valid arguments for this command are:

-d

enters debug mode, for use with DB2 Service

-D

Moves the DAS from a higher code level on one path to a lower code level installed on another path.

-h|-?

Displays usage information.

Explanation

An invalid argument was entered for the db2nqadm command. Valid arguments for this command are:

start start all NetQ services and daemon
stop  stop all NetQ services and daemon

You must specify one of the arguments.

Explanation

DB2 requires certain kernel parameters to be updated.

Explanation

There are multiple methods for installing database software, including the DB2 Setup wizard and the db2_install command.

This message is returned when a component or Feature is selected to be installed, but the selected component or Feature cannot be installed until after the database server is installed.

Explanation

The database product you selected requires an AIX version that is 4.3 or greater.

Explanation

There are multiple methods for installing database software, including the DB2 Setup wizard and the db2_install command.

This message is returned when a component or Feature is selected to be installed, but the selected component or Feature cannot be installed until after the database server is installed.

Explanation

One of the following packages has been selected for installation: "<pkg-name>" Either the installed "<pkg-name>" file set level is below "<name>" or it cannot be detected.

Explanation

An attempt to mount the specified file system has failed.

Explanation

An attempt to unmount the specified file system has failed.

Explanation

The file system specified is not defined on this workstation.

Explanation

One of the following packages has been selected for installation: "<name>" However, the installed "<name>" file set level is below "<name>"

Explanation

The File-systems "/", "/var", "/usr", and "/tmp" cannot be converted to a dlfs File-system. This has been done to avoid booting problems that may arise by making these dlfs File-systems.

Explanation

On Aix, a File-system can be changed to dlfs only if its vfs is fsm or jfs. Dlfs is not supported for any other vfs.

Explanation

The national language package can only be used to add national language support to installed database products that include:

Explanation

On UNIX operating systems, you can install all features of a database product to a specified path by calling the db2_install command.

This message is returned when the db2_install command is called with invalid parameters or syntax.

Explanation

-b

Specifies the path where the database product will be installed. Mandatory when -n is specified. The length of the path is limited to 128 characters and is a full path name.

-p

Specifies the database product to be installed. Mandatory when -n is specified.

-c

Specifies the location of the related national language pack (NLPACK). This parameter is mandatory when -n is specified.

The NLPACK locations needs to be provided explicitly if the all of the following conditions are all met:

• The -n option is specified
• The current installation requires needs to install National Language (non-English) language supports
• The NLPACK is neither on the installation media nor in the same subdirectory as the database product being installed

-l

Specifies the log file. The default log file is /tmp/doce_install.log$$, where $$ is the process id.

-t

Turns on the debug mode. The debug information is written to the file name specified.

-n

Specifies non-interactive mode. When specified, you must also specify -b, -p, and -c.

-L

Specifies national language support. To install multiple languages at the same time, this parameter can be specified multiple times.

For example, to install both English and German, specify -L EN -L DE.

-h|-?

Displays help information.

Explanation

The syntax for the db2_deinstall command is:

db2_deinstall -F <featureName> | -a | -r <RspFile>
              [-l <logFile>]
              [-b <installPath>]
              [-t <trcFile>]
              [-s GPFS]
              [-s TSAMP]
              [-f sqllib]
              [-h|-?]

For details about the parameters of the db2_install command, refer to the documentation for Linux, UNIX, and Windows.

Explanation

-a

Removes all installed database products in the current location.

-b <installPath>

This option is valid if the command is run from the installation media. It specifies the absolute path where the database product was installed and will be uninstalled. The command will prompt for the path if the option is not specified.

-l <logFile>

Specifies the log file. The default log file is /tmp/doce_deinstall.log$$, where $$ is the process id.

-t <trcFile>

Turns on the debug mode. The debug information is written to the file name specified.

-r <response_file>

Removes the Information Center using a response file. For example, doce_deinstall -r db2un.rsp. Cannot be combined with the -a parameter.

-h|-?

Displays help information.

Explanation

-q

Specifies that this is a query of the local components. By default, only the visible components (features) are displayed unless -a is also specified. Mandatory when -p is specified.

-b <installpath>

When using the global db2ls command, you need to specify which directory you are querying. The global db2ls command will simply call the db2ls from that install path and pass in the rest of the parameters.

-c

Prints the output as a colon-separated list of entries rather than column-based. Allows you to use shell scripts to accurately work with this information.

For example: #FEATURE:NAME:VRMF:FIXPACK: SPECIALINSTALL:PREREQS.

-f <feature response file ID>

Queries to check if the specific feature is installed. If the feature is installed, the return code is zero. If the feature is not installed, the return code is non-zero.

-l <logfile>

Specifies the log file name.

-p

Lists the database products installed. Cannot be combined with -f or -a. Must include -q.

-a

Lists all hidden components and visible features. The default is to only list visible features.

Explanation

Your current operating system is not supported or this version of the operating system is not supported.

Explanation

This program can only be run under a non-root user ID.

Explanation

Special privileges are required to execute some DB2 database commands.

This message is returned when a non-root user ID issues a database command that requires root user authority.

Explanation

Creating the instance's home directory on this type of file system is not supported. Instance's home directory must exist either on a local file system or on a NFS mounted file system.

Explanation

You can update the installed database products in a given location, on all UNIX and Linux platforms by using the installFixPack command.

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

Explanation

The message file required by the instance commands is missing from the system; it may have been deleted or the database products may not be installed properly.

Explanation

-d

Turns debug mode on.

-f

Specifies a specific file name to update the runtime path. The specified file name should have the path name relative to the base of the current database product install location. Root authority is required, and this command must be run directly from DB2DIR/install directory.

Explanation

The required locale directory, /usr/lib/locale/LANG/LC_MESSAGES, does not exist, where LANG is the name of your current locale.

Explanation

The gunzip utility must be available on your system to install or update database products.

Explanation

An incorrect name has been entered. The package either does not exist or the name has been entered incorrectly.

Explanation

An error occurred when verifying software pre-requisites. The indicated file set or package must be installed before using this command.

Explanation

The indicated file set or package must be installed before using this command.

Explanation

The indicated PTF or patch must be installed before using this command. This PTF or patch is required to complete this command successfully.

Explanation

The user that is being used to create the DB2 Administration Server is being used by the database manager instance. You should not create the DB2 Administration Server with this user.

Explanation

An error has occurred during the execution and that has caused this program to terminate prematurely.

Explanation

This program has been terminated by the user.

Explanation

No compressed-tar HTML files can be found in the DB2DIR/doc/"<locale-name>"/html directory, where

DB2DIR =
    /usr/opt/db2_08_xx, where xx is 01 or FPn,
    where n is the FixPak number
 or /opt/IBM/db2/V8.x, where x is 1 or FPn,
    where n is the FixPak number

Explanation

After uncompress and un-tar, all the HTML files cannot be saved in the indicated directory because the file system is full.

Explanation

An unexpected error occurred during the execution of this program.

Explanation

Because the db2licm command failed to add the license, the database product will run with a Try-and-Buy license until a product license is installed.

Explanation

An attempt was made to update or upgrade an administration server. An administration server does not exist.

Explanation

The administration server cannot me migrated. The administration server is running at a level which is not a supported DB2 migration level.

Explanation

The DB2 pureScale Feature requires the use of Remote Direct Memory Access (RDMA) capable network adapters to provide a low latency cluster interconnect. A supported RDMA adapter was not found.

Explanation

The user that is being used to create the database manager instance has been used by the DB2 Administration Server. You should not create the instance with this user.

Explanation

The database product installer uses the installSAM utility to update the SA MP. The installSAM utility returned errors. The installSAM log file contains more complete information.

TSAMP_RC is the return code from the installSAM utility.

Note that you must have root authority to use the database product installer to update SA MP.

SA MP was not updated.

Explanation

All processed and failed operations have been saved into this log file.

Explanation

There is not enough free space available in the file system or directory.

Explanation

A file or directory that is required to process this command is missing.

Explanation

A file or directory that the command needs to create already exists.

Explanation

An error occurred when removing the given file or directory. This may be due to an inappropriate ownership on this given file or directory.

Explanation

An error occurred when creating the given file or directory.

Explanation

An error occurred when attempting to relocate the given file or directory. The command could not be processed successfully.

Explanation

An error occurred when attempting to duplicate the given file or directory. The command could not be processed successfully.

Explanation

The given link cannot be created. It could be that the write permission on its parent directory has been turned off, or that a file or directory with the same name already exists.

Explanation

This message can be returned for multiple reasons, including the following reasons:

• The given name is not a directory, or the directory does not have read and execute permission.
• The given directory can be created but cannot be accessed.
• The permissions on any of the parent directories of the given directory do not meet requirements for DB2 database instance and database directories.

If the home directory of the database manager instance is located on a mounted drive, this message can be returned if the DB2 database install utility fails to validate the permissions of the mount point.

Explanation

Explanation

An error occurred while updating the given file.

Explanation

An error occurred when changing permissions on the given file or directory. This may be due to an inappropriate ownership on this file or directory.

Explanation

An error occurred when changing ownership on the given file or directory. This may be due to an inappropriate ownership on this given file or directory.

Explanation

An error occurred when changing group ownership on the given file or directory. This may be due to an inappropriate ownership on this file or directory.

Explanation

The tool encountered an access error during an I/O operation with the directory server.

Explanation

A file or directory that the command needs to create already exists.

Explanation

This message can be returned when a file or directory that the command requires does not exist.

This message can also be returned when the DB2WORKDIR environment variable is set to an invalid value:

• A directory that does not exist
• The /tmp directory

Explanation

Valid arguments for this command are:

-h|-?

Displays help information.

-c

Verifies that the DB2 High Availability (HA) scripts exist in /usr/sbin/rsct/sapolicies/db2, and that they are at the proper level.

-f

Forces a reinstall of the DB2 HA scripts in /usr/sbin/rcst/sapolicies/db2. Without this argument, if the version of the DB2 HA scripts that are already installed is the same as or higher than the version of the scripts being installed, then the installed scripts are not overwritten.

-r

Removes the directory /usr/sbin/rsct/sapolicies/db2. This dicrectory is where the DB2 HA scripts for the IBM Tivoli System Automation for Multiplatforms (SA MP) are located. These scripts and this directory will only be removed if the SA MP is not installed.

This utility installs or updates the DB2 HA scripts in /usr/sbin/rsct/sapolicies/db2. You need these DB2 HA scripts to use the IBM Tivoli System Automation for Multiplatforms (SA MP) with the DB2 HA feature.

By default, this utility installs the DB2 HA scripts in /usr/sbin/rsct/sapolicies/db2 if they aren't already installed there, or if the version of the scripts already installed is older than the version of the scripts being installed. This utility installs or updates the DB2 HA scripts if and only if the SA MP is already installed.

This command must be run with root authority.

This command can be found on the database product install media in the directory:

• db2/<plat>/tsamp

where <plat> is:

• aix for DB2 for AIX
• linux for DB2 for Linux on 32-bit AMD and Intel systems (x86)
• linuxamd64 for DB2 for Linux on AMD64 and Intel EM64T systems (x86-64)
• linuxppc for DB2 for Linux on POWER (iSeries(TM) and pSeries) systems
• linux390 for DB2 for Linux on System z9 and zSeries

The command is also available at <DB2DIR>/install/tsamp directory where <DB2DIR> is the installation path of DB2 database.

Explanation

You need DB2 HA scripts to use the IBM Tivoli System Automation for Multiplatforms with the DB2 HA feature.

These DB2 HA scripts are located at /usr/sbin/rsct/sapolicies/db2. The database product installer detects whether these DB2 HA scripts need to be installed or updated.

The database product installer successfully installed the DB2 HA scripts.

Explanation

The command failed because another instance management command (eg. db2icrt, db2idrop, or db2iupdt) is running. The instance management commands acquire an exclusive lock to avoid conflicting simultaneous commands against the same instance.

Explanation

Explanation

Explanation

The system detects that the Administration Server has already been created on your system. You can only create one Administration Server on each system.

Explanation

An attempt to drop the Administration Server failed. The system detects that the Administration Server does not exist.

Explanation

The system detects that the DB2 Data Links Manager Administrator has already been created on your system. You can only create one DB2 Data Links Manager Administrator on each system.

Explanation

An attempt to drop the DB2 Data Links Manager Administrator failed. The system detects that the DB2 Data Links Manager Administrator does not exist or has been created under a different user ID.

Explanation

While creating a dlfm instance,or migrating a dlfm instance from DB2 V7 or earlier, the -g DLFMGid must be specified.

DLFMGid can be a numeric group id or a group name. The named group must be in the secondary group list of the named DLFM user.

If migrating a V8 or later dlfm instance, if -g DLFMGid is specified which is not the same as the DLFMGid already set up for the instance, the specified parameter will be ignored and the old Gid will be used.

Explanation

Some of the kernel parameters are not configured properly.

Explanation

You need DB2 HA scripts to use SA MP with the DB2 HA feature.

These DB2 HA scripts are located at /usr/sbin/rsct/sapolicies/db2. The database product installer detects whether these DB2 HA scripts need to be installed or updated.

The database product installer successfully updated the DB2 HA scripts.

Explanation

The FencedID parameter must be specified with this command. The FencedID parameter is set to the name of the user under which fenced User Defined Functions (UDFs) and fenced Stored Procedures will be run.

Explanation

Explanation

The FencedID parameter entered on the command line is different from the one used before for this userid. New value for this parameter is ignored.

Explanation

You need DB2 HA scripts to use SA MP with the DB2 HA feature.

The db2cptsa utility expects to find these scripts, as well as a file named "spec", in /usr/sbin/rsct/sapolicies/db2.

The database product installer could not find the DB2 HA scripts, or the spec file.

Explanation

Explanation

The high availability feature being installed requires scripts with a version the same as or higher than the version of the scripts on the install media.

This message is returned when the version of the scripts currently installed is lower than the version of the scripts on the install media.

Explanation

The high availability feature being installed from the install media requires scripts with a version the same as or higher than the version of the scripts on the install media.

This message is returned when the version of the scripts currently installed is higher than the version of the scripts on the install media.

Explanation

The user ID for the instance or DAS name is using the Korn Shell but does not have a .profile file under its home directory. The database product installation script has created the .profile file for the user ID and has populated the file with entries necessary for setting the default instance or DAS environment. This is done so that when the user logs in, the user will automatically acquire the instance or DAS environment.

Explanation

The high availability feature being installed from the install media requires scripts with a version the same as or higher than the version of the scripts on the install media.

This message is returned when the version of the scripts currently installed is the same as the version of the scripts on the install media.

Explanation

An attempt was made to drop an instance which may still be active.

Explanation

An attempt was made to drop the Administration Server using "db2idrop". This operation is not allowed since it will cause the registry to be in an inconsistent state.

Explanation

An attempt was made to either update or upgrade an instance. This instance cannot be updated or upgraded because:

• One of the following commands cannot be used to either update or upgrade this instance: db2iupdt, db2iupgrade, or db2nrupdt.
• The instance is still active.

Explanation

An attempt was made to update the Administration Server using "db2iupdt". This operation is not allowed since it will cause the registry to be in an inconsistent state.

Explanation

This message is returned when upgrading an instance fails for one of several reasons:

• The instance is still active and the -prepare parameter was not specified.
• Upgrading this instance is not supported.
• This version of the db2iupgrade command cannot be used to upgrade this instance.
• The version of the currently installed product is the same as the version to which the upgrade was being attempted.

Explanation

An attempt was made to drop the DB2 Data Links Manager Administrator using "db2idrop". This operation is not allowed since it will cause the registry to be in an inconsistent state.

Explanation

The db2iupgrade command calls the db2ckupgrade command. The instance upgrade fails if the db2ckupgrade command returns any errors.

The db2ckupgrade command has identified one or more views that are dependent on database entities that have changed. This might cause the UPGRADE DATABASE command to fail.

The identified views are listed in the db2ckupgrade log file.

Explanation

You need DB2 HA scripts to use the SA MP with the DB2 HA feature.

You cannot uninstall these scripts while the SA MP is still installed. This is to prevent unexpected behavior resulting from using the SA MP with the DB2 HA feature without the scripts being installed.

The DB2 HA scripts were not uninstalled.

Explanation

An attempt was made to drop the Administration Server using "dlfmdrop". This operation is not allowed since it will cause the registry to be in an inconsistent state.

Explanation

An attempt was made to update the Administration Server using "dlfmupdt". This operation is not allowed since it will cause the registry to be in an inconsistent state.

Explanation

There are system prerequisites for installing or updating SA MP. These prerequisites have not been met.

The mentioned log file has the details for the unsatisfied prerequisites.

To find out more about the system prerequisites for the SA MP Base Component, see the SA MP Base Component documentation's Installation and Configuration Guide.

SA MP cannot be installed or updated.

Explanation

An attempt to access the given user ID failed. One of the following situations has occurred:

• This user ID does not exist on the system.
• The home directory of this user does not exist or is not set up properly.
• One of the user attributes needed by the database manager is unset.
• The UID of this user is 0

Explanation

The regular license for SA MP is named sam31.lic, and the try-and-buy license is named sam31tb.lic. One, but not both, of these files must exist in the specified directory on the database product install media for the database product installer to install or update SA MP.

SA MP cannot be installed without the proper license.

Explanation

The current host is part of an IBM General Parallel File System (GPFS) cluster. You cannot remove the GPFS cluster from the host on which the command was run. Also, the uninstallGPFS command is not a supported command.

Explanation

You need DB2 HA scripts to use the SA MP with the DB2 HA feature. You do not need these scripts if you are not using the SA MP.

The DB2 HA scripts were not installed.

Explanation

The primary group name of the instance user ID:

1. Cannot be one of "guests", "admins", "users" or "local".
2. Cannot start with "sql" or "ibm".
3. Cannot start with a numeral number.
4. Can contain only lowercase letters (a-z), numbers (0-9), and the underscore character ( _ ).

Explanation

The instance you are upgrading is a Server instance. A database server product has not been detected. The instance will be upgraded only if the -F parameter is specified.

Explanation

The instance you are upgrading has Data-Links functionality. Data-Links File Manager is not supported in the version of the database product you are upgrading to.

Explanation

Relational Connect was not detected in the version you are migrating to, but a setting file was detected for the instance you are migrating. This configuration will be migrated but Relational Connect has to be installed to make use of these configuration parameters.

Explanation

Relational Connect was not detected in the version you are migrating to but environment variables have been found that indicate that you have non-DB2 data sources. This instance cannot be migrated if Relational Connect is not installed.

Explanation

The db2isetup script can perform configuration and database manager instance setup tasks using a response file, or it can launch the instance Setup wizard to perform these tasks using a graphical user interface. Currently, only the response file support mode is installed. To use the graphical mode, the instance Setup wizard feature must be installed.

Explanation

The user ID specified is not a database manager instance.

Explanation

The user ID specified is not an Administration Server.

Explanation

The current DB2 copy was not installed by the user who is running the program.

Explanation

You cannot create or upgrade to a 64-bit Express server instance. If you want to run a 64-bit server instance, you must have the database server installed.

Explanation

You cannot create or upgrade to a 64-bit Express server instance. If you want to run a 64-bit server instance, you must have the database server installed.

Explanation

tool-name can not be run by users with root authority.

Explanation

AIO needs to be enabled on the system to run DB2.

Explanation

The command failed because you tried one of the following actions, which are not supported:

1. Update the non-root instance to become a root instance
2. Upgrade the non-root instance to become a root instance
3. Drop the non-root instance by running the db2idrop command from a root installation location

Explanation

A complete system check cannot be performed because root authority is required.

Explanation

The parameter-or-value passed to the installer command cmd is not valid.

Explanation

Explanation

You can configure non-root installations by using the db2nrcfg utility.

Syntax:

  
  db2nrcfg [-h|-?]
           [-d]
           [-a AuthType]
           [-p PortName]
           [-s InstType]

Explanation

The syntax for the db2nrupdt command is:

db2nrupdt [-a AuthType]
          [-d]
          [-k ] 
          [-j "TEXT_SEARCH" |
           -j "TEXT_SEARCH,portnumber"]
          [-h|-?]

For details about the parameters of the db2nrupdt command, refer to the documentation for Linux, UNIX, and Windows.

This command must be run from the $HOME/sqllib/instance directory where the $HOME is the home directory of the non-root database manager instance ID. This command can be run only as the non-root instance who owns the non-root database product installation at $HOME/sqllib.

Explanation

To enable the remote connection, please provide a value for entry-name in the configuration file.

Explanation

Your db2nodes.cfg file is referring to nodes that cannot be accessed from this node. Furthermore, the remote node might also not be sharing the sqllib with this node. With DPF, all nodes must have the same sqllib mounted.

Explanation

The file name of the specified file set has been modified or corrupted.

Explanation

The syntax for the db2ckgpfs command is:

db2ckgpfs  [-d]
           [-l <logFile>]
           [-v install | media]
           [-s install | media]
           [-c]
           [-n <cluster-name>]
           [-h|-?]

Explanation

The installed level of bos.rte.libc is lower than 5.1.0.28, the minimum required level for supporting 64-bit instances.

Explanation

The DB2 HTML Documentation is not installed or it cannot be found.

To update the DB2 HTML Documentation to this FixPak, the DB2 HTML Documentation must be installed.

Explanation

The syntax for the db2cktsa command is:

db2cktsa  [-d]
          [-l <logFile>]
          [-v install | media]
          [-i install | media]
          [-c]
          [-n <cluster-name>]
          [-h|-?]

Explanation

64-bit instances are not supported or implicit on this platform.

Explanation

The installed level of one or both of bos.rte.libc and bos.adt.prof is lower than 4.3.3.50, the minimum required level for supporting 64-bit instances.

Explanation

You can only update a 32-bit Workgroup server instance to a 64-bit server instance if you have a database server installed.

Explanation

The IBM General Parallel File System (GPFS) version level installed on your system is lower than the GPFS version level on the installation media. GPFS cannot be automatically upgraded. Also, the installGPFS command is not a supported command.

Explanation

Please confirm that you have reviewed the license terms and conditions located in the db2/license directory for the installed products. If you accept these license terms and conditions, restart the FixPak installation and specify the '-y' option.

By specifying the '-y' option, you indicate your agreement to the license terms and conditions provided with this product.

Explanation

An attempt has been made to update an instance to a code level that is lower than the one being used by the instance currently.

Explanation

An attempt has been made to update a DAS to a code level that is lower than the one being used by the DAS currently.

Explanation

The PortName parameter is used for inbound TCP/IP connections and is not applicable to client instances.

Explanation

The current platform does not support 32-bit server instances.

Explanation

64-bit instances are not supported on this platform.

Explanation

The instance you are trying to upgrade has Warehouse Manager or Warehouse Manager Connectors functionality. Warehouse Manager and Warehouse Manager Connectors are not supported in the product release to which you are trying to upgrade. A successful upgrade means that the upgraded instance will not have these capabilities. If this is the expected outcome, you can re-issue the db2iupgrade command.

Explanation

The instance you are upgrading has Spatial Extender functionality. Spatial Extender was not detected in the installed database product.

Explanation

The instance you are migrating has Life Sciences Data Connect functionality. Life Sciences Data Connect was not detected in the installed database product.

Explanation

Explanation

An attempt to create the DB2 Warehouse Control Database has failed.

Explanation

Explanation

The instance can not be updated because it is still active.

Explanation

The database product installer cannot continue. Either the system command was run on an unsupported operating system, or, there is a problem with the specified system command.

Explanation

The database product installer cannot continue. Either the system command was run on an unsupported processor type, or, there is a problem with the specified system command.

Explanation

The database product installer could not determine the Linux distribution on the specified host. This can happen if there is a problem with the Linux release files.

Explanation

The command cannot proceed because the specified directory does not point to the required version of the database products.

Explanation

All hosts in the same cluster must be running on the same type of operating system.

Explanation

The instance cannot be upgraded because:

1. Upgrading from this version of the instance is not supported.
2. The instance is already using the current version of the product and upgrade is not required.

Explanation

You need DB2 HA scripts to use SA MP with the DB2 HA feature.

These scripts have been removed.

Explanation

The sample configuration file has examples of valid values for this keyword.

Explanation

The following list provides the reasons why a database cannot be upgraded and the corrective action to take:

• Database is in Backup pending state. Perform backup of the database.
• Database is in Roll-forward pending state. Perform a roll-forward database to end of logs and stop.
• Database is in Restore pending state. Perform restore of the database.
• Database is inconsistent. Restart database to return it to a consistent state.
• Database has one or more table space not in normal state. Perform a roll-forward database.
• Database contains database objects that have a schema name of SYSCAT, SYSFUN, SYSIBM, SYSPUBLIC, or SYSSTAT. Drop the object and re-create the object with a correct schema name (qualifier). If the object is a table you should first export its data, drop the table, re-create the table with a correct schema name, and then import or load the data to the new table.
• Database contains database objects that have a dependency on the SYSFUN.DIFFERENCES function. Possible violated objects and the associated action to correct the violation are:
  • constraint - alter table to drop the constraint
  • function - drop the function
  • trigger - drop the trigger
  • view - drop the view
• Database contains user-defined data types that are reserved in the new version. Rename the data types.
• Database contains orphan rows in system catalog tables. Contact IBM technical service representative.
• Cataloged database does not exist. Create cataloged database.
• Database does not allow successful connection as an HADR primary database. Stop HADR on primary database.
• A database has HADR standby role. Stop HADR on the standby database and drop the standby database. Upgrade the HADR primary database. Reinitialize the standby database from the copy of upgraded primary database via restore or db2inidb.

Explanation

Can not reserve the service in the services file. Possible reasons are:

• The service name and port number are used in services file.
• The service name or port number are not valid values.

Explanation

keyword is needed in the configuration file to enable the root feature feature-name.

Explanation

A system error such as running out of disk space or memory has been encountered during the directory upgrade. Instance upgrade failed.

Explanation

The upgrade process of the local database directory is not complete because of an unexpected error occurred. Without the local database directory, databases that are cataloged in the local database directory will no longer be accessible.

Explanation

db2_deinstall uses the uninstallSAM utility to uninstall the SA MP. db2_deinstall expects to find the uninstallSAM utility in the specified directory, but did not find it there in this case. This might be because the current version of the SA MP is earlier than version 2.2. The option to uninstall the SA MP with the db2_deinstall command is only supported for SA MP Version 2.2 or higher.

The SA MP was not uninstalled.

Explanation

All valid identifiers from the image have been removed. The installer cannot determine which valid product(s) are available on the image and cannot display the installation choices.

Explanation

SA MP requires a valid license certificate to work with the DB2 High Availability (HA) feature. This license certificate was successfully installed or updated.

Explanation

SA MP requires a valid license certificate to work with the DB2 High Availability (HA) feature. This license certificate was not successfully installed or updated.

If you used the database product installer to install or update this license certificate, you can find more detailed information about why the install or update failed in the database product install log file.

Explanation

The process of upgrading a node directory did not complete because an unexpected error occurred.

Explanation

Either the node directory files are not the same or the node directory file is corrupted.

Explanation

Either the primary and backup system database directory files are not the same or system database directory is corrupted.

Explanation

Either the primary and backup database directory files are not the same or the local database directory file is corrupted.

Explanation

The source host and target host must run on the same processor type.

Explanation

One or more cataloged database entries were detected with an authentication type different than the authentication type for the instance that owns these databases. If no action is taken, all cataloged local database entries will inherit the authentication type from the instance.

Explanation

The hosts must be running on the same Linux distribution. The target host must have the same Linux distribution as the source host.

Explanation

Some configuration tasks can be performed against database server instances only. Such configuration tasks include remote connection and DB2 text search.

Explanation

One of the following conditions is true:

• The selected DB2 copy for upgrade is an installation of previous releases of DB2 Run-Time, DB2 Run-Time Client Lite, DB2 Runtime Client, or Data Server Runtime Client.
• The database product being installed is IBM Data Server Runtime or IBM Data Server Driver Package.

The DB2 copy upgrade is not supported from previous releases of DB2 Run-Time, DB2 Run-Time Client Lite, DB2 Runtime Client, or Data Server Runtime Client. Also, DB2 copy upgrade is not supported to IBM Data Server Runtime or IBM Data Server Driver Package.

Explanation

DB2 copy upgrade is not supported for the selected DB2 copy due to one or both of the following reasons:

1. One or more database manager instances have an instance type that is not supported by the database product that you want to install. On Windows operating systems, upgrading to an instance type of a lower level is not supported.
2. The DB2 DAS is related to the installation location from which the DB2 copy upgrade was requested, but the database product to be installed does not support the DB2 DAS.

Explanation

The specified database manager instance cannot be upgraded to the current DB2 copy. On Windows operating systems, upgrading to an instance type of a lower level is not supported.

Explanation

Possible reasons:

1. The database manager for the instance inst-name is still active.
2. The DB2 Text Search instance service is still active.

Explanation

An instance cannot be dropped if the DB2 Text Search instance service is active.

Explanation

The specified database manager instance cannot be updated. Downgrading the instance type is not supported.

Explanation

The database product installer only supports the installation of one product at a time.

Explanation

The instance being upgraded or updated is a multi-partition instance. The current DB2 copy to which the instance is being upgraded to or updated does not support multi-partition instances.

Explanation

The database manager has to be stopped on all the instances related to the current installation before the specified components can be dropped.

Explanation

You can create a DB2 managed General Parallel File System (GPFS) for a DB2 pureScale environment using the db2cluster_prepare utility.

This message is returned when the db2cluster_prepare command is called with an invalid parameter.

A GPFS file system was not created.

Explanation

The database manager could not be started when attempting to check if cataloged local databases can be upgraded.

Explanation

The command to start the DB2 Information Center is already processed.

The command cannot be processed.

Explanation

The specified installation path of DB2 contains one or more space characters, which is not supported for database product installation on the Unix and Linux platforms.

Explanation

Starting from DB2 9, the db2_deinstall command can only be run from a database product installation path. It can be found under DB2DIR/install, where DB2DIR represents the directory where the database product is installed.

Explanation

To uninstall a database product, you must use the db2_deinstall command that is at the same version level.

Explanation

To uninstall the DB2 Information Center, you must use the doce_deinstall command that is at the same version level.