DBI1500 - DBI1999

DBI1500I

An incorrect argument was entered. The command accepts an optional flag -f which is followed by the path of the database product installer response file.

Re-enter the command with a valid argument.

DBI1501E

While installing database components and related, bundled software the database product installer verifies operating system requirements and configuration settings. This message is returned when the database product installer detects a problem that will prevent successfully installing or running the database product.

This message can be returned for many different reasons, including the following common reasons:

• There is a problem with the contents of the /etc/hosts file:
  • The /etc/hosts file does not contain the IP address or host name of the local computer
  • The /etc/hosts file contains conflicting entries for an IP address or host name
• IBM Tivoli System Automation for Multiplatforms (SA MP) was not installed successfully
• Ports that are assigned for the database server to use are not available or are assigned to other services
• The host name of the local computer has changed

Perform one or more of the following troubleshooting steps:

• Verify the contents of the /etc/service file by running the hostname command.
• Verify the contents of the /etc/hosts file manually.
• Verify the availability of IP addresses by running the nslookup command.
• Install the database product by running the db2_install command instead of using the Setup wizard.
• If the SA MP software that is bundled with the database product is not needed, install the database product without the SA MP component by running the db2_install command with the -f NOTSAMP option.

If the problem persists after the above troubleshooting steps have been taken, collect diagnostic information by running the db2setup command with the -t option, and then contact IBM software support for assistance.

DBI1502E

DBI1503E

DBI1504E

Set the environment variables DB2IRCX and DB2ICAT to the absolute location of db2inst.rcx and db2inst.cat respectively.

DBI1505E

An error was detected when attempting to allocate memory.

DBI1506E

The Tivoli SA MP product must be at the version level included in the database product installation image. To avoid any potential problems with the existing peer domain, the database product installer does not attempt to upgrade Tivoli SA MP when a peer domain is in use. There is a Reliable Scalable Cluster Technology (RSCT) peer domain on the system preventing the installer from upgrading the Tivoli SA MP installation.

Manually upgrade the Tivoli SA MP product before attempting to install the DB2 pureScale Feature.

DBI1507E

An error was detected when attempting to start up the database product installer. Another instance of the database product installer is still running.

Terminate all instances of the database product installer and restart the install process. If the problem persists, remove the lock file /tmp/.db2inst.lck and restart the database product installer.

DBI1508W

Only one SA MP copy can be installed on a system, and the database product installation required that the SA MP product installed be upgraded to the version of SA MP integrated with the database product installation media.

If other software has dependencies on SA MP verify that the software is compatible with the updated SA MP version.

DBI1509W

Failure to upgrade Tivoli SA MP can be caused if the Reliable Scalable Cluster Technology (RSCT) peer domain is offline or in maintenance mode.

Manually upgrade the Tivoli SA MP product after the database product installation or update completes. See the Tivoli SA MP Base Component Installation and Configuration Guide for more information.

DBI1510E

The database manager instance processes are run with the user ID for non-root database product installations. All instances are required to run with a unique ID, this restricts a non-root user to a single copy.

Upgrade the installed non-root DB2 copy with by upgrading with a response file, specifying the keyword "UPGRADE_PRIOR_VERSION". Alternatively, you can run "db2_install -m" to upgrade the installed copy.

DBI1511E

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

TSAMP_RC is the return code fom the installSAM utility.

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

SA MP was not installed.

See the mentioned log file for details.

To install SA MP manually, use the installSAM command.

For more information about the installSAM command, see the SA MP Base Component documentation.

DBI1512E

The database product is supported on more operating systems than the DB2 pureScale Feature. The detected operating system does not support DB2 pureScale.

Review the prerequisites for DB2 pureScale before attempting another installation.

DBI1513E

db2_deinstall uses the uninstallSAM utility to uninstall SA MP. The uninstallSAM utility returned errors. The uninstallSAM log file contains more complete information.

TSAMP_RC is the return code fom the uninstallSAM utility.

Note that you must have root authority to use db2_deinstall to uninstall SA MP.

SA MP was not uninstalled.

See the mentioned log file for details.

To uninstall SA MP manually, use the uninstallSAM command.

DBI1514I

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.

No action is required.

DBI1515E

An error was detected when attempting to startup a subprocess.

DBI1516E

An error was detected when attempting to terminate a subprocess.

DBI1517E

DBI1518E

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 tried to install or update the DB2 HA scripts, but was not successful.

Use the command db2cptsa to manually install or update these scripts.

DBI1519E

The database product is not able to extend the DB2 pureScale instance to the host. The set up of DB2 cluster services failed on the remote host.

Examine the log file db2iupdt.log in /tmp/db2iupdt/ on the host, correct the conditions, and rerun the db2iupdt command.

DBI1520E

Your current terminal or window size is not large enough. This program requires a minimum terminal display size of 24 lines by 80 columns.

Check your terminal or window size and try again.

DBI1521E

DBI1522E

An error was detected when attempting to restore your terminal display to the original state.

DBI1523E

The host name is not currently a cluster caching facility. The host is a DB2 member.

Rerun this command with a cluster caching facility name.

DBI1525E

The db2idrop command was run without using the -g option for a DB2 pureScale instance. To completely drop a DB2 pureScale instance, the -g option is required.

If the DB2 pureScale instance needs to be completely dropped on all the hosts, rerun the db2idrop command with the -g option. Otherwise, run the db2iupdt command with the -drop option.

DBI1527E

The GPFS license is provided for use with the DB2 pureScale Feature only. The DB2 pureScale must be selected in the installation response file to install GPFS.

Edit the installation response file to select both components for installation.

DBI1528E

To add a product to a DB2 copy, the installed product and the product being installed must be at the same version and fix pack level.

You can update the installed copy to the version on the installation image, before installing the new product to the same path. Alternatively, you can install a new DB2 copy.

DBI1529W

When the installation-initiating host installs the DB2 pureScale Feature, the installation image copied to members does not include language packs or products that were not selected. Excluding these files from the installation image results in a smaller disk footprint and less network traffic during installation. When adding a language feature or product after the initial DB2 pureScale instance is created, they must be manually installed on each of the other members of the instance because they do not exist in the installation image on the other members. After adding additional language features or products, new members added to the DB2 pureScale instance will include all languages and products that are installed on the installation-initiating host.

Add the language features and products to other members by manually installing the products added to this host on the others.

DBI1530E

Restart the install process and retry with a correct path name.

DBI1531E

This instance type cannot be validated using the db2val command.

No action required.

DBI1532W

Only one Tivoli SA MP copy can be installed on a system. The database product installation requires that the installed Tivoli SA MP product be upgraded to the version of SA MP integrated with the database product installation media.

If other software has dependencies on Tivoli SA MP verify that the software is compatible with the updated Tivoli SA MP version.

DBI1533W

You can uninstall database products, features, or languages on Linux and UNIX operating systems by using the db2_deinstall command. If IBM General Parallel File System (GPFS) software was installed as part of a DB2 pureScale Feature installation, the db2_deinstall utility will uninstall the GPFS product by default.

In order for the db2_deinstall utility to uninstall the GPFS product, the GPFS cluster and file system that the database product or feature being uninstalled is using must be manually removed before the db2_deinstall command is run. You can cause the db2_deinstall utility to skip uninstalling the GPFS product by specifying the "-s GPFS" option.

