Configuring Teradata Vantage™ After Installation

Configuring Teradata Vantage™
After Installation
Release 1.1
July 2019
B700-4014-079K
DOCS.TERADATA.COM
Copyright and Trademarks
Copyright © 2019 by Teradata. All Rights Reserved.
All copyrights and trademarks used in Teradata documentation are the property of their respective owners. For more information, see
Trademark Information.
Product Safety
Safety type Description
Indicates a situation which, if not avoided, could result in damage to property, such as to equipment
NOTICE or data, but not related to personal injury.
Indicates a hazardous situation which, if not avoided, could result in minor or moderate personal
CAUTION injury.
Indicates a hazardous situation which, if not avoided, could result in death or serious personal injury.
WARNING
Warranty Disclaimer
Except as may be provided in a separate written agreement with Teradata or required by applicable law, the information available
from the Teradata Documentation website or contained in Teradata information products is provided on an "as-is" basis, without
warranty of any kind, either express or implied, including the implied warranties of merchantability, fitness for a particular purpose,
or noninfringement.
The information available from the Teradata Documentation website or contained in Teradata information products may contain references
or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not
imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local
Teradata Corporation representative for those features, functions, products, or services available in your country.
The information available from the Teradata Documentation website or contained in Teradata information products may be changed or
updated by Teradata at any time without notice. Teradata may also make changes in the products or services described in this information
at any time without notice.
Feedback
To maintain the quality of our products and services, e-mail your comments on the accuracy, clarity, organization, and value of this document
to: teradata-books@lists.teradata.com
Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed nonconfidential. Without
any payment or other obligation of any kind and without any restriction of any kind, Teradata and its affiliates are hereby free to (1) reproduce,
distribute, provide access to, publish, transmit, publicly display, publicly perform, and create derivative works of, the Feedback, (2) use any
ideas, concepts, know-how, and techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing,
and marketing products and services incorporating the Feedback, and (3) authorize others to do any or all of the above.
Contents
Chapter 1: You Are Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2: Configure and Validate Vantage Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 3: Configure NewSQL Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Planning Worksheet for NewSQL Engine Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Logging on to Teradata Vantage Using BTEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Changing the Password for User DBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Setting Up the Spool Reserve Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Methods for Managing Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Assigning Perm Space for Crashdumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SQL Requests for Checking Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Creating the SYSDBA Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Creating Databases for Tables and Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Granting Role and Profile Privileges to SYSDBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Creating Administrative Roles and Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Modifying the SYSDBA User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating General User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating General User Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Creating a Test User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Creating a Test Table with Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Using SELECT to Query the Test Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Removing the Test User and Test Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Logging off Teradata Vantage Using BTEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 4: Validate QueryGrid Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Validating NewSQL Engine to Machine Learning Engine Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 5: Validate Analytic Functions on NewSQL Engine and Machine Learning Engine . . . . . . 21
Validating Analytic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Setting Up to Validate NewSQL Engine Analytic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Validating NewSQL Engine Analytic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Setting Up to Validate Machine Learning Engine Analytic Functions . . . . . . . . . . . . . . . . . . . . . . . . . 23
Validating Machine Learning Engine Analytic Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Removing Users with CONNECT THROUGH Granted on the Machine Learning Engine . . . . . . . . . 28
Setting Up Users to Access Query Level Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Validating Queries Using Query Level Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 6: Configure Teradata Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Configuring Teradata Vantage™ After Installation, Release 1.1 3

Contents
Planning Worksheet for Teradata Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Logging on to the Viewpoint Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Adding LDAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Adding a NewSQL Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Adding a Teradata Machine Learning Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Adding QueryGrid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Adding and Assigning Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Setting Up Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Adding Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Monitor Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Chapter 7: Configure Teradata AppCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Planning Worksheet for AppCenter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Adding Built-In OpenLDAP Configuration for Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Adding Corporate LDAP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Adding a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Creating a Teradata System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring an SMTP Email Account for Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Logging on to AppCenter as an LDAP or OpenLDAP User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Creating a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Chapter 8: Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Advanced SQL Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
AppCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Machine Learning Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
QueryGrid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Chapter 9: Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Vantage Component Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Vantage Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Directory Management of Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Vantage Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
User Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Data Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Vantage Security Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Security Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Chapter 10: Analytic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 11: Analytic Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Appendix A: Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

1
You Are Here
When you begin using this When you're done

What you'll do in this guide:
guide: with this guide:
The hardware is running and the • Finalize the Vantage configuration for: Vantage is set up and
Teradata Vantage™ software is ◦ Advanced SQL Engine you're ready to analyze
installed at the supported anything, anywhere, at
◦ Teradata® Viewpoint
versions. See Preparing Your any time.
Site for Teradata Vantage™ ◦ Teradata® AppCenter
Hardware, B035-6210 for • Validate the following are installed and
supported versions. configured correctly:
◦ Teradata QueryGrid™ connector for
Advanced SQL Engine-to-ML Engine
◦ Analytic functions
The audience for this content is database administrators (DBAs) and end users (such as data scientists).
See Users.
Teradata Vantage™ is our flagship analytic platform offering, which evolved from our industry-leading
Teradata® Database. Until references in content are updated to reflect this change, the term Teradata
Database is synonymous with Teradata Vantage.

2
Configure and Validate Vantage Software
Here is an overview of the procedures involved in configuring and validating Vantage. Each step links to
detailed procedures.
Perform the following tasks in the order listed. Skip the tasks for components that are not installed in your
environment.
1. Configure NewSQL Engine.
2. Validate QueryGrid Configuration.
3. Validate Analytic Functions on NewSQL Engine and Machine Learning Engine.
4. Configure Teradata Viewpoint.
5. Configure Teradata AppCenter.
6. Review the following informational content:
a. Backup and Restore
b. Security Overview
c. Analytic Tools
d. Analytic Languages

3
Configure NewSQL Engine
Planning Worksheet for NewSQL Engine Configuration

After the Vantage installation is complete, review the planning worksheet and note the information needed
to configure Advanced SQL Engine.
Note:
You do not need to repeat procedures previously done as part of hardware or software installation.
Your
Category/Input Item Description
Information
Domain
Vantage system hostname Fully Qualified Domain Name (FQDN):

with primary domain • Used by clients (BTEQ, Teradata Studio, and so on)
to access Advanced SQL Engine
• Used to access the OS
Domain Domain portion of the FQDN
Advanced SQL Engine IP address of the Advanced SQL Engine system node
public IP address for the eth0 interface. Assigned to FQDN.
DBC user
Username DBC Database administrator default account
Password DBC user password
Site security policy
Recommended password Teradata recommends that passwords expire every 90

expiration period days. Your site may have different guidelines.
SYSDBA user
Username SYSDBA
Password SYSDBA password

SYSDBA is created in the following procedures or it
may have been created during installation if data
migration was done.
Logging on to Teradata Vantage Using BTEQ

3: Configure NewSQL Engine
You need a client installed on your local workstation to access Vantage. See Analytic Tools.
To configure Advanced SQL Engine, use any client application that can run SQL requests, such as Teradata
Studio or Basic Teradata Query Utility (BTEQ). These client applications allow users to:
• Perform administrative tasks, including creating databases, tables, and views using SQL DCL, DDL,
and DML requests.
• Format reports for both print and screen output.
For the sake of simplicity, the following procedures for configuring Advanced SQL Engine use only BTEQ
to access the database.
1. Start BTEQ.
For example, in Windows, click the Microsoft logo on the lower left of your screen and in the dialog box
type: Run.
2. In the Open box, type cmd to open a command window.
3. Type BTEQ.
4. Enter, for example: .logon systemname.your_company.com/dbc;.
where systemname is the primary database node (the name by which the Vantage system is known to
the network, also called the TDPID).
5. Type password dbc.
Tips for Using BTEQ

To make sure you can see all the columns in request results, run these commands in BTEQ before you
run SQL requests:
.sidetitles on
.foldline on ALL
You can call BTEQ from a script or run it from the command line. Follow these tips to copy and paste SQL
statements at the command line:
• To run a single-statement SQL request, press Enter at the end of the line.
• To run a multistatement SQL request, press Enter after the last line. If you do not press Enter, every
statement runs automatically except the statement on the last line.
For details on using BTEQ from a script, see Teradata Vantage™ - Database Administration, B035-1093.
Changing the Password for User DBC

1. From a client application (such as BTEQ or Teradata Studio), open two different sessions and log on
to Vantage as DBC in both sessions. For example:
.logon systemname.your_company.com/dbc;
where systemname is the primary database node (the name by which the system is known to the
network, also called the TDPID).

2. In both sessions, type the default password, dbc.

3. In one session, modify the DBC password:
MODIFY user dbc as PASSWORD = new_password;
4. Stay logged on to the session with the default password. Log off the session in which you changed the
password.
.logoff
5. Log on to the session again as DBC using the new password.
.logon systemname.your_company.com/new_password;
6. When the logon with the new password is successful, log off the session with the default password.
Setting Up the Spool Reserve Database

Running queries need temporary work space, called spool space. Teradata strongly recommends creating
one large area that all users can draw from called the spool reserve database. This space will never hold
data. It should use 20-30% of the maximum permanent space (MaxPerm) held by DBC.
To create the spool reserve database, perform the following steps:
1. Log on as DBC.
2. Determine the MaxPerm for DBC by running this request:
SELECT sum(maxperm)
FROM DBC.DiskSpaceV WHERE databasename='dbc';
3. Calculate 20-30% of DBC MaxPerm to use as the perm value in the following step.
4. Create the spool reserve database:
create database Spool_Reserve from dbc as perm=12E12;
where perm=12E12 can be customized for your system.
Methods for Managing Space

You can manage space using either Teradata SQL or the following Viewpoint portlets:
Portlet Description
System Health Tracks system-level space usage. The portlet displays segmented bar graphs that show
normal, degraded, and critical space usage ranges.
Space Usage Tracks detailed space usage by database or user. The portlet shows available space,
current usage, and peak usage for each space type.
Assigning Perm Space for Crashdumps

The Crashdumps database holds Advanced SQL Engine memory dumps resulting from unplanned
database restarts. Teradata Customer Support can remotely access the Crashdumps database to
investigate dumps.
1. From an administrative client, such as BTEQ, log on as DBC.
2. If not known, calculate the available permanent database space by running the following SQL request:
SELECT SUM(MaxPerm) FROM DBC.DiskSpaceV;
3. Calculate the optimal perm space for the Crashdumps database, which holds three typical dumps per
node, using this formula:
Crashdumps Perm Space = Maxperm * 0.02
4. Run, for example, the following:
MODIFY DATABASE Crashdumps as perm = 400E9;
Note:
To make sure there is enough space for crashdump tables, regularly monitor space usage and
remove older crashdumps.
SQL Requests for Checking Space

