Administer > Configure NNMi in a High Availability Cluster > Troubleshooting the HA Configuration > nmsdbmgr Does Not Start after High Availability Configuration

nmsdbmgr Does Not Start after High Availability Configuration

This situation usually occurs as a result of starting NNMi after running the nnmhaconfigure.ovpl command but without the nnmhadisk.ovpl command with the -to option having been run. In this case, the HA_POSTGRES_DIR entry in the ov.conf file specifies the location of the embedded database on the shared disk, but this location is not available to NNMi.

To fix this problem, follow these steps:

  1. On the active node in the High Availability (HA) cluster, disable HA resource group monitoring by creating the following maintenance file:

    • Windows: %NnmDataDir%\hacluster\<resource_group>\maintenance
    • Linux: $NnmDataDir/hacluster/<resource_group>/maintenance
  2. Copy the NNMi database to the shared disk:

    • Windows:

      %NnmInstallDir%\misc\nnm\ha\nnmhadisk.ovpl NNM 
      -to
      <HA_mount_point>
    • Linux:

      $NnmInstallDir/misc/nnm/ha/nnmhadisk.ovpl NNM 
      -to
      <HA_mount_point>

    Caution To prevent database corruption, run this command (with the -to option) only one time. For information about alternatives, see Re-Enable NNMi for High Availability after All Cluster Nodes are Unconfigured.

    • Windows:

      %NnmInstallDir%\misc\nnm\ha\nnmhastartrg.ovpl NNM <resource_group>
    • Linux:

      $NnmInstallDir/misc/nnm/ha/nnmhastartrg.ovpl NNM <resource_group>
  3. Start NNMi:

    ovstart

  4. Verify that NNMi started correctly:

    ovstatus -c

    All NNMi services should show the state RUNNING.

  5. After completing your troubleshooting, delete the maintenance file:

    • Windows: %NnmDataDir%\hacluster\<resource_group>\maintenance
    • Linux: $NnmDataDir/hacluster/<resource_group>/maintenance