This message is returned when the db2_deinstall command is run on a host machine that is part of a GPFS cluster and the "-s GPFS" option was not specified with the db2_deinstall command.

Respond to this error in one of the following ways:

• If there are no database manager instances using a GPFS cluster on the current host machine, perform the following steps:
  1. Remove the GPFS cluster and file system manually.
  2. Complete the process of uninstalling database products and Features as well as uninstalling the GPFS product by calling the db2_deinstall command again.
• If other instances are using a GPFS cluster on the current host machine, uninstall the database product or Feature without uninstalling the GPFS product by calling the db2_deinstall command again, specifying the "-s GPFS" option.

DBI1534E

The db2_deinstall command cannot continue because the current host is part of a RSCT peer domain.

If IBM Tivoli System Automation for Multiplatforms (SA MP) is required on this host, remove any DB2 pureScale instances that are on this host using either the "db2iupdt -drop" or "db2idrop -g" command. If the peer domain is needed, by-pass the Tivoli SA MP binary removal by running "db2_deinstall -a -s TSAMP". If there are no resources using the peer domain on this host, before re-issuing the command, manually remove Tivoli SA MP.

DBI1535W

The pre-installation validation detected that it cannot upgrade Tivoli SA MP. If the Reliable Scalable Cluster Technology (RSCT) peer domain is offline or in maintenance mode it can cause the validation to fail.

Manually upgrade the Tivoli SA MP product after the database product installation or update completes. See the Tivoli SA MP Base Component Installation and Configuration Guide for more information.

DBI1536E

Tivoli SA MP is a required component of the DB2 pureScale environment. The Tivoli SA MP product was not installed or updated due to the unexpected error.

Manually install the Tivoli SA MP product, then install the DB2 pureScale product. See the Tivoli SA MP Base Component Installation and Configuration Guide for more information.

DBI1537E

A database manager instance cannot be updated while any member or cluster caching facility (CF) is active.

1. Identify active members or CFs in the instance by issuing the following command:

    db2instance -list 

2. Stop any active member by issuing the following command:

    db2stop member <member-id> 

3. Stop any active CF by issuing the following command:

    db2stop CF <CF-id> 

4. Stop the instance by issuing the following command:

    db2stop instance on <host> 

5. Retry the fix pack update operation.

DBI1538E

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

This message is returned when a command is called with a parameter specified that is valid for only DB2 pureScale instances.

Respond to this message in one of the following ways:

• Re-issue the command without specifying parameters that are valid for only DB2 pureScale instances.
• To use DB2 pureScale functionality, update the instance to a DB2 pureScale instance and then call the command again.

DBI1539E

The code level of a given database product is comprised of product details such as: version, release, modification level, interim fix pack level, and special build tokens. The current effective code level (CECL) is the code level at which an instance is said to be operating.

The curr_eff_code_level configuration parameter shows the CECL for an instance.

Online fix pack updates of an instance towards a code level that is lower than the CECL of the instance is not supported.

Update the instance by performing an offline update.

DBI1540E

Check the path and try the command again. Note that all file and directory names in Unix are case sensitive.

DBI1541E

DBI1544E

The database manager instance was created but it is missing some data structures. Some DB2 functionality might not be available or have unpredictable behavior.

Drop and create the instance again. If the problem persist, contact IBM support.

DBI1546E

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

This message is returned in two scenarios:

• The version of the currently installed database product is not supported by the installFixPack command
• The fix pack being applied is a different release from the release of the currently installed database product

Upgrade the installed database product to the same release as the fix pack, and then apply the fix pack.

DBI1547E

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

This message is returned when an attempt is made to perform an online fix pack update while an offline fix pack update is in progress. An online fix pack update cannot be performed until the offline fix pack update is committed or canceled.

To respond to this message, perform the following steps:

1. Wait until the offline fix pack update that is in progress is committed or canceled.
2. Initiate the online fix pack update again.

DBI1548E

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

This message is returned when an attempt is made to perform an offline fix pack update while an online update is in progress. An offline fix pack update cannot be performed until the online fix pack update is committed or canceled.

To respond to this message, perform the following steps:

1. Wait until the online fix pack update that is in progress is committed or canceled.
2. Retry the offline fix pack update.

DBI1549E

The code level of a given database product is comprised of product details such as: version, release, modification level, and fix pack level. During a fix pack update operation, it is possible for some DB2 members or CFs in a DB2 cluster to be at one code level while other members or CFs in the same DB2 cluster are at a second code level.

Performing a fix pack update of a database manager instance is only supported when the members and CFs in a DB2 cluster are at a maximum of two distinct code levels.

This message is returned when an attempt is made to perform a fix pack update to a new code level that is different than the code level of the fix pack update performed on several DB2 members and CFs in the same DB2 cluster.

To perform the fix pack update to the specified code level, perform the following steps:

1. Update all members and CFs in the DB2 cluster to the same code level as the fix pack update that is in progress.
2. Retry the fix pack update to the specified code level.

DBI1550E

An error was encountered when trying to allocate more disk space on the file system.

Retry the command after enough space has been freed up for the specified operation.

DBI1551E

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

This message is returned when an attempt is made to perform an online fix pack update between two code levels, and online fix pack updates is not supported between those two code levels.

Perform an offline fix pack update.

DBI1552E

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

This message is returned when an attempt is made to perform an online fix pack update from code level A to code level C, and the online fix pack update to code level C requires the instance to have a CECL that is higher than code level A.

Respond to this message in one of the following ways:

• Perform an offline fix pack update to the specified code level.
• Perform the online fix pack update to the specified code level by following these steps:
  1. Determine the minimum committed code level from which you can perform an online fix pack update to the new code level by using the installFixPack -show_level_info command.
  2. Update and commit the instance to the minimum code level that you determine in the previous step.
  3. Perform the online fix pack update to the specified code level.

DBI1554E

You can update the version to a higher code level within a release without having to bring your database offline by using an online fix pack update. This message is returned in two cases:

• An attempt is made to perform an online fix pack update to a special build, but performing an online fix pack update from the current code level to that special build is not supported unless a service password is specified.
• An attempt is made to perform an online fix pack update from a special build to another code level, but performing an online fix pack update from the special build to new code level is not supported unless a service password is specified.

Respond to this message in one of the following ways:

• Update the instance by performing an offline fix pack update.
• Work with the assistance of IBM support to set the service password.

DBI1556E

You can update the version of a database manager instance to a higher code level by performing an offline fix pack update. You can update the version of a DB2 pureScale instance to a higher level without having to bring your database offline by performing an online fix pack update.

This message is returned when a problem is encountered with an internal configuration file that is used for fix pack updates.

The reason code is useful for assisting only IBM support personnel troubleshoot the problem:

1

An invalid record was found.

2

A duplicate record was found.

3

A required record does not exist.

4

The configuration file content is invalid, or the fix pack update operation encountered an error reading the configuration file.

5

The fix pack update operation cannot find the configuration file.

6

An error occurred while writing to the configuration file.

For reason code 6, confirm that your user id has read and write access permission to the sqllib_shared directory as well as read and write access permission to the subdirectories of the sqllib_shared directory.

Perform the fix pack update operation again.

If this error persists, take note of this message identifier and reason code and contact IBM software support.

DBI1557E

You can update the version of the database product to a higher code level by performing offline fix pack updates or online fix pack updates to keep databases online.

