Teradata Database versions prior to 14.00 - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
15.00
Language
English (United States)
Last Update
2018-09-25
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

Teradata Database versions prior to 14.00

  • If Online Logging is requested on a table that is involved in a load operation (by Fastload or Multiload), Teradata ARC displays the following DBS warning message:
  • *** Warning 9136: Online archive logging cannot be enabled on one or more tables.

    Error code 9136 is returned by the DBS for one of the following conditions:

  • The table is a MultiLoad or FastLoad target table that was aborted in the apply phase
  • The table is an aborted multiload work table
  • When Teradata ARC receives the 9136 error code, Online Logging is not enabled on the table and when Teradata ARC attempts to archive the table, the table will be skipped.

    Although the table is skipped, the table header will still be archived but no data is archived. When the table is restored from the archive file, only the table header is restored, resulting in an empty table after the restore or copy operation.

  • If Online Logging is requested for a table that is already enabled for logging, the Teradata Database will return an error and Teradata Archive/Recovery Utility will abort. An exception is when the NOSYNC option has been specified. In this case, the error will be ignored and the archive job will continue.
  • If the Teradata ARC user does not have the DUMP access right (or permission) on the table to be enabled for ONLINE ARCHIVE, Teradata ARC will display an error message and the Teradata Archive/Recovery Utility will abort. If the NOSYNC option is specified, the error will be ignored and the archive job will continue.
  • If the table that we are trying to enable Online Logging on has a lock on it, Teradata ARC will be blocked. Teradata ARC will be blocked on that lock until it is freed up and Teradata ARC can obtain it.
  • NOSYNC Considerations

    The NOSYNC option tells Teradata ARC to handle all of the tables in a DB-level online archive request as if they were TB-level objects. Teradata ARC takes the DB-level request and breaks it down to send a TB-level online archive request for each table in the database.

    By using the NOSYNC option, no read lock or access lock is placed on that database and no synchronization is done to make sure that all of the tables are enabled with online archive before access to those tables is allowed. This means that these tables do not have a single common consistency point. Each table has its own consistency point in the event of a restore. Each table restores to the state it was in when the Online Archive NOSYNC processing reached that particular table when activating the Online Archive change logs.