Creating the Database Administrator Profile - 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

Profiles determine certain system resources available to member users, and can also set password control parameters.

  1. From an administrative client, log on as user DBC.
  2. Create the profile for the database administrator. To do this, specify values for the following fields and controls:

    Do not enter values at this time for fields not listed.

    Field Description
    Profile Name Required. The name of the database administrator profile.

    Administrative procedures in this publication use the name AdminProfile.

    User DBADMIN will be the only member of this profile. Because of space and ownership concerns, you must create a separate profile for other administrative users.
    Account Optional. An account string defines the following characteristics for profile member sessions in the database:
    • Session priority. This classification is in effect only when TASM or TIWM classification processes do not match the request to a user-defined workload.
    • Account ID (to assign charges for system time and resources)
    • Date stamp
    • Time stamp

    Recommendation: Define at least one account string per profile. If necessary, you can add an account string later using a MODIFY PROFILE statement.

    For more about accounts, see Setting Up Your Administrative Environment: All DBAs.

    Spool Space Optional. The spool space specification is only a limit to the amount of space available for intermediate query results or formatted answer sets to queries and volatile tables. The system borrows spool space for a user from unused permanent space anywhere in the system.

    Recommendation: Set this value equal to the amount of space in the Spool_Reserve database.

    Temporary Space Optional. Required only when using global temporary tables and other features that require temporary space.

    Recommendation: Temporary space is not normally needed. Specify temporary space only when you develop a strategy for using the features that need temporary space. If necessary, you can add a temporary space later with a MODIFY USER statement.

    Password Optional. Specify values for password control attributes if profile members cannot use default values.
    Other password controls Optional.

    Recommendation: Set other password controls globally by updating DBC.SysSecDefaults if required by your site security policy. Be sure to review the default password control values to determine whether they conform to your site security requirements.

    For information on the default password control values and how to change them, see “Managing Database Passwords,” in Teradata Vantage™ NewSQL Engine Security Administration, B035-1100.

For example:

ACCOUNT=('$H-DBC-MANAGER','  account__str2','  account_str3')

Reference Information

Reference topics are arranged according to the first step in which the topic appears.

Step Topic Resources for Further Information
2 Setting up accounts Working with Users, Roles, and Profiles: Operational DBAs.
The default password control values and how to change them Teradata Vantage™ NewSQL Engine Security Administration, B035-1100