A fix pack update has several steps. The final step is to commit the fix pack update. Before committing the fix pack update, you can optionally verify that the fix pack update operation is ready for commit by using the -check_commit parameter with the db2iupdt command or the installFixPack command.

This message is returned when the pre-commit verification or commit of the fix pack update operation determines that the new level of code is the same as the CECL.

No response is required.

DBI1558E

You can update the version of the database product to a higher code level by performing offline fix pack updates or online fix pack updates to keep databases online.

A fix pack update has several steps. The final step is to commit the fix pack update. Before committing the fix pack update, you can optionally verify that the fix pack update operation is ready for commit by using the -check_commit parameter with the db2iupdt command or the installFixPack command.

This message is returned when the pre-commit verification or commit of the online fix pack update operation determines that not all DB2 members or CFs in the DB2 pureScale instance use the same code level.

Update all DB2 members and CFs in the DB2 pureScale instance to the same code level. Then perform the pre-commit verification or commit of the online fix pack update again.

DBI1559E

An offline fix pack update has several steps. The final step is to commit the fix pack update. Before committing the fix pack update, you can optionally verify that the fix pack update operation is ready for commit.

This message is returned when the pre-commit verification or commit of the offline fix pack update operation determines that the database manager instance is online. The instance must be offline.

Respond to this message by performing the following steps:

• Stop the instance by issuing the db2stop command.
• Commit the offline fix pack update.

DBI1560E

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

A service password might be required to perform a online fix pack update with a special build or a fix pack with test fix that has been provided by IBM support.

This message is returned when an invalid service password was specified to perform an online fix pack update that requires a service password.

Work with the assistance of IBM support to obtain the required service password and then perform the online fix pack update again.

DBI1562E

You can update the version to a higher code level within a release by performing an offline fix pack update or an online fix pack update to keep the database online.

This message is returned when an online fix pack update fails because there was an error in updating instance information in the database manager configuration.

Perform the fix pack update operation again.

DBI1563W

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

An online fix pack update has several steps. The final step is to commit the online fix pack update. In this final step, the database manager configuration for each DB2 member and CFs in the DB2 cluster is updated.

This message is returned when the online fix pack update operation encounters errors while updating the in-memory database manager configuration for one or more DB2 members or CFs.

Respond to this message by performing the following actions:

1. Determine which members or CFs need to be restarted by issuing the following command:

    db2pd -rustatus 

2. Restart the affected members and CFs.

DBI1564E

You can update the version to a higher code level by performing offline fix pack updates or online fix pack updates to keep databases online.

A fix pack update performs several tasks. This message is returned when an error is encountered in one of these tasks.

Respond to this message by performing the following troubleshooting steps:

• Review the diagnostic information in the given log file or log files.
• Review the explanation and user response for the given message identifier.
• Resolve the cause of the underlying error.
• Complete the fix pack update operation.

DBI1565E

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

This message is returned when an attempt is made to perform and online fix pack update that requires a service password, but the service password environment variable has not been configured.

Work with the assistance of IBM support, to set the service password environment variable.

DBI1567E

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

You can specify where the fix pack is to be installed with the -p parameter

This message is returned when an empty path is specified with the -p parameter because this parameter is mandatory for DB2 pureScale instances.

Re-issue the installFixPack command specifying a valid new installation path with the -p parameter.

DBI1568E

If you are performing a fix pack update on a DB2 pureScale instance (dsf type instance), you must specify a path to install the fix pack that is different than the existing installation. This path must be the same on all DB2 members and cluster catching facilities (CFs).

To replace the existing installation, you must also specify the -f level parameter. However, if you specify the same path as the existing installation, you cannot cancel the fix pack update.

This message is returned when the path that is specified with the -p parameter is the same path as the current database product install path, but the -f level parameter was not specified with the installFixPack command.

Respond to this message in one of the following ways:

• Re-issue the installFixPack specifying an install path with the -p parameter that is not the same as the current database product install path.
• Re-issue the installFixPack command specifying the same install path with the -p parameter and specify the -f level parameter.

DBI1569E

You can create a new database manager instance by using the db2icrt command. You can update an existing instance by using the db2iupdt command. For both the db2icrt command and the db2iupdt command, you can specify a list of interconnect netnames for a DB2 member by using the -mnet parameter, and you can specify a list of netnames for a cluster caching facility (CF) by using the -cfnet parameter. The maximum number of netnames that can be specified for a DB2 member or CF is four.

This message is returned when an attempt is made to specify more than four netnames for a DB2 member or CF while using the db2icrt command or the db2iupdt command.

Call the command again, specifying no more than four netnames for any DB2 members or CFs.

DBI1570I

Enter the command again as follows: db2olset InstName

DBI1571E

For many database manager utility commands, some parameter are valid in only certain conditions. This message is returned when a command is called in a DB2 pureScale environment with a parameter that is not valid for DB2 pureScale environments.

Call the command again without specifying parameters that are not valid for DB2 pureScale environments.

DBI1572E

When a failed DB2 member cannot be restarted on its original host, or home host, DB2 cluster services restarts that member on one of the other available members in a DB2 pureScale instance. This process is known as restart light.

This message is returned when an attempt is made to perform a fix pack update on a DB2 member that is involved in a restart light process. Fix pack updates are not supported on DB2 members that are involved in a restart light process.

Monitor the DB2 member and retry the fix pack update when the restart light process is resolved.

DBI1573W

DB2 cluster services includes three major components, including a cluster manager, Tivoli SA MP, which includes RSCT.

When you update your database product to a new DB2 fix pack level on a DB2 member or cluster caching facility (CF), the database product install utility will automatically update the Reliable Scalable Cluster Technology (RSCT) software on that member or CF, if needed. If the version of RSCT that is already installed on that member or CF is supported by the new fix pack level, the database product install utility will not update the RSCT software on that member or CF.

This message is returned when a fix pack is being updated on a DB2 member or CF, and the version of RSCT that is currently installed on the member or CF is supported with the new fix pack level.

No action is required.

DBI1574E

In a DB2 pureScale instance, the DB2 cluster services provide essential infrastructure for the instance to be highly available and to provide automatic failover and restart as soon as the instance has been created. RSCT is one of the three major components included by DB2 cluster services.

This message is returned when an attempt is made to perform a fix pack update on DB2 member or CF that has an earlier version of RSCT installed. The fix pack update operation will update to a higher version of RSCT.

If the fix pack update is cancelled, manual installation of the earlier version of RSCT is required.

DBI1575E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online. During the fix pack update, the instance is stopped to perform the update.

This message is returned when an attempt to stop the instance on the member or CF that is being updated fails.

Stop the instance on the host by issuing the following command:

 db2stop INSTANCE ON host-name FORCE 

Once the instance is stopped, perform one of the following actions:

• Perform again the fix pack update.
• Cancel the fix pack update on the instance as follows:

   db2start INSTANCE ON host-name db2start member member-id or  db2start CF CF-identifier 

DBI1576E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online. During the fix pack update, the member is stopped to perform the update.

This message is returned when the attempt to stop the DB2 member that is being updated fails.

Stop the DB2 member by issuing the following command:

 db2stop member member-id 

Once the member is stopped, perform one of the following actions:

• Perform again the fix pack update.
• Cancel the fix pack update on the member by restarting the member as follows:

  db2start member member-id 

DBI1577E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online. During the fix pack update, the CF is stopped to perform the update.

This message is returned when the attempt to stop the CF that is being updated fails.

