Explanation

There are applications that are still running that are using the specified instance. All applications using this instance must be terminated before the command can be completed successfully. You can get a list of the applications that are currently using the instance by issuing the command:

    db2 list applications

Explanation

The db2iupgrade command is unable to initialize the clustering service or is unable to find the existing DB2 resource to upgrade.

Explanation

DB2 requires a resource type to be available in the clustering service but the command to register the resource type failed.

Explanation

An error occurred while creating the cluster resource required for this instance. The existing cluster resource for this instance was removed and could not be restored.

Explanation

In order to upgrade the instance, the cluster resource must be removed and a new cluster resource must be created using the database server type. The command was not able to remove the existing cluster resource and therefore cannot upgrade this instance.

Explanation

The required configuration file to create the specified instance type can not be found.

Explanation

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

You must specify the absolute path to the shared device on which the GPFS file system will be created using the required -instance_shared_dev parameter.

This message is returned when the db2cluster_prepare command is called without the -instance_shared_dev parameter.

A GPFS file system was not created.

Explanation

The command to start the DB2 Information Center was unsuccessful.

Explanation

An attempt was made to read from the given response file failed. Ensure that the response file has read access permission and the given path to the response file is correct.

Explanation

The value specified in the response file is not valid for its corresponding keyword. Refer to the sample response file for a list of valid entries.

Explanation

The given keyword in the response file is not valid. Refer to the sample response file for a list of valid keywords.

Explanation

This message is returned when some processes and operations have failed. Detailed information about the error was written to the log file.

Explanation

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

Explanation

One of the file sets to be installed is not found on the installation media. If the file set is not located on the installation media then it cannot be installed.

Explanation

An error has been detected when processing the response file. Install cannot be continued unless the problem has been corrected.

Explanation

Explanation

An attempt to configure the instance for DB2 Text Search failed. Possible reasons are:

1

DB2 Text Search is not installed. Install DB2 Text Search from the installation media then try again.

2

The service name or port number specified is not valid. A valid service name must not exceed 14 characters in length, and a valid port number must be in the range 1024-65535.

3

The port number specified is being used by another application. Choose a port number that is available on the system.

4

The specified service name or port number conflict with existing values in the TCP/IP services file. Provide a service name and a port number that is available on the system.

5

The TCP/IP services file could not be accessed. Check that you have permission to read and write to the services file. Also, ensure that the content of the file is valid and no duplicate entries exist.

6

The default service name is reserved to a port number that is different from the one provided. Provide a service name and port number that do not conflict with existing entries in the TCP/IP services file.

7

The default service name is reserved to a port number that is being used by another application. Choose a service name and port number that is available on the system.

8

The service name provided is reserved to a port number that is being used by another application. Choose a service name and port number that is available on the system.

9

An attempt to create or copy DB2 Text Search directories or files in the instance directory failed.

10

An attempt to read or write to DB2 Text Search configuration files in the instance directory failed.

11

An attempt to create the DB2 Text Search instance service Windows service failed.

12

An unexpected internal error occurred.

Explanation

An attempt to stop the DB2 Text Search instance service failed. The Windows service could not be stopped.

Explanation

An attempt to stop the DB2 Text Search instance service failed.

Explanation

You can only update the database product installation by running the installFixPack command under the user ID that performed the database product installation.

You have to run the installFixPack command as a user with root privilege to update a DB2 root installation.

Explanation

When setting up the runtime path with db2chgpath, a path was given that does not match the current path that the database manager is running from.

Explanation

A warning has been raised when processing the response file. The database product installer will carry on without stopping.

Explanation

A notice has been issued when processing the response file. The database product installer will carry on without stopping.

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 a duplicate parameter.

A GPFS file system was not created.

Explanation

An error occurred when attempting to initialize the database manager configuration file. A database manager instance could not be created or upgraded.

Explanation

An error was detected when attempting to merge two database manager configuration files. The previous database manager configuration file could not be merged with the new database manager configuration file. This error could happen if the instance is being upgraded or updated from a higher instance type to a lower instance type.

If the instance update or upgrade was successful, a new instance is created using the default configuration settings for the instance-type-upgrade.

This error could happen if the instance is being upgraded or updated from a higher instance type to a lower instance type. The new instance uses the default configuration settings for the new instance type if update or upgrade was successful.

Explanation

The SVCENAME parameter and/or the DB2COMM registry values could not be updated during instance creation.

Explanation

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

Explanation

Explanation

Reasons for this error include:

