Frequently asked questions about installation, instance creation, and rollback problems with the Db2 pureScale Feature

Use the answers in this list of frequently asked questions to help you provide possible solutions to problems that might arise during the installation process of the IBM® Db2 pureScale Feature.

Ensure that you issue any installation or creation commands with the debug (-d) parameter to generate the trace file which will assist in any debugging attempts.

Where can I find the installation log files?

The most important source of information for troubleshooting installation problems are the installation log files. The Db2 setup log file, db2setup.log by default, captures all Db2 installation information including errors. The Db2 error log file, db2setup.err, captures any error output that is returned by Java™ applications (for example, exceptions and trap information).

By default, the log files are located in the DB2DIR/tmp directory. You might have overridden this default when you issue the db2setup command. The Db2 installer copies the Db2 setup log file to the DB2DIR/install/logs/ directory, and renames it db2install.history. If there are insufficient details in the log files on the installation-initiating host (IIH), you can also check the host logs that detail the actions on each remote host, and can be found under the DB2DIR/tmp/db2log.xxxx directory (where xxxx represents the process id) and DB2DIR/tmp/db2log directory.

What is a rollback?

A rollback occurs when an operation was unsuccessful and the Db2 installer will clean up the environment. You can have an instance rollback and a Db2 binaries rollback. If the Db2 installer fails to create a Db2 instance, it will trigger a rollback of the instance on all hosts. An instance rollback does not rollback Db2 binaries.

A partial rollback occurs when you can set up an instance, but it cannot be extended to a particular host.

What if the Db2 binary installation fails on one or more hosts?

Check the installation logs on the IIH and if more failure details are required, check the logs on the appropriate remote hosts. Resolve the errors and restart the installation.

What if my instance was not created?

If your instance creation has failed, a rollback of the instance on all involved hosts has occurred. Refer to the installation log for more details. If the Db2 binaries are successfully installed on a host, they will not be rolled back. Resolve the errors outlined in the installation logs and run the appropriate command (db2isetup or db2icrt) command to create the instance again. You do not need to launch the Db2 installer.

What if my instance was only partially created? What if my instance was created, but some of my members and CFs were not created?

It might occur during an installation that your instance was created only on some of the target hosts. Instance rollback happens on the hosts where the instance creation was not completed without triggering a binary rollback. You will receive a post installation message showing the hosts that have not been included in the instance due to an error.
Resolve any errors outlined in the installation logs. After you've resolved the problem, you can run the db2isetup or db2iupdt command to add the members or CFs:
  • You can validate the host and add it to the instance by using the Db2 Instance Setup wizard (by issuing db2isetup command).
  • You can extend your instance by issuing the db2iupdt -add command from a host that already belongs to the instance.

What if I cannot install the rsct.basic file?

If you have RSCT packages installed that have a higher version number than the provided rsct.basic file, you cannot install Tivoli® SA MP. To resolve this error, refer to the rsct.basic cannot be installed on AIX® support documentation.