Stop CF by issuing the following command:

 db2stop CF CF-identifier 

Once the CF is stopped, perform one of the following actions:

• Perform again the fix pack update.
• Cancel the fix pack update on the CF by restarting the CF as follows:

   db2start CF CF-identifier 

DBI1578E

To ensure that DB2 members or cluster caching facilities (CFs) are not restarted on the host when making updates to the cluster manager, you can put the cluster manager into maintenance mode.

This message is returned when an attempt is made to perform a fix pack update but the cluster manager cannot be put in maintenance mode to be updated.

1. Verify that the cluster manager can be put into maintenance mode successfully by issuing the db2cluster command, specifying the following parameters: -cm -enter -maintenance.
2. Take the cluster manager out of maintenance mode by issuing the db2cluster command, specifying the following parameters: -cm -exit -maintenance.
3. Perform the fix pack update by issuing the installFixPack command, specifying the "-f level" parameter.

DBI1579E

To ensure that DB2 members or cluster caching facilities (CFs) are not restarted on the host when making updates to IBM General Parallel File System (GPFS) software, you can put GPFS into maintenance mode.

This message is returned when an attempt is made to perform a fix pack update but the update operation cannot put GPFS in maintenance mode to update it.

Manually put GPFS in maintenance mode, then perform the fix pack update again, specifying the -f level parameter.

DBI1580E

After making updates to the cluster manager, you can exit maintenance mode to remove the host from maintenance mode and put the domain online.

This message is returned when an attempt is made to perform a fix pack update but the cluster manager cannot exit maintenance mode.

Manually remove the cluster manager from maintenance mode, and then perform the fix pack update again, specifying the -f level parameter.

DBI1581E

After making updates to GPFS, you can exit maintenance mode to remove a host from maintenance mode and put the domain online.

This message is returned when an attempt is made to perform a fix pack update but GPFS cannot exit maintenance mode.

Manually remove GPFS from maintenance mode, and then perform the fix pack update again, specifying the -f level parameter.

DBI1582E

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

This message is returned when an online fix pack update is performed on an instance with a type different than a DB2 pureScale instance.

Perform an offline fix pack update on the specified instance.

DBI1583E

You can specify a list of instances to update with the -I parameter of the installFixPack command. All the instances in the list have to be either pureScale instances or other types that are not pureScale instances. A list that includes pureScale instances and other types that are not pureScale instances is not supported.

This message is returned when -I parameter of the installFixPack command was specified with a list of instances that includes pureScale instances and other types that are not pureScale instances.

To respond to this message perform one of the following actions or both:

• Issue the installFixPack command with one pureScale instance name.
• Issue the installFixPack command with a list of other type of instances that are not pureScale instances.

DBI1584E

You can specify a list of instances to update with the -I parameter of the installFixPack command. All the instances in the list must have the same installation path. A list of instances that have different installation paths is not supported.

This message is returned when -I parameter of the installFixPack command was specified with a list of instances that have different installation paths.

To respond to this message, issue the installFixPack command with a list instances that have the same installation path.

DBI1585E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online.

A fix pack update has several steps. The commit is the final step that completes the fix pack update. The cluster manager update is committed during the commit.

This message is returned when the commit of the fix pack update cannot commit the cluster manager update.

1. Manually commit the cluster manager update by running the following command:

    db2cluster -cm -commit 

2. Commit the fix pack update by running the following command:

    installFixPack -commit_level -I <instance-name> 

DBI1586E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online.

An fix pack update has several steps. The commit is the final step that completes the fix pack update. The GPFS update is committed during the commit.

This message is returned when the commit of the fix pack update cannot commit the GPFS update.

1. Manually commit the cluster manager update by running the following command:

    db2cluster -cfs -commit 

2. Commit the fix pack update by running the following command:

    installFixPack -commit_level -I <instance-name> 

DBI1587E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online.

A fix pack update has several steps. The commit is the final step that completes the fix pack update. The CECL and CEAL update is committed during the commit.

This message is returned when the commit of the fix pack update cannot commit the CECL and CEAL update.

1. Troubleshoot the cause of the problem by running the installFixPack command with the -check_commit parameter.
2. Resolve the underlying cause of the problem.
3. Run the installFixPack command again with the -commit_level parameter.

DBI1588E

You can update the version of DB2 pureScale instance to a higher code level by using an online fix pack update to keep databases online. During the online fix pack update, the instance is restarted to perform the update.

This message is returned when an attempt to restart the instance on the DB2 member or CF that is being updated fails.

1. Start the instance on the DB2 member or CF by issuing the following command:

    db2start INSTANCE ON <host-name> 

2. Start any DB2 members and CFs on the host machine as well.

DBI1589E

You can update the version of DB2 pureScale instance to a higher code level by using an online fix pack update to keep databases online. During the online fix pack update, the DB2 member or CF is restarted to perform the update.

This message is returned when an attempt to restart the DB2 member or CF that is being updated fails.

Manually restart the DB2 member or CF.

• To restart a DB2 member, issue the following command:

  db2start member member-id 

• To restart a CF, issue the following command:

  db2start CF CF-id 

DBI1590E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online. During the fix pack update, the database software components are updated.

This message is returned when an attempt to update the DB2 software fails.

Complete the fix pack update by performing the following steps:

• Identify the underlying cause of the problem by reviewing the error messages in the log file.
• Resolve the underlying cause of the problem.
• Re-issue the fix pack update command.

DBI1591E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online. During the fix pack update, the following software components are updated:

• IBM Tivoli System Automation for Multiplatforms (SA MP)
• IBM General Parallel File System (GPFS)

This message is returned when an attempt to update the software for SA MP or GPFS fails.

To respond to this message, perform one of the following actions:

• Complete the fix pack update by performing the following steps:
  • Check error message in the log file and perform the corrective action.
  • Perform again the fix pack update operation.
• Cancel the fixpack update by issuing the installFixPack command with the -f level parameter from the install directory of the previous fix pack release.

DBI1592E

You can update the version of DB2 pureScale instance to a higher code level by using offline fix pack updates or online fix pack updates to keep databases online. During the fix pack update, the existing instance configuration is updated.

This message is returned when an attempt to update the instance configuration fails.

To complete the online fix pack update, perform the following actions:

• Check the log file and perform a corrective action.
• Start the instance on the local host by issuing the following command:

  db2start INSTANCE ON host-name 

• Start the DB2 member or CF by issuing one of the following commands:

  db2start member member-id 

  or

  db2start CF CF-id 

To complete the offline fix pack update, perform the following actions:

• Check the log file and perform a corrective action.
• Perform again the fix pack update operation.

To cancel the fix pack update, issue the installFixPack command with -f level parameter from the install directory of the previous fix pack release.

DBI1593E

During an instance creation or upgrade changes to the instance configuration are committed to complete the command.

This message is returned when committing the instance configuration changes during an instance creation or upgrade fails.

Manually commit the instance configuration changes by issuing the following commands:

 db2iupdt -commit_new_level <instance-name> db2start INSTANCE ON <instance-name> 

DBI1594E

You can install and configure a DB2 pureScale instance without having to enable passwordless SSH by running the setup_db2locssh command before performing the install or configuration operation.

This message is returned when the setup_db2locssh command is invoked with invalid or missing parameters.

Enter the command again specifying only valid parameters.

DBI1595E

