Teradata Database contains many log tables in the Data Dictionary that accumulate data, either automatically or after certain features are enabled. Because log data grows over time, you must purge older information to avoid using up permanent space. You can also use the data to generate your own performance analysis reports or use a reporting solution from Teradata Professional Services.
| Logs | Description |
|---|---|
| Logs that can be purged or archived using Teradata Viewpoint. | |
| Access Log (DBC.AccLogTbl) | Data collected as defined in a BEGIN LOGGING statement, for each privilege check of an attempted user access of a database object. |
DBQ Logs, such as:
|
Data collected during database query logging (DBQL), if DBQL is enabled. |
| Disk space log (DBC.DatabaseSpace) | Data collected automatically on space allocation for databases and tables. |
| Event Log (DBC.EventLog) | Data collected automatically by the system for each user logon event. |
ResUsage Logs, such as:
|
ResUsage tables collect data on system resource usage. You can enable ResUsage data collection and set the collection rate using either:
The collection rate determines how quickly data accumulates and when the logs should be purged. |
| SWEvent Log (DBC.SW_Event_Log) | The system automatically inserts rows in response to software errors and system events, for use by Teradata Customer Service. |
TDWM Logs:
|
Logs for Teradata Viewpoint workload management functions. |
| Logs that must be purged manually purged | |
| In Doubt transaction Log (DBC.InDoubtResLog) | Contains a row for each transaction where completion was in doubt. |