Frequently asked questions about post-installation problems

Use the answers in this list of frequently asked questions to help you resolve problems that arise after the installation of the IBM® Db2 pureScale Feature.

What if my members or cluster caching facilities are not in STARTED, PEER, or CATCHUP state?

If one of your members or cluster caching facilities is not in the STARTED, PEER, or CATCHUP state, perform the following steps:
  1. Stop the instance by issuing the db2stop command.
  2. Restart the instance by issuing the db2start command.
  3. Review the messages from the failed db2start command, and resolve the problem.
  4. If the problem persists, review the db2diag log file, which might have more details about the problem.
  5. If reviewing the file does not yield a probable cause of the problem, perform the following steps:
    1. Drop the member or cluster caching facility by issuing the db2iupdt -drop command.
    2. Add the member or cluster caching facility again by issuing the db2iupdt -add command.

What if the db2start command fails with SQL1517N?

This error indicates that there are inconsistencies between the db2nodes.cfg file and the cluster manager. See the "Repairing the cluster manager resource model" topic for more details on how to repair the cluster manager resource model.

What if I can't create my database?

If you attempted to create a database using the create database command and received an SQL1032N error (No START DATABASE MANAGER command was issued). Ensure that you are logged on to a host that is acting as a Db2 member. You cannot create a database on a host that is acting as a cluster caching facility. Log onto a Db2 member and issue the CREATE DATABASE command again.

What if the db2iupdt -drop command failed to shrink the RSCT peer domain?

To manually remove failed hosts from the RSCT peer domain:
  1. Check whether there are still resources attached to the peer domain by logging on to the failed host as the root user and issuing the lssam command.1 The lssam command shows all resources in the domain, not just those on a particular host. Review the listing to ensure that the host that you are attempting to drop does not have any resources attached.
  2. If no resources are attached, from the installation-initiating host (IIH), enter db2cluster -cm -remove -host host_name .
  3. If there are still resources attached, perform the following steps:
    1. From the IIH, switch to the instance owner by entering su - instance_owner .
    2. Remove the resource by entering db2cluster -cm -delete -resources. This step deletes all resources in the cluster.
    3. Switch back to root.
    4. Remove the failed hosts from the RSCT peer domain by entering db2cluster -cm -remove -host host_name.
    5. Switch to the instance owner again.
    6. Re-create the resources on the hosts that did not fail by entering db2cluster -cm -create -resources.
    7. Switch back to root.
1 For more information on Tivoli® SA MP commands, see this link.