You can install and configure a DB2 pureScale instance without having to enable passwordless SSH by running the setup_db2locssh command before performing the install or configuration operation.

This message is returned when the setup_db2locssh command fails with an unexpected error.

The reason code in the runtime token is an error number that can assist IBM support personnel to troubleshoot the cause of the error. The runtime token might sometimes be empty.

Contact IBM support for assistance.

DBI1596W

In DB2 pureScale environments, the non-root user ID (sometimes referred to as "db2sshid") is used to establish a secure shell (SSH) network protocol between host machines.

You perform install, upgrade, or configuration tasks by using commands such as db2icrt or db2iupdt. When you call one of these commands you can configure a new non-root user ID by specifying the proposed user ID with the -i parameter.

This message is returned when a command such as db2icrt or db2iupdt is called and the -i parameter is specified with a proposed user ID, but the utility detects that a non-root user ID already exists on the system. Because there may exist only one non-root user ID on a given system at a time, the utility uses the existing non-root user ID instead of configuring a new one.

No response is required.

DBI1597I

You can install and configure a DB2 pureScale instance without having to enable passwordless SSH by running the setup_db2locssh command before performing the install or configuration operation. Running the setup_db2locssh command enables database manager processes to communicate between host machines without using passwordless SSH.

Utilities such as db2icrt and db2iupdt will communicate without using passwordless SSH, if the capability to do so has been configured. This message is printed when a utility must use passwordless SSH because the capability to communicate without using passwordless SSH has not been configured.

No response is required.

DBI1600E

DBI1601W

DBI1631E

DBI1632E

One of the following situations has occurred:

• The feature to "auto-start" the instance is already enabled.
• An error was encountered while adding an entry to "/etc/inittab" file. This could be a file permission problem.
• The db2uit tool is missing.

If any of these three situations apply, then correct the problem and retry the command. If the problem persists, contact IBM Support with the following information:

• Message number
• Problem description

DBI1633E

One of the following situations has occurred:

• The feature to "auto-start" the instance is not enabled.
• An error was encountered while removing an entry to "/etc/inittab" file. This could be a file permission problem.
• The db2uit tool is missing.

If any of those three situations apply, then correct the problem and retry the command. If the problem persists, contact IBM Support with the following information:

• Message number
• Problem description

DBI1634W

An attempt to update /etc/rc.db2v08 to enable the auto-mounting of the dlfs file system on system reboot has failed.

Manually edit the file /etc/rc.db2v08, and add the following lines to it: if [ -x /etc/rc.dlfs ]; then /etc/rc.dlfs fi

DBI1635E

An error was detected when attempting to add a database manager instance to the Administration Server group list.

If you are running this command on an NIS client, try to append the group name of the database manager instance to the secondary group of the Adminstration Server on your NIS server.

DBI1637W

Click OK if you wish to proceed. Otherwise click Cancel.

DBI1639E

The given instance name does not belong to an existing instance.

DBI1640W

Some of the DB2 components can only be configured for database server instances.

DBI1651E

Retry with a different user ID.

DBI1652E

Retry with a different user name.

DBI1653E

Retry with a different group ID or group name.

DBI1654E

Retry with the user's home directory specified on the system or a different directory.

DBI1655E

Retry with a different password.

DBI1657E

An instance with the same name already exists on your system.

Verify with the list of instances as reported by the "db2ilist" command. Retry with a different user name.

DBI1701E

Correct the problem and try again.

DBI1702E

The service name or port number conflicts with existing values in the services file. The service name might already be used with a different port number, or the port number might already be used with a different service name.

Specify a service name and port number that does not conflict with existing entries in the services file.

DBI1703E

No valid service name or port number for this instance can be found in the TCP/IP services file. This information is either missing or is invalid.

If you installed "DB2 Extended Server Edition" product, a service name must be specified for the instance before using this command.

Specify valid service name and port number for this instance and enter this command again.

DBI1704W

TCP/IP is not running on your system. TCP/IP services file will not be updated.

DBI1705E

The port number specified cannot be used because it is being used by another application that is currently running.

Specify another port number that is not in use. The port number must be in the range 1024 to 65535.

DBI1709E

An attempt to add a service name and port number to the TCP/IP services file failed.

If the user wishes to use the service name instead of the port number in the node directory entry, the node must be manually uncataloged and then recataloged using the service name. The services file must also be updated manually. If Network Information Services (NIS) is being used, the local services file may have been updated but the NIS server must be updated manually. In this case, the node was also cataloged using the port number.

DBI1711E

Correct the problem and try again.

DBI1715E

The NetWare User ID and NetWare Password that you specify must already exist and is used to register the DB2 Object Name at a NetWare file server and must have supervisory or equivalent authority.

Correct the problem and try again.

DBI1720E

NIS is running on your system. A new User ID or Group ID cannot be created while you have NIS running on your system.

Use a previously created User ID or Group ID and try again.

DBI1722E

NIS is running on your system. A new service cannot be added to the /etc/services file while you have NIS running on your system.

Use a previously created service name and port number from the /etc/services file and try again.

DBI1725W

TCP/IP is not running on the system. The install will proceed but you need to create Agent Daemon and Logger services manually.

Activate TCP/IP on the system and run the installer.

DBI1740W

Using the default instance user ID here allows this instance to have full access permission to other instances on your system. It is highly recommended to use a different user ID for security reasons.

To avoid the possibility of a security risk, use a different user ID.

DBI1741W

You have selected a protocol that is not detected. The database product installer cannot update all of the protocol's required settings. However, you can provide values for this protocol's settings.

No actions required.

DBI1744W

You have not created the DB2 Data Links Manager Administrator. Without the DB2 Data Links Manager Administrator, you cannot administer the DB2 Data Links Manager.

No actions required.

DBI1745W

You have not created a Administration Server. Without the Administration Server, you cannot provide services to support client tools that automate the configuration of connections to databases, and cannot administer databases from your server system or a remote client.

No actions required.

DBI1746W

You have not created a database manager instance. An instance is an environment where you store data and run applications.

No actions required.

DBI1747W

The directory specified in the Home Directory field already exists. If you choose to use this directory you may run into permission problems.

Choose a different directory if this may be a problem.

DBI1750W

Using the default instance user ID here allows this instance to have full access permission to other instances on your system. It is highly recommended to use a different user ID for security reasons.

DBI1751W

You have selected a protocol that is not detected. The database product installer cannot update all of the protocol's required settings. However, you can provide values for this protocol's settings.

DBI1753W

You have not created an Administration Server. Without the DB2 Administration Server, Data Warehouse Agent will not be fully set up.

DBI1754W

You have not created the DB2 Data Links Manager Administrator. Without the DB2 Data Links Manager Administrator, you cannot administer the DB2 Data Links Manager.

DBI1755W

You have not created a Administration Server. Without the Administration Server, you cannot provide services to support client tools that automate the configuration of connections to databases, and cannot administer DB2 from your server system or a remote client.

• Press OK to continue, or
• Press Cancel to go back.

DBI1756W

You have not created a database manager instance. An instance is an environment where you store data and run applications.

DBI1757W

The directory specified in the Home Directory field already exists. If you choose to use this directory you may run into permission problems.

DBI1758W

You have selected to removed the entire database product. However, a database manager instance or Administration Server has been detected on your system. If you remove the database product without dropping these instances first, your instances might not be able to function properly later on.

DBI1759W

You do not have the Administration Server selected. This will cause all of your Administration Server and database manager instance configurations to be discarded.

