Operational Considerations | Teradata Unity - 17.00 - Unity Operational Considerations - Continuous Availability - Teradata Unity

Teradata® Unity™ User Guide

Product
Continuous Availability
Teradata Unity
Release Number
17.00
Published
September 2020
Language
English (United States)
Last Update
2020-09-15
dita:mapPath
fmz1594836948704.ditamap
dita:ditavalPath
qqk1595871525984.ditaval
To avoid any operational issues, a DBA must be aware of the following aspects of the unitymgmt user. This user helps Unity monitor connectivity to the managed Teradata systems.
  • This unitymgmt user must be excluded from all backup jobs running on the Teradata system. It has no data to store in backups. Executing a backup on this database can result in locks that block incoming requests and result in an unintended outage.
  • The unitymgmt user must be prioritized in the TASM rule set as a high priority tactical user (never queued). Failing to do so could result in database locking issues that lead to unintended outages.
  • The dictionary scanner requires the unitymgmt user to have SHOW permission on scanned databases to retrieve the object text and default database for stored procedures.