• The given directory or file is on a local file system of the current machine, but the user id running the program does not have write permission for that directory or file.
• The given directory or file is on an NFS mounted file system mounted on the current machine, but the current user id does not have write permission for that directory or file.
• The current user id does not have write permission for the given directory or file located at the target partition. This can happen when the current machine's operating system is IBM AIX Version 6.1 or later and a Workload Partition root user id is attempting to write to a Global Partition.
• The current user id does not have write permission for the directory or file located at the target zone. This can happen when the current machine's operating system is Sun Solaris 10 or later and a local zone root user id is attempting to write to a global zone.
• The current machine is running the Sun Solaris Operating System in a local zone which does not have the write permission for the directory or file located on the global zone.

Explanation

The database product install or instance utility attempted to configure permission and ownership for DB2 ACS files that are located in the sqllib/acs directory under the DB2 instance home directory. The given log file contains information about why the database product install or instance utility failed.

DB2 ACS might not be usable because the database product install or instance utility failed to configure permission and ownership for these files.

Explanation

Explanation

The specified instance was not found in the instance list.

Explanation

The instance that is being created or upgraded is already in the instance list.

Explanation

Before you can use DB2 ACS, the services must be started. The database product install or instance utility attempted to start the services, but failed.

You can use the database manager instance, but you cannot use DB2 ACS until the services are started.

Explanation

Explanation

Before you can update or upgrade a database manager instance, DB2 ACS must be stopped. The database product install or instance utility attempted to stop the services, but failed.

You cannot update or upgrade the instance until DB2 ACS is stopped.

Explanation

Explanation

Before you can drop a database manager instance, or remove a non-root install of IBM Data Server, DB2 ACS must be stopped. The database product install or instance utility attempted to disable the services, but failed.

You cannot drop an instance, or remove a non-root install of IBM Data Server until DB2 ACS is disabled.

Explanation

Several DB2 profile registry variables can be grouped together and set as one aggregate DB2 profile registry variable. When you configure an aggregate DB2 profile registry variable, the DB2 profile registry variables that are members of that set are automatically configured to their predefined values.

DB2 profile registry variables that are members of an aggregate set, can not be nulled using the following db2set command syntax:

db2set variable-name=

The variable was not nulled.

Explanation

The command options are:

-g

Access the global profile variables.

-i

Specifies the instance profile to use instead of the current or default.

-n

Specifies the remote DB2 Administration Server node name.

-u

Specifies the user ID to use for the Administration Server attachment.

-ul

Access the user profile variables

-ur

Refreshes user profile variables

-p

Specifies the password to use for the admin server attachment.

-r

Resets the profile registry for the given instance. The default/current instance will be used if none is provided.

-im | -immediate

Specifies that the update takes effect the next time an SQL statement is compiled for registry variables that support this feature.

-info

Returns the properties of the specified variable. The properties state whether an immediate change is supported by the variable and whether the change is immediate by default

-l

Lists all instance profiles.

-lr

Lists all supported registry variables.

-v

Verbose mode.

-?

Displays the command help message.

-h

Same as -? option.

-all

Displays all occurrences of the local environment variables as defined in:

• The environment, denoted by [e]
• The user level registry, denoted by [u]
• The node level registry, denoted by [n]
• The instance level registry, denoted by [i] and
• The global level registry, denoted by [g]

-null

Sets the variables value to null at the specified registry level to prevent looking up the value in the next registry level as defined in the variable value search order.

Notes:

• db2set with no variable name displays all defined variables.
• db2set <variable> displays <variable>'s value.
• db2set <variable>= (nothing) deletes the <variable>.
• db2set <variable>=<value> modifies the <variable>'s value.
• db2set <variable> -null sets <variable>'s value to NULL.
• db2set <variable> -all displays all defined <variable>'s values.
• db2set -ur refreshes the current user profile.
• db2set <variable> -ul displays defined <variables> at the user level.
• db2set -all displays all defined variables in all registry levels.

Explanation

You can configure many aspects of DB2 database functionality by setting DB2 profile registry variables. You can set DB2 profile registry variables by using the db2set command.

This message is returned when an attempt is made to use the db2set command to set a DB2 profile registry variable to a value that is invalid.

Explanation

An invalid parameter was used.

Explanation

The variable was not set in the profile registry.

Explanation

The tool encountered an unexpected system error.

Explanation

The target machine does not have a profile registry setup.

Explanation

The instance is not defined in the target machine registry.

