- DBC (at the top of the hierarchy)
- SYSTEMFE (owned by DBC)
- SYSADMIN (owned by DBC)
All permanent space not consumed by SYSTEMFE and SYSADMIN is allocated to user DBC. The ramifications of the space allocation for each of the three system users are discussed in the subsections that follow.
System User DBC
The PERM space allocation of system user DBC is used for the following:
DBC Space | Service Performed | Function on Which Service is Performed |
---|---|---|
PERM | Provides ownership | 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.
|
Creates and maintains the WAL log/transient journal | Storing a before-image copy of every row affected by data modifications in all current sessions and Redo and Undo WAL records. | |
Stores system table, index, macro, trigger, and view definitions | Setting up the data dictionary. | |
Provides permanent space |
|
|
TEMP | Provides temporary space | Data inserted into materialized global temporary tables. |
SPOOL | Provides maximum defined SPOOL space per creator-defined allocation to each user and database |
|
System User SYSTEMFE
System user SYSTEMFE is owned by user DBC.SystemFE contains special macros and objects. The quantity of PERM space allocated to SYSTEMFE is minimal.
Only Teradata field support personnel log on under this user name.
System User SYSADMIN
System user SYSADMIN is owned by DBC.SysAdmin contains special views and macros. The quantity of PERM space allocated to SYSADMIN is minimal.
Only Teradata field support personnel log on under this user name.