Enforcing Temporary Logon Restrictions When Restoring Data - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantage™
An attempt to execute a RESTORE DBC may fail and cause a database restart if users other than DBC are logged on to the system. This and other administrative activities may require that you temporarily disable all logons to the database until the activity is complete. Do not use REVOKE LOGONS for this purpose. Instead use the DISABLE LOGONS command to:
  • Prevent subsequent non-DBC logons
  • Disallow the execution of RESTORE DBC until all non-DBC users are off the system
Users logged on at the time a DISABLE LOGONS command is issued continue their sessions to completion.

To safely run a RESTORE DBC operation and avoid an unplanned database restart:

  1. Use Database Window (xdbw) to submit the DISABLE LOGONS, and prevent subsequent non-DBC user logons. All current session continue to completion.
  2. When all non-DBC users are off the system, run the RESTORE operation.
  3. When the RESTORE is complete, you can use the Database Window ENABLE ALL LOGONS command to re-enable all user logon privileges defined in the database.

For more information, see “Database Window” in Teradata Vantage™ - Database Utilities , B035-1102 .