Chapter 5 Setting up Administrative Users. Teradata 2800
विज्ञापन
विज्ञापन
CHAPTER 5
Setting up Administrative Users
This section provides administrative setup procedures that must be done prior to creating databases and tables.
Implementation Task Overview
Setting up administrative users requires that you perform the following tasks completely and in the order presented.
1
2
3
4
Configure basic administrative settings. See
“Configuring Default Administrative Settings” on page 151
.
Configure disk space for system-level functions. See “Allocating Space for System-Level
Set up the Database Administrator user. See “Setting Up the Database Administrator User” on page 158
.
Set up Database Administrator privileges. See
“Setting Up Database Administrator Access to Teradata Viewpoint” on page 168
.
Configuring Default Administrative Settings
Setting Up the Teradata Administrator GUI
1
2
From the principal administrative client configured in Chapter 4: “Setting Up Teradata
Clients,” access Teradata Administrator, click Start>Programs>Teradata Administrator.
The Please Select a Data Source dialog box appears. Do the following:
3 a
In the left field, highlight the alias name for the Teradata Data Warehouse Appliance
2800.
b a
In the Root Database field enter
DBC
.
c
In What to Load, select All Databases and Users and click OK.
In the Teradata Database Connect dialog box do the following:
In the Username field enter
DBC
.
b
In the Password field, enter the user DBC password provided by your Teradata
Customer Service representative.
Teradata Data Warehouse Appliance 2800 Implementation Guide 151
Chapter 5: Setting up Administrative Users
Configuring Default Administrative Settings
4 c
Do not change other fields. Click OK.
[Optional] Set Preview Mode as the default so that SQL statements generated from using the GUI fields and controls will appear in the Query Window before the statement is executed.
a b
From the Teradata Administrator menu, click Tools>Options.
Click the Confirmation tab.
c
Check the Preview SQL before submitting check box and click OK.
Note: Setting Preview Mode as the default is optional, but it will help new Teradata
Database users to become familiar with Teradata Database SQL statements. You can send generated SQL without previewing it at any time by un-checking the Preview SQL before
submitting check box.
Defining the Data Directory
The Teradata Administrator data directory stores generated SQL for later reference and use.
The default location is:
Documents and Settings\Network_UserId\My Documents\Teradata\Teradata
Manager\Data
.
If you can use the default location, skip this procedure and go on to “Changing the
PasswordExpire Parameter” on page 153 .
If you want to change the location, use the following procedure to relocate the data directory.
1
2
3
4
From the Teradata Administrator main window, click Tools>Options.
Click the Directory tab.
Note the following directory display fields:
•
Old Path - The current path to the data directory
•
New Path - The new path to the data directory
Navigate to the desired directory.
The directory path changes automatically in the New Path box.
Click OK to save your path changes and exit the dialog box.
Setting Global Default Values
Certain global database setting must be reset from the system default values. To minimize the number of database restarts, make as many as possible of the necessary changes to global database settings at one time.
•
Reset the PasswordExpire parameter as shown in
Parameter” on page 153 to force the creation of a private password at first logon for user
DBC and all other subsequently created users.
•
To enable the new settings you must restart the database as shown in
Teradata Database Software” on page 342
.
152 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Configuring Default Administrative Settings
Changing the PasswordExpire Parameter
1
2
This procedure forces the creation of a private password for user DBC and all other subsequently created users:
Log on to Teradata Administrator as user DBC.
From the Teradata Administrator main screen, click the Query button on the bottom of the left menu bar. The Teradata SQL Assistant query window opens.
3
Enter the following SQL into the query window and click the Run Query button :
Update DBC.SysSecDefaults SET ExpirePassword = 90
Setting the PasswordExpire value to a non-zero number of days causes temporary passwords, including the user DBC password, to expire at the first logon and forces all users to create a private password. The password for each user then expires each time the increment of days passes.
Ninety days is a typical setting. Specify a different value for this and other password controls if required by your site security policy.
4
Click File/Exit to close the Teradata SQL Assistant application. Click Yes at the prompt.
5
Click File>Exit to close Teradata Administrator. The Save Changes prompt appears. For this and other procedures, click Yes if you want to save the changes to the directory defined
in “Defining the Data Directory” on page 152 .
6
Restart the database to enable the new password expiration setting, as shown in
“Restarting the Teradata Database Software” on page 342
.
7
When the database completes the restart, log on to Teradata Administrator as user DBC.
8
At the prompt create a private password for user DBC.
Note: When a user password expires, the user automatically has the privilege to specify a new password using the MODIFY USER statement.
Reference Information
Reference topics are arranged according to the step in which the topic appears.
5
6
For step...
Information on...
3, 6, 7 and
8 password control options and how to set them, password format requirements, and other password features the data directory location restarting the database
Is available in...
Chapter 6: “Managing Database Passwords,” in Security
Administration, B035-1100.
“Defining the Data Directory” on page 152
“Restarting the Teradata Database Software” on page 342
Teradata Data Warehouse Appliance 2800 Implementation Guide 153
Chapter 5: Setting up Administrative Users
Allocating Space for System-Level Functions
Allocating Space for System-Level Functions
All storage space available to Teradata Database is initially owned by the system-generated user DBC, and must be reallocated to individual users and databases.
About Database Space
You must allocate two types of database space:
•
Permanent space (perm space): Space for storing the data is allocated to the user or database that owns the table containing the data.
•
Spool space: Temporary work space used by running queries. Spool space is automatically drawn from any space that is not being used to store data.
Database space must first be allocated to system-generated users, then to administrators, and finally to databases. Allocating space to an end user is optional depending on the type of activities the user performs in the database.
For information on allocating user space, see
“Working with Database Users” on page 257 .
About System-Generated Users
During initial setup, the appliance generates several default users and assigns them perm space.
Note: The system also creates other default users, but they need not be considered for the initial allocation of system space.
System Generated User
Crashdumps
DBC
Function
Temporarily stores PDE memory dumps.
Contains:
•
Data Dictionary tables
•
Views and macros
•
System tables
•
Logs and transient journals
SysAdmin
Note: Do not reuse the name SysAdmin.
Sys_Calendar
Contains tables, views and macros for network-based load jobs.
Contains tables and views for daterelated functions.
Perm Space Default
~1 GB
Can be reset per site needs.
Initially owns all usable disk space. After you allocate space to databases and other users, some perm space must remain assigned to user DBC (~10% of available space).
Note: DBC space is not usable for database administration functions.
~40 MB
~15 MB
154 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Allocating Space for System-Level Functions
System Generated User Function
SystemFe Contains diagnostic tables and macros for use by Teradata Customer
Service.
Perm Space Default
~60 MB
Required System-Level Space Allocation Tasks
1
2
Create the spool space reserve. See “Creating the Spool Space Reserve” on page 155 .
Optimize perm space for the crashdumps database according to site needs. See
Perm Space to Crashdumps” on page 156 .
Creating the Spool Space Reserve
Before assigning permanent space to users and databases, create the spool space reserve from the space available to user DBC, to ensure that there will be enough free space to run queries.
If system-wide use of spool space exceeds the spool reserve, the system draws needed spool space from uncommitted DBC perm space.
Note: When you specify spool space in CREATE USER or CREATE PROFILE statements, you define the maximum spool that is available to users or profile members
3
4
5
The following procedure sets the spool space reserve at a nominal 20% of total available space, which you may need to adjust later, depending on the number of simultaneous queries and the size of the tables in the database.
1
Determine the perm space owned by user DBC:
a
On the Teradata Administrator main screen, click Tools>Modify User. The Modify
User screen appears.
2 b
Read the number in the Perm Space dialog box, for example 6347.75 GB, and note which of the three boxes, KB, MB, and GB is checked.
Calculate a value in bytes equal to 20% of the DBC space, using the number obtained in
, to set aside as spool space reserve, for example:
(6347.75) *(.20) = 1269.55 (units are selected in the previous step)
Write down this number for use in step 5
.
Close the Modify User dialog box.
On the Teradata Administrator main screen, click Tools>Create>Database.
In the Create Database Dialog Box, enter the following:
a
For the Database Name field enter
Spool_Reserve
.
b
For the Owner field enter
Spool_Reserve database.
DBC
, the owner of the space in which you are creating the
c
For the Perm Space field, enter the value calculated in step 2
. You can express the value in KB, MB (the default), or GB, depending on which of these is selected. The value displays in bytes.
Teradata Data Warehouse Appliance 2800 Implementation Guide 155
Chapter 5: Setting up Administrative Users
Allocating Space for System-Level Functions
d e
Check FallBack. Before Journal and After Journal are checked No by default.
Click Create to create the Spool_Reserve database.
The Query Window displays the generated CREATE DATABASE statement, for example:
CREATE DATABASE "Spool_Reserve" FROM "DBC"
AS PERM = perm_space
NO FALLBACK
NO BEFORE JOURNAL
NO AFTER JOURNAL where the perm_space shown is the amount of space, in bytes, entered in the Perm
Space field.
6
7 f g
Close the Query window and the Create User dialog box.
To view information about the new database:
a
From the Query window, click the Run Query button .
Expand database DBC in the left pane of the main Teradata Administrator screen.
b
Click the New Database Host icon to refresh the display.
c
Select the Spool Reserve database.
d
Open the Database menu at the top of the screen.
e
Select Database Information to display the characteristics of the Spool Reserve database.
Note: Periodically monitor space utilization and adjust space allocations as necessary, as
shown in “About Space Management” on page 293 .
Keep Teradata Administrator open for use in the “Assigning Perm Space to Crashdumps” on page 156
.
Reference Information
Reference topics are arranged according to the first step in which the topic appears.
For step...
5
Information on...
the CREATE DATABASE statement strategy and tools for managing space utilization
Is available in...
SQL Data Definition Language Syntax and Examples,
B035-1144
•
“About Space Management” on page 293
•
Teradata Viewpoint User Guide, B035-2206
•
Database Administration, B035-1093
Assigning Perm Space to Crashdumps
Assign perm space to the system-defined crashdumps user to contain PDE memory dumps, as follows.
156 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Allocating Space for System-Level Functions
1
2
Calculate optimal perm space for the crashdumps database using the formula:
Crashdumps Perm Space = (Number of TPA Nodes) * (Memory in GB per node) * (6)
Note: To verify the number of nodes, navigate to the SMWeb Home page, click SMClient, and refer to the Tree View, as shown in
.
This equation is based on the following assumptions:
•
32 GB of memory per node
•
a crashdump uses approximately 50% of node memory capacity
•
allocate space for at least 3 crashdumps
•
specifying FALLBACK protection for tables (the default) doubles the required space
For a 4-node system, the calculation would look similar to the following:
Crashdumps Perm Space = (4) * (32 GB) * (6), or 768 GB.
Note: Crashdumps appear as table images and will accumulate as long as there is available space. They are used by Teradata Customer Support to investigate crashes. You must remove crashdump files manually.
Modify the crashdumps default perm space value from the 1 GB default to the calculated value by doing the following:
a
Log on to Teradata Administrator as user DBC.
b
In the left pane of the main screen select the crashdumps database.
c
At the top of the Teradata Administrator main screen click Tools>Modify User.
d
For the Perm Space field, select GB (the default is MB), and enter the amount of perm
space in GB for the crashdumps database, as calculated in step 1 .
e
Retain all default settings. Click Modify.
The Query Window pops up and displays the generated MODIFY USER statement, for example:
MODIFY USER "Crashdumps" AS
PERM= perm_space
STARTUP = ''
FALLBACK
NO BEFORE JOURNAL
NO AFTER JOURNAL
COLLATION = HOST
DEFAULT CHARACTER SET = LATIN
DATEFORM = INTEGERDATE
TIME ZONE = NULL where the perm_space shown is the amount of space, in bytes, entered in the Perm
Space field.
Note: Some options appear in the SQL that were not specified in the procedure. They are system defaults and should be left as they are.
f g
From the Query window, click the Run Query button
Close the Query window and the Modify User dialog box.
.
Teradata Data Warehouse Appliance 2800 Implementation Guide 157
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
3
Note: Periodically monitor space utilization and adjust space allocations as necessary, as
shown in “About Space Management” on page 293 .
Keep the Teradata Administrator utility open for use in the
Administrator User” on page 158
.
Reference Information
Reference topics are arranged according to the first step in which the topic appears.
For step...
Information on...
1 and 2 the use and maintenance of the crashdumps database details about perm space
2 the MODIFY DATABASE statement
Is available in...
Chapter 15: “Handling Teradata Crashdumps,” in
Database Administration, B035-1093
Chapter 4: “Space,” in Database Administration,
B035-1093
SQL Data Definition Language Syntax and
Examples, B035-1144
Setting Up the Database Administrator User
Create the principal database administrator, user DBADMIN (or the name your site uses), and grant space and privileges to the user before proceeding with database implementation. User
DBADMIN can then create databases, tables, users, and other objects in the space it owns.
Note: For larger systems, you may find it useful to create additional administrative users to share database administration duties. See the sections beginning with “Administrative Users” in Chapter 3 of Security Administration, B035-1100.
Required Database Administrator Setup Tasks
1
2
3
4
Create the database administrator profile. See “Creating the DBADM Profile” on page 158
.
Create the principal database administrator. See “Creating User DBADMIN” on page 161
.
Grant database privileges to the principal database administrator. See
Privileges to User DBADMIN” on page 163 .
Provide Teradata Viewpoint privileges to the administrator. See
Administrator Access to Teradata Viewpoint” on page 168
.
Creating the DBADM Profile
Profiles determine certain system resources available to member users, and can also set password control parameters.
1
2
From an administrative client configured in Chapter 4: “Setting Up Teradata Clients,” log
on to Teradata Administrator as user DBC.
Create the profile for the database administrator, user DBADMIN:
158 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
a b
From the menu, click Tools>Create>Profile.
Specify values for the following fields and controls:
Note: Do not enter values at this time for fields not listed.
Field Description
Profile Name Required. The name of the database administrator profile.
Recommendation: Administrative procedures in this publication use the name
DBADM for the administrator profile.
Note: 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.
On the General tab...
Account Optional. An account string defines the following characteristics for profile member sessions in the database:
•
Account ID (to assign charges for system time and resources)
•
Date stamp
•
Time stamp
The account string also contains an indication of the general priority level for queries that run under the account, but the actual priority level is controlled by
workload management criteria. See the topics beginning with “Teradata
Integrated Workload Management” on page 308
.
Recommendation: Define at least one account per profile. If necessary, you can define additional accounts later using a MODIFY PROFILE statement.
For more about accounts, including resource cost accounting, see the sections
beginning with “Working with User Accounts” on page 251 .
Password
Spool Space
Required. The temporary password for DBADMIN.
Recommendation: Create a simple temporary password. Each user is prompted to change the temporary password to a permanent, private password at first logon to the database.
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 defined in
“Allocating Space for System-Level
.
Temporary
Space
Comment
Not applicable. Required only when using global temporary tables and other advanced features.
Recommendation: Temporary space specification is not normally needed.
Specification of temporary space requires that you develop a strategy for use of the advanced features that need temporary space. If necessary, you can add a temporary space specification later with a MODIFY USER statement.
Optional. Use this space to describe the profile or note contingencies. The string has a 255 character limit.
Teradata Data Warehouse Appliance 2800 Implementation Guide 159
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
Field Description
On the Password tab...
Expire Required. The number in days until a password expires. Set this value to a positive, non-zero number to cause passwords to expire.
Recommendation: 90 days is a common password expiration interval.
Other password controls
Optional.
Recommendation: Set other password controls globally, by updating the
DBC.SysSecDefaults, if required by your site security policy.
Note: 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 Chapter 6: “Managing Database Passwords,” in Security
Administration, B035-1100.
c d
Do not use the Users in Profile dialog box. You can specify profile membership in
“Creating User DBADMIN” on page 161 .
Click the Create button to create the profile. The Query Window displays a generated
CREATE PROFILE statement similar to the following:
CREATE PROFILE "dbadm" AS
SPOOL=spool_space
TEMPORARY=NULL
ACCOUNT=('$H-DBC-MANAGER',' account__str2',' account_str3')
DEFAULT DATABASE="All"
PASSWORD = password
(EXPIRE=90,MINCHAR=NULL,MAXCHAR=NULL,MAXLOGONATTEMPTS=NULL,LOCKEDU
SEREXPIRE=NULL,REUSE=NULL,DIGITS=NULL,RESTRICTWORDS=NULL,SPECCHAR=
NULL)
f e
In the Query Window, click the Run Query button . A Query Complete message appears in the bottom left corner of the main window when the query executes.
Close the Query Window and the Create Profile dialog box.
Reference Information
For step...
Information on...
2 setting up user accounts the default password control values and how to change them
Is available in...
“Working with User Accounts” on page 251
Security Administration, B035-1100
160 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
Creating User DBADMIN
1
2
From an administrative client configured in Chapter 4: “Setting Up Teradata Clients,” log
on to Teradata Administrator as user DBC.
Create the database administrator as follows:
a b
From the menu, click Tools>Create>User.
Specify values for the following fields and controls:
Note: Do not enter values at this time for fields not listed.
Field
User Name
Owner
Password
Description
Required. The name of the database administrator user.
Recommendation: All administrative procedures in this publication use the name DBADMIN for the principal administrator.
The owner of user DBADMIN, that is, DBC.
Required. The temporary password for DBADMIN.
Recommendation: Any simple password will work that follows the default system password controls. Each user is prompted to change the temporary password to a permanent, private password at first logon.
Note: Be sure to review the default password control values to determine whether they conform to your site security requirements.
For information on password control options, see Security Administration,
B035-1100.
Permanent
Space
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: Spool space specification is not normally needed. Spool is already allocated in the DBADM profile.
Default
Database
Required. The space in bytes that contains all objects that user DBADMIN creates or owns. Because user DBADMIN will create and own nearly all Teradata databases and tables, assign it the majority of space on the system.
Recommendation: 60-65% of available system (DBC) space. For information
on how to determine DBC space, see step 1 on page 155
.
Profile
Optional. The user or database containing the space in which the Teradata
Database stores or searches for new or target objects unless a different database is specified in the transaction SQL.
Recommendation: Specify DBADMIN.
Required. The name of the profile in which the user has membership. A user can be a member of only one profile.
Recommendation: Enter DBADM, the profile created for user DBADMIN in
“Creating the DBADM Profile” on page 158 .
Teradata Data Warehouse Appliance 2800 Implementation Guide 161
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
Field
FALLBACK
Description
Optional. Specification of FALLBACK automatically creates a duplicate of each table stored in the user space, in addition to the duplicates already created by disk mirroring, to which the system can revert in the event of a failure.
Recommendation: Uncheck Fallback. FALLBACK is only recommended for individual mission-critical tables or tables so large that their size prevents timely backup to tape or external disk.
c
Note: You can adjust the space assignments if required, using the Modify User GUI.
Click Create.
The Query Window pops up and displays the generated CREATE USER statement, for example:
CREATE USER "DBADMIN" FROM "DBC"
AS PERM = perm_space
PASSWORD = "temp"
SPOOL = spool_space
PROFILE = DBADM
STARTUP = ''
NO FALLBACK
NO BEFORE JOURNAL
NO AFTER JOURNAL
Note: Some options appear in the SQL that are not specified in the procedure. These are system defaults and should remain as they are. For example Before Journal and
After Journal are checked No by default.
d
From the Query window, click the Run Query button .
e
Close the Query window and the Create User dialog box.
3
Keep the Teradata Administrator utility open for use in the
Note: After you create the administrative user DBADMIN, do not log on as user DBC to perform subsequent administrative activities except during activities that only user DBC can perform.
162 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
Reference Information
Reference topics are arranged according to the first step in which the topic appears.
For step...
Information on...
1 log on to Teradata Administrator
2 user types and characteristics syntax and options for the
CREATE USER statement guidelines for managing of space
Is available in...
“Configuring Default Administrative Settings” on page 151
Chapter 5: “Creating Users and Granting
Privileges,” in Security Administration, B035-
1100
SQL Data Definition Language Syntax and
Examples, B035-1144
Chapter 4: “Space,” in Database Administration,
B035-1093
Chapter 6: “Managing Database Passwords,” in
Security Administration, B035-1100 the default password control values and how to change them
Granting Database Privileges to User DBADMIN
1
2
Log on to Teradata Administrator as user DBC.
Grant object access privileges to system tables and other objects owned by user DBC.
a
From the main window, click Tools>Grant/Revoke>Object Rights.
b
Specify values for the following fields:
Field
Database Name
Object Type
To/From User
Normal
Grant
Description
The name of the user or database that owns the objects on which the privileges are being granted.
Select DBC from the Database Name drop-down list.
The object on which the privileges are given.
Select Database from the Object Type drop-down list.
The name of the user that receives the privileges.
Select DBADMIN from the To/From User drop-down list.
Specifies the privileges granted to the user. Check the following boxes:
•
Execute
•
Select
Specifies that the user is granted the WITH GRANT OPTION privilege, that is the user can grant the privileges to other users.
Check the Grant box.
c
Click the Grant button.
Teradata Data Warehouse Appliance 2800 Implementation Guide 163
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
The Query window appears and displays the generated GRANT statement:
GRANT EXECUTE, SELECT ON "DBC" TO "DBADMIN" WITH GRANT OPTION.
3 d a
From the Query window, click the Run Query button .
e
Close the Query window.
Grant object-level database privileges to the database administrator on all objects subsequently created in DBADMIN space.
From the main window, click Tools>Grant/Revoke>Object Rights.
b
Specify values for the following fields:
Field
Database Name
Object Type
To/From User
All
Grant
Description
The name of the user or database that owns the objects on which the privileges are being granted.
Select DBADMIN from the Database Name drop-down list.
The object on which the privileges are given. Includes all databases and all objects created in the database(s).
Select Database from the Object Type drop-down list.
The name of the user that receives the privileges.
Select DBADMIN from the To/From User drop-down list.
Specifies all rights for all objects created in DBADMIN space.
Check the All box.
Specifies that the user is granted the WITH GRANT OPTION privilege, that is the user can grant all included privileges to other users.
Check the Grant box.
c
Click the Grant button.
The Query window appears and displays the generated GRANT statement.
GRANT EXECUTE, SELECT, INSERT, UPDATE, DELETE, STATISTICS, DUMP,
RESTORE, CHECKPOINT, SHOW, EXECUTE PROCEDURE, ALTER PROCEDURE,
EXECUTE FUNCTION, ALTER FUNCTION, ALTER EXTERNAL PROCEDURE, CREATE
OWNER PROCEDURE, CREATE TABLE, CREATE VIEW, CREATE MACRO, CREATE
DATABASE, CREATE USER, CREATE TRIGGER, CREATE PROCEDURE, CREATE
FUNCTION, CREATE EXTERNAL PROCEDURE, CREATE AUTHORIZATION, DROP
TABLE, DROP VIEW, DROP MACRO, DROP DATABASE, DROP USER, DROP
TRIGGER, DROP PROCEDURE, DROP FUNCTION, DROP AUTHORIZATION ON
"DBADMIN" TO "DBADMIN" WITH GRANT OPTION;
4 d
From the Query window, click the Run Query button .
e
Close the Query window.
Grant object-level privileges on DBC tables and views to DBADMIN.
164 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
a b
From the main window, click Tools>Grant/Revoke>Object Rights.
Specify values for the following fields:
Field
Database Name
Object Type
To/From User
Access
Grant
Description
The name of the user or database that owns the objects on which the privileges are being granted.
Select DBC from the Database Name drop-down list.
The object on which the privileges are given. Includes all databases and all objects created in the database(s).
Select Database from the Object Type drop-down list.
The name of the user that receives the privileges.
Select DBADMIN from the To/From User drop-down list.
Specifies privileges for all DBC tables and views.
Check the Access box.
Specifies that the user is granted the WITH GRANT OPTION privilege, that is the user can grant all included privileges to other users.
Check the Grant box.
c
Click the Grant button.
The GRANT statement generates and automatically submits the following SQL statements without previewing them.
GRANT EXECUTE, SELECT, STATISTICS, SHOW ON "DBC" TO "DBADMIN" WITH
GRANT OPTION
5 d
From the Query window, click the Run Query button .
e
Close the Query window.
Grant additional system-level privileges not included with the object-level privileges granted in
a
Deselect the Preview Mode button at the top of the main screen. The sub-procedure that follows generates a compound SQL statement that cannot be submitted from
Preview Mode.
b
From the main window, click Tools>Grant/Revoke>System Rights.
c
Specify values for the following fields:
Field
To/From User
Description
The name of the user that receives the privileges.
Select DBADMIN from the To/From User drop-down list.
Teradata Data Warehouse Appliance 2800 Implementation Guide 165
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
Field
All
Grant
Description
Specifies all rights for all objects created in DBADMIN space.
Check the ALL box.
Specifies that the user is granted the WITH GRANT OPTION privilege, that is the user can grant all included privileges to other users.
Check the Grant box.
d
Click the Grant button.
The GRANT statement generates and automatically submits the following SQL statements without previewing them.
GRANT MONRESOURCE, MONSESSION, ABORTSESSION, SETSESSRATE,
SETRESRATE, REPLCONTROL, CREATE PROFILE, CREATE ROLE, DROP PROFILE,
DROP ROLE TO "DBADMIN" WITH GRANT OPTION;
6
GRANT UDTTYPE, UDTMETHOD ON SYSUDTLIB TO DBADMIN WITH GRANT OPTION;
e
Close the Grant/Revoke System dialog box.
Grant additional system-level privileges not covered by GRANT shown in step 5
.
a
Click the Query button, the lowest button on the left edge of the main screen to open the Teradata SQL Assistant query window. This allows you to construct and submit an
SQL statement without using the GUI interface.
b
Enter the following SQL statement:
GRANT CTCONTROL ON "DBADMIN" TO "DBADMIN" WITH GRANT OPTION;
7 c
Click the Run Query button .
Grant privileges on Sys_Calendar, which contains tables and views for date-related system functions.
a
Click the Preview Mode button to enable previewing SQL statements before submitting them.
b
From the main window, click Tools>Grant/Revoke>Object Rights.
c
Specify values for the following fields:
Field
Database Name
Object Type
Description
The name of the user or database that owns the objects on which the privileges are being granted.
Select Sys_Calendar from the Database Name drop-down list.
The object on which the privileges are given. Includes all databases and all objects created in the database(s).
Select Database from the Object Type drop-down list.
166 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Setting Up the Database Administrator User
Field
To/From User
Normal
Grant
Description
The name of the user that receives the privileges.
Select DBADMIN from the To/From User list.
Allows specification of rights for the named objects.
Check the Select, Insert, Update, and Delete boxes.
Specifies that the user is granted the WITH GRANT OPTION privilege, that is the user can grant all included privileges to other users.
Check the Grant box.
d
Click the Grant button. The Query window appears and displays the generated SQL statement.
GRANT SELECT, INSERT, UPDATE, DELETE ON "Sys_Calendar" TO "DBADMIN"
WITH GRANT OPTION;
8 e a
From the Query window, click the Run Query button .
f
Close the Query window and the Grant/Revoke Object dialog box.
Click File>Define Data Source. The ODBC Data Source Administrator box appears.
On the System DSN tab select the data source, that is, the system name.
b
Click the Configure button. The ODBC Driver Setup for Teradata Database dialog box appears.
c
Change the value of the Username parameter to DBADMIN.
d
Change the value of the password to the temporary password for DBADMIN specified
“Creating User DBADMIN” on page 161 .
Note: User DBADMIN will be prompted to change the temporary password to a permanent, private password at first logon.
e
Click Yes to store the password, then click OK.
f
Click OK to exit the ODBC Data Source Administrator dialog box.
9
10
Click File>Exit to close Teradata Administrator.
Immediately reopen Teradata Administrator, which logs on to Teradata Database as
DBADMIN using the temporary password specified in Step 9 sub step d
.
Note: You do not need to execute a GRANT LOGON statement for user DBADMIN or any other user created in the database. All users automatically have the right to log on to the database from any connected client, unless a REVOKE LOGON statement is issued.
11
When prompted, create a private password for user DBADMIN. This client is now configured for use by user DBADMIN. Conduct all future administrative tasks as user
DBADMIN or another administrative user.
12
Exit Teradata Administrator by entering File>Exit, or continue to
Administrator Access to Teradata Viewpoint” on page 168
.
Teradata Data Warehouse Appliance 2800 Implementation Guide 167
Chapter 5: Setting up Administrative Users
Checkpoint
Reference Information
Reference topics are arranged according to the first step in which the topic appears.
2
3
For step...
1
Information on...
Is available in...
logon to Teradata Administrator
“Configuring Default Administrative Settings” on page 151
system tables and views user privileges
Data Dictionary, B035-1092
Chapter 5: “Creating Users and Granting
Privileges” in Security Administration, B035-
1100
SQL Data Control Language, B035-1149 2 through 6 syntax and options for GRANT
(SQL form) and (Role form)
10 password format rules Chapter 6: “Managing Database Passwords,” in
Security Administration, B035-1100
Setting Up Database Administrator Access to Teradata Viewpoint
DBADMIN and other administrative users can benefit from using Teradata Viewpoint to monitor and manage the database during implementation.
1
Set up administrator client computers as shown in
Chapter 4: “Setting Up Teradata
2
Create Teradata Viewpoint administrative users and assign roles, as shown in
Teradata Viewpoint Users” on page 287 .
Checkpoint
Before leaving Chapter 5: “Setting up Administrative Users,” make sure that:
Result
The Teradata Administrator GUI is set up on the principal administrative client.
The PasswordExpire parameter is reset and the database restarted to apply the new values.
Crashdumps has perm space assigned to it.
There is a spool space reserve.
Reference
“Setting Up the Teradata Administrator
“Assigning Perm Space to Crashdumps” on page 156
“Creating the Spool Space Reserve” on page 155
168 Teradata Data Warehouse Appliance 2800 Implementation Guide
Chapter 5: Setting up Administrative Users
Checkpoint
Result
An administrative user called DBADMIN, exists in the database and has:
•
A profile
•
The database privileges necessary to carry out database administrator duties
User DBADMIN has access to Teradata
Viewpoint.
Reference
“Setting Up the Database Administrator
“Setting Up Database Administrator
Access to Teradata Viewpoint” on page 168
If you do not have these results, return to the section in the Reference column and review/ rerun that procedure.
Teradata Data Warehouse Appliance 2800 Implementation Guide 169
Chapter 5: Setting up Administrative Users
Checkpoint
170 Teradata Data Warehouse Appliance 2800 Implementation Guide
डाउनलोड
सार्वजनिक लिंक अपडेट किया गया
आपकी चैट का सार्वजनिक लिंक अपडेट कर दिया गया है. You may view and manage your chat links after registration here.
दस्तावेज़ सार्वजनिक लिंक
विज्ञापन
