Roll Back Database to Earlier Epoch
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.
Vertica provides the ability to roll the entire database back to a specific epoch primarily to assist in the correction of human errors during data loads or other accidental corruptions. For example, suppose that you have been performing a bulk load and the cluster went down during a particular COPY command. You may wish to discard all epochs back to the point at which the previous COPY command committed and re-execute the one that did not finish. You can determine that point by examining the log files (see Monitoring the Log Files).
An epoch represents committed changes to the data stored in a database between two specific points in time. In other words, an epoch contains all COPY, INSERT, UPDATE, and DELETE operations that have been executed and committed since the end of the previous epoch.
- On the Advanced menu, select Roll Back Database To Earlier Epoch.
- Select the database to roll back. The database must be stopped.
- Accept the suggested restart epoch or specify a different one.
- Confirm that you want to discard the changes after the specified epoch.
- The database restarts successfully.
