Creating instance resources hangs the installation

This example scenario involves a hang while creating the Db2® instance and cluster services resources as part of the installation process. The objective is to determine the problem and diagnose the cause of the hang. There are two cases for this scenario.

Case 1: Messages exist in the install log or the db2diag log file

Symptoms

The initial symptom in this case is a hang during the installation process. More specifically, the hang occurs during the process of creating the instance.

Diagnosis and resolution:
  • Check the /tmp/db2setup.log and/or the /tmp/db2icrt.log. For this example, the following message exists 
    Creating resources for the instance "db2inst1" has failed.
There was an error with one of the issued cluster manager commands. 
Refer to the db2diag log file and the Db2 documentation for details.
    Check to see if you have a similar message.
  • Check the /tmp/db2diag.log for messages similar to the following ones:
    • Line # : 6884---2610-403 The resource is stale. or
    • Line # : 9578---2610-422 Cannot execute the command on node <hostname>. The resource manager IBM.RecoveryRM is not available.
  • On AIX, these errors indicate that the IBM® Tivoli® System Automation for Multiplatforms (SA MP) recovery resource manager daemon experienced a problem. The daemon serves as the decision engine for Tivoli SA MP and is identified as IBM.RecoveryRM in the system. Diagnostic data will be written by Tivoli SA MP to diagnose the problem.
  • On AIX, the Tivoli SA MP diagnostic data is written into the directories /var/ct/<domain_name>/log/mc/ (for error logs) and /var/ct/<domain_name>/run/mc/ (core dumps) and /tmp/db2_cluster_manager_spooling/ (default trace directory). The value for domain_name can be obtained by running:
    db2cluster -cm -list -domain
  • Pacemaker diagnostic data is written into the directories /var/log/pacemaker (for error logs)
  • IBM service and development teams use trace and core files for troubleshooting. If you would like IBM service to analyze the diagnostic data, gather the data listed under the topic Manual trace and log file collection
  • Follow these instructions to upload data to IBM Technical Support:
  • The IBM Technical Support website is a good source of information, where you can identify known problems based on symptoms or error log messages

Case 2: No errors or messages in the install log or the db2diag log file

Symptoms
  • The initial symptom is a hang during the installation process.
  • The state of the hang is such that there might not be any messages reported into the /tmp/db2setup.log install log, or the log does not exist
Diagnosis and resolution:
  • If the /tmp/db2setup.log and/or /tmp/db2icrt.log exist, check if you have a similar message to:
    • Creating resources for the instance "db2inst1" has failed.
    • There was an error with one of the issued cluster manager commands. Refer to the db2diag log file and the Db2 documentation for details.
  • If the /tmp/db2diag.log exists check for messages similar to the following ones:
    • Line # : 6884---2610-403 The resource is stale. or
    • Line # : 9578---2610-422 Cannot execute the command on node <hostname>. The resource manager IBM.RecoveryRM is not available.
  • If you see these errors, this indicates the Tivoli SA MP recovery resource manager daemon experienced a problem. The daemon serves as the decision engine for Tivoli SA MP and is identified as IBM.RecoveryRM in the system. Diagnostic data will be written by Tivoli SA MP to diagnose the problem.
  • Tivoli SA MP diagnostic data is written into the directories /var/ct/<domain_name>/log/mc/ (for error logs) and /var/ct/<domain_name>/run/mc/ (core dumps) and /tmp/db2_cluster_manager_spooling/ (default trace directory). The value for domain_name can be obtained by running:
    db2cluster -cm -list -domain
  • If the /tmp/db2setup.log or /tmp/db2diag.log files do not exist or are empty, gather as much of the remaining data listed under the topic Manual trace and log file collection as possible. Contact IBM service for assistance.
  • Follow these instructions to upload data to IBM Technical Support: