Restart Database With Catalog Version
Use this command only when instructed to do so by
Technical Support.
To submit problem reports, questions, comments, and suggestions, please use the Technical Support page on the Vertica Systems, Inc. Web site:
http://www.vertica.com/support
You must be a registered user in order to access the page.
Before reporting a problem, please run the Diagnostics Utility described in the Troubleshooting Guide and attach the resulting .zip file.
This command discards changes made to the catalog back to a specific version. When a database starts up, all
instances of Vertica must agree on a common catalog version. The dialog below appears when one or more nodes cannot agree on a catalog version, a situation that can occur when a cluster cannot shut down safely. The command allows you to discard versions of the catalog that did not get replicated on all nodes.
An instance of Vertica consists of the running Vertica process and disk storage (catalog and data) on a host. There can be only one instance of Vertica running on a host at any time.
- On the Advanced menu select Roll Back Database To Catalog Version.

- Select the database to roll back. The database must be stopped.

- Click OK unless instructed to specify a catalog version number by
Technical Support.To submit problem reports, questions, comments, and suggestions, please use the Technical Support page on the Vertica Systems, Inc. Web site:
http://www.vertica.com/support
You must be a registered user in order to access the page.
Before reporting a problem, please run the Diagnostics Utility described in the Troubleshooting Guide and attach the resulting .zip file.

- Confirm that you really want to discard the catalog changes made after the specified version.

- The database restarts successfully.

If the restart fails, you may have specified a catalog version that is not known to any node.