Book Contents

Book Index

Next Topic

Home

Database ... did not appear to stop...

Error Message

Explanation

If you have a large database, the Vertica process may need more time to complete a moveout. Shutting down the database cancels in-progress sessions and stops the ATM so it is unlikely that any other operations have not completed.

Workaround

Vertica Systems, Inc. recommends that you wait as long as possible before taking action. You can cause data loss by, for example, interrupting a database that is still performing a moveout.

  1. Check the log files to see if any messages are being logged. A moveout causes a pair of <INFO> messages to appear in the log files. If you a message indicating that a moveout has begun but no message indicating that it finished (commited), the moveout is still running.
  2. Check the processes and system resource usage for database activity.
  3. If you are certain that no moveouts are still in progress, go to Advanced > Stop Vertica on Node.
  4. If that does not work, go to Advanced > Kill Vertica Process on Node. This command forces the cluster to go through recovery at startup.