Frequently asked questions about uninstallation problems with the DB2 pureScale Feature

What if the db2idrop command failed to remove the host from the GPFS cluster?

To help determine the cause of the failure, review the db2cluster command log file in the DB2DIR/tmp/ibm.db2.cluster.* directory. After resolving the problem, reissue the db2idrop command.

What if the db2idrop command failed because the instance is not usable?

To help determine the cause of the failure, review the db2idrop command log in the DB2DIR/tmp directory. Check if instance_user/sqllib/db2nodes.cfg is valid.

What if the db2idrop command failed when removing the GPFS CLUSTER global registry (or the PEER DOMAIN global registry) on specific hosts?

If this failure occurs, contact IBM Software Support.

What if the db2idrop command failed to remove the RSCT peer domain?

If the db2idrop command failed to remove the RSCT peer domain, you will have to manually remove it by following these steps:

1. Check if there is still resource attached to the peer domain by running the lssam command.¹
2. If there are still resources attached, perform the following steps:
   1. Switch to the instance owner by entering su - instance_owner.
   2. Remove the resource by entering db2cluster -cm -delete -resources.
   3. Switch back to root.
3. Remove RSCT peer domain by running the db2cluster -cm -delete -domain domain_name command from the DB2DIR/bin directory. Run the lsrpdomain command to determine the domain name to specify.

For more information, see Manually cleaning up an IBM Reliable Scalable Cluster Technology peer domain.

What if the db2_deinstall command failed?

The db2_deinstall command can uninstall DB2 database products, features, or languages on the host where the db2_deinstall command is run. The db2_deinstall command might fail because the host is still part of the GPFS™ cluster or the host still belongs to the RSCT peer domain. If the host is still part of the GPFS cluster, run the db2_deinstall -s GPFS command to remove it.

If there still exists a DB2 pureScale instance, you can use the db2iupdt -drop or db2idrop -g command to remove the DB2 pureScale instance. Then rerun the db2_deinstall command.

If you want to keep the peer domain, you can bypass the IBM Tivoli System Automation for Multiplatforms binary file removal by running the db2_deinstall -a -s TSAMP. If there are no resources using the peer domain on this host, before reissuing the command, manually remove the Tivoli SA MP.