Explanation

The instance node is not defined in the target machine registry.

Explanation

The tool encountered an “out of memory resource” error.

Explanation

The tool encountered an operating system error.

Explanation

The tool does not support the remote registry option.

Explanation

To display the group definition, the registry variable must be an aggregate type registry variable.

Explanation

The target instance is not a DB2 MPP instance.

Explanation

A duplicate instance node already exists.

Explanation

The value specified for the registry variable exceeds the maximum limit. The maximum length for a registry variable value is 255 bytes.

Explanation

An aggregate registry variable has been configured to a value whose group definition contains settings for a variable which has been explicitly configured. The explicitly configured value will be retained.

Explanation

This script is used to gather information useful to IBM Support to debug the problems you may be experiencing. This information may be of a sensitive nature. You may wish to edit the output file, db2ginfo.txt, before sending it to IBM Support.

Explanation

The ulimit setting for the current non-root database manager instance has values for 'data' and 'nofiles' smaller than the values recommended by DB2 on the current platform. Set the 'data' to 'unlimited' and 'nofiles' to '65536' or the maximum value allowed on the system. If setting 'data' to 'unlimited' cannot be done, the following formula can be used as reference to decide the estimate value in kilobytes of 'data' required by DB2 for the current platform:

default_data_ulimit + ( ( 20 * max_concurrent_active_databases ) + estimated_max_connections ) * max_querydegree * 8192

where:

1. default_data_ulimit is the default value of 'data' of ulimit for a user on the system. For example, the default value is 262144 on IBM AIX system.
2. max_concurrent_active_databases is the maximum number of concurrent active databases for the instance.
3. estimated_max_connections is the estimated maximum number of database connections for the instance.
4. max_querydegree is the value of the parameter "MAX_QUERYDEGREE" for database manager configuration when the INTRA_PARALLEL is enabled in the database manager configuration. If INTRA_PARALLEL is not enabled, the max_querydegree's value is 1.

Explanation

Syntax:

db2iprune -r input_file_path 
          -o destination_dir_path | -c
         [-t trace_file]                 
         [-l log_filename]
         [-h|-?]

Explanation

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

-d

Specifies the full path to the output directory for generated files. If the output directory specified is an existing directory, the directory must be empty and writable. If the output directory specified does not exist, the new directory is created if the location is writable. This parameter is mandatory.

-i instance

Generates the specified instance configuration and saves this information in the generated response file and instance configuration profile. This parameter is optional. By default, all instances are selected. To specify multiple instances, specify this parameter multiple times. For example, -i db2inst1 -i db2inst3.

-t trace-file

Linux and UNIX operating systems only. Turns on the debug mode. The debug information is written to the file name specified as trace-file.

-h|-?

Displays help information.

Explanation

At least one instance is still running the DB2 Text Search instance service.

Explanation

Before running the database manager instance command, the Text Search instance service was not stopped. The database manager process stopped the Text Search instance service. However, the database manager process is unable to restart the Text Search instance service.

Explanation

The home directory of the instance owner cannot be a subdirectory under the directory in which the database product is installed.

For example, if the database product is installed in the directory named /opt/db2v97, the home directory of the user who will be the instance owner cannot be in any directory under /opt/db2v97.

This message is returned in the following scenario:

• On Linux and UNIX operating systems: the home directory of the instance owner is a subdirectory under the directory in which the database product is installed.

The database manager instance was not created.

Explanation

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

You must specify the absolute path to the shared device on which the GPFS file system will be created using the required -instance_shared_dev parameter. The db2cluster_prepare utility will create the GPFS file system in the specified location.

This message is returned when the db2cluster_prepare command is called without a value specified for the -instance_shared_dev parameter.

A GPFS file system was not created.

Explanation

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

-o

Specifies that only the installation files will be validated; validation of the instance, database, and extended security will not be performed. If this parameter is specified, the -i, -a, -b, and -s parameters are ignored.

-i inst_name

Specifies that the name of the instance to validate. To specify validation of multiple instances, specify this parameter multiple times. For example, -i inst1 -i inst2.

• On Windows operating systems, if this parameter is not specified, the current instance will be used as the default value.
• On Linux and UNIX operating systems, this parameter can only be used by root users in a root installation of a DB2 copy.

-a

Validates all instances in the DB2 copy. On Linux and UNIX operating systems, this parameter can only be used by root users in a root installation of a DB2 copy. This option overrides the -i option.

-b db_name

