System User DBC - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ - Database Administration

Teradata Database
Teradata Vantage NewSQL Engine
Release Number
March 2019
English (United States)
Last Update
Product Category
Teradata Vantage

The space allocation of system user DBC is used for the following:

DBC Space Purpose
PERM Provides ownership of the Teradata production database space, which must accommodate the maximum PERM space allocated to each user and database by its creator.

The allocated space is used to store the rows in the data tables created by each user, including the following items:

  • Primary data table rows
  • Join index table rows
  • Hash index table rows
  • LOB and XML subtable rows
  • Secondary index subtable rows
  • Optional permanent journal image rows
  • Optional fallback rows, which replicate the rows of primary data tables, index subtables, hash and join index tables, and permanent journals
Creates and maintains the WAL log/transient journal, storing a before-image copy of every row affected by data changes in all current sessions and Redo and Undo WAL records.
Stores in the Data Dictionary the definitions for system tables, indexes, macros, triggers, and views.
Provides permanent space for the following:
  • Table headers.

    Note that each materialized global temporary table also requires a minimum of 512 bytes from the PERM space of its containing database or user for its table header.

  • CRASHDUMPS database.
TEMP Provides temporary space for data inserted into materialized global temporary tables.
SPOOL Provides maximum defined SPOOL space to each user and database for the following uses:
  • Dynamic allocation and release of intermediate and final result sets during query processing.
  • Volatile temporary tables.