Access Privileges - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

To restore a database or a data table within the database, the user name specified in LOGON must have one of the following:

  • The RESTORE privilege on the database or table that is being restored
  • Ownership of the database or table

Only these users can restore database DBC:

  • User DBC
  • Users granted the RESTORE privilege on database DBC
Full access privileges are required for archiving or restoring DBC. If the DBC does not have full privileges, those rights need to be granted prior to performing the archive. If the source system is not available, such as restoring from tape, then once DBC has been restored, full privileges have to be explicitly granted for each DBC object, view, and macro before running the post_dbc_restore script and DIP.

To restore a journal table, the user name must have one of the following:

  • The RESTORE privilege on the journal table itself or the database that contains the journal table
  • Ownership of the database that contains the journal table

To use the restored journal in recovery activities also requires RESTORE privilege on the data tables being rolled forward.

To Restore a UIF object, the user named in the LOGON statement must have:

  • The RESTORE privilege on the database to be restored
You are cannot grant the RESTORE privilege on the UIF object itself, but with the database-level RESTORE privilege, you can do a table-level restore of the individual UIF object.