Validates the local database creation and connection with the given database name. This parameter is ignored in the following scenarios:

• the instance to be validated is a client instance
• -a and -i are not specified when db2val is run by root users (on Linux and UNIX only).

-t trace_file

Specifies the full path and name of trace file specified by trace_file.

-d

This parameter is deprecated and might be removed in a future release. Use the the -t parameter instead. Valid only on Linux and UNIX operating systems. Use this parameter only when instructed by DB2 Support. Turns the debug mode on.

-s

Starts the database manager for the specified instance that is part of a partitioned database environment. This parameter overrides parameter -i.

-l log_file

Writes the log to the file name specified. Unless the -l parameter is specified, the default log path is:

• On Linux and Unix, /tmp/db2valxx.log
• On Windows, My Documents\DB2LOG\db2valxx.log

where xx is a generated value.

-h|-?

Displays the usage information.

Explanation

The file IWH.environment contains global information for all instances. Updating this file might affect all instances. Do you wish to continue?

Explanation

Some features or components have missing files or are the wrong size.

Explanation

The template file for IWH.environment is needed.

Explanation

You can verify the basic functions of a DB2 copy, checking the state of installation files, instance setup, and local database connections, by using the db2val utility.

This message is returned when the db2val utility detected problems with the DB2 copy that is installed at the given location.

The reason code indicates more specifically what the problem is:

1

Some features or components have missing files or files with the wrong size.

2

The installation image inside the install path has missing files.

3

The embedded runtime path for some DB2 library or executable files is not set properly.

4

The installation path is not accessible to the database manager.

5

The /etc/services file is not accessible to the database manager.

Explanation

1. The format of the DB2 node configuration file (db2nodes.cfg) is incorrect.
2. The other database partition servers are not accessible.
3. The start and end ports for Fast Communication Manager (FCM) are not reserved properly on all database partition servers.
4. The instance profile directory is not accessible from all database partition servers.
5. The instance service is running under a non-domain account. This will prevent the database manager instance from starting.
6. The installation directory for the instance is not accessible from all database partition servers.
7. The code level on each database partition server is not consistent.
8. On Windows operating systems, if the db2val command is run to validate a multiple partition instance, domain user account authority is required.
9. An unexpected internal error occurred.

Explanation

1. The default instance is not set.
2. Some files in the instance directory are damaged. The symbolic links of the files are not pointing to the current DB2 copy installation path, and the file permission and ownership might have been changed.
3. The DB2 Extended Security setup does not allow the current user to start an instance. If Extended Security is enabled, the user needs to be in the DB2ADMNS group.
4. To start the instance, read permission is required to the /etc/services file.
5. The appropriate authority is required to validate this instance.
6. The partitioned database environment setting is not correct.
7. The instance failed to start because of system errors.
8. An unexpected internal error occurred.

Explanation

The appropriate authority is required to run the command.

Explanation

The specified instance does not exist in the current DB2 copy and will not be validated.

Explanation

Creating an instance requires the users who manage the instance to have read permission to the /etc/services file.

Explanation

Database validation failed because of one of the following reasons:

1. Database creation failed because of system errors.
2. Database connection failed because of system errors.
3. An unexpected internal error occurred.

Explanation

Explanation

The database manager has detected IWM schema objects, possibly from a previous install of IWM.

Explanation

An attempt to create the IWM schema objects has failed.

Explanation

The node number is not defined in the db2nodes.cfg.

Explanation

The directory named as a container for the table space already exists.

Explanation

There was a problem binding the bind files listed in named file(s).

Explanation

The database likely does not exist.

Explanation

The database manager has failed to modify the .profile file or the .login file of this user. These files may not exist, or you may not have write permission to them. Without the modification you need to set your environment manually each time when you log in as this user to use DB2 Query Patroller.

Explanation

The database might be in use by other applications.

Explanation

The database might still be in use.

Explanation

DB2 Text Search configuration can only be performed on server instances.

Explanation

The DB2 Text Search feature cannot be configured for this instance.

Explanation

The user's account is locked by the operating system.

Explanation

The syntax for the db2isetup command is:

   db2isetup   [-h|-?] 
               [-i <language_code>] 
               [-r <response_file>] 
               [-t <trace_file>] 
               [-l <log_file>]

Explanation

You can upgrade a non-root database manager instance to a new database product version by issuing the db2nrupgrade command.

This message is returned when the db2nrupgrade command is issued and an unsupported parameter is specified with the command.

Explanation

database_name