From a client application, such as BTEQ or Teradata Studio, run the following optional queries to check
space.
Note:
In BTEQ, to make sure you can see all result columns, run these commands before you run the SQL
requests:
.sidetitles on
.foldline on ALL
To check... Run this request...
Total available disk SELECT SUM(MaxPerm) FROM DBC.DiskSpaceV;

space in the system
(MaxPerm)
Maximum database SELECT SUM(t3.Maxperm) FROM

space (MaxPerm) (SELECT
t1.DatabaseName
,t1.Permspace AS Maxperm
,ZEROIFNULL(SUM(t2.CurrentPerm)) AS Currentperm
FROM dbc.databases t1
LEFT OUTER JOIN dbc.tablesize t2
ON (t1.databasename=t2.databasename)
WHERE (Maxperm > 0)

GROUP BY 1,2) t3
;
Database space: Select

maximum available t1.DatabaseName
and currently in use ,t1.Permspace AS Maxperm
,ZEROIFNULL(sum(t2.CurrentPerm)) AS Currentperm
FROM dbc.databases t1
LEFT OUTER JOIN dbc.tablesize t2
ON (t1.databasename=t2.databasename)
WHERE (Maxperm > 0)
GROUP BY 1,2
ORDER BY 1;
Disk space currently SELECT SUM(CurrentPerm),

in use SUM(MaxPerm),
((Cast(Sum(Currentperm) as float) /
NullifZero(Cast(Sum(maxperm) as float))
*100))
(Title '%MaxPerm', Format 'z z9.99')
FROM DBC.DiskSpaceV;
Spool space on Select

active queries Vproc
,DatabaseName
,MaxSpool
,CurrentSpool
,PeakSpool
from dbc.diskspace
where currentspool > 0
order by 2,1
;
Users who are SELECT Databasename (format 'X(12)')

running out of ,SUM(maxperm)
permanent space ,SUM(currentperm)
,((cast(SUM(currentperm) as float))/
NULLIFZERO (cast(SUM(maxperm) as float)) * 100)
(format 'zz9.99%', TITLE 'Percent // Used')
FROM DBC.DiskSpaceV
GROUP BY 1 HAVING (cast(SUM(currentperm) as float) /
NULLIFZERO (cast(SUM(maxperm) as float)))
> 0.9
ORDER BY 4 DESC;
You can change the value 0.9 to whatever threshold ratio is appropriate for your site.
Percentage of SELECT Databasename (format 'X(12)')

space used by each ,SUM(maxperm)
database in the ,SUM(currentperm)
system ,((cast(SUM(currentperm) as float))/
NULLIFZERO (cast(SUM(maxperm) as float)) * 100)
(FORMAT 'zz9.99%', TITLE 'Percent // Used')
FROM DBC.DiskSpaceV

GROUP BY 1
ORDER BY 4 DESC
WITH SUM (currentperm), SUM(maxperm);
Users who are using SELECT databasename

excessive spool ,SUM(peakspool)
FROM DBC.DiskSpaceV
GROUP BY 1 HAVING SUM(peakspool) > 5000000000
ORDER BY 2 DESC;
You can change the value 500000000 to whatever value is appropriate for your site.
Some sites with more space may have a greater tolerance for higher spool usage
and spool limits.
Unallocated space
remaining in the SELECT databasename, allocatedperm, maxperm, permskew, maxperm-
database allocatedperm (TITLE 'UnallocatedSpace') FROM DBC.GlobalDBSpaceV;
Maximum allocated SELECT databasename, PeakAllocatedSpool from DBC.GlobalDBSpaceV;

peak spool for a
given user
Disk space for a SELECT SUM(currentperm)

given table FROM DBC.tablesizeV
WHERE databasename='xxx'
AND tablename = 'xxxx';
Creating the SYSDBA Login

Use the SYSDBA administrative user login to perform routine DBA operations such as adding, deleting,
and modifying users, databases, passwords, perm, and spool limits.
For SYSDBA, allocate approximately 59% of remaining MaxPerm space, assuming Spool_Reserve is 30%,
DBC is 10%, and Crashdumps are 1% of available space. Specify less spool space to SYSDBA than DBC.
To avoid accidental propagation of large limits, specify spool at 50% or less of the perm space specified for
SYSDBA. See Teradata Vantage™ - Database Administration, B035-1093.
1. Log on as DBC.
2. Create user SYSDBA with 23592 GB permanent space, 11800 GB spool, and 0 temporary space. For
example:
CREATE USER SYSDBA FROM DBC AS PERM=23592E9, SPOOL=11800E9, TEMPORARY=0,
PASSWORD=secret;
3. Provide SYSDBA with SELECT and EXECUTE access on the DBC database. For example:
GRANT SELECT,EXECUTE ON DBC TO SYSDBA WITH GRANT OPTION;
4. Provide SYSDBA with full self-access. For example:
GRANT ALL ON SYSDBA TO SYSDBA WITH GRANT OPTION;

5. Provide SYSDBA with SELECT access on database SYS_Calendar. For example:

GRANT SELECT ON SYS_CALENDAR TO SYSDBA WITH GRANT OPTION;
6. [Optional] Provide all users with SELECT access on database DBC. For example:
GRANT SELECT ON DBC TO PUBLIC;
Note:
Because this step enables any user to view all user submitted SQL queries, make sure this access
is consistent with corporate security policies.
Creating Databases for Tables and Views

Tables Database
The Tables_Database provides permanent space for tables containing data. Only privileged users or batch
jobs can modify the tables and data in this database. General users cannot directly access or modify data
in the Tables_Database. Tables do not have permanent space allocations, automatically taking the space
required to contain data from the owning database. You can create child databases within the Tables
database, dividing the Tables_Database permanent space according to the size of the tables each database
contains. You can optionally create additional child databases within the Tables_Database to group tables
by function or department.
Views Databases
The General_Views and Update_Views databases contain only views of database tables and macros or
stored procedures. The views databases have SELECT WITH GRANT OPTION access to the
Tables_Database. Views and macros provide access control and can restrict users to performing specific
query and update functions. You can allocate a small amount of permanent space for stored procedures,
for example 100 MB, and then adjust the allocation later using the MODIFY DATABASE statement.
For accessibility, you can create several views databases according to the needs of various departments
or user groups, for example:
• Views by department, such as Finance_Views and Purchasing_Views
• Views by user type, such as Batch_User_Views and General_User_Views
You can also create views databases by functional layer, for example:
• Read-write views where each view mirrors a table, usable for batch loads and updates without direct
access to data tables
• Read-only views that contain selected columns from one or more tables to combine related information
from multiple tables or restrict access
Use the WITH CHECK OPTION syntax in views to control which data rows users with the appropriate
privileges can modify. See CREATE VIEW WITH CHECK OPTION in Teradata Vantage™ SQL Data
Definition Language Syntax and Examples, B035-1144.

You can create a views database for each type of user:

Type of User Typical Access Rights
General users Select and execute access to query data on the Views_Database
Privileged users Select, execute, and update access to update data through the Views_Database
Database Hierarchy
Your database environment can have a hierarchy similar to the following:
• DBC
• SYSDBA
◦ Tables_Database
◦ Update_Views
◦ General_Views
Creating the Tables and Views Databases

1. Log on as SYSDBA.
2. Create the Tables_Database. For example:
CREATE DATABASE Tables_Database FROM SYSDBA AS PERM=200E9;
3. Create the General_Views database. For example:
CREATE DATABASE General_Views FROM SYSDBA AS PERM=0;
4. Create the Update_Views database. For example:
CREATE DATABASE Update_Views FROM SYSDBA AS PERM=0;
5. Grant privileges to the General_Views database on the Tables_Database. For example:
GRANT SELECT ON Tables_Database TO General_Views WITH GRANT OPTION;
6. Grant privileges to the Update_Views database on the Tables_Database. For example:
GRANT SELECT, INSERT, DELETE, UPDATE ON Tables_Database
TO Update_Views WITH GRANT OPTION;
Granting Role and Profile Privileges to SYSDBA

Initially, only DBC has the ability to create roles and profiles.
Grant the ability to create, drop, and administer roles and profiles to SYSDBA. SYSDBA can then grant role
and profile privileges to other users. See Teradata Vantage™ SQL Data Control Language, B035-1149.
1. Log on as DBC.
2. Grant administrative privileges for roles to SYSDBA. For example:
GRANT ROLE TO SYSDBA WITH GRANT OPTION;

3. Grant administrative privileges for profiles to SYSDBA. For example:

GRANT PROFILE TO SYSDBA WITH GRANT OPTION;
Creating Administrative Roles and Profiles

Create administrative roles and profiles to provide additional users with administrative privileges. Add a
descriptive prefix to each role and profile name. For example:
• R_role_name
• P_profile_name
1. Log on as DBC.
2. Create the master administrative role R_Master_Admin. For example:
CREATE ROLE R_Master_Admin;
3. Provide privileges on DBC to the master administrative role. For example:
GRANT SELECT, EXECUTE ON DBC TO R_Master_Admin;
4. Provide privileges on sys_calendar to the master administrative role. For example:
GRANT SELECT, EXECUTE ON sys_calendar TO R_Master_Admin;
5. Create the master administrative profile P_Master_Admin. For example:
CREATE PROFILE P_Master_Admin AS SPOOL=350e9, TEMPORARY=0;
Modifying the SYSDBA User

Assign the administrative role and profile to the SYSDBA user. You cannot specify WITH GRANT OPTION
for roles. You specify WITH ADMIN OPTION to enable SYSDBA to change permissions in the role and
determine to whom to grant or revoke the role. Omit this option for non-administrative users.
1. Log on as DBC.
2. Grant the master administrative role to SYSDBA. For example:
GRANT R_Master_Admin TO SYSDBA WITH ADMIN OPTION;
3. Modify the SYSDBA administrative user. For example:
MODIFY USER SYSDBA AS DEFAULT ROLE=R_Master_Admin, PROFILE=P_Master_Admin;
4. Log off.
Creating General User Profiles

Create user profiles for general, update, and batch operations.
2. Create the general user profile P_General_User with the default database General_Views, 10 GB of
spool space, and 0 bytes of temporary space. For example:

CREATE PROFILE P_General_User AS

DEFAULT DATABASE=General_Views, SPOOL=10e9, TEMPORARY=0;
3. Create an update user profile P_Update_User with the default database Update_Views and 0 bytes of
temporary space. For example:
CREATE PROFILE P_Update_User AS
DEFAULT DATABASE=Update_Views, TEMPORARY=0;
4. Create a batch user profile P_Batch_User with 100 GB of spool space and 0 bytes of temporary space.
For example:
CREATE PROFILE P_Batch_User AS
SPOOL=100e9, TEMPORARY=0;
Creating General User Roles