DBI1760E

You have chosen to configure a DB2 component for an instance. You will not be able to do so unless the package is installed.

Install the package and try again.

DBI1761W

An error occurred when verifying software prerequisites on the indicated file set or package. Continuing may result in the product not functioning properly. Do you want to continue without installing its pre-requisites?

• Press OK to continue without installing its prerequisites, or
• Press Cancel to abort installation.

DBI1762W

An error occurred when verifying software dependencies on the indicated file set or package. Continuing may result in removing all of its software dependencies. Do you want to remove its software dependencies?

• Press OK to continue, or
• Press Cancel to go back.

DBI1763I

The English HTML documentation files are required when you select any non-English HTML documentation files for installation. This is to ensure that users will be able to search the entire documentation library.

DBI1765W

The registry is containing a non-existing user ID. This can be caused by just removing the instance user ID without first dropping the instance. This will not affect the normal operation of DB2, but it is recommended to remove this obsolete user ID from the instance list in the registry.

To remove this user ID from the registry with the command: db2iset -d "<InstName>"

DBI1766W

An error code was returned when attempting to change the secondary group list of the given user ID. One of the following situations has occurred:

• NIS is running.
• One or more processes are currently being executed under the given user ID.

Add the given group ID to the secondary group list of the user ID so that the Administration Server can function properly.

• If there happens to be any process run under the given user ID, terminate all of these processes and follow the instructions in this message to set up the secondary group list of this user ID.
• If you are running this command on an NIS client, try the instructions to set up the secondary group list of this user ID on your NIS server.

DBI1767W

The registry may contain invalid instance information. This is probably due to the fact that an instance or the Administration Server is not deleted properly before removing the database product. If you are re-installing the product and want to keep the existing instance information in the registry, press Cancel. Otherwise, press OK to re-create the registry. Do you want to re-create the registry?

DBI1768W

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.

Respond in one of the following ways:

• Add the profile to the .profile file
• Add the location of db2cshrc to the .profile file

DBI1769W

If you receive a message concerning missing db2profile or db2chsrc, locate your .profile or .login file and comment out the following: . sqllib/db2profile from your .profile file source sqllib/db2cshrc from your .login file

DBI1770E

The following DB2 Data Links Manager specific entry is required in the /etc/vfs file: dlfs dlfs_num /sbin/helpers/dlfs_mnthelp none

Manually edit the /etc/vfs file, and add the entry for dlfs into this file.

DBI1771I

For DB2 Data Links Manager to work, the following line has to be inserted into the /etc/vfs file: dlfs dlfs_num /sbin/helpers/dlfs_mnthelp none

A backup copy of the original /etc/vfs file has been placed in /tmp/.db2.etcvfs.backup.

DBI1775W

The database manager has modified an existing /etc/rc.dlfs file with the new dlfs file system mount entry.

Examine the file /etc/rc.dlfs to ensure that all entries are correct.

DBI1780W

DBI1782E

You must specify at least one language from those available.

Issue the command with no parameters for a complete list.

DBI1783E

You must specify at least one topic from those available.

Issue the command with no parameters for a complete list.

DBI1784E

You specified a language that is not available for installation.

Issue the command with no parameters for a complete list.

DBI1785E

You specified a documentation package that is not available for installation.

Issue the command with no parameters for a complete list.

DBI1790E

ODSSI utilities have not been installed. These utilities (config_search, config_view and config_help) are required to create the search index for the DB2 online documentation.

Install the ODSSI utilities, then run the following commands: /opt/IBM/db2/V8.x/doc/db2insthtml lang_locale, where x is 1 or FPn, where n is the FixPak number

to create the search index for documentation in the language locale lang_locale. Note that whenever you install documentation in any language, English documentation is installed as well. So you should also run the following command to index the English files: /opt/IBM/db2/V8.x/doc/db2insthtml en_US, where x is 1 or FPn, where n is the FixPak number

DBI1791W

DB2 runs the system utilities config_view and config_help to create or remove DB2 search index to be used with SCOHELP. However, error messages may be returned if there exists other non-DB2 indexes on the system that have not been created/removed properly.

DBI1792I

Search index for documentation files are being created. Depending on the language(s) you have selected, this may take some time.

DBI1793W

The specified user is unknown or cannot be found on the current system.

Please verify that the user exists on this system and try again.

DBI1794E

An attempt has been made to place more icons into the required folder than are allowed by the desktop manager.

Please remove any unnecessary icons from your desktop and retry the command.

DBI1795E

The icon creation utility ran out of memory during icon generation.

Close any unnecessary programs and try again.

DBI1796W

This user ID does not have the permissions required to create icons for the requested user.

Log on as a user with root authority or with the permissions required to create files in the user directory and retry the command.

DBI1797I

DBI1900N

The database manager is unable to access the Microsoft Cluster Server (MSCS) cluster.

Ensure the Microsoft Cluster Server (MSCS) support has been correctly installed and the Cluster Service has been started.

DBI1901N

An error was encountered when attempting to grant the necessary user rights to the account specified for use with the DB2 service.

Ensure a valid account has been specified and that you have the necessary privilege to grant user rights.

DBI1902N

The database manager encountered an error when attempting to update the DB2 or Microsoft Cluster Server (MSCS) cluster service configuration.

Ensure the Service Database has not been locked and is accessible. Also ensure the DB2 or Microsoft Cluster Server (MSCS) cluster service has been created.

DBI1903N

The database manager encountered an error when attempting to read or update the Cluster registry.

Ensure the Microsoft Cluster Server (MSCS) support has been correctly installed and the Cluster Service has been started. Ensure that the current logon user account has sufficient authority to access the Cluster registry.

DBI1904N

The database manager attempted to access an instance to perform cluster operations but the instance was not identified as a DB2 Cluster instance.

Verify the instance was created with the Cluster options. The instance may be dropped and re-created using the Cluster option but the Node directory, Database Directory, and Database Manager Configuration file will be lost.

DBI1905N

A system error was detected while the database manager was performing a Cluster operation.

Check to make sure the Windows operating system is at the correct level for Cluster Support.

Also ensure the Microsoft Cluster Server (MSCS) support has been correctly installed and the Cluster Service has been started.

DBI1906N

An error was encountered while attempting to update a node to support a DB2 Cluster instance.

Ensure the remote system is on-line and accessible over the LAN. Also ensure you have the necessary privilege to update the Registry on the remote system.

DBI1907N

An error was encountered while attempting to delete a node from a DB2 Cluster instance.

Ensure the remote system is on-line and accessible over the LAN. Also ensure you have the necessary privilege to update the Registry on the remote system.

A workstation cannot drop cluster support from itself. The instance must be dropped to perform this task.

DBI1908N

A error was detected while attempting to create the instance profile on a remote system to enable Cluster Support.

Ensure the remote system is on-line and accessible over the LAN. Also ensure you have the necessary privilege to update the Registry on the remote system.

DBI1909N

A error was detected while attempting to delete the instance profile on a remote system to disable Cluster Support.

Ensure the remote system is on-line and accessible over the LAN. Also ensure you have the necessary privilege to update the Registry on the remote system.

DBI1910N

The user specified incorrect arguments to the DB2NCRT command.

Re-issue the command specifying a clustered instance and a valid workstation name for the cluster node.

DBI1911N

The user specified incorrect arguments to the DB2NLIST command.