Specifies the name of a database to be scanned.

-e

Specifies that all local cataloged databases are to be scanned.

-l logfile

Mandatory parameter. Specifies a log file to keep a list of errors and warnings generated for the scanned database.

-u userid

Specifies the user ID of the instance owner.

-p password

Specifies the password of the instance owner.

-h|?

Displays the usage information.

Explanation

An attempt was made to upgrade the instance. This instance cannot be upgraded because either:

• The DB2 version running the db2nrupgrade command is not a supported version to upgrade the current instance.
• The instance is still active

Explanation

The directory cannot be accessed.

Explanation

The deprecated command will be removed from a future release.

Explanation

The current instance is of type client or DB2 pureScale. The command completed, but the -j "TEXT_SEARCH" option was ignored.

Explanation

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

You can cause the db2cluster_prepare utility to generate a trace file by specifying an absolute path for the trace file using the -t parameter. The db2cluster_prepare utility will create the trace file in the specified location. You can use this trace file to investigate any errors that occur while the GPFS cluster is being created.

This message is returned when the db2cluster_prepare command is called with a trace file location specified with the -t parameter and the db2cluster_prepare utility cannot access the specified trace path.

The db2cluster_prepare utility runs with the same authority as the user who runs the db2cluster_prepare command. This means that the user who runs the db2cluster_prepare command must have access to the path specified with the parameter.

A GPFS file system was not created.

Explanation

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

The db2cluster_prepare utility generates a log file that you can use to investigate any errors that occur while the GPFS cluster is being created. You can set the location for the log file by specifying an absolute path for the log file using the -log_file_path parameter. The db2cluster_prepare utility will create the log file in the specified location.

This message is returned when the db2cluster_prepare command is called with a log file location specified with the -log_file_path parameter and the db2cluster_prepare utility cannot access the specified log path.

The db2cluster_prepare utility runs with the same authority as the user who runs the db2cluster_prepare command. This means that the user who runs the db2cluster_prepare command must have access to the path specified with the -log_file_path parameter.

A GPFS file system was not created.

Explanation

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

The db2cluster_prepare utility generates some temporary files for internal use. This message is returned when the db2cluster_prepare command is unable to create these internal, temporary files.

The db2cluster_prepare utility runs with the same authority as the user who runs the db2cluster_prepare command. This means that to run the db2cluster_prepare command, you must have access to the named path.

A GPFS file system was not created.

Explanation

The Administrative Task Scheduler (ATS) could not be enabled. Enabling ATS is a prerequisite for using DB2 Text Search.

Explanation

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

The db2cluster_prepare utility generates a log file that you can use to investigate any errors that occur while the GPFS cluster is being created. You can set the location for the log file by specifying an absolute path with the -log_file_path parameter. If you do not use the -log_file_path parameter, the db2cluster_prepare utility will attempt to create a log file named db2prepare_cluster.log in the default directory location /tmp.

This message is returned when the db2cluster_prepare command is called without a log file location being specified with the -log_file_path parameter the db2cluster_prepare utility cannot access the directory named /tmp.

The db2cluster_prepare utility runs with the same authority as the user who runs the db2cluster_prepare command. This means that you must be able to access the directory named /tmp to be able to call the db2cluster_prepare command without specifying the -log_file_path parameter.

A GPFS file system was not created.

Explanation

In a DB2 pureScale environment, all data and logs must be on a General Parallel File System. Existing data and logs that are not on GPFS must be moved to GPFS before upgrading to a DB2 pureScale environment. You can set up a DB2 managed GPFS cluster and file system, so that the data and logs can be moved to it in preparation for the upgrade to a DB2 pureScale environment using the db2cluster_prepare utility.

Explanation

The db2licm tool performs basic license functions. It adds, removes, lists, and modifies licenses installed on the local system. Execute db2licm tool with -l parameter to find out the product identifier for your product:

db2licm [-a filename]
        [-e product-identifier HARD | SOFT]
        [-p product-identifier
        REGISTERED | CONCURRENT | OFF]
        [-r product-identifier]
        [-u product-identifier num-users]
        [-c product-identifier num-connectors]
        [-l]
        [-v]
        [-?]

The command options are:

-a

Adds a license for a product. Specify a file name containing valid license information. This can be obtained from your licensed product CD or contact your IBM representative or authorized dealer.

-e

Updates the enforcement policy on the system. Valid values are: HARD and SOFT. HARD specifies that unlicensed requests will not be allowed. SOFT specifies that unlicensed requests will be logged but not restricted.

