ROLLFORWARD recovers specified data tables, with after journals, to their state following a modification.
where:
Syntax Element |
Description |
(dbname) |
Name of the database to be rolled forward |
ALL |
Rolls forward the named database and its descendants |
(dbname.tablename) |
Name of the table to be rolled forward When recovering a specific AMP, the specified table must be non-fallback because fallback tables are completely recovered by any previous activity. |
EXCLUDE |
Prevents the named database from recovery |
(dbname) |
Name of the database excluded from recovery |
ALL |
Excludes from recovery the named database and its descendants |
(dbname1) TO (dbname2) |
Alphabetical list of client databases to be excluded from recovery The delimiting database names need not identify actual databases. Database DBC is not included as part of a range. |
chkptname or chkptname, eventno or eventno |
Specifies the termination point for the rollforward operation |
PRIMARY DATA |
Applies primary and fallback row images during the rollforward process Teradata ARC ignores secondary index rows and fallback rows for online AMPs. |
RELEASE LOCK |
Releases utility (HUT) locks on the named databases automatically when rollforward completes |
NO DELETE or DELETE |
Deletes, or refrains from deleting, the restored journal subtable after the rollforward is complete. The default is DELETE. |
ABORT |
Aborts the roll operation if an AMP to which a non-fallback archive to be recovered is offline This option affects only all-AMPs roll operations. It does not affect specific AMP operations. |
CURRENT or RESTORED |
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. |