Create user roles for general, update, and batch operations.
2. Create the general user role. For example:
CREATE ROLE R_General_User;
3. Grant the necessary privileges to the general user role. For example:
GRANT SELECT, EXECUTE ON General_Views TO R_General_User;
4. Create the update user role. For example:
CREATE ROLE R_Update_User;
5. Grant the necessary privileges on the General_Views and Update_Views databases to the update user
role. For example:
GRANT SELECT, EXECUTE ON General_Views TO R_Update_User;
GRANT SELECT, EXECUTE, INSERT, DELETE, UPDATE ON Update_Views

TO R_Update_User;
6. Create the batch user role. For example:
CREATE ROLE R_Batch_User;
7. Grant the necessary privileges to the batch user role. For example:
GRANT SELECT, INSERT, DELETE, UPDATE, TABLE, CHECKPOINT, DUMP, RESTORE
ON Tables_Database TO R_Batch_User;
Creating a Test User

Create a temporary user named Alex to test the configuration.

2. Create a test user called Alex, who is administered by SYSDBA, with a role of R_Batch_User, using
the profile P_Batch_User, with 10 GB perm and 20 GB spool:
CREATE USER Alex FROM SYSDBA AS DEFAULT ROLE=R_Batch_User, PROFILE=P_Batch_User,
PERM=10E9, SPOOL=20E9, PASSWORD=secret;
3. Log off.
Creating a Test Table with Data

Log on as the temporary user, Alex, to create a test table and insert rows.
1. Log on as Alex using secret as the password.
2. Set the default database for the session to Tables_Database. For example:
DATABASE Tables_Database;
3. Create a table named employee with emp_id, emp_name, and start_date columns. For example:
CREATE SET TABLE employee (
emp_id INTEGER,
emp_name CHARACTER(20) CHARACTER SET LATIN NOT CASESPECIFIC,
start_date DATE)
PRIMARY INDEX (emp_id);
4. Insert rows of data into the table. For example:
INSERT INTO employee (emp_id, emp_name, start_date)
VALUES (1001, 'Mary', '2010-01-10');

VALUES (1002, 'Sam', '2014-07-01');

VALUES (1003, 'Charles', '2016-02-10');
Using SELECT to Query the Test Table

Use the SELECT statement to query the employee test table. See Teradata Vantage™ SQL Data
Manipulation Language, B035-1146.
Use the LOCKING ROW FOR ACCESS syntax in views to prevent deadlock when there is contention
accessing table data. See LOCKING Request Modifier in Teradata Vantage™ SQL Data Manipulation
Language, B035-1146.
1. Log on as Alex using secret as the password.
2. Query the employee table to find the employees who were hired prior to 2015. For example:
SELECT emp_id, emp_name, start_date
FROM Tables_Database.employee

WHERE start_date < '2015-01-01'

ORDER BY emp_id;
3. Verify the results:
emp_id emp_name start_date
1001 Mary 2010-01-10
1002 Sam 2014-07-01
4. Log off.
Removing the Test User and Test Table

2. Remove the test table, employee. For example:
DROP TABLE Tables_Database.employee;
3. Remove the test user, Alex. For example:
DROP USER Alex;
Logging off Teradata Vantage Using BTEQ

This BTEQ command... Does this...
.LOGOFF Ends the current Vantage session without exiting BTEQ.
.EXIT or .QUIT Ends the current Vantage session and exits BTEQ. If you are not logged on to
Vantage, the command just exits BTEQ.

4
Validate QueryGrid Configuration
Vantage comes with QueryGrid configured and ready to work with Machine Learning Engine. When
QueryGrid is deployed on a Vantage system, QueryGrid links are automatically created between Advanced
SQL Engine and Machine Learning Engine communication. The default foreign server name for Machine
Learning Engine is td_server_db.coprocessor.
If you have an existing QueryGrid environment, Vantage QueryGrid must be clustered with your existing
QueryGrid Manager to enable Advanced SQL Engine to communicate with all the existing QueryGrid-
connected databases.
Note:
The option to cluster an external QueryGrid environment with Vantage QueryGrid must be determined
at the time of purchase. Clustering is done by Teradata Customer Support as part of the Vantage
installation.
Contact Teradata Professional Services to merge an external QueryGrid cluster to Vantage QueryGrid if all
of the following are true:
• You have a QueryGrid environment outside of Vantage.
• Your external QueryGrid environment is running QueryGrid version 02.08.00.02 or later.
• The external QueryGrid Manager was not clustered with Vantage QueryGrid during installation.
Validating NewSQL Engine to Machine Learning Engine

Link
1. From a client application (such as BTEQ or Teradata Studio), log on to Vantage as DBC. For example:
.logon systemname.your_company.com/dbc
where systemname is the primary database node (the name by which Vantage is known to the network,
also called the TDPID).
Note:
If you run this as another user, the user must have the ANY privilege granted on the server object
(td_server_db.coprocessor) to display the output from HELP FOREIGN SERVER.
2. Run the command:

help foreign server td_server_db.coprocessor;
The command returns a list of databases on the Machine Learning Engine. For example:

4: Validate QueryGrid Configuration
Name
------------------
beehive
If an error results:
Error Condition Result Resolution
MLE functions are # help foreign server td_server_db. You can grant the user
available, the user coprocessor; permission. Run:
does not have *** Failure 3523 The user does not have any GRANT EXECUTE FUNCTION
permissions on the access to TD_SERVER_DB.coprocessor. on TD_SERVER_DB.
foreign server coprocessor TO <user>;
MLE functions are not # help foreign server td_server_db. Contact Teradata Customer
available coprocessor; Support.
*** Failure 3807 Object 'TD_SERVER_DB.
coprocessor' does not exist.

5
Validate Analytic Functions on NewSQL
Engine and Machine Learning Engine
Validating Analytic Functions
The following explains how to validate if ML Engine and Advanced SQL Engine functions are installed,
accessible, and functioning. It is an easy way to get you started using the analytic functions when you first
receive your Vantage system or to validate connectivity between Advanced SQL Engine and ML Engine
after a maintenance system reboot.
You can run the following commands from any client (such as BTEQ or Teradata Studio).
Note:
If you use BTEQ, you can copy and paste SQL statements at the command line as follows:
• To run a single-statement SQL request, press Enter at the end of the line.
• To run a multistatement SQL request, press Enter after the last line. If you do not press Enter,
every statement runs automatically except the statement on the last line.
1. From a client application (such as BTEQ or Teradata Studio), log on to the Vantage system as DBC.
For example:
2. Run the following command:
help foreign schema "public"@coprocessor;
Note:
In this command, public must be enclosed in quotation marks because it is a reserved word.
The command returns a list of functions that are installed. If an error is reported, the command will not
return a complete list of objects in the schema.
Setting Up to Validate NewSQL Engine Analytic Functions

For example:

5: Validate Analytic Functions on NewSQL Engine and Machine Learning Engine
2. Add a test user for running the validation steps. For example:
CREATE USER hal
FROM DBC
AS
PASSWORD=hal
PERM=2000000000
SPOOL=5000000000
TEMPORARY = 3000000000
FALLBACK;
3. Log off:
.logoff
Validating NewSQL Engine Analytic Functions

For information about Advanced SQL Engine analytic functions, see Teradata Vantage™ - Advanced SQL
Engine Analytic Functions, B035-1206.
1. From a client application (such as BTEQ or Teradata Studio), log on to the Vantage system. For
example:
.logon systemname.your_company.com/hal
2. Create input tables:
create multiset table attribution_1 (user_id integer, event varchar(20), time_stamp
timestamp);
insert into attribution_1 values(1, 'impression', '2001-09-27 23:00:01');
insert into attribution_1 values(1, 'email', '2001-09-27 23:00:15');
create multiset table attribution_2 (user_id integer, event varchar(20), time_stamp
timestamp);
insert into attribution_2 values(1, 'socialnetwork', '2001-09-27 23:00:20');
insert into attribution_2 values(1, 'direct', '2001-09-27 23:00:21');
insert into attribution_2 values(1, 'referral', '2001-09-27 23:00:22');
insert into attribution_2 values(1, 'paidsearch', '2001-09-27 23:00:23');
create multiset table conversion_event_table (conversion_events varchar(20));
insert into conversion_event_table values('socialnetwork');
insert into conversion_event_table values('paidsearch');

create multiset table excluding_event_table (excluding_events varchar(20));

insert into excluding_event_table values('email');
create multiset table optional_event_table (optional_events varchar(20));
insert into optional_event_table values('organicsearch');
insert into optional_event_table values('direct');
insert into optional_event_table values('referral');
create multiset table model1_table (id integer, model varchar(30));
insert into model1_table values('0', 'segment_rows');
insert into model1_table values('1', '3:0.5:exponential:0.5,second');
insert into model1_table values('2', '4:0.3:weighted:0.4,0.3,0.2,0.1');
insert into model1_table values('3', '3:0.2:first_click:NA');
create multiset table model2_table (id integer, model varchar(30));
insert into model2_table values('0', 'segment_seconds');
insert into model2_table values('1', '6:0.5:uniform:NA');
insert into model2_table values('2', '8:0.3:last_click:NA');
insert into model2_table values('3', '6:0.2:first_click:NA');
3. [Optional, for BTEQ users only] Set the page width for wider output:
.WIDTH 1024
4. Run the following Attribution query:
SELECT * FROM Attribution (
ON attribution_1 AS InputTable1
PARTITION BY user_id ORDER BY time_stamp
ON attribution_2 AS InputTable2
PARTITION BY user_id ORDER BY time_stamp
ON conversion_event_table AS ConversionEventTable DIMENSION
ON excluding_event_table AS ExcludedEventTable DIMENSION
ON optional_event_table AS OptionalEventTable DIMENSION
ON model1_table AS FirstModel DIMENSION
ON model2_table AS SecondModel DIMENSION
USING
EventColumn ('event')
TimeColumn ('time_stamp')
WindowSize ('rows:10&seconds:20')
) AS dt ORDER BY user_id, time_stamp;
The output is similar to the following:
user_id event time_stamp attribution time_to_conversion
------- ------------- -------------------------- ------------------- ------------------
1 impression 2001-09-27 23:00:01.000000 0.28571428571428575 -19.0
1 impression 2001-09-27 23:00:05.000000 0.0 ?
1 impression 2001-09-27 23:00:19.000000 0.7142857142857143 -1.0
1 socialnetwork 2001-09-27 23:00:20.000000 ? ?
1 direct 2001-09-27 23:00:21.000000 0.5 -2.0
1 referral 2001-09-27 23:00:22.000000 0.5 -1.0
1 paidsearch 2001-09-27 23:00:23.000000 ? ?
Setting Up to Validate Machine Learning Engine Analytic

Functions

