PERMANENT JOURNAL in Teradata

The purpose of a permanent journal is to maintain a sequential history of all changes made to the rows of one or more tables. Permanent journals help protect user data when users commit, uncommit or abort transactions.
Permanent journaling involves keeping an audit trail of all new, deleted or changed data. For example, if a table has one million rows and is fallback protected then there are one million fallback rows. If a Permanent Journal is used instead of FALLBACK, the only rows copied to the journal are for the inserts, updates, and deletes since the last JOURNAL backup. Therefore, in most cases this is far less expensive than storing the additional one million rows needed for fallback.

Permanent journal can be used up with fallback.

By default, AFTER JOURNAL is available for him to protect his data when the hardware failure occurs.

Default option : In this case, by default the table has AFTER JOURNAL option.
CREATE TABLE forgetcode.tbl_name
( field1 INTEGER,
field2 INTEGER)
PRIMARY INDEX field1;


Explicit option: here, explicitly user defines NO AFTER JOURNAL.
CREATE TABLE forgetcode.tbl_name
FALLBACK,
NO AFTER JOURNAL
( field1 INTEGER,
field2 INTEGER)
PRIMARY INDEX field1;