in black and white
Main menu
Share a book About us Home
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

Teradata RDBMS Database Administration - NCR

NCR Teradata RDBMS Database Administration - NCR , 2004. - 616 p.
Download (direct link): teradatadatabaseadmin2004.pdf
Previous << 1 .. 15 16 17 18 19 20 < 21 > 22 23 24 25 26 27 .. 218 >> Next

The GRANT statement enables you to grant any of the privileges you have to another user. For example, when logged on as user DBC you need to grant all the privileges retained by DBC to your new DBAdmin user:


The GIVE statement enables you to transfer ownership of a database or user to a non-owner. GIVE transfers to the recipient not only the specified database or user space, but also all of the databases, users, and objects owned by that database or user.

Caution: Transferring ownership affects space allocation. Plan carefully and check space distribution and object ownership before using the GIVE statement.

The following privileges are necessary before you can execute GIVE:

CREATE DATABASE or CREATE USER on the receiving database/user.

DROP DATABASE or DROP USER on the database/user being given.

You cannot DROP databases or users that own objects (tables, views, I macros, journals, indexes, stored procedures, or children databases).

1 - 2

Teradata RDBMS Database Administration Chapter 1: Database Hierarchy

The Initial Teradata Database

The Initial Teradata Database

When the Teradata RDBMS software is installed, the Teradata RDBMS contains the following system users/databases:




After installation, you can use the Database Initialization Program (DIP) utility to run one or more of the executable files containing SQL scripts that create other special system users, databases, and administrative tools.

For example, executing the DIPCRASH script creates the Crashdumps user and its associated database. (See Appendix E: "Database Initialization" and "DIP Utility" in Teradata RDBMS Utilities.)

DBC Contents

The system user named DBC is at the top of the hierarchy. DBC is the default database associated with user DBC. The usable (PERM) disk space in DBC initially reflects the entire system hardware capacity, minus space for the following system users, databases, and objects:

All the space available for your databases, users, journals, data tables, indexes, stored procedures, and temporary tables. (DBC owns all unallocated space. It does not become permanent or spool space until so defined in a CREATE DATABASE or CREATE USER statement.)



The system Transient Journal (TJ), which stores the before-change image of every data row involved in a transaction, the row ID of every inserted row, and other control records used by Teradata RDBMS to automatically recover your data from transaction aborts.

During installation, the DIP Utility should have been run to execute a series of scripts. These create in DBC:

The system catalog tables of the Data Dictionary.

A suite of user-accessible views defined on those tables

The suite of tables used to store query logging rules and data when you enable the Database Query Log (DBQL) feature. DBQL objects include:

- DBQLAccessMacro, an empty macro created to protect the control statements used to enable, control, and disable the DBQL feature

- DBQLRules view, to access the contents of the DBQLRuleTbl after you have enabled the DBQL feature and defined logging rules

- QryLog view, to access the contents of the DBQLogTbl

Teradata RDBMS Database Administration

1 - 3 Chapter 1: Database Hierarchy

The Initial Teradata Database

- QryLogObjects view, to access the contents of the DBQLObjTbl

- QryLogSummary view, to access the contents of the DBQLSummaryTbl

- QryLogSteps view, to access the contents of the DBQLStepTbl

- QryLogSQL view, to access the contents of the DBQLSQLTbl

SysAdmin Contents

System user DBC.SysAdmin contains several administrative views and macros, as well as a restart table for network-based FastLoad jobs. (For information and instructions on using the FastLoad client utility, see Teradata FastLoad Reference.).

To protect these objects and jobs, only a database or system administrator or NCR personnel should log on as user SYSADMIN.

SysAdmin is created with a small amount of permanent space for table storage. You may want to submit a MODIFY USER statement to increase its PERM allocation.

Suggested PERM for SysAdmin is 5 MB minimum. Allocate even more than this if you want to use SysAdmin as a reservoir of spool space. (For more details, see Chapter 3: "Space Considerations".)

SystemFE Contents

DBC.SystemFE is a system user created with a small amount of permanent space for tables. The contents of SystemFE include the following:

IF ... THEN SystemFE contains . Comment For further information, see .
the DIPSYSFE script has been executed and Target Level Emulation (TLE) is disabled macros that generate diagnostic reports for NCR personnel logged on as this user. Special privileges associated with user SystemFE are needed to execute the macros. Appendix E: "Database Initialization" Teradata RDBMS SystemFE Macros
1 The DIPSYSFE script has been executed 2 You enabled the Target Level Emulation (TLE) feature via the Target Level Emulation field of the DBS Control Globally Distributed Object (DBSCONTROLGDO) special tables and macros used by Teradata Support Center (TSC) personnel to perform Target Level Emulation (TLE) functions. TLE enables NCR personnel to run your SQL applications on a configuration that emulates your Teradata RDBMS. It is a useful way to test, diagnose, and debug your queries. "Target Level Emulation (TLE)" on page 13-3 "Target Level Emulation" in Teradata RDBMS SQL Reference, Volume 2 "Target Level Emulation" in the chapter titled "DBS Control Utility" in Teradata RDbMs Utilities
Previous << 1 .. 15 16 17 18 19 20 < 21 > 22 23 24 25 26 27 .. 218 >> Next