To run analytic functions on Machine Learning Engine you must be logged on as a user that has certain
privileges, such as EXECUTE FUNCTION on QGEXECUTEFOREIGNQUERY, CREATE SERVER on
td_server_db, and many more.
For example:
2. Grant the necessary privileges to the user.
Note:
Use the same user that created the tables in Validating NewSQL Engine Analytic Functions
because this user owns the tables you will query next.
grant ctcontrol on hal to td_ffe_svc_acct;

grant connect through td_ffe_svc_acct to permanent hal without role;
grant execute function on TD_SYSFNLIB.QGEXECUTEFOREIGNQUERY to hal;
grant execute function on TD_SYSFNLIB.QGINITIATOREXPORT to hal;
grant execute function on TD_SYSFNLIB.QGINITIATORIMPORT to hal;
grant execute function on TD_SYSFNLIB.QGREMOTEEXPORT to hal;
grant execute function on TD_SYSFNLIB.QGREMOTEIMPORT to hal;
grant create server on td_server_db to hal;
GRANT select ON TD_SERVER_DB.coprocessor TO hal;

GRANT insert ON TD_SERVER_DB.coprocessor TO hal;
GRANT execute function on TD_SERVER_DB.coprocessor to hal;
grant create function on hal to hal with grant option;

grant execute function on hal to hal with grant option;
grant execute function on td_sysfnlib.script to hal;

grant execute on sysuif.default_auth to hal;
grant execute procedure on sysuif.install_file to hal;
grant execute procedure on sysuif.remove_file to hal;
grant execute procedure on pm.remove_afile to hal;
grant execute procedure on pm.install_afile to hal;
grant create external procedure on hal to hal;
grant select on td_server_db.coprocessor_ddl to hal;
grant execute function on syslib to hal with grant option;
3. Log off as DBC:
.logoff

4. Log on as SYSDBA:
.logon sysdba
5. Grant the user access to Tables_Database. For example:
GRANT SELECT, INSERT, DELETE, UPDATE, TABLE, CHECKPOINT, DUMP, RESTORE
ON Tables_Database TO hal;
6. Log off:
.logoff
Validating Machine Learning Engine Analytic Functions

