Do the History Files Contain Errors?

Description

If the problem still persists, inspect the HADB history files. Some of the more likely error messages to look for are:

• Could not verify node address

  This message occurs when another process is using the port that an HADB server is trying to process. It can occur in several situations:

  • The portBase is used by another process running on this host machine.

    Set the PortBase attribute to another value using the following command:

    hadbm set portbase=value
    

  • An attempt to stop the HADB node for maintenance failed.

    Try again to stop the node with the hadbm command. If that fails, kill the OS process clu_nsup_srv for this node without the -9 option. The nsup process should then stop its hadb child process. If the parent process nsup does not exist, kill all the child processes using kill -9.

  • The HADB node was stopped for maintenance and an inetd process restarted the HADB node before you intended to start it.

    Make sure that inetd does not start the HADB node before stopping it.

• hadbm command fails with internal error:"The database could not be started”

  Check the following:

  • Shared memory is all correct on all machines in the HADB configuration.

  • No other HADB databases are running on the machines, or any other processes that could be using the same port numbers.

  • All necessary directories exist and have write permissions.

  • There is enough space in directory where devices are going to be written.

Solutions

After verifying that none of the above errors have occurred, try the following remedies, in order:

• Delete the database and retry.

• Delete the database, reboot, and retry.

• Delete database, reinstall the HADB software, and retry.

• Contact Support.

For more information, refer to the Error Message Reference.