ROLLBACK
Purpose
ROLLBACK recovers specified data tables, with before journals, to the state they were in before they were modified.
Syntax
where
|
Syntax Element |
Description |
|
(dbname) |
Name of the database to be rolled back |
|
ALL |
Indicates that the rollback affects the named database and its descendants ALL recovers all database tables with after images. |
|
(dbname.tablename) |
Name of the table Specify only distinct tables within the list. If recovering a specific AMP, the specified table must be non-fallback because fallback tables are completely recovered by any previous all-AMPs rollback. |
|
EXCLUDE |
Prevents the named database from being recovered |
|
(dbname) |
Name of the excluded database |
|
ALL |
Excludes the named database and its descendants from being recovered |
|
(dbname1) TO (dbname2) |
Alphabetical list of client databases to be excluded from the recovery operation The delimiting database names need not identify actual databases. Database DBC is not included as part of a range. |
|
chkptnamechkptname, eventno or eventno |
Specifies the termination point for the rollback |
|
PRIMARY DATA |
Applies primary and fallback row images during the rollback process Teradata ARC ignores secondary index rows and fallback rows for online AMPs. |
|
RELEASE LOCK |
Releases utility locks on the named databases automatically when the rollback operation completes |
|
NO DELETE or DELETE |
Deletes, or refrains from deleting, the restored journal subtable after the rollback is complete The default is DELETE. |
|
ABORT |
Stops the operation if an AMP to which a non-fallback archive is to be recovered is offline This option does not affect specific AMP operations. |
|
USE CURRENT JOURNAL or USE RESTORED JOURNAL |
Uses the current journal or a subtable that was previously restored to the Teradata Database CURRENT uses the active journal subtable followed by any saved subtable. |