-p

Updates the license policy type to use on the system. The keywords CONCURRENT, REGISTERED, or CONCURRENT REGISTERED can be specified. Specify OFF to turn off all policies.

-r

Removes the license for a product. After the license is removed, the product functions in "Try & Buy" mode. To get the password for a specific product, invoke the command with the -l option.

-u

Updates the number of user entitlements that have been purchased. Specify the password of the product for which the entitlements were purchased and the number of users.

-c

Updates the number of connector entitlements that have been purchased. Specify the password of the product for which the entitlements were purchased and the number of connectors.

-l

Lists all the products with available license information, including the product identifier.

-v

Displays version information.

-?

Displays help information. When this option is specified, all other options are ignored, and only the help information is displayed.

Explanation

The db2licm tool performs basic license functions. It adds, removes, lists, and modifies licenses installed on the local system.

To determine the product identifier for your product issue the db2licm -l command.

db2licm [-a filename]
        [-e product-identifier HARD | SOFT]
        [-p product-identifier
        REGISTERED | CONCURRENT | OFF]
        [-r product-identifier]
        [-u product-identifier num-users]
        [-c product-identifier num-connectors]
        [-l]
        [-v]
        [-?]

The command options are:

-a

Adds a license for a product. Specify a file name containing valid license information. This can be obtained from your licensed product CD or contact your IBM representative or authorized dealer.

-e

Updates the enforcement policy on the system. Valid values are: HARD and SOFT. HARD specifies that unlicensed requests will not be allowed. SOFT specifies that unlicensed requests will be logged but not restricted.

-p

Updates the license policy type to use on the system. The keywords CONCURRENT, REGISTERED, or CONCURRENT REGISTERED can be specified. Specify OFF to turn off all policies.

-r

Removes the license for a product. After the license is removed, the product functions in "Try & Buy" mode.

-u

Updates the number of user entitlements that have been purchased. Specify the password of the product for which the entitlements were purchased and the number of users.

-c

Updates the number of connector entitlements that have been purchased. Specify the password of the product for which the entitlements were purchased and the number of connectors.

-l

Lists all the products with available license information, including the product identifier.

-v

Displays version information.

-?

Displays help information. When this option is specified, all other options are ignored, and only the help information is displayed.

Explanation

The given identifier is invalid, or a license for this product was not found.

Explanation

The license policy type that was entered was not valid for the product specified.

Explanation

License certificate file is not in the correct format.

Explanation

The file is not found or access to the file is denied.

Explanation

The enforcement policy type specified is not valid for this product.

Explanation

You can perform basic license functions such as adding, removing, listing, or modifying licenses and policies by using the db2licm command.

Explanation

You can perform basic license functions such as adding, removing, listing, or modifying licenses and policies by using the db2licm command.

This message is returned when a license cannot be removed.

Explanation

The return code is “<return-code>”.

Explanation

The license policy specified does not apply to this product or is not supported.

Explanation

You can not configure a license policy for a product until the product is installed.

Explanation

The return code is “<return-code>”.

Explanation

Features that are required to perform this action are only accessible once an instance has been created.

Explanation

The return code is “<return-code>”.

Explanation

The database manager cannot update the license for the OLAP server while the OLAP server is running.

Explanation

The number of licensed processors entered exceeds the number of maximum licensed processors allowed for this product.

Explanation

You can perform basic license functions such as adding, removing, listing, or modifying licenses and policies by using the db2licm command.

This message is returned when a license could not be added because the date in the certificate file is later than the current operating system date.

Explanation

This program can be run only under the root user ID or a user ID with SYSADM authority.

Explanation

This product has used the maximum number of evaluation licenses.

Explanation

The specified number of license entitlements is not in the valid range.

Explanation

The installer failed to activate this license entry, therefore the database product will run with the previous license configuration until this license is activated.

Explanation

DB2 First Steps requires a supported Web browser.

Explanation

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

You can cause the db2cluster_prepare utility to generate a trace file by specifying an absolute path for the trace file using the -t parameter. The db2cluster_prepare utility will create the trace file in the specified location. You can use this trace file to investigate any errors that occur while the GPFS cluster is being created.

This message is returned when the db2cluster_prepare command is called without a value specified for the -t parameter.

A GPFS file system was not created.

Explanation

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

The db2cluster_prepare utility generates a log file that you can use to investigate any errors that might occur while the GPFS cluster is being created. You can set the location for the log file by specifying an absolute path with the parameter named -l. If you use the parameter named -l, the db2cluster_prepare utility will create the log file in the specified location.