Re-issue the command specifying a clustered instance.

DBI1912I

The user request was successfully processed.

No action required.

DBI1913N

The database manager encountered an error when attempting to connect to the Windows registry on a remote machine.

Ensure that the target machine is running and that the computer name specified is correct. Also ensure that the current logon user account has sufficient authority to connect to the remote machine registry.

DBI1914N

The database manager encountered an error when attempting to connect to the Cluster registry.

Ensure that the Microsoft Cluster Server (MSCS) support has been correctly installed and the Cluster Service has been started.

DBI1915N

The command failed for one of the following reasons:

(1)

The db2iclus utility attempted to remove a machine from a DB2 MSCS instance but the target machine had not been added to the DB2 MSCS instance, or

(2)

The db2iclus utility attempted to add a machine to a DB2 MSCS instance but the target machine does not have the required Microsoft Cluster Server (MSCS) support software installed.

Follow the action corresponding to the cause of the problem:

(1)

Ensure that the machine is part of the DB2 MSCS instance by running the "db2iclus list" command, or

(2)

Install the Microsoft Cluster Server (MSCS) cluster software on the target machine and issue the command again.

DBI1916N

The instance specified by the instance name parameter does not exist for the local machine.

To find a list of valid instances, run the db2ilist command. Issue the command again using a valid instance name.

DBI1917I

The instance upgrade or instance update is not able to determine which ODBC data sources are associated with the instance that was upgraded or removed. As a result, these data sources were not modified.

Reconfigure the data sources using the DB2 CATALOG ODBC DATA SOURCE command, the Configuration Assistant or the Data Sources (ODBC) control panel applet so you can access these data sources.

DBI1918N

The database manager encountered an error when attempting to read or update the Windows registry of the target machine.

Ensure that the current logon user account has sufficient authority to access the Windows registry of the target machine. If you already have a clustered instance, ensure the cluster service is started. If the problem persists, contact your IBM service representative for assistance.

DBI1919N

The database manager encountered an error when reading or updating the TCP/IP services file.

Ensure that the services file exists in the system and that the file can be accessed for read and write authority. Also, ensure that the contents of the file are valid and no duplicate of entries exist in the services file.

DBI1920N

The database manager is unable to access the database manager instance profile path specified because the path does not exists or write access has not been given to the current logon user account.

Ensure that the path name for the database manager instance profile points to a valid directory and that the current logon user account has write access to the directory.

DBI1921N

The user account or the password is not valid.

Issue the command again with the correct account.

DBI1922N

The TCP/IP host name parameter is not valid or does not exist.

Ensure that TCP/IP is operational on the system. If a domain name server is used, ensure that the domain name server machine is active. Issue the command again using the correct TCP/IP host name.

DBI1923N

The db2icrt utility requires the TCP/IP port range to be specified when creating a partitioned database instance if the entries for TCP/IP port range for the instance have not been added to the services file.

Choose a range of TCP/IP ports that are available for the system and issue the db2icrt command again with the -r option.

DBI1924N

The computer name parameter is not valid

Ensure that the target machine is running and that the computer name specified is correct. Also ensure that the current logon user account has sufficient authority to connect to the target machine registry.

DBI1925N

The database manager is unable to query the service status.

Ensure that the database manager service exists on the target machine. Ensure that the current logon user account has sufficient authority to query the service status on the target machine.

DBI1926N

The account password has expired.

Change your password, then retry the request using the new password.

DBI1927N

Enter the command again using valid parameters

DBI1928N

When creating a partitioned database instance or adding a node to a partitioned database instance, you must specify the user account parameter. Under the Windows environment, each database manager partition (or MPP node) is required to run under a valid Windows account to access the network share which contains the instance directory.

Issue the command again with the -u option to specify the user account name and password.

DBI1929N

An attempt to upgrade an instance into an MSCS instance failed because the instance is already configured for MSCS support.

No action required.

DBI1930N

An attempt to add an MSCS node to the DB2 MSCS instance failed because The target machine is already part of the DB2 MSCS instance.

No action is necessary.

DBI1931N

The database partition server can not be dropped or modified because it is active.

Ensure that the database partition server is stopped before attempting to drop or change it. To stop a database partition server, use the db2stop command as follows:

        db2stop dbpartitionnum <db-partition-number> 

DBI1932N

The db2ncrt command failed to add a new database partition server on a remote machine because there is an existing instance on the remote machine.

If the instance on the remote machine is no longer used, remove the instance by running the db2idrop command on the remote machine.

DBI1933N

When the db2nchg command is issued with the /m:machine option, the command will move the database partition server to a new machine. The db2nchg will fail if there is existing database(s) in the system.

To move the database partition server to a new machine when there is database(s), use the db2start restart command. For more information on the db2start command, refer to the DB2 Command Reference.

DBI1934N

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

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

Enter the command again using valid arguments.

DBI1935N

Ensure that the db2audit.cfg file exists in the \SQLLIB\CFG directory and that the current logon account has sufficient authority to create files and directories in the instance directory. The instance directory is located in \SQLLIB\InstName (where InstName is the name of the instance).

DBI1936N

The db2iupdt command failed to update the database manager configuration file because the previous database manager configuration file is corrupted or missing. The current instance is in inconsistent state and can not be used.

Copy the default database manager configuration file to the instance directory then re-submit the command. The instance directory is located in \SQLLIB\InstName. The default database manager configuration file is named db2systm and can be found in the \sqllib\cfg directory.

DBI1937W

The db2nodes.cfg file is not updated to include the new node until all nodes are simultaneously stopped by the STOP DATABASE MANAGER (db2stop) command. Until the file is updated, the existing nodes cannot communicate with the new node.

Issue db2stop to stop all the nodes. When all nodes are successfully stopped, issue db2start to start all the nodes, including the new node.

DBI1940N

The DB2 Administration Server cannot be modified because it is active.

Ensure that the DB2 Administration Server is stopped before attempting to change it. To stop the DB2 Administration Server, use the db2admin command as follows: db2admin stop

DBI1941W

The DB2 Administration Server was not found on the machine.

Create the DB2 Administration Server on the machine.

DBI1942N

The operation could not be completed because the DB2 Administration Server already exists on the target machine.

Remove the DB2 Administration Server from the target machine and retry the operation.

DBI1943N

The database manager attempted to access a DB2 Administration Server to perform cluster operations but the DB2 Administration server is not configured for MSCS support.

Verify the DB2 Administration Server is configured for MSCS support.

DBI1944N

An attempt to upgrade a DB2 Administration Server failed because the DB2 Administration Server is already configured for MSCS support.

No action required.

DBI1945N

To update or upgrade an instance to a specific DB2 copy, the DB2 copy must exist. The DB2 Copy Name provided does not exist or the DB2 registry is corrupted.

Check the DB2 registry table and provide a valid DB2 Copy Name. For a list of the DB2 copies installed, run the db2ls command.

DBI1946N

You can upgrade a database manager instance from one release to a later release by using the db2iupgrade command.

This message is returned when the db2iupgrade command is invoked with an invalid argument.

Enter the command again, specifying valid parameters.

DBI1947N

The db2iupgrade command failed to update the database manager configuration file because the previous database manager configuration file is corrupted or missing. The current instance is in an inconsistent state and cannot be used.

Copy the default database manager configuration file to the instance directory, then re-submit the command. The instance directory is located in \SQLLIB\instanceName. The default database manager configuration file is named db2systm and can be found in the cfg directory under your installation path.