For information about Machine Learning Engine analytic functions, see Teradata Vantage™ Machine
Learning Engine Analytic Function Reference, B700-4003.
1. From a client application (such as BTEQ or Teradata Studio), log on to the Vantage system as a user
with the necessary permissions to access Machine Learning Engine. For example:
.logon systemname.your_company.com/hal
2. If you are running the commands from the BTEQ command line, set SIDETITLES and FOLDLINE to
ON, so wide output is readable:
.SET FOLDLINE ON ALL
.SET SIDETITLES ON ALL
3. Run the following Attribution query. This query uses the Machine Learning Engine version of Attribution,
which is called with the syntax: Attribution_MLE
Note:
When using functions that exist on both Advanced SQL Engine and Machine Learning Engine,
you must use the suffix _MLE to use the Machine Learning Engine version. (The functions nPath®
and NTree are exceptions. For these functions, you must use the suffix @coprocessor to use the
Machine Learning Engine version.)
SELECT * FROM Attribution_MLE (

ON attribution_1 AS input1
PARTITION BY user_id
ORDER BY time_stamp
ON attribution_2 AS input2
PARTITION BY user_id
ORDER BY time_stamp
ON conversion_event_table AS ConversionEventTable DIMENSION
ON excluding_event_table AS ExcludedEventTable DIMENSION
ON optional_event_table AS OptionalEventTable DIMENSION
ON model1_table AS FirstModelTable DIMENSION

ON model2_table AS SecondModelTable DIMENSION

USING
EventColumn ('event')
TimeColumn ('time_stamp')
WindowSize ('rows:10&seconds:20')
) AS dt ;
The output is similar to the following:
user_id event time_stamp attribution time_to_conversion
------- ------------- -------------------------- ------------------- ------------------
1 impression 2001-09-27 23:00:01.000000 0.28571428571428575 -19.0
1 impression 2001-09-27 23:00:05.000000 0.0 ?
1 impression 2001-09-27 23:00:19.000000 0.7142857142857143 -1.0
1 socialnetwork 2001-09-27 23:00:20.000000 ? ?
1 direct 2001-09-27 23:00:21.000000 0.5 -2.0
1 referral 2001-09-27 23:00:22.000000 0.5 -1.0
1 paidsearch 2001-09-27 23:00:23.000000 ? ?
4. When you use Machine Learning Engine functions that do not have counterparts on Advanced SQL
Engine, a suffix is not required. Create the input tables:
create multiset table kmodes_input (model varchar(30), mpg double PRECISION, cyl integer, disp double PRECISION,
hp double PRECISION, drat double PRECISION, wt double PRECISION, qsec double PRECISION, vs varchar(30), am
varchar(30), gear integer, carb integer);
insert into kmodes_input values('mazda
rx4',0.150884825,6,-0.570619819,-0.53509284,0.567513685,-0.610399567,-0.777165145,'s','manual',4,4);
insert into kmodes_input values('mazda rx4
wag',0.150884825,6,-0.570619819,-0.53509284,0.567513685,-0.349785269,-0.46378082,'s','manual',4,4);
insert into kmodes_input values('datsun
710',0.449543447,4,-0.990182091,-0.783040459,0.473999587,-0.917004624,0.426006817,'v','manual',4,1);
insert into kmodes_input values('hornet 4
drive',0.217253407,6,0.220093694,-0.53509284,-0.96611753,-0.002299538,0.890487156,'v','automatic',3,1);
insert into kmodes_input values('hornet
sportabout',-0.230734526,8,1.043081228,0.412942174,-0.835197792,0.227654255,-0.46378082,'s','automatic',3,2);
insert into kmodes_input
values('valiant',-0.3302874,6,-0.046166978,-0.60801861,-1.564607761,0.248094592,1.326986752,'v','automatic',3,1);
insert into kmodes_input values('duster
360',-0.960788935,8,1.043081228,1.433902959,-0.722980874,0.360516446,-1.124126363,'s','automatic',3,4);
insert into kmodes_input values('merc
240d',0.715017777,4,-0.677930938,-1.235180235,0.174754472,-0.027849959,1.203871481,'v','automatic',4,2);
230',0.449543447,4,-0.725535119,-0.753870151,0.604919325,-0.068730634,2.826754593,'v','automatic',4,2);
280',-0.147773797,6,-0.509299179,-0.345485837,0.604919325,0.227654255,0.252526208,'v','automatic',4,4);
280c',-0.380063837,6,-0.509299179,-0.345485837,0.604919325,0.227654255,0.588295128,'v','automatic',4,4);
450se',-0.612353876,8,0.363713088,0.485867945,-0.98482035,0.871524874,-0.251127171,'s','automatic',3,3);
450sl',-0.463024565,8,0.363713088,0.485867945,-0.98482035,0.524039143,-0.139204198,'s','automatic',3,3);
450slc',-0.811459624,8,0.363713088,0.485867945,-0.98482035,0.575139986,0.084641749,'s','automatic',3,3);
insert into kmodes_input values('cadillac
fleetwood',-1.607882616,8,1.946753815,0.850496796,-1.246659826,2.077504765,0.073449451,'s','automatic',3,4);
insert into kmodes_input values('lincoln
continental',-1.607882616,8,1.849931752,0.996348337,-1.115740088,2.255335698,-0.016088927,'s','automatic',3,4);
insert into kmodes_input values('chrysler
imperial',-0.894420352,8,1.688561647,1.215125648,-0.685575235,2.174596366,-0.239934874,'s','automatic',3,4);
insert into kmodes_input values('fiat
128',2.042389431,4,-1.226589294,-1.176839619,0.90416444,-1.039646647,0.907275602,'v','manual',4,1);
insert into kmodes_input values('honda
civic',1.710546517,4,-1.25079481,-1.381031775,2.493904115,-1.637526508,0.375641479,'v','manual',4,2);
insert into kmodes_input values('toyota

corolla',2.291271616,4,-1.287909934,-1.191424773,1.166003916,-1.4126828,1.147909994,'v','manual',4,1);
insert into kmodes_input values('toyota
corona',0.233845553,4,-0.892553178,-0.724699843,0.193457291,-0.76881218,1.20946763,'v','automatic',3,1);
insert into kmodes_input values('dodge
challenger',-0.761683187,8,0.704204008,0.048313323,-1.564607761,0.309415603,-0.54772305,'s','automatic',3,2);
insert into kmodes_input values('amc
javelin',-0.811459624,8,0.591244935,0.048313323,-0.835197792,0.22254417,-0.307088658,'s','automatic',3,2);
insert into kmodes_input values('camaro
z28',-1.126710392,8,0.962396176,1.433902959,0.24956575,0.636460997,-1.364760755,'s','automatic',3,4);
insert into kmodes_input values('pontiac
firebird',-0.147773797,8,1.365821438,0.412942174,-0.96611753,0.641571082,-0.446992374,'s','automatic',3,2);
insert into kmodes_input values('fiat
x1-9',1.196190002,4,-1.224168743,-1.176839619,0.90416444,-1.310481114,0.588295128,'v','manual',4,1);
insert into kmodes_input values('porsche
914-2',0.980492108,4,-0.890939476,-0.812210767,1.55876313,-1.100967659,-0.642857578,'s','manual',5,2);
insert into kmodes_input values('lotus
europa',1.710546517,4,-1.094265808,-0.491337378,0.324377029,-1.741772228,-0.530934604,'v','manual',5,2);
insert into kmodes_input values('ford pantera
l',-0.71190675,8,0.970464681,1.711020886,1.166003916,-0.048290296,-1.874010283,'s','manual',5,4);
insert into kmodes_input values('ferrari
dino',-0.064813069,6,-0.691647397,0.412942174,0.043834734,-0.457097039,-1.314395417,'s','manual',5,6);
insert into kmodes_input values('maserati
bora',-0.844643915,8,0.567039419,2.746566825,-0.105787824,0.360516446,-1.818048797,'s','manual',5,8);
insert into kmodes_input values('volvo
142e',0.217253407,4,-0.885291523,-0.549677994,0.960272899,-0.44687687,0.420410668,'v','manual',4,2);
5. As an example, run this KModes query:

SELECT * FROM KModes (
ON kmodes_input AS InputTable
OUT TABLE OutputTable (kmodes_clusters1)
USING
NumClusters (3)
TargetColumns ('mpg:carb')
NumericAsCategorical('cyl','gear','carb')
) AS dt ;
The output should be similar to what is shown in the table, but displayed vertically.
Note:
Because KModes is a random algorithm, the numbers in the output will not be exactly the same.
set_ between_cluster_ total_within_

summary pseudo_f
id error cluster_error
0 Number of Clusters: 194. 115. 16.

3 95312046325273 04687954956962 380686190908744
Number of
Iterations: 3
Model Converged:
true
Number of Data
Points: 32.0

Postrequisite:
Clean up the test tables:
drop table kmodes_input;
drop table kmodes_clusters1;
Removing Users with CONNECT THROUGH Granted on

the Machine Learning Engine
To access the Machine Learning Engine, users must be granted CONNECT THROUGH on the Machine
Learning Engine service account (td_ffe_svc_acct). To delete these users, CONNECT THROUGH must be
revoked first.
1. Check if your user has CONNECT THROUGH granted on td_ffe_svc_acct:
SELECT TrustUser, ProxyUser, ProxyUserType, GrantStatus, WithoutRole from
dbc.connectrulesv;
TrustUser ProxyUser ProxyUserType GrantStatus WithoutRole

--------------- -------------------- ------------- ----------- -----------
td_ffe_svc_acct hal P G Y
td_ffe_svc_acct TDAP_ADMIN P G Y
2. Revoke CONNECT THROUGH from the user. For example:
REVOKE connect through td_ffe_svc_acct to permanent hal;
3. Delete all the tables for the user. For example:
delete user hal;
4. Remove the user from the database. For example:
drop user hal;
Setting Up Users to Access Query Level Monitoring

To select information from the Query Level Monitoring (QLM) database, the user must be granted SELECT
privilege on it. By default, DBC does not have select on that database, so DBC can also grant itself SELECT
on QLM, if needed.
Note:
A good practice is to create a role that contains the SELECT privilege and then assign the role to the
users that need it.
For example:

2. [Optional] You can grant select to an existing user or create a new user. For example:
CREATE USER rose FROM DBC AS PASSWORD=rose PERM=20000000 SPOOL=50000000
TEMPORARY = 30000000 FALLBACK;
3. Grant SELECT on the database to the user:
grant select on td_mle_db.querylog to rose;
4. [Optional] Grant SELECT to DBC:
grant select on td_mle_db.querylog to DBC;
5. Log off:
.logoff
Validating Queries Using Query Level Monitoring

You can check the QLM query log to validate queries are running on ML Engine.
1. From a client application (such as BTEQ or Teradata Studio), log on to the Vantage system as a user
that has SELECT on td_mle_db.querylog. For example:
.logon systemname.your_company.com/rose
2. Count the number of queries stored in the QLM log. Run:
select count(*) from td_mle_db.querylog;
The result should be non-zero.

3. Log off:
.logoff
Postrequisite:
If you created a test user (such as rose), remove the user. For example:
delete user rose;
drop user rose;
.logoff

6
Configure Teradata Viewpoint
Planning Worksheet for Teradata Viewpoint

Prepare the information needed for configuration.
Your
Information
Log On
Viewpoint portal address The browser address for Viewpoint
Username Username and password for Viewpoint access to

perform system level tasks
Password
LDAP Server [Optional]
Server LDAP server name
URL LDAP server location
Prerequisite info from User-entry details in LDIF format

LDAP Admin dn: cn=joec,dc=User Accounts,dc=acme,dc=com
cn: joec
givenName: Joe
sn: Customer
telephoneNumber: +1 888 555 6789
telephoneNumber: +1 888 555 1232
mail: [joe.customer@acme|mailto:joe.
customer@acme].com
sAMAccountName: customerjoe
objectClass: inetOrgPerson
memberOf: cn=Sales,ou=Groups,dc=acme,dc=com
memberOf: cn=DBA,ou=Groups,dc=acme,dc=com
LDAP Username
LDAP Password
Monitoring Systems Portlet
TDPID (NewSQL Engine)
Host ID NewSQL Engine
NewSQL Username Advanced SQL Engine system username and password
Host ID for Machine

Learning Engine

6: Configure Teradata Viewpoint
Your
Information
Machine Learning Engine

Username
Machine Learning Engine Machine Learning Engine username and password

Password
Host ID for QueryGrid
QueryGrid Username QueryGrid username and password
QueryGrid Password
Logging on to the Viewpoint Portal

Log on to the Viewpoint portal.
1. In a browser, enter the address for your Viewpoint portal.
2. Log on to the Viewpoint portal with the username and password to perform system level tasks.
Adding LDAP Server

Follow these steps if your corporation requires an LDAP server for Viewpoint setup. See Determining LDAP
Configuration Mode in Teradata® Viewpoint Configuration and Upgrade Guide, B035-2207.
1. From the Viewpoint portal page, select .
2. Open the LDAP Servers portlet.
3. Next to Servers, select .
4. Enter a nickname for the LDAP server, up to 8 characters.
5. [Optional] Select the Enable server to activate LDAP.
6. Enter the URL of at least one LDAP server.
7. Select a Name Matching method:
Method Steps
DN Pattern Define the search strings using {0} as the username.

Bind
User a. [Optional] To search using a specific account, enter a valid service account DN and
Search password. If these fields are empty, the Viewpoint portal connects to the LDAP server
anonymously.
b. Enter a search pattern.
c. Enter a search base to specify a base directory for the search pattern. Example:
OU=User Accounts,DC=td,DC=acme,DC=com
d. [Optional] For Search Extent, select the Recursive scan check box to include
subdirectories of the base directory in the search.

8. Under Key User Information, enter the LDAP attribute names.

9. [Optional] Test credentials.
a. Under Settings Test, enter a username and password.
b. Select Test.
When the test is successful, you receive the full DN and key user information for the user. If you receive
an error, verify that the credentials are valid and the host is available.
10. Select Apply.
11. Log off, and then log on as a corporate LDAP user.
See Auto-Provisioning and Role Mapping in Teradata® Viewpoint User Guide, B035-2206.
Adding a NewSQL Engine

Add a Advanced SQL Engine to the Monitored System portlet to begin collecting data. Your system may
be set up for you. Follow these steps if your Advanced SQL Engine is not set up.
2. Open the Monitored Systems portlet.
3. Next to Systems, select , then select Add Teradata System.
4. Under General System Details, enter a system nickname, up to 30 characters.
5. [Optional] Select the Enable system check box.
After it is enabled, the system starts collecting data.
6. Enter the TDPID of the Advanced SQL Engine if not shown.
7. [Optional] Enter the site ID assigned by Teradata Customer Services.
After enabling a system, the Site ID becomes read-only if Viewpoint detects a value for the system.
A site ID is required when using Elastic Performance on Demand.
8. Enter a login name and password.
Specify an account string and authentication, add more logons, test the logon settings, and grant access
to a Advanced SQL Engine. Add any logins used for Viewpoint data collection to the system-level
bypass. To define system-level bypass settings, use the Workload Designer portlet.
9. [Optional] Click Test to verify that the login settings are correct.
If the operation is successful, appears. If the operation fails, appears. If you receive an error, verify
that the login credentials are valid and the host can be reached.
10. [Optional] Under Authentication Options, specify which authentication mechanisms are available in
the portlets.
11. [Optional] Under Character Set, select default character sets and enter a JDBC Flag value:
• Select a character set from the Session list.
• Select a character set from the Monitor list.
• Enter a JDBC Flag value.
12. Under Time Zone, select the time zone the system uses to log DBQL and ResUsage data.
13. [Optional] Under Collectors, select Enable Data Collectors (Configure in Data Collectors) to begin
collecting data.

The data collectors can be enabled and configured individually in Data Collectors.
Portlet Data Collectors
Elastic Performance Elastic Limit and Elastic Usage
TVS Monitor Virtual Storage
Stats Manager Stats Manager
Query Log Query Log data collectors for historical DBQL data
14. [Optional] Under Enhanced TASM Functions, select Enable this option if your Teradata has license
entitlement to TASM.
The workload management features are available with your TASM license in SLES 11.
15. Select Apply.
that the settings are correct and try again.
Adding a Teradata Machine Learning Engine

Adding a Machine Learning Engine includes registering a certificate, testing login settings, and adding data
collectors. Your Machine Learning Engine may be already set up for you. Follow these instructions if your
Machine Learning Engine is not set up.
1. Before adding a Machine Learning Engine system to Viewpoint, download and register the SSL CA
certificate from https://master-node-IP:30009/ where master-node-IP is the IP address of the
master node.
4. Next to Systems, select , then select Add Teradata Machine Learning Engine.
7. Enter the Host ID of the system.
The Host ID is the IP address or host name of the system.
8. [Optional] Enter the site ID assigned by Teradata Customer Services.
After enabling a system, the Site ID becomes read-only if Viewpoint detects a value for the system.
The logon is case-sensitive.
11. [Optional] Under Collectors, select Enable all data collectors (Configure in Data Collectors) to
collect data on this system.

12. Select Apply.
Adding QueryGrid
QueryGrid may already be set up for you. Follow these steps if your QueryGrid is not set up.
1. Register the cluster's SSL CA certificate.
4. Next to Systems, click , then select Add QueryGrid.
7. Enter the IP address as the host ID of QueryGrid.
10. [Optional] Under Collectors, select Enable all data collectors (Configure in Data Collectors).
11. Click Apply.
Adding and Assigning Roles

2. Open the Roles Manager portlet.
3. Select Add Role.
You can use spaces, alphanumeric characters, and underscores (_).
4. [Optional] Select Enable role to activate the role for use in Viewpoint.
5. Enter a Description.
6. [Optional] Under Portal Permissions, select Enable rewind to view data for a different date and time
when available.
7. [Optional] Under Notifications, select notifications to appear in the portal for users assigned this role.
8. Select Apply.
9. From the Roles Manager view, select a role from the list.
10. Select the Users tab and locate a user.

11. Select one or more users from the left pane, then click to add users to role.
12. Select Apply.
13. Select the Portlets tab, then select all the portlets to include with this role.
14. Select Apply.
15. Select the Systems tab, then select all the systems to enable with this role.
16. [Optional] Select other tabs to specify additional role settings, select Apply.
Setting Up Alerts
The following are alerts specifically for Machine Learning Engine. For other alerts, see Alert Setup in
Teradata® Viewpoint User Guide, B035-2206.
3. Select the Machine Learning Engine.
4. In the Setup column, select an Alert Type, select .
Alert Type Complete these fields: Description
Data • Alert Name DCS finds errors for the

Collectors • Severity specified data collectors.
• Data Collectors
• Action (Set up in Alerts Setup portlet)
• Timeframe before repeating alert [Optional]
• [Optional] Message
Pod • Alert Name Performances reach the

• Severity specified threshold at the
queen or worker level.
• Threshold rule (Click to set up multiple rules)
Process • Alert Name Performance on Machine

• Severity Learning Engine reaches
the threshold at the
• Threshold rule (Click to set up multiple rules) process level.
• [Optional] Time requirements for alert rule
• [Optional] Timeframe before repeating alert
System • Alert Name Performance on Machine

• Severity Learning Engine reaches
the specified threshold.
• Threshold rule (Click to set up multiple rules)
• Time requirements for alert rule [Optional]

Alert Type Complete these fields: Description

System Enter the following: System health of Machine

Health • Alert Name Learning Engine reaches
• Severity the specified level.
• Trigger level
• [Optional] Timeframe before repeating alert [Optional]
Time requirements for alert rule
5. Select Apply.
Adding Portlets
To monitor the Vantage systems, add pages to the Viewpoint portal. When you add more than one page,
a page list appears.
1. In theViewpoint portal, select , then select .

2. Select Blank, enter a page name up to 30 characters, then select Create.
A new page appears.
3. Select Add Content to add portlets.
4. Highlight a portlet, and then click Add.
Monitor Portlets
Add these portlets to monitor Machine Learning Engine on Viewpoint.
Portlet Usage Use Examples
Alert Viewer Monitor alerts • View the source, system, and timestamp for an alert.
• See when systems exceed thresholds.

See Alert Viewer in Teradata® Viewpoint User Guide,

B035-2206
Canary Analyze trends in single- • Identify canary response times to help you plan
Response system performance over maintenance
Times a 60-minute or 120- • Use canary response times to compare current
minute using canary performance against average performance.
queries
See Canary Response Times in Teradata® Viewpoint User
Guide, B035-2206
Completed View the final status of • Investigate queries that take a long time
Queries queries
See Completed Queries in Teradata® Viewpoint User
Guide, B035-2206
Metric Monitor single systems to • Find a period of low usage to schedule a large job
Heatmap see periods of high and
See Metric Heatmap in Teradata® Viewpoint User Guide,
low usage
B035-2206
Metrics Analyze usage trends for • Graph resources between systems to compare trends
Analysis one or more systems
See Metrics Analysis in Teradata® Viewpoint User Guide,
B035-2206
Node Monitor Monitor nodes. See • View CPU and network traffic information at the pod level
queens and workers in ML • See a snapshot of the Machine Learning Engine status
Engine.
• View statistics for the last 24 hours
See Node Monitor in Teradata® Viewpoint User Guide,
B035-2206
Node Monitor physical and • See the percentage of CPU used by nodes or vprocs
Resources virtual resources to • Monitor how system resource usage is spread across
determine performance or vprocs
system issues
See Node Resources in Teradata® Viewpoint User Guide,
B035-2206
Productivity Monitor system health • View the queries that have completed in the last hour
and query performance
See Productivity in Teradata® Viewpoint User Guide,
trends
B035-2206
Query Monitor Manage queries running • See the progress of submitted queries
on ML Engine and other • Track down issues with long-running queries
systems
See Query Monitor in Teradata® Viewpoint User Guide,
B035-2206
Query View completed queries • Select times to see which queries ran longer than the
Spotlight that exceed thresholds threshold
• Graph job steps to identify problem times
See Query Spotlight in Teradata® Viewpoint User Guide,
B035-2206

QueryGrid Monitor queries in a data • Monitor a query between a local and remote server
analytic fabric that
connects data from one or Note:
more sources Add the QueryGrid portlet to a separate page to prevent
refresh issues. The QueryGrid portlet appears at the top of
the page and refreshes all other portlets on the page.
See Teradata® QueryGrid™ Installation and User Guide,

B035-5991
Space Usage Monitor Advanced SQL • See the perm, temp, and spool usage for each system
Engine disk space usage
See Space Usage in Teradata® Viewpoint User Guide,
B035-2206
System Health Check the health of a • See the number of users and applications currently
monitored system connected to the engine
• See details on a component that is down
See System Health in Teradata® Viewpoint User Guide,
B035-2206

7
Configure Teradata AppCenter
After Teradata® AppCenter has been installed in Teradata Vantage, the root user can complete configuration
that enables users to log in, create scripts, run jobs, view and share results, and so on. See Teradata
AppCenter User Guide, Version 1.8 or later.
Planning Worksheet for AppCenter Configuration

After the AppCenter installation is completed and before you begin the required AppCenter configuration,
review the planning worksheet and work with your DBA to gather the information you will need for
configuration.
Your
Information
Domain
AppCenter URL URL for AppCenter browser access. URL and associated
domain information are specified during installation.
Note:
If you did not provide a certificate authority (CA) digital
certificate for AppCenter during installation, the browser will
display a security warning when users access the AppCenter
URL. Work with your network security or IT administrator for
assistance obtaining a CA-signed certificate.
Root User
Username Root user credentials to access AppCenter LDAP and email

notification settings. Root user credentials are specified during
installation and can be found in the stacki-override-
appcenter.yaml file.
Password
Authentication Settings (LDAP)
Server Corporate LDAP information for AppCenter user authentication.

You can create multiple authentications, including groups.
AppCenter includes built-in OpenLDAP with two users that you
can optionally add for testing AppCenter before you add your
corporate LDAP. See Adding Built-In OpenLDAP Configuration
for Testing.
URL
Port
Base domain

7: Configure Teradata AppCenter
Your
Information
Domain search user
Domain search
password
Vendor
User object classes
ID Field User Service Column Names (For LDAP Authentication).
Name Field
Group Base [Optional] For LDAP Groups.
AppCenter User
Username or Email User who is part of the configured LDAP and who will log in after
configuration to confirm LDAP settings.
To use the built-in OpenLDAP users for testing before you
configure your corporate LDAP, see Adding Built-In OpenLDAP
Configuration for Testing.
System
Name Teradata Vantage system on Teradata IntelliFlex® for testing the

script process in AppCenter.
Name appears in a drop-down option when running the script.
System Type TERADATA For purposes of initial configuration, select TERADATA for the
system type.
Host For Vantage clusters with limited CLAN connections, use the
host: teradata-sqlengine.td-platform.svc.cluster.
local
For other clusters, use the Teradata host domain or IP address.
Port Unless otherwise advised by your DBA, use the default port
1025.
Database [Optional] Default database for SQL queries. If not specified,

AppCenter uses the default database for the user specified.
Username Required.
Password Required.
Notification Email
Server Address When the email account is configured, AppCenter sends

notification about job status and results, script updates, script
ownership changes, and script comments.
Port

Your
Information
Reply Address
SMTP Username
SMTP Password
Anonoymous Logon Advanced Configuration. Selected by default.
Use SSL
Server Timeout Default is 5000 ms.
Note:
For AppCenter running as stand-alone, applications that run until stopped with registries and Docker-
based containers are supported. For AppCenter running in Vantage Version 1.1, applications that run
until stopped with registries and Docker-based containers are temporarily disabled, pending
implementation of increased security for Docker-based containers. The security update is in progress
and expected to be complete for the next release of in AppCenter in Vantage.
Adding Built-In OpenLDAP Configuration for Testing

AppCenter includes built-in OpenLDAP with two users that you can use to testAppCenter before adding
your corporate LDAP. The built-in OpenLDAP configuration is optional and is not for production purposes.
When you add corporate LDAP, the OpenLDAP configuration will still work with your instance of AppCenter.
1. Log on to AppCenter as root user.
2. Select > Settings > Authentication.
3. Select , then complete configuration fields with these entries:
Setting OpenLDAP Entry
Server openldap
URL openldap.appcenter.svc.cluster.local
Port 389
Base domain dc=example,dc=org
Domain search user cn=admin,dc=example,dc=org
Domain search password admin
Vendor other
User object classes top,posixAccount,person
ID Field uid

Setting OpenLDAP Entry
Member of Field uid
Member Field uid
Email Field uid
Note:
LDAP group fields are not applicable to built-in OpenLDAP.
4. Follow the instructions in Adding a User to add corporate LDAP users or the built-in OpenLDAP user1
and user2.
Adding Corporate LDAP Configuration

After AppCenter is installed on Vantage, the root user can complete configuration that enables users to log
in, create scripts, run jobs, view and share results, and so on. See Teradata AppCenter User Guide, Version
1.8 or later.
2. Select > Settings > Authentication.
3. Select , then complete the following LDAP configuration fields:
Setting Type Required Fields Optional Fields
Server and Base Domain • Server

• URL
• Port
• Base domain
• Domain search user
• Domain search password
• Vendor
• User object classes
User Service Column Names • ID Field • Group Base

• Name Field • Group Id
• Member Field
• Email Field
For an LDAP configuration example, see Adding LDAP Configurations in Teradata AppCenter User
Guide, Version 1.8 or later.
Adding a User

Root users and administrators can add other users who are part of a configured LDAP domain and optionally
promote them to an administrator. You cannot remove a user once they have been added. For purposes
of initial configuration, add yourself or another user for whom you have username and password LDAP
credentials, or built-in OpenLDAP users.
1. Log on to AppCenter as root user or administrator.
2. Select > Manage Users > ADD USERS.
3. Type any part of the user's credentials, then select SEARCH & IMPORT.
Note:
If you are using built-in OpenLDAP, type user
AppCenter searches for and adds the users. In the case of built-in OpenLDAP,AppCenter adds user1
and user2.
4. Select CLOSE.
Note:
If you are using built-in OpenLDAP, you cannot add additional users.
Creating a Teradata System

Systems are databases or file systems from which scripts query data and provide results that answer
business questions. AppCenter supports Teradata, Aster Database, and Hive systems. The root user must
first create systems for users to select when creating or running scripts. For initial configuration, create a
Teradata system. For assistance with the associated settings, contact your DBA.
2. Select > Manage Systems > , then complete configuration:
Required Optional
Considerations
Fields Fields
Name • Enter a name that will identify this system for you.
• Name appears in a drop-down option when running the script.
System Type • Select TERADATA.
Host • For Vantage clusters with limited CLAN connections, use the host:
teradata-sqlengine.td-platform.svc.cluster.local
• For other clusters, use the Teradata host domain or IP address.
Port • Unless otherwise advised by your DBA, enter the default port 1025.
Database • If you do not specify a database, AppCenter uses the default

database for the user specified.

Required Optional
Considerations
Fields Fields
Username
Password
For information about creating Aster and Hive systems, see Creating Systems in Teradata AppCenter
User Guide, Version 1.8 or later.
3. For System Type, select TERADATA
4. Select TEST CONNECTION > SAVE.
AppCenter saves the system and opens the list of all existing systems.
5. [Optional] To edit or delete a system, select in the system card.
Configuring an SMTP Email Account for Notifications

Root users can add an external SMTP email account so AppCenter will send notifications to users about
script and job activity, including permission changes.
2. Select > Settings > Notifications.
3. Select CONFIGURE, then complete the account configuration:
Setting Required Fields Optional Fields
Email Configuration • Server Address

• Port
• Reply Address
• SMTP Username
Appears and required if Anonymous Logon is off.
• SMTP Password
Appears and required if Anonymous Logon is off.
Advanced • Server Timeout • Anonymous Logon

Configuration • Use SSL
When the email account is configured, AppCenter sends the following notifications:
Activity Notification Recipients
Job execution status Job owner
Shared job result Selected users
Script update Other script owners
Script ownership changes Users added or removed
Script comments submitted Other script owners

Logging on to AppCenter as an LDAP or OpenLDAP User

1. Log off of AppCenter as root user.
2. Log on to AppCenter with LDAP or built-in OpenLDAP credentials.
Note:
For built-in OpenLDAP, the password for user1 is user1 and the password for user2 is user2.
Successful login confirms LDAP or built-in OpenLDAP configuration.

To learn about differences among user types, including who can do what, see User Roles in Teradata
For information about promoting users to administrators, see Modifying User Permissions in Teradata
Creating a Script
Once you have LDAP configured and the Teradata system configured, you are ready to create your first
script.
Note:
Built-in OpenLDAP is provided for testing purposes only, not production
1. Log on to AppCenter as a regular user, administrator, or built-in OpenLDAP user.

2. Follow the instructions for Creating Scripts in Teradata AppCenter User Guide, Version 1.8 or later.
For an end-to-end example of how users or administrators can create a script that visualizes data in a
Sankey diagram, see Create an SQL Script with a Visualization (with Video) in Teradata AppCenter
User Guide, version 1.8.

8
Backup and Restore
Advanced SQL Engine

For Advanced SQL Engine, backup and restore is performed using the DSA application. DSA is accessed
through Teradata Viewpoint, using the BAR Setup configuration portlet and BAR Operations portlet.
DSA is not an installed component of Vantage. You must have an existing DSA environment that points
to the Advanced SQL Engine instance as a monitored system. For information on configuring your existing
DSA environment to work with Advanced SQL Engine, see:
• Teradata® DSA - DSE for Veritas NetBackup Installation, Configuration, and Upgrade Guide,
B035-3151
• Teradata® DSA - DSE for IBM Spectrum Protect Installation, Configuration, and Upgrade Guide,
B035-3155
• Teradata® DSA - DSU Installation, Configuration, and Upgrade Guide, B035-3153
• Teradata® DSA - DSE for IBM Spectrum Protect Installation, Configuration, and Upgrade Guide,
B035-3155
For information on backing up and restoring your database, managing the DSC repository, and using other
features of DSA, see Teradata® Data Stream Architecture User Guide, B035-3150.
Viewpoint
For information about backing up and restoring Viewpoint, see Teradata® Viewpoint Installation,
Configuration, and Upgrade Guide for Customers, B035-2207.
AppCenter
Contact your Teradata Customer Support representative to initiate backup and restore of AppCenter .
Machine Learning Engine

Backup and restore for Machine Learning Engine is not supported for this release. If you have questions,
contact your Teradata representative.
QueryGrid
Contact your Teradata Customer Support representative to initiate backup and restore of QueryGrid.

9
Security Overview
Vantage Component Security

Vantage
Security Overview
Component
Advanced See the rest of this section (starting at Vantage Security Overview) for an overview of
SQL Engine Advanced SQL Engine security.
Machine • Access to Teradata Machine Learning Engine analytic functions is controlled by

Learning permissions on the coprocessor foreign server object and by permissions on individual
Engine function mappings.
• Users on Machine Learning Engine are automatically provisioned on first access:
◦ Users are automatically given their own private schema
◦ Data is not shared between users on Machine Learning Engine
◦ Data does not persist within the Machine Learning Engine
See Teradata Vantage™ User Guide, B700-4002.
QueryGrid • HTTPS based connections to QueryGrid Manager (TLSv1.2)

• Communication policies can be defined at different security levels for data transfers
between the initiating connector (the connector starting the query) and the target
connector (the connector receiving the query). Security levels can be set for
authentication, integrity, and encryption
• Fabric supports encryption over the wire
• Fabric communications between Advanced SQL Engine and Machine Learning Engine
are authenticated
• Fabric supports LAN and WAN communication policies
◦ LAN Policy – Enables key based authentication, credentials are encrypted using
AES-128 encryption standard
◦ WAN Policy – Enables key based authentication, both credentials and data are
encrypted using AES-256 encryption standard
• Permissions in Viewpoint restrict the users who can modify the QueryGrid configuration
See Teradata® QueryGrid™ Installation and User Guide, B035-5991.
Viewpoint • Connections to portlets are secured using HTTPS (TLSv1.2)

• Authentication and encryption (with certificates) enabled for Viewpoint services:
◦ DCS, ActiveMQ, Postgres, tdNotification
• External users are managed by connected LDAP servers:
◦ LDAP authentication and group authorization
• Enhanced password controls for local users
• Automatic log off after a period of inactivity
• Portlet access is controlled at different levels by setting permissions for Viewpoint users:
◦ Global, Role, User
• Role-based permissions are applied for different categories of users
• Access logging

9: Security Overview
Vantage
Security Overview
Component
See Teradata® Viewpoint User Guide, B035-2206.
AppCenter • AppCenter uses the corporate LDAP directory for user authentication to AppCenter, and
also supports LDAP domains.
• In AppCenter, a role is assigned to each user that is imported from LDAP. User roles
determine privileges. The roles are:
◦ Standard users, Admins, Root users
• App and script permissions control access to an app or script
• Job Results Privacy settings control access to an app or script job result
• Support for configuring scripts with service accounts
• Integration with Service Mesh
• Appctl encrypt/decrypt functionality for charts
• Single sign-on (SSO) mechanism using JSON Web Tokens
See Teradata® AppCenter User Guide, B035-1111.
Kubernetes/ Containerized Vantage components deployed in hardened Kubernetes pods:

Docker • Disabled deployment of Kubernetes Dashboard
• Removed all unneeded objects
• Pod Security Groups implemented
• Roles and RoleBindings implemented to support Pod security policies
• Tightened permissions on local Kube account
• Disable anonymous access to the Kubelet
• Insecure bind address is removed on all masters
• Audit policies created on all masters
Vantage Security Overview

Vantage security is based on the following concepts.
Security Element Description
User An individual or group of individuals represented by a single user identity
Privileges Database privileges explicitly or automatically granted to a user or database
Logon Process of submitting user credentials when requesting access to the database
Authentication Process by which the user identified in the logon is verified
Authorization Process that determines the database privileges available to the user
Security Mechanism Method that provides specific authentication, confidentiality, and integrity services
for a database session

Security Element Description
Network Traffic Process for protecting message traffic between the database and mainframe-
Protection attached and workstation-attached clients against interception, theft, or other form
of attack
Message Integrity Checks data sent across the network against what was received to make sure no
data was lost or changed
Access Logs Logs that provide the history of users accessing the database and the database
objects accessed
See Teradata Vantage™ - Advanced SQL Engine Security Administration, B035-1100.
Users
Users that access Vantage must be defined in the database or a supported directory.
Directory Management of Users

Normally, users that log on to Vantage have been defined in the database using CREATE USER. However,
because many potential database users may already be defined in a directory running within the client
network, Vantage allows for authentication and authorization of users by supported directories. Vantage
can autoprovision a database user object upon first LDAP authentication.
See Teradata Vantage™ - Advanced SQL Engine Security Administration, B035-1100.
Supported Directories
Vantage is certified for use with any LDAPv3 compliant directory server.
Vantage Privileges
Users can access only the database objects (databases, tables, views, macros, procedures, and so on) for
which they have privileges. The following table lists the types of privileges and describes how they are
acquired by a user.
Privilege Description
Implicit Privileges implicitly granted by the database to the owner of the space in which
(Ownership) database objects are created.
Automatic Privileges automatically provided by the system to:

• The creator of a database, user, or other database object.
• A newly created user or database.
Inherited Privileges that are passed on indirectly to a user based on its relationship to another
user or role to which the privileges were granted directly.

Privilege Description
Explicit (GRANT) Privileges granted explicitly to a user or database in one of the following ways:
• GRANT directly to a user or database.
• GRANT to a role, then GRANT the role to one or more users.
Roles, external roles, and profiles are used to assign privileges to users.
Type Description
Roles Roles are used to define privileges on database objects for groups of users with similar needs,
rather than granting the privileges to individual users. Roles require less dictionary space
than individually granted privileges.
External External roles are used to assign privileges to directory users because those users do not
Roles exist in the database.
Profiles To simplify user management, an administrator can define a profile and assign it to a group
of users who share similar values for the following types of parameters:
• Default database assignment
• Account strings permitted
• Password security attributes
User Authentication
When logging on to Vantage, users are authenticated, meaning their identity is verified and checked against
a list of approved users. Users are authenticated by Vantage or authenticated externally.
Vantage Authentication by Vantage requires that the user and its privileges are defined in the
Authentication database.
External External authentication allows Vantage users to be authenticated by an agent running

Authentication on the same network as Vantage and its clients.
Vantage supports the following external authentication logon types:
• Single sign-on (SSO)
• Directory sign-on (authentication by the directory server)
• Sign-on As (user logs on to Vantage with credentials the client also recognizes)
For additional information, see Teradata Vantage™ - Advanced SQL Engine Security Administration,
B035-1100.
User Authorization
Once users have been authenticated, they are authorized database privileges according to their defined
privileges.

Authorization of Permanent Vantage Users

Permanent Vantage users are defined in the database with a CREATE USER statement. Once
authenticated at logon, permanent users are authorized privileges in one of the following ways:
• By a GRANT statement
• Indirectly (inherited from another user or role)
• By the role the user is assigned
Authorization of Directory-Based Users

After being authenticated by the directory, directory-based users are authorized database access
privileges according to the following rules:
• If the directory maps users to database objects (users, external roles, and profiles), each directory
user is authorized the privileges of the objects to which it is mapped.
• If the directory does not map users to database objects, but the directory username matches a
database username, the directory user is authorized all the privileges belonging to the matching
database user.
• If a directory user is neither mapped to any database objects, nor does the directory username match
a database username, the directory user has no privileges to access the database.
Note:
One or more setup tasks (depending on implementation) must be completed before a directory user
can access the database. See Teradata Vantage™ - Advanced SQL Engine Security
Administration, B035-1100.
Authorization of Middle-Tier Application Users

Middle-tier applications stand between end users and Vantage, accepting requests from users,
constructing queries from those requests, passing the queries to the database, and then returning results
to the users. The middle-tier application logs on to the database, is authenticated as a permanent database
user, and establishes a connection pool. The application then authenticates the individual application end
users, some of whom may request access to the database through the connection pool.
For sites that require end users to be individually identified, authorized, and audited, the middle-tier
application can be configured to offer trusted sessions.
By default, all end-users accessing the database through a middle-tier application are authorized database
privileges and are audited in access logs, based on the single permanent database user identity of the
application.
Data Protection

Vantage provides the following features to enhance data protection:

• By default, the logon string is encrypted to maintain the confidentiality of the username and password
used to log on.
• Optional data encryption of messages maintains confidentiality of the data transmitted to and from
Vantage.
• Automatic integrity checking insures that the data is not corrupted during the encryption/transmission/
decryption cycle.
• Optional BAR and DSA encryption provides confidentiality of data backups between the BAR server
and the storage device.
• Optional SSL/TLS protection for systems using LDAP authentication with simple binding, including:
◦ Encryption of the LDAP authentication sequence between Vantage and the directory server.
◦ Advanced TLS protection, which requires that Vantage authenticate itself to the directory or that
Vantage and the directory mutually authenticate.
Vantage Security Monitoring

To ensure optimal database security, the security administrator should configure the system to audit security
events, then monitor the logs to detect breaches in security and, where necessary, repel security threats.
If unauthorized or undesirable activity is detected, the administrator can take remedial actions to address
the problem.
Vantage monitors and logs system accesses by database users, directory users, and middle-tier
application users.
Logon information, such as the username, session number, and unsuccessful logons, is stored in
DBC.LogOnOffV.
Optionally, access information, such as type of access, type of request, username, referenced database
object, and frequency of access is logged to the DBC.AccessLogV view.
See Teradata Vantage™ Data Dictionary, B035-1092.
Security Policy
It is possible to define security policy to:
• Restrict users to authentication mechanisms
• Enforce Quality of Protection (QoP) standards with network encryption

10
Analytic Tools
The following table lists analytic tools that provide access to Vantage along with links to installation and user
guides.
Analytic
Description References
Tool
AppCenter AppCenter is a web-based platform that allows you to create, Teradata AppCenter User
share, and use custom apps and scripts to query data on Guide
Vantage ( Advanced SQL Engine and Machine Learning
Engine) and Hive systems. You can also create helpful
visualizations.
AppCenter is useful to developers who build, share, and deploy
analytical use cases and also non-technical users who run apps
and scripts, study job results data, and share insights.
BTEQ Basic Teradata Query (BTEQ) is a general-purpose, command- • Basic Teradata Query
based program that enables users on a workstation to (BTEQ) Installation
communicate with one or more Vantage systems, and to format • Basic Teradata Query
reports for both print and screen output. Use BTEQ to submit Reference
SQL queries to Vantage. BTEQ formats the results and returns
them to the screen, a file, or to a designated printer.
Database Teradata DBW allows database administrators, system Teradata Database Window
Window operators, and support personnel to control the operation of
Advanced SQL Engine.
DBW is also the primary vehicle for starting and controlling the
operation of Advanced SQL Engine utilities.
Jupyter Jupyter is an open source set of standards for interactive • Teradata Vantage™
computing across dozens of programming languages. Jupyter Modules for Jupyter
Notebooks is an open-source web application that allows you Installation Guide,
to create and share documents that contain live code, B700-4010
equations, visualizations, and narrative text. Teradata provides • With the Teradata Python
a set of Jupyter extensions that facilitates using Jupyter with Package you can execute
Teradata Vantage. This set of extensions must be installed on Python statements on
your Jupyter instance. Vantage from a
Sample SQL and Python notebooks and additional information JupyterLab notebook.
about using the SQL extension for Jupyter can be found at: For information about
https://teradata.github.io/jupyterextensions/. using the Teradata
Python Package, see the
following documents:
◦ Teradata Python
Package User Guide,
B700-4006
◦ Teradata Python
Package Function
Reference, B700-4008

10: Analytic Tools
Analytic
Description References
Tool
Note:
If performing a manual
installation, see
Teradata Python
Package User Guide,
B700-4006.
RStudio RStudio is an IDE for R. In addition to a console and editor, • https://db.rstudio.com/

RStudio includes tools for plotting, history, debugging, and databases/teradata/
workspace management. • https://downloads.
teradata.com/download/
connectivity
Studio Teradata Studio is a client-based graphical interface for • Teradata Studio

performing database administration, query development, and Installation
management tasks on Vantage (Advanced SQL Engine, • Studio User Guide
Machine Learning Engine) and Hadoop systems.
Teradata Studio is built on the Eclipse Rich Client Platform
(RCP) framework to build and deploy native GUI applications.
It extends the Eclipse Data Tools Platform (DTP) to provide
enhancements for accessing objects and data stored in
Teradata-supported databases.
Teradata Studio supports the Teradata Unified Data
Architecture (UDA) by integrating administration, data
management and transfer, and SQL query development
across the Vantage and Hadoop platforms.
TPT Teradata Parallel Transporter (TPT) is an object-oriented client Teradata Parallel

application that provides scalable, high-speed, parallel data for Transporter (TPT) User
extraction, loading, and updating data. These functions can be Guide
extended with customizations or with third-party products.
TPT uses and expands on the functionality of the traditional
Teradata extract and load utilities such as FastLoad, MultiLoad,
FastExport, and TPump, collectively referred to as standalone
utilities.
Viewpoint The Viewpoint portal is a framework where web-based • Teradata Viewpoint

applications, known as portlets, are displayed. IT professionals Installation,
and business users can customize their portlets to manage and Configuration, and
monitor their Teradata systems using a web browser. Upgrade Guide
Portlets enable users across an enterprise to customize tasks • Teradata Viewpoint User
and display options to their specific business needs. You can Guide
view current data, run queries, and make timely business
decisions, reducing the database administrator workload by
allowing you to manage your work independently. Portlets are
added to a portal page using the Add Content screen. The
Viewpoint administrator configures access to portlets based on
your role.

11
Analytic Languages
The following table lists supported analytic languages for Vantage along with links to installation and user
guides.
Application Description References
Python Teradata provides an SQL driver and an analytic library for Teradata Python package:
Python that can be loaded into the client Python • Installation: See Teradata
environment. These packages allow you to develop Python Package User Guide.
Python scripts that access data in the Vantage system • Functions: See Teradata
and run Vantage analytic functions. Vantage also allows Python Package Function
execution of Python scripts on the server. Reference
The Python library package teradataml uses
SQLAlchemy and works with verbs and functions of
Pandas library.
R Teradata provides an ODBC driver and an analytic library Teradata R package:

for R that can be loaded into the client R environment. • Installation: See Teradata R
These packages allow you to develop R scripts that access Package User Guide
data in the Vantage system and run Vantage analytic • Functions: See Teradata R
functions. Vantage also allows execution of R scripts on Package Function Reference
the server through the ExecR system table operator.
The R library package tdplyr conforms and works with
the verbs and functions of the dplyr and dbplyr libraries.
SQL Analytic functions can be called from SQL. The analytic Analytic functions:
functions run in-database on Advanced SQL Engine or on • Teradata Vantage™ -
Machine Learning Engine. Advanced SQL Engine
Analytic Functions,
B035-1206
• Teradata Vantage™ Machine
Learning Engine Analytic
Function Reference,
B700-4003

A
Additional Information
Users
Teradata Vantage documentation refers to users to indicate who might perform a task we describe. Your
organization may use different names for these users.
Use this table to clarify the skill set Teradata assigns to each user.
User Typical Responsibilities
System Administrator / IT Specialist • Monitors and manages systems and applications

• Configures and integrates new technologies
• Configures and monitors system security
• Performs installation activities
Database Administrator (DBA) • Administers and maintains the Vantage system and connections
• Controls optimization, workload, and security
• Plans and supports installation activities
Data Scientist • Builds analytic models and solutions

• Delivers insights for customer journey
• Prepares, moves, and samples data in a secure environment
Business Analyst • Solves critical business issues and measures business value
• Studies business requirements and use cases
• Converts business needs into IT plans
Teradata Links
Link Description
https://docs.teradata.com/ Teradata documentation (HTML)
https://www.info.teradata.com Teradata documentation (PDF)
https://access.teradata.com One-stop source for Teradata community support, software

downloads, and product information.
Log in for customer access to:
• Community support
• Software updates
• Knowledge articles
• Orange Books
https://www.teradata.com/products-and-services/TEN Teradata education network

A: Additional Information
Link Description
https://community.teradata.com Link to Teradata community (also available from the customer

portal)

Configuring Teradata Vantage™ After Installation

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuring Teradata Vantage™ After Installation

Uploaded by

Copyright:

Available Formats

Configuring Teradata Vantage™

Safety type Description

Chapter 1: You Are Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2: Configure and Validate Vantage Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3: Configure NewSQL Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 4: Validate QueryGrid Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 6: Configure Teradata Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configuring Teradata Vantage™ After Installation, Release 1.1 3

Planning Worksheet for Teradata Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 7: Configure Teradata AppCenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 8: Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 9: Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 10: Analytic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 11: Analytic Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Appendix A: Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Configuring Teradata Vantage™ After Installation, Release 1.1 4

When you begin using this When you're done

Configuring Teradata Vantage™ After Installation, Release 1.1 5

Configuring Teradata Vantage™ After Installation, Release 1.1 6

Planning Worksheet for NewSQL Engine Configuration

Vantage system hostname Fully Qualified Domain Name (FQDN):

Domain Domain portion of the FQDN

Username DBC Database administrator default account

Password DBC user password

Site security policy

Recommended password Teradata recommends that passwords expire every 90

Password SYSDBA password

Logging on to Teradata Vantage Using BTEQ

Configuring Teradata Vantage™ After Installation, Release 1.1 7

Tips for Using BTEQ

Changing the Password for User DBC

Configuring Teradata Vantage™ After Installation, Release 1.1 8

2. In both sessions, type the default password, dbc.

Setting Up the Spool Reserve Database

Methods for Managing Space

Assigning Perm Space for Crashdumps

Configuring Teradata Vantage™ After Installation, Release 1.1 9

SQL Requests for Checking Space

To check... Run this request...

Total available disk SELECT SUM(MaxPerm) FROM DBC.DiskSpaceV;

Maximum database SELECT SUM(t3.Maxperm) FROM

Configuring Teradata Vantage™ After Installation, Release 1.1 10

To check... Run this request...

Database space: Select

Disk space currently SELECT SUM(CurrentPerm),

Spool space on Select

Users who are SELECT Databasename (format 'X(12)')

Percentage of SELECT Databasename (format 'X(12)')

Configuring Teradata Vantage™ After Installation, Release 1.1 11

To check... Run this request...

Users who are using SELECT databasename

Maximum allocated SELECT databasename, PeakAllocatedSpool from DBC.GlobalDBSpaceV;

Disk space for a SELECT SUM(currentperm)

Creating the SYSDBA Login

Configuring Teradata Vantage™ After Installation, Release 1.1 12

5. Provide SYSDBA with SELECT access on database SYS_Calendar. For example:

Creating Databases for Tables and Views

Configuring Teradata Vantage™ After Installation, Release 1.1 13

You can create a views database for each type of user:

Creating the Tables and Views Databases

Granting Role and Profile Privileges to SYSDBA

Configuring Teradata Vantage™ After Installation, Release 1.1 14

3. Grant administrative privileges for profiles to SYSDBA. For example:

Creating Administrative Roles and Profiles