This message is returned when the db2cluster_prepare command is called without a value specified for the parameter named -l.

A GPFS file system was not created.

Explanation

The registry was successfully updated with the new value, however, it is never possible for the change to the variable specified by the db2set -immediate call to take effect immediately. The -immediate option has been ignored.

Explanation

Although the offline registry was updated successfully, the value cannot be applied immediately by one or more members because db2set could not attach to the instance.

Explanation

The offline registry was successfully updated, and the registry update has been made immediately on all of the hosts or members db2set could access.

On the hosts or members that db2set could not access, however, the setting for the variable specified could not be applied immediately.

Explanation

The aggregate registry variable was successfully updated immediately. Some of the variables governed by the aggregate variable were changed dynamically, but other variables governed by the aggregate variable require the instance to be restarted to take effect.

Explanation

On the Windows operating system, registry variables are stored within the operating system registry of each host. Currently at least one registry variable has been set to a number of different values across hosts. It is highly recommended to keep each registry variable set consistently on all hosts.

Explanation

The database product installation path passed to the db2ls command with the -b option must be the location of a copy with DB2 Version 9 or later installed.

Explanation

The execution of the command requires a Java Runtime Environment (JRE). If IBM Software Development Kit (SDK) for Java is installed with the related DB2 copy, the JRE is found in <DB2DIR>/java/jdk64/jre/bin for 64-bit Linux systems, or <DB2DIR>/java/jdk32/jre/bin for 32-bit Linux systems, where <DB2DIR> represents the installation path of the related DB2 copy.

If a JRE is not found in either path, the program looks for a JRE in either:

• the current user's ${JAVA_HOME}/jre/bin, or,
• the default PATH environment.

In this case, the JRE must meet the current DB2 version requirements.

Explanation

On Linux operating systems, main menu entries for database tools can be created and removed manually or automatically. Main menu entries for database tools, such as db2fs, can be created manually by running the db2addicons command, or created automatically when some commands are run. These main menu entries can be removed manually by running the db2rmicons command, or removed automatically when some commands are run. Errors occurred during either the creation or removal of these main menu entries.

Explanation

The db2addicons command creates main menu entries for the database tools, such as db2fs, for the current user. The main menu entries for the database manager tools are created by manually running the db2addicons command, or are created automatically when some commands are run.

The only argument for this command is:

-h

displays the usage information.

Explanation

The db2rmicons command removes main menu entries for the database tools, such as db2fs, for the current user. The main menu entries for the database tools are removed by manually running the db2rmicons command, or are removed automatically when some commands are run.

The only argument for this command is:

-h

displays the usage information.

Explanation

On Linux operating systems, the database manager instance environment needs to be set for the current user before the command can be run. An instance environment can be setup with:

• <Instance_HOME>/sqllib/db2profile (for Bourne shell and Korn shell users), or
• <Instance_HOME>/sqllib/db2chsrc (for C shell users)

where <Instance_HOME> is the instance owner's home directory.

Explanation

Specified component name is either incorrect or misspelled. If the component name is correct, this component name might not be valid on this operating system or platform.

Explanation

The db2val command does not support validation on a DB2 pureScale instance.

Explanation

The specified instance is a DB2 pureScale instance. When the db2rspgn command is run against a DB2 pureScale instance the information on the specified instance is not added to the generated response file and the instance profile is not created.

Explanation

The command is only supported on the coordinating member of the instance.

Explanation

The product or feature must not be associated with any instances when it is uninstalled. The db2ilist command is used to list installed instances.

Explanation

The db2iupdt command can be used to update an instance to a higher level within a release. The db2iupgrade command upgrades an instance to a DB2 copy of the current release from a DB2 copy of a previous release. The instance update and upgrade are only supported on the instance-owning member.

Explanation

You can uninstall database products, features, or languages using the db2_deinstall command.

Before you can uninstall any part of a non-root installed database manager instance, all operating system processes and resources for that instance must be release. This message is returned when an attempt is made to uninstall a non-root installed instance while some DB2 database-related system resources have not been freed. For example, this message can be returned for the following reasons:

• DB2 database-related operating system processes are still running
• DB2 database-related libraries are still loaded in memory

Explanation

When using the db2setup command, if the -c parameter is specified to validate the contents of a response file, the -r parameter indicating the response file must also be specified.

Explanation