DBI1948N

An error occurred when removing files or directories belonging to the specified instance.

Ensure that you have write access to the location where the files are located.

DBI1949E

The instance cannot be upgraded because either:

• Upgrading from this version of the instance is not supported.
• The instance is already using the current version of the product and upgrading is not required.

Make sure that the instance version is supported for upgrade and try the command again with a supported instance name or a valid DB2 Copy Name.

DBI1950W

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

Verify that the list of instances as reported by the db2ilist command is correct.

DBI1951W

The specified instance was not found in the instance list.

Verify that the list of instances as reported by the db2ilist command is correct.

DBI1952E

The instance name is invalid because of one of the following reasons:

1. The name is more than 8 characters long.
2. The name starts with sql, ibm, or sys.
3. The name contains characters other than a-z, $, #, @, _, or 0-9.
4. The name does not exist.

Try the command again with a valid instance name.

DBI1953E

You can update a database manager instance to a higher level by using the db2iupdt command. You can remove an instance by using the db2idrop command.

Before you can update or drop an instance, all processes that are running for the instance must be stopped. This message is returned when an attempt is made to update or drop an instance that is active.

1. Wait for all applications that are using the instance to finish processing.
2. Stop the instance by using the db2stop command from the instance user ID.
3. Issue the db2idrop or db2iupdt command again.

DBI1954E

The instance cannot be created because it is currently used by the DB2 Admin Server.

Try the command again with a different instance name.

DBI1956I

The db2ilist command lists the names of database manager instances associated with the database product installation path where db2ilist is run.

The syntax for the db2ilist command is:

 db2ilist [-h]          [-g <Instname>]          [-d] 

Valid arguments for this command are:

-h

Displays the usage information.

-g <Instname>

Displays the instance name and attributes of the instance, separated by a colon. If no instance name is provided, lists all root-based registered instances for all copies of Db2.

-d

Enable debug mode. For use with the assistance of IBM software support.

Enter the command again without any parameters.

DBI1957E

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

This message is returned when an invalid parameter or parameter value is specified with the db2icrt command.

Enter the command again using the valid parameters.

DBI1958N

An error occurred when adding the instance profile to the registry. The instance was not created.

Contact your IBM service representative.

DBI1959N

An error occurred when creating the required files or directories for the new instance. The instance was not created.

Ensure that you have write access to the location where the instance directory is created. The instance directory is created under the path where the product is installed. You can move the instance to another directory by using the /p option in db2iupgrade.

DBI1960N

DBI1961N

An error occurred when adding a node key for the new instance in the instance profile registry.

Contact your IBM service representative.

DBI1962N

An error occurred when adding the new node to the instance profile registry.

Contact your IBM service representative.

DBI1963N

When configuring the account for the DB2 Service, the account must be granted the user rights:

1. Act as part of the operating system
2. Create a token object
3. Increase quota
4. Logon as a service
5. Replace a process level token

An error occurred when granting the user rights to the account for the instance.

If the machine belongs to a domain, ensure that the primary domain controller is active and accessible over the network. Otherwise, contact your IBM service representative.

DBI1964N

An error occurred when assigning a logon account to the DB2 service.

Ensure user that the user name and the password for the logon account is valid.

DBI1965N

The specified node was not found in the node list.

Verify that the node exists by displaying the list of nodes using the DB2NLIST command.

DBI1966N

An error occurred when removing the specified node from the instance profile registry.

Contact your IBM service representative.

DBI1967N

An error occurred when de-registering a DB2 service.

Ensure that you have sufficient authority to delete a Windows service.

DBI1968N

An error occurred when changing the node configuration in the profile registry.

Contact your IBM service representative.

DBI1969N

An internal error occurred when creating a new file in the instance directory.

Ensure that you have write access to the instance directory.

DBI1970N

An internal error occurred when reading from or writing to a file in the instance directory.

Contact your IBM service representative.

DBI1971N

An error occurred when removing the instance profile from the registry.

Contact your IBM service representative.

DBI1972N

An error occurred when removing the required files or directories belonging to the specified instance.

Ensure that you have write access to the location where the instance directory is located.

DBI1973N

An error occurred when setting the DB2 service to start automatically.

Reboot the machine and try the command again. If the problem persists, contact your IBM service representative.

DBI1974N

An error occurred when setting the profile variable DB2ADMINSERVER in the profile registry.

Contact your IBM service representative.

DBI1975N

An error occurred when removing the environment variable DB2ADMINSERVER in the profile registry.

Contact your IBM service representative.

DBI1978E

When you have multiple DB2 copies installed, you can update an instance that is currently running on one DB2 copy to run on a different DB2 copy by using the db2iupdt command. However, you can only update an instance from one DB2 copy to another if both copies are at the same release.

This message is returned when an attempt is made to update an instance that is currently running on one DB2 copy, copy1, to run on a different DB2 copy, copy2, and copy1 and copy2 are not at the same product release.

To upgrade the instance to a different product release, invoke the db2iupgrade command.

To update the instance to run on a different DB2 copy, specify a DB2 copy that is at the same release as the DB2 copy on which the instance is running.

DBI1980W

The user ID that you provided during product installation could not be created in User Profile Management (UPM). This user ID is required to start the DB2 Administration Server.

Manually create a user ID and password using UPM and then manually start the DB2 Administration Server. You may need to set the DB2 Administration Server to use this user ID and password combination using the db2admin command.

DBI1981E

The instance is still active.

Ensure that you stop the instance and rerun the command.

DBI1982E

The member is still active.

Ensure that the member is stopped and rerun the command.

DBI1983E

The secondary CF is not in peer state.

Ensure that the secondary CF is in peer state and rerun the command.

DBI1984I

Valid arguments for this command are:

-h|-?

Displays help information.

-i

Install Db2 resource agent scripts for Pacemaker in /usr/lib/ocf/resource.d/heartbeat.

-r

Removes the directory /usr/lib/ocf/resource.d/heartbeat. The heartbeat directory contains the Db2 resource agent scripts for the Pacemaker cluster manager.

This utility installs or updates the Db2 resource agent scripts in /usr/lib/ocf/resource.d/heartbeat. These Db2 resource agent scripts are used by the Pacemaker cluster manager with the Db2 HA feature.

By default, this utility installs the Db2 resource agent scripts in /usr/lib/ocf/resource.d/heartbeat. If they are not already installed there, this utility installs or updates the Db2 resource agent scripts only if the Pacemaker software packages are already installed.

This command must be run with root authority.

Reenter the command.

DBI1985E

The Db2 resource agent scripts are used by the Pacemaker cluster manager with the Db2 HA feature.

These Db2 resource agent scripts are located at /usr/lib/ocf/resource.d/heartbeat. The database product installer detects whether these Db2 resource agent scripts need to be installed or updated.

The database product installer failed to install or update the Db2 resource agent scripts.

Use the command db2cppcmk to manually install or update these scripts.

DBI1986I

The Db2 resource agent scripts are used by the Pacemaker cluster manager with the Db2 HA feature.

These Db2 resource agent scripts are located at /usr/lib/ocf/resource.d/heartbeat. The database product installer detects whether these Db2 resource agent scripts need to be installed or updated.

No action is required.

DBI1987I

The syntax for the db2ckpcmk command is:

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

Enter the command again using valid parameters.