You can update the installed database products to the same level by using the installFixPack command.

In DB2 pureScale environments only, you can update multiple hosts in a DB2 cluster by specifying the -H parameter with the installFixPack command.

This message is returned when the -H parameter is specified with the installFixPack command in an environment that is not a DB2 pureScale environment.

Explanation

Validation process in progress.

Explanation

Invalid entries were detected in the response file. For more details, refer to the log file.

Explanation

There are specific parameters related to specific actions in the installFixPack command. Some parameters cannot be specified for some actions.

This message is returned when two parameters of the installFixPack command cannot be specified together because the syntax does not support such usage.

Explanation

An error was detected in the specified host list file. The error can occur for any of the following reasons: the file does not exist, the file is not readable, the file is empty or contains an invalid character, the path name is not specified, or the HOST keyword is not valid.

Explanation

The specified reason code indicates one of the following errors occurred:

1

The IBM Reliable Scalable Cluster Technology (RSCT) peer domain is not online

2

The IBM General Parallel File System (GPFS) cluster is not online

3

At least one db2 cluster services alert is indicated

Explanation

The db2ndrop command is used to drop a database partition server from an instance that has no databases.

The db2ndrop command cannot drop the instance owning database partition server (0). To drop a database partition server that is assigned to the logical port 0 from a machine that is running multiple logical database partition servers, all other database partition servers assigned to the other logical ports must be dropped first. Each database partition server must have a database partition server assigned to logical port 0.

Explanation

The validation failed on the specified hosts.

Explanation

The instance might be in the rolling update stage.

Explanation

The specified reason code indicates one of the following errors occurred:

1

Validation on the specified host did not finish before time-out.

2

The instance is configured to use passwordless SSH and passwordless SSH communication between the specified host and other hosts failed.

3

Instance shared directory cannot be accessed from the given host or is not shared between the given host and the local host.

4

Some files in the instance directory are damaged. The symbolic links of the files are not pointing to the instance shared directory.

5

The specified host is offline in the RSCT peer domain.

6

The specified host is stopped in the GPFS cluster.

7

Installation file validation failed for the DB2 copy on the specified host.

Explanation

The validation process completed successfully.

Explanation

The deprecated parameter will be removed from a future release.

Explanation

The deprecated parameter might be removed from a future release.

Explanation

In the specified command, the path specified for the instance shared mount point must be a new path and must not be a sub-directory of an existing GPFS file system.

Explanation

To install the DB2 pureScale Feature you must be logged in as the root user. Installation is restricted to the root user because components required by DB2 pureScale affect shared resources on the system.

Explanation

This message is returned when the db2_install command is issued with the "-f PURESCALE" option and another option is also specified that is not supported with the "-f PURESCALE" option.

Explanation

The syntax entered was invalid. See the corresponding reason code for an explanation of the cause of the error.

1. The -cfs_takeover and -instance_shared_dev option are mutually exclusive, when specifying one option for db2cluster_prepare the other cannot be used.
2. The db2cluster_prepare command failed because one or more parameters were specified multiple times.
3. The db2cluster_prepare command failed because no value was specified for the -instance_shared_dev parameter.
4. The db2cluster_prepare command failed because no value was specified for the -t parameter.
5. The db2cluster_prepare command failed because no value was specified for the parameter named -l.
6. The db2cluster_prepare command failed because no value was specified for the -instance_shared_dev parameter.

Explanation

The GPFS efixes detected by the installer were not installed by the database product. The installer can only remove efixes installed as part of a database product installation. The specified efixes must be removed manually.

Explanation

The DB2NDROP utility drops a node from a partitioned system.

DB2NDROP /n:node
         [/i:instance]

The command options are:

• /i Specify the instance if different from the default/current instance

Explanation

DB2NDROP failed because the node does not exist.

Explanation

The DB2NDROP processing has completed successfully.

Explanation

The '-s' option skips the removal of a feature, and the '-F feature-name' option specifies that feature feature-name, should be removed. These two options must not contain the same feature identifier.

Explanation

The GPFS feature cannot be removed with '-F GPFS' option of the db2_deinstall command. By default, the GPFS feature will be removed with the 'db2_deinstall -a' command when you remove the last DB2 copy and GPFS is not still in use, if GPFS was installed by the database product installer.

Explanation

If an RSCT peer domain is present, the Tivoli SA MP component is not uninstalled with the DB2 copy to prevent adverse behavior of other copies or applications, which might depend on the peer domain or Tivoli SA MP.