Getting Started with Teradata Mapping Manager.pdf

Getting Started with

Teradata Mapping Manager (TMM)

July 2015

Teradata Mapping Manager is a licensed product of Teradata Corporation.

Teradata is a registered trademark of Teradata Corporation.

Microsoft and Windows are registered trademarks of Microsoft Corporation.

PENTIUM and PENTIUM PROCESSOR are registered trademarks of Intel Corporation.

Java and Java Runtime Environment are trademarks of Sun Microsystems, Inc. or its subsidiaries

in the United States and other countries.

ERwin is a registered trademark of CA, Inc.

VMware is a registered trademark of VMware, Inc.

It is the policy of Teradata Corporation to improve products as new technology, components,

software, and firmware become available. Teradata Corporation, therefore, reserves the right

to change specifications without prior notice.

All features, functions, and operations described herein may not be marketed by Teradata

Corporation in all parts of the world. Therefore, before using this document, consult your

Teradata representative or Teradata office for information that is applicable and current.

Copyright 2009-2015 by Teradata Corporation

Dayton, Ohio U.S.A.

All Rights Reserved

Confidential, Unpublished

Property of Teradata Corporation

Teradata Proprietary and Confidential

Getting Started with Teradata Mapping Manager (TMM)

July 2015 i Teradata Proprietary and Confidential

Table of Contents

Teradata Mapping Manager is a licensed product of Teradata Corporation. .. ii

Introduction ..................................................................................................... 1

How to Use This Guide ............................................................................................ 1

What is Teradata Mapping Manager? ...................................................................... 1

Who Should Use Teradata Mapping Manager? ....................................................... 2

Features .................................................................................................................... 2

What’s New in the Latest Point Release .................................................................. 3

Supported Languages and Character Sets ................................................................ 3

Localization of Graphical User Interface ............................................................. 3

Import and Export File Supported Languages and Character Sets ...................... 3

Help File Supported Languages and Character Sets ............................................ 3

Minimum System Requirements ..................................................................... 5

Performance Considerations .................................................................................... 5

Installing on PCs with Limited Disk Space ............................................................. 6

Install with Smallest Database Size ..................................................................... 6

Install on External Hard Drive ............................................................................. 6

Installing on PCs with Non-administrative Privileges ............................................. 6

Installing the Software ................................................................................... 10

Install and Set-Up Teradata Express ...................................................................... 10

Uninstall Previous Versions of Teradata Express .............................................. 10

Install Teradata Express ..................................................................................... 11

Restore Teradata Mapping Manager Repository ............................................... 11

Delete Sample Databases ................................................................................... 11

Install Teradata Mapping Manager ........................................................................ 13

User Rights ........................................................................................................ 13

Install Teradata Mapping Manager .................................................................... 14

Starting Teradata Mapping Manager for the First Time................................ 16

Start Teradata Database ......................................................................................... 16

Start Teradata Mapping Manager .......................................................................... 16

Create and Connect to a Repository ....................................................................... 16


July 2015 ii Teradata Proprietary and Confidential

Create a Project....................................................................................................... 20

Set Teradata Mapping Manager Preferences .......................................................... 23

Exit Teradata Mapping Manager ............................................................................ 25

Migrating from a Previous Version of Teradata Mapping Manager .............. 26

Migrating from Teradata Mapping Manager v1.0 or Later .................................... 26

Next Steps and Additional Resources ............................................................ 27

Documentation Resources ...................................................................................... 27

Sample Files ........................................................................................................... 27

Multiple Users ........................................................................................................ 27

Teradata Mapping Manager Concepts ........................................................... 28

What is a Data Representation? .............................................................................. 28

What is a Working Data Set? ................................................................................. 29

What is a Map Set? ................................................................................................. 29

What are Custom and System Properties? .............................................................. 30

What is Mapping Discovery? ................................................................................. 31

What is Cross-mapping? ......................................................................................... 32

Uninstalling the Software .............................................................................. 33

Uninstall Teradata Mapping Manager .................................................................... 33

Uninstall Teradata Express ..................................................................................... 33

Support ........................................................................................................... 34

Teradata Mapping Manager Help System .............................................................. 34

Known Problems and Workarounds ....................................................................... 34

Problems Fixed ....................................................................................................... 35

Contact Technical Support ..................................................................................... 36

Other Support Resources ........................................................................................ 36

Appendix A: Installing and Using Teradata Express for VMware ................ 38

Additional System Requirements for Teradata Express on VMware ..................... 38

Download and Install Tools and Utilities (TTU) ............................................... 39

Using TD Express/Linux Virtual Machine ............................................................. 39

Start Teradata ......................................................................................................... 40

Accessing Teradata from Host ............................................................................... 41

Stop Teradata/Virtual Machine .............................................................................. 42


July 2015 iii Teradata Proprietary and Confidential

Appendix B: How to Debug Problems Starting Teradata Mapping Manager43

Windows script host is missing on the client machine .......................................... 43

You do not have write permission to the My Documents folder and subfolders or

the disk is full ......................................................................................................... 44

Another instance of Teradata Mapping Manager is already running on the PC .... 44

Glossary ......................................................................................................... 46


July 2015 iv Teradata Proprietary and Confidential

Revision Record

Release Date Description

Release 1.0 September 30,

2009

First release.

Release 1.0.4 December 1, 2009 Patch release. Installation instructions

updated.

Release 1.0.6 January 5, 2010 Updated Supported Languages and Character

Sets

Release 1.1.1 April 30, 2010 Updated to reflect Teradata Mapping Manager

version 1.1.1 and support for Teradata

Express 13, including added instructions on

migrating to new versions of the software.

Release 1.2.0 November 9, 2010 Added “What’s New for 1.2,” which includes

mapping collaboration, additional detail on

finding JRE version number, and usability

improvements.

Release 1.2.3 January 12, 2011 Added information on performance

improvements to the “What’s New” and “Set

Teradata Mapping Manager Preferences”

sections. Also added new section on

“Migrating from a Previous Version of

Teradata Mapping Manager.”

Release 1.3.0 March 10, 2011 Added “What’s New for 1.3” and updated

other sections to reflect usability

improvements, new features, and other

changes.

Release 2.0.0 September 30,

2011

Added “What’s New for 2.0”.

Updated Supported Languages and Character

Sets to identify support for ANSI character set

in text fields and Windows 7.

Added Appendix A with installation

instructions for using Teradata Express for

VMware.

Release 2.0.1 February 22, 2012 Added reference to Teradata Developer

Exchange forum, updated Teradata branding,

updated “Create and Connect to a Repository”

section, added notes for non-administrator

users.


July 2015 v Teradata Proprietary and Confidential

Release 2.0.3 April 20, 2012 Removed instructions on installing Java

Runtime Environment (JRE) as this is now

installed with Teradata Mapping Manager.

Updated installation location for certain files,

uninstall information, and appendix B.

Release 2.1.0 October 2, 2012 Updated sections “Features”, “What’s New”,

and “Minimum System Requirements.”

Teradata Express 14 for VMware now

supported.

Release 2.1.4 March 18, 2013 Updated TD Express for VMware installation

instructions in appendix A.

Release 2.1.6 June 3, 2013 TDE for Windows is now only supported for

Win XP due to user problems with Win 7 32-

bit. Updated broken hyperlink to TDE for

Windows.

Release 2.2.0 April 2, 2014 Many changes to reflect new functionality and

to acknowledge that Windows 7 is now the

predominate operating system for Teradata PS

users.

Release 2.2.2 May, 2014 Updated the Tutorial document to sync with

2.2.0 changes and updated Back Readme

v4.pdf with instructions for backup/restore

using Arcmain for Linux in the Teradata

Express virtual machine.

Release 3.0.0 July 2015 Rewrote the Tutorial document to enhance it

based on user feedback, and to add 3.0.0

workbook functionality training. Added

TMM-support for Teradata Express 15.0 for

VMware.


Introduction

July 2015 1 Teradata Proprietary and Confidential

Introduction

This document provides a starting point for using Teradata Mapping Manager (TMM).

It provides an overview of TMM, install and uninstall instructions, setup instructions,

descriptions of key TMM concepts, and a glossary of terms.

How to Use This Guide

You should read through this “Introduction”, and then review the “Minimum System

Requirements” section to ensure your PC has enough resources to install and run

Teradata Mapping Manager and the required software. Then proceed to the “Quick

Start” section for guidance on how to use the rest of this document based on your

installation needs.

You can use the Table of Contents to quickly jump to a section of the document. Hold

your mouse over the page number, then hold the Control key down and click on the

page number.

The following typographical conventions are used in this document.

Format Meaning

Bold Names of interface labels for menus, buttons, and

dialog boxes, and dialog box controls.

term Italicized words are Teradata Mapping Manager

terms or other terms included in the glossary.

http://developer.teradata.com/ Hyperlinks

filename.ext Filenames

What is Teradata Mapping Manager?

Teradata Mapping Manager is a mapping tool for creating and maintaining data

mapping documentation. By providing an easy-to-use mapping interface, a relational

mapping metadata repository, and mapping functionality, this tool is intended to

reduce time to solution for building and supporting data warehouse architectures.

Design consumes much of the time in delivering a data warehouse project. Mapping

plays an important role in design work and in properly scoping development work.

Data mapping is usually a very labor-intensive and manual process.

Data mapping specifications are documented in various formats and are usually

hard to use beyond the context of a single project.

Data mapping documentation in a non-relational format limits analysis and reuse.

Most mapping tools are focused on use by developers rather than a broader

audience of data and requirements mappers, which may include less technical

users.


Introduction


Teradata Mapping Manager is designed to address all these issues, combining the

flexibility and ease-of-use of state-of-the-art spreadsheet applications with the power

and capabilities of a relational database. The tool provides easier mapping to industry

standards or for compliance, aids in accelerating data integration efforts, and allows

easier collaboration and re-use of mappings.

Note: Teradata Mapping Manager is not intended to replace ETL automation or ETL

code generation tools.

Who Should Use Teradata Mapping Manager?

Data modelers, data analysts, and others who create and use data mappings, such as

ETL developers and business analysts, can use Teradata Mapping Manager. It is

assumed you are familiar with using other Windows-based applications, data

modeling terminology and structures, and have experience creating or using some type

of data models.

You do not need to be familiar with physical data modeling nor have experience in

Teradata implementation such as SQL or ETL (extract, transform, load) development.

Features

Following is the list of features included in this release of Teradata Mapping Manager.

Flexible, easy-to-use interface for creating and managing mappings

Support for mapping notes to provide essential information to business analysts,

ETL developers, and others

Import data models, requirement lists, source system flat file structures, etc.

(called data representations) and, optionally, mappings between these data

representations. Import sources include ERwin and Excel and exports can be

viewed in Excel.

Support for mapping to and from data elements, data structures, subject areas,

literals (user-defined fixed value), and data representations.

Custom ERwin reports for creating import files for ERwin data models and PK to

FK mappings

Mapping gap identification

Mapping discovery using the Auto-Find Potential Mappings algorithms including

full string exact match, best match based on the longest common subsequence

algorithm, short-list mapping (select mapping destination from a short list of data

elements based on similar mappings) and cross-mapping (using existing mappings

to identify new mappings) to automatically find and create new mappings

Automatic copying of mappings when importing a new version of a data

representation


Introduction


Data representation and mapping metadata stored in a relational database, with a

set of published views of this metadata to enable user-defined reports, analysis,

connectors, etc.

Pre-defined mapping reports

Basic/simple SQL generation of INSERT…SELECT and REPLACE VIEW SQL

statements

Collaborative mapping using a shared networked Teradata server and application-

level features to protect against multi-user metadata corruption problems

Local mapping metadata storage using Teradata Express for Windows or

VMWare on your PC and remote/shared mapping and metadata storage using a

networked Teradata server

Acquisition layer generation of DDL, scripts and GCFR metadata registration to

quickly build and load a structured acquisition layer (requires ACQGen external

application/PS asset, only available for use by Teradata professional services

consultants)

What’s New in the Latest Point Release

See the following web page for a list of added features by point/patch release:

What's New in TMM (DevX)

Supported Languages and Character Sets

Localization of Graphical User Interface

In this release of Teradata Mapping Manager, all text fields support user input and

editing using the Win-1252/ANSI character set in addition to US-ASCII. Therefore,

single-byte character Western European languages are supported.

Localization is currently only supported for US English.

Double-byte character languages are not certified but should work. (we are looking for

a beta site to complete certification of this capability)

Import and Export File Supported Languages and Character Sets

Comma delimited (.csv) files are used for importing and exporting. The Win-

1252/ANSI character set, in addition to US-ASCII, is supported for importing,

therefore, single-byte character US and Western European languages are supported.

Double-byte character languages are not supported, although copy and paste of custom

property values should work.

The default csv separator character is a comma, however, you can change this in the

tool preferences for compatibility. For example, some Western European computers

use semi-colon list separators. Import templates are provided for both comma and

semi-colon separators.

Help File Supported Languages and Character Sets

Help files are in U.S. English.

http://developer.teradata.com/tools/reference/whats-new-in-tmm


Introduction



Minimum System Requirements



The pre-requisites and minimum system requirements for Teradata Mapping Manager

are as follows:

Pentium-class PC

Minimum of 1GB of memory for Win XP or 4 GB for Win 7.

Note: This minimum is for all configurations except when using Teradata Express

for VMware on your local PC, which requires a minimum of 4GB (for minimally

acceptable performance) or 8 GB (for better performance)

Teradata Express 13.0 for Windows, Teradata Express 13.10, 14.0, 14.10 or 15.00

for VMware, or remote connection to a Teradata 13, 14 or 15 Server

Notes:

- If your PC is running Win XP (SP 3), install Teradata Express 13.0 for

Windows for best local repository performance.

- If you already have Teradata Express 12 installed on your PC, you can use

this version.

- For collaborative mapping or to use Teradata Mapping Manager over a shared

network, get remote access to a Teradata 13, 14 or 15 server.

- See Appendix A for additional requirements for Teradata Express for

VMware.

Windows requirements:

- Windows 7 (32 bit or 64 bit) or Windows XP, Service Pack 3

Minimum of 115 MB of disk space for TMM

See the specific version of Teradata Express that you will be using for disk

requirements if installing it on your PC. The newer versions have larger minimum

virtual disk capacity which results in a much larger install footprint, so you may

want to use an older version. TDE 14.0 for VMware 4GB is a good choice (around

13.6 GB install footprint).

Performance Considerations

There are several things that can impact the performance of Teradata Mapping

Manager. These include using a remote instance of a Teradata Mapping Manager

repository, large amounts of data in the repository, many users of a repository, and

preference settings. See the following section in this document: Set Teradata Mapping

Manager Preferences, and the topic “Improving Performance” in the online help

(under “Introduction to Teradata Mapping Manager”) for important information on

how to get the best performance, especially for manual mapping operations.




Installing on PCs with Limited Disk Space

The following instructions assume you will be installing Teradata Express.

If you do not have enough disk space available on your hard drive, you can use a

smaller version of Teradata Express or purchase an external hard drive (or USB

“thumb” drive) and install Teradata Express for VMware on it (and Teradata Mapping

Manager too if the 115MB makes a difference).

Install with Smallest Database Size

If you choose the 512MB database size, you must delete unneeded databases from

Teradata Express to free up enough disk space to create a repository data base for

Teradata Mapping Manager. See the section Delete Sample Databases.

TD Express for VMware 14.0 is the newest version to offer a 4GB virtual disk space.

Newer versions start at 40GB which really drives up the install footprint. 14.0 is a

good choice if you have 13.6 GB of disk space or so.

Install on External Hard Drive

To install on an external hard drive, simply install each component and when

prompted, change the install directory to your external hard drive.

Note: If you install Teradata Express on an external hard drive, that hard drive must be

plugged into the computer when you boot up; otherwise, when you attempt to start up

the Teradata database, you will receive a message indicating that you need to re-boot.

Installing on PCs with Non-administrative Privileges

If you do not have administrative privileges on the PC you plan to install or use

Teradata Mapping Manager from, you should try to install Teradata Mapping Manager

to your \My Documents folder or another folder for which you have write permissions

(for example, \My Documents\Teradata Mapping Manager\Program Files). The install

wizard offers an option to change the default install location.

If you try to install or use Teradata Mapping Manager on a PC for which you do not

have administrator privileges or write permissions to the C:\Program Files folder, you

will receive an error message indicating certain files could not be written to the

C:\Program Files folder or that certain files could not be created. If you have already

installed Teradata Mapping Manager, then uninstall it and re-install it to your \My

Documents folder. If a user with administrative privileges installed the tool, they will

need to uninstall it.

Note: If you receive a similar error message, first ensure that your disk is not full as

that situation can produce similar error messages.

For many or most environments where a PC user is not allowed to login as a Windows

administrative user, the User Account Control settings, or some other security

policy/software, will not allow the user to run an install program even if the target

location is under you’re My Documents folder. In that situation, you may need to have

a Windows administrator install Teradata Mapping Manager for you using the full

explicit path to one of your my Documents folders (for program files), then make sure

you have appropriate permissions to the install files/folders..




If an administrator installs Teradata Mapping Manager for you, then you will be

logging into the PC with a different username to use Teradata Mapping Manager, then

the default local non-Program Files file storage will be under a My Documents folder

for the administrator and not for you. In this case, there is a feature under Tools >

Preferences > Startup tab that allows you to move the default non-Program Files file

storage location to a folder that you can read and write. Press the Change button on

this tab to activate this feature.

For more details on having an administrator install Teradata Mapping Manager for a

non-admin user, see the Teradata Mapping Manager in-application help topic:

“Introduction to Teradata Mapping Manager” > “Special instructions for using

TMM as Windows non-admin user”

...or Teradata employees can download this topic in white paper form from the

Teradata Mapping Manager sharepoint:

Using TMM as Windows non-admin user

https://teradatanet2.teradata.com/ps/tmm/_layouts/WordViewer.aspx?id=/ps/tmm/Shared_Documents/Using_TMM_as_non-admin_Windows_user.docx&Source=https%3A%2F%2Fteradatanet2%2Eteradata%2Ecom%2Fps%2Ftmm%2FShared%5FDocuments%2FForms%2FAllItems%2Easpx&DefaultItemOpen=1&DefaultItemOpen=1




Quick Start

Use the following table to determine how to proceed.

If you are: Then do the following:

Installing Teradata Express and

Teradata Mapping Manager for the

first time and you do not need

detailed instructions

Complete the steps in this section below.

Installing Teradata Mapping

Manager for the first time and you

want detailed instructions

Proceed to the section “Installing the

Software.”

Installing a new version of Teradata

Express and you have a previous

version installed

If you already have Teradata Express 12 for

Windows installed on your PC, it is not

necessary or recommended to upgrade to a

newer version of Teradata Express to use the

current version of Teradata Mapping Manager.

However, if you need to migrate to a newer

version of Teradata Express, see the

instructions in the user guide for that newer

version of Teradata Express - typically found

on Teradata Developer Exchange.

Installing a new version of Teradata

Mapping Manager and you have a

previous version installed

Uninstall the older version Teradata Mapping

Manager before installing the newer version.

Next, install the new version. When you start

Teradata Mapping Manager and connect to the

repository, the repository is automatically

migrated if necessary (after a confirmation

dialog).

See the section Migrating from a Previous

Version of Teradata Mapping Manager for

guidelines when you have multiple users of a

repository.




Complete the following steps if you are installing the software for the first time on a

Windows XP or Windows 7 system and do not need a step-by-step, detailed

walkthrough of the installation process. If you will be using Teradata over a shared

network, skip the first step regarding installing Teradata Express. If you encounter any

issues or need additional information for a particular step, see the section Installing the

Software.

1. If you do not already have Teradata installed on your PC and if you do not have

access to a networked Teradata server for use as a Teradata Mapping Manager

metadata repository, then install Teradata Express for VMware on your PC. See

Appendix A: Installing and Using Teradata Express for VMware for instructions.

2. To install Teradata Mapping Manager, go to Teradata Developer Exchange and

the Teradata Mapping Manager download page at

http://downloads.teradata.com/download/tools/teradata-mapping-manager.

3. Continue with the section Starting Teradata Mapping Manager for the First Time

to create and set up a repository database and tool preferences.

http://downloads.teradata.com/download/tools/teradata-mapping-manager


Installing the Software



To use Teradata Mapping Manager, you need a Teradata database and Teradata

Mapping Manager. Teradata Express provides you a local Teradata database. If you

will be using Teradata over a shared network, skip any instructions regarding Teradata

Express installation and setup.

Install and Set-Up Teradata Express

A Teradata database is required to use Teradata Mapping Manager. This database will

hold the Teradata Mapping Manager repository.

If you are only going to be using a pre-existing networked Teradata server for your

Teradata Mapping Manager repository, then you can skip the installation and set-up of

Teradata Express.

If you need to use Teradata Mapping Manager without connecting to a networked

Teradata Server, then you will need a TMM-supported version of Teradata Express

database installed on your PC. You could also install Teradata Express on a networked

system and use it as a shareable, networked Teradata server for the Teradata Mapping

Manager repository.

Notes:

If you already have Teradata Express 12 for Windows installed on your PC, it is

not necessary or recommended to upgrade to a newer version of Teradata Express

to use the current version of Teradata Mapping Manager.

Uninstall Previous Versions of Teradata Express

If you want to run Teradata Mapping Manager locally from your PC, you must use

either Teradata Express 13.0 for Windows (recommended and supported only if you

have Windows XP), Teradata Express 13.10, 14.0, 14.10 or 15.0 for VMware, or

Teradata Express 12 (Windows XP only). If you have a version of Teradata Express

prior to 12 installed, you should migrate to the recommended version.

To migrate to Teradata Express 13, 14 or 15, you must back up any repositories you

want to migrate, and then uninstall Teradata Express and the related Teradata Tools

and Utilities (TTU) before installing Teradata Express 13, 14 or 15. There may be

limitations on how many versions of Teradata Express you can migrate data from/to.

See the Teradata Express documentation if you need to do this, especially if you want

to skip 2 or more point releases (e.g. 13.10 to 15.0). Exit Teradata Mapping Manager

before backing up or restoring.

Important! Be sure to do the backup before you uninstall Teradata Express because

the uninstall process deletes the entire database.

1. Back up the Teradata Mapping Manager repository.

You need Teradata ARC and Teradata BTEQ, included with the Teradata Tools

and Utilities (TTU), to create and restore the archive. If you do not have these

installed, install the latest version.




Instructions and files for backing up and restoring the repository are located in the

following folder:

\My Documents\Teradata Mapping Manager\Backup

See the Backup Readme.pdf file for instructions.

Tip: It is also a good idea to export all of your mappings to csv file as an

emergency backup, in case the Teradata Express data migration has problems.

Also export your data representations if you do not already have import files for

them that represent the current state of the data representations.

2. Uninstall Teradata Express and the Teradata Tools and Utilities.

See your Teradata Express documentation for this. The location of this

documentation varies by release.

Install Teradata Express

The following versions of Teradata Express are supported as the database for Teradata

Mapping Manager’s repository:

1. Teradata Express 12.0 or 13.0 for Windows (only if already installed because the

install package is no longer available)

2. Teradata Express 13.10, 14.0, 14.10 or 15.0 for VMware. This is supported on

Windows XP (SP3) and Windows 7 (32-bit and 64 bit). See Appendix A: Installing

and Using Teradata Express for VMware for installation instructions.

Restore Teradata Mapping Manager Repository

If you backed up one or more Teradata Mapping Manager repositories from a previous

version of Teradata Express and you want to restore them for use with the new version

of Teradata Express, follow the instructions in the Backup Readme.pdf file located in

the following folder:

\My Documents\Teradata Mapping Manager\Backup

Or see the “Back Up and Restore a Repository” topic in the Teradata Mapping

Manager in-application help system under “Working with Repositories”.

Note: If you run into issues restoring the repository, see the Teradata Express

documentation for help.

Delete Sample Databases

If you installed Teradata Express and selected the database size of 256MB or 512MB,

you need to delete the sample databases to have enough space to create the Teradata

Mapping Manager repository. Also, if you restored multiple Teradata Mapping




Manager repositories, but have determined you no longer need one or more of them,

you can delete them to free up database space.

To delete the Teradata Express sample databases and unneeded Teradata Mapping

Manager repositories from the Teradata Express database, you can use Teradata

Administrator. This is included with the Teradata Tools and Utilities you installed

with Teradata Express. Complete the following steps:

1. Shut down Teradata Mapping Manager if it is running.

2. From the Windows Start menu, click All Programs, then Teradata

Administrator <X.X>.

Note: If the Windows Installer dialog box displays, just click Cancel. You may

need to do this multiple times.

3. In the Please Select a Data Source dialog box, select DEMOTDAT if it is not

already selected and click OK.

If DEMOTDAT does not exist, create it in Teradata Administrator as follows:

a. From the File menu, choose Define Data Source.

b. Click on the System DSN tab.

c. Click Add.

d. Scroll to the end of the list, select Teradata and click Finish.

e. Enter the following in each specified field:

Name: DEMOTDAT

Name(s) or IP Address(es): See appendix A or C for “Teradata IP

Address”, depending on the version of Teradata Express you are using.

Username: dbc

Password: dbc

f. Click OK.

g. Click Yes to the warning about storing passwords.

h. Click OK to close the ODBC Administrator dialog box.

4. Select Connect from the File menu.

5. Select DEMOTDAT from the list of data sources in the

Please Select a Data Source dialog.

6. Click OK. After a few seconds, the left pane displays.

7. In the left pane, expand the Samples database as shown

in the picture to the right.

8. Complete the following steps to delete a sample

database:

a. Select the database to delete (for example,

financial).




b. From the File menu, choose Drop All Objects in Database.

c. Click Delete in the Delete Database dialog box.

d. From the File menu, click Drop. Click Drop in the Drop Database dialog

box.

e. Repeat these steps for each database under Samples (manufacturing, retail,

tpch, and so on).

9. When you have deleted all the sample databases, select the Samples database,

then from the File menu, click Drop. Click Drop in the Drop Database dialog

box. This step frees up the needed space.

10. From the File menu, click Disconnect, then click Yes.

11. From the File menu, click Exit to close Teradata Administrator.

Install Teradata Mapping Manager

The Teradata Mapping Manager install program installs Teradata Mapping Manager

and the appropriate version of Java Runtime Environment (JRE). The JRE will be

installed under the C:\Program Files\ Teradata Mapping Manager\bin\java folder and

will only be used by Teradata Mapping Manager.

User Rights

The Teradata Mapping Manager installation assumes that you have Windows

administrative privileges. If you do not have full administrative Windows privileges,

then it is still possible to install and use the tool.

First, do the following:

During the Teradata Mapping Manager installation, select an installation folder

where you have read and write privileges. The folder \My Documents\Teradata

Mapping Manager\Program Files is recommended.

If this does not work (you receive error messages indicating that certain files could

not be created or that you do not have the appropriate permissions), check the

following:

Your login user must belong to the Windows “Users” group. You can verify this

by performing the following steps:

1. Right-click on My Computer or Computer on your desktop and select

Manage.

The Computer Management dialog box displays.

2. Expand folder in left pane tree named Local Users and Groups.

3. Double-click on the Groups folder to show groups in right pane.

4. Double-click on each of the following groups to show a list of users in that

group:

Administrators




Power Users

Users

Verify that your user is in one of the groups. (It is possible that other user

groups can install and use Teradata Mapping Manager, but we have not

verified it).

5. Close the Computer Management dialog box and any other dialog boxes

you opened.

You must have access to the Teradata database instance where Teradata Mapping

Manager will be storing its metadata. You can test this by using Teradata

Administrator to connect to that database. There are additional database privileges

that are required by Teradata Mapping Manager (see the in-application help topic

Working with Repositories > Create a Repository for details).

Install Teradata Mapping Manager

From the Teradata Mapping Manager download file you received, complete the

following steps:

1. Uninstall any previous version of Teradata Mapping Manager.

2. Run the Teradata Mapping Manager install program.

3. On the welcome screen, click Next.

4. Click I Agree to accept the license agreement.

5. Enter a destination folder:

If you have Windows administrative privileges, accept the default destination

folder or click Browse to select another (such as an external hard drive), then

click OK.

If you do not have Windows administrative privileges, click Browse and

create a folder under \My Documents (for example, \My Documents\Teradata

Mapping Manager\Program Files) or another folder for which you have write

permissions), then click OK.

6. Click Install.

The installation completes and gives you the option to open and read the Getting

Started with Teradata Mapping Manager guide (this document).

7. Click Yes to read or print the document; otherwise, click No.

8. If you want Teradata Mapping Manager to run automatically when you complete

the install, leave the option Run Teradata Mapping Manager checked.

Otherwise, uncheck this option so that Teradata Mapping Manager is not started

when the install completes. If the Teradata repository database is not running at

this point, then uncheck the option, finish the import wizard and start Teradata

before starting Teradata Mapping Manager.




Note: If you do not have the appropriate Windows administrative privileges, an

error message displays indicating certain files could not be created. See Installing

on PCs with Non-administrative Privileges.

9. Click Finish. Teradata Mapping Manager is now installed.

10. If you are installing Teradata Mapping Manager for the first time, continue with

the next section “Starting Teradata Mapping Manager for the First Time” to create

a repository.

If you are migrating from a previous version of Teradata Mapping Manager, see

the section Migrating from a Previous Version of Teradata Mapping Manager.


Starting Teradata Mapping Manager for the First Time


Starting Teradata Mapping Manager for the First

Time

If you installed Teradata Mapping Manager for the first time, complete the steps in

this section to create and connect to a Teradata database repository and set up the tool.

Start Teradata Database

At the end of the Teradata Mapping Manager install, there is an option set by default

to run Teradata Mapping Manager when the install completes. If you left this option

checked, Teradata Mapping Manager was started, but the Teradata database must be

started to continue. If you are using a remote Teradata Server, the database should

already be running, so you can skip to the next section.

If you are using Teradata Express for VMware, follow the instructions in this section

of Appendix A:

Using TD Express/Linux Virtual Machine

Continue following these instructions though the succeeding sections of Appendix A

until Teradata is started.

Start Teradata Mapping Manager

If Teradata Mapping Manager is not yet running, start it using either of the following

methods:

Double-click the desktop icon .

From the Windows Start menu, click the following:

Start > All Programs > Teradata Mapping Manager > Teradata Mapping

Manager

Warning! If you migrated to a new version of Teradata Mapping Manager, the next

time you connect to an existing repository, it will be migrated to the new version (with

a few exceptions where the macros and/or repository structure did not change). All

users of the database need to use a compatible version of the tool for a given

repository version. See the section, Migrating from a Previous Version of Teradata

Mapping Manager.

Note: If you receive an error message indicating certain files could not be created

when you try to start the tool, you may not have the appropriate Windows user

permissions. See Installing on PCs with Non-administrative Privileges.

Continue with the next section to create a repository.

Create and Connect to a Repository

You must create a repository to store all the data representations you import and the

mappings you create. If you are using Teradata Express on your local PC and want to




create a new repository database under the root, DBC database, (simplest

recommended configuration) complete the steps below.

For other configurations, such as creating a repository on a networked Teradata server

or creating a repository in Teradata Express under a database other than DBC, you can

also follow the steps below. If you need more information, refer to the help topic

“Create a Repository” in the in-application help system. To locate this topic, from the

Help menu, choose Help Topics, then in the Table of Contents, expand “Working

with Repositories”.

Notes:

If you installed Teradata Express with a database size of 512MB or smaller, you

must delete the sample databases that come with Teradata Express to have enough

space to create the repository for Teradata Mapping Manager. If you have not

done this already, complete the instructions in Delete Sample Databases.

If you want to connect to an existing repository created using Teradata Mapping

Manager instead of creating a new one, see Migrating from a Previous Version of

Teradata Mapping Manager.

To create a new repository and connect to it, complete the following steps:

1. If the Welcome to Teradata Mapping Manager dialog box is displayed, click

Create. If not, from the Tools menu, click Create Repository Database.

The Create Repository Database dialog box displays.

2. Unless you have been instructed to create the repository tables in an existing

database, select Create repository in a new database. This is the typical option

to use when creating a new repository.

If a database administrator, or someone else, has already created an empty

database to hold the repository tables for your Teradata Mapping Manager, select

Create repository in an existing database. Use this option with care as it will

delete all of the contents of the existing database.

The options that display in the dialog box depend on which option you select in

this step.




3. If you are creating a repository in a new database in Teradata Database Express,

enter the following information to use dbc as the parent database and

TMM_Repository (or other name as desired) as the new database name:

Name or IP Address: If using Teradata Express for Windows, then enter

127.0.0.1.

If using Teradata Express for VMware, then see the following section of

Appendix A for instructions to find the Teradata IP Address: Accessing

Teradata from Host.

If you are using a networked Teradata server, ask the database administrator

for the IP address, Teradata Process ID or DNS Name.

Authentication Method: Select ldap if using a networked Teradata server

that is using ldap authentication, else leave blank.

Existing Parent Database Name: dbc

Existing Parent Database Username: dbc

Parent Database Password: dbc

New Database Name: TMM_Repository

Authentication Method: Select ldap if using a networked Teradata server

that is using ldap authentication, else leave blank.

New or Existing Database Username: <user name>

Database Password: <password>

Confirm Database Password: <password>

If you want to create the repository database under a different parent database,

specify the IP address, database name, username, and password for that parent

database.

Important!

Make sure the Existing Parent Database User has the appropriate CREATE

and GRANT rights. By default, the Teradata Database Express root database

user, dbc, has these rights.

It is strongly recommended that the parent database not be a production

database used by another application or other users. The repository is a

metadata database. Teradata Mapping Manager’s use of this database is OLTP

(on-line transaction processing) in nature and uses a lot of resource locking to

protect the metadata from multi-user deadlocks or corruption. This sort of

OLTP application usage of a decision support data warehouse can cause

serious performance issues for the decision support applications.

4. In the Select Repository Size (Perm Space) section, select the size you want the

new repository to be using the following guidelines:

150 MB - Choose this option if you installed Teradata Express with a 256MB or

512MB database.




2000 MB - Choose this option if you installed Teradata Express with a 4GB or

larger database or you are using a different database instance with adequate

space.

User-Defined Value - Choose this option and enter a value (100MB minimum) if

you want to specify another size for the repository.

An example of a completed dialog box is shown below.

5. Click Create Repository. As the repository is created, the status is displayed in

the text box at the bottom of the dialog box.

Notes:

If you receive the following error message, there is not enough space to create

the repository:

Not enough perm space. The request to assign permanent space to create TMM repository is invalid.

Choose a smaller database size or delete the sample databases that came with

Teradata Express if you have not already done this. See the section Delete

Sample Databases. If you are trying to create a repository on a networked

server, contact the database administrator and request more perm space in the

parent database.

If you receive a message that the connection is not available, Teradata may

not be started. See Start Teradata Database if you have Teradata installed on




your local PC or contact your Teradata database administrator if you are using

a networked Teradata server.

If you receive a warning that you do not have the appropriate user rights, ask

your database administrator to give you the required rights. Click the Help

button in the warning dialog for more details. This help topic also discusses

some options where the database administrator creates an empty database and

Teradata Mapping Manager database users, so that you do not need the

database rights to create databases or users.

6. When complete, click OK. You are connected to the new repository.

Create a Project

After creating and connecting to a

repository, the Open Project dialog

box displays.

Note: This dialog box is also available

from the File menu, Open Project

option.

1. To create a new project, click New.

Note: You do not need to create a new project now; however, you can set a

preference to automatically open a project when Teradata Mapping Manager

starts. If you want to set that preference in the next section, create a project now.

Otherwise, click Cancel.




2. In the Project Editor, enter a name in the Project Name field. You can optionally

add a description for the project in Project Desc.

3. Click Add. A message box displays indicating the new project has been added to

the repository.

4. Click OK to close the message box.

5. If you want to connect to that project now, click on the Modify/Delete Project

tab, select the project you just created in the Project Name drop-down list and

click Open.

The Auto-Refresh Option dialog box displays.




6. Keep the default option to optimize performance, particularly if you have a remote

connection to the Teradata Mapping Manager repository.

Select the option Auto-Refresh DSW mapping counts and entire MSW after

each manual mapping operation if you want to see the results in the data set

windows (DSW) and map set windows (MSW) each time you create a mapping. It

can take several seconds or more to see the results of each mapping, depending on

the type of connection you have to the repository.

Check Do not show this message again if desired (you can change this option

selection under Tools > Preferences > Other). Click OK when you are finished.

7. Click Close to close the Project Editor.

Note: You can use the Project Editor to change the name of the project if desired.

To access the Project Editor, from the Edit menu, select Project Editor.

Teradata Mapping Manager has been successfully started for the first time. You

should see a window similar to the one below on your desktop if you did not open

a project.




The left side of the window is referred to as the Object Navigator and the right side of

the window is referred to as the task pane.

Set Teradata Mapping Manager Preferences

Teradata Mapping Manager allows you to set startup preferences as well as other

preferences to improve performance and make using the tool more effective for you.

To set these preferences, complete the following steps:

1. From the Tools menu, select Preferences.

2. Click the Startup tab.

3. In the Repository Connection area, if you want to have Teradata Mapping

Manager automatically connect to the repository on startup:

Check the option Auto-Connect to repository when opening tool

Enter the same connection information you entered when you created the

repository in a previous step.

Object Navigator task pane




4. In the Project Connection area, if you want a default project to be opened on

startup:

Check the option Open this project after connecting to repository.

From the Project Name list, select the project to open on startup.

Note: The Project Name list is not populated unless you are already

connected with the repository.

5. If you are using Teradata Express for VMware or accessing Teradata over a high

latency network, you may want to change preference settings that can affect the

performance of manual mapping operations. If so, click the Other tab, and change

the following default settings:




Auto-refresh DSW mapping counts and entire MSW after each manual

mapping operation – Uncheck this option to improve performance of manual

mapping operations.

Note: If you uncheck this option, you must click the Refresh Window

tool on the map set and data set windows after creating a mapping manually to

see the results in these windows.

Log SQL – It is recommended you keep this option checked. However, if you

notice that manually creating mappings takes too long, you can uncheck this

option to see if it noticeably improves performance.

See the topic “Improving Performance” in the help file (expand “Introduction to

Teradata Mapping Manager”) for more information on how to improve the

performance of Teradata Mapping Manager.

6. Click OK to save your changes.

Exit Teradata Mapping Manager

To close down Teradata Mapping Manager, do one of the following:

From the File menu, choose Exit.

Click the X in the upper right corner of the window.


Migrating from a Previous Version of Teradata Mapping Manager


Migrating from a Previous Version of Teradata

Mapping Manager

Migrating from Teradata Mapping Manager v1.0 or Later

If you are migrating from Teradata Mapping Manager v1.0 or later, then the next time

you start Teradata Mapping Manager and connect to a repository, Teradata Mapping

Manager attempts to automatically migrate the repository to the current version, after

you agree to the confirmation/warning dialog.

Warning! All users of the database will need to use a compatible version of the tool

for a given repository version. This repository migration may force other users to

upgrade their version of Teradata Mapping Manager.

Before migrating the repository, Teradata Mapping Manager queries Teradata to see if

there are other users connected to it. By default, Teradata Mapping Manager does not

migrate the repository if another user with a different database username is connected

to it. If there are non-Teradata Mapping Manager applications that remain connected

to the repository, you can ignore the users associated with each of these applications

by adding those user names to an Ignore Users list in the preferences. To do this,

complete the following steps:

1. Exit the migration confirmation/warning dialog box without migrating.

2. From the Tools menu, select Preferences.

3. Click the Ignore Users tab.

4. To add a user to ignore, in the first text box, enter the name of a user to ignore,

then click Add.

5. To remove a user from the list, in the bottom list box, select the username, then

click Remove.

6. When done, click OK.

7. To complete the migration, connect to the repository.

You can do this by exiting and restarting Teradata Mapping Manager if you have

preferences set to automatically connect to the repository on startup, or you can

choose the Establish Connection option from the Tools menu.


Next Steps and Additional Resources


Next Steps and Additional Resources

Documentation Resources

Now that you have completed initial setup of Teradata Mapping Manager, you should

review the following additional resources as needed.

Review this section: Teradata Mapping Manager Concepts to get a high-level

picture of how the tool is used and an understanding of some of the basic

terminology used.

Teradata Mapping Manager Tutorial – This document provides a tutorial that

teaches you the basic features of the tool. You can access this document from the

Help menu > Tutorial or from the Windows Start menu > All Programs >

Teradata Mapping Manager > Teradata Mapping Manager Tutorial.

Online help – Accessible from the Help menu, Help Topics option, the online

help provides detailed instructions on how to use the features and functions

available in the tool as well as best practices and mapping scenarios.

Methodology and best practices - See the topics in the help under “Introduction to

Teradata Mapping Manager” for guidelines on when to use the tool as part of a

data warehouse implementation, for a description of the mapping process using

Teradata Mapping Manager, for example mapping scenarios, guidelines on

optimizing tool performance, and other best practices.

“Glossary” – Refer to the glossary at the end of this document or in the online

help for definitions of terminology used by Teradata Mapping Manager.

Sample Files

The following sample files are available:

Tutorial sample import files – Sample data representation import template files are

installed to \My Document\Teradata Mapping Manager\Import Files\Sample Files

for your use with the tutorial.

Multiple Users

Teradata Mapping Manager supports multi-user collaboration. The Help file describes

the multi-user features and different scenarios for how collaboration can be used. The

help file also contains guidelines for setting up multiple users on remote instances of a

Teradata server. From the Help menu, choose Help Topics, then from the table of

contents, review the topics under Introduction to Teradata Mapping Manager >

Collaborative Mapping and Sharing of Mapping Content.


Teradata Mapping Manager Concepts



There are several terms and concepts that you need to understand before using

Teradata Mapping Manager. Let’s start by looking at the basics of the mapping

process.

To create mappings, you need specifications of the data models, requirement lists, or

other data files, such as source data flat files, that will be mapped to each other. These

are called data representations. For example, to map a data source (in flat file format)

to a logical data model (LDM), you need two data representations: the specification of

the source data flat file as well as the specification of the logical data model itself.

You import these data representations into the Teradata Mapping Manager repository,

then create working data sets from them to be used to create your mappings. You

assign one data representation as the origin and the other as the destination, then create

mappings between them.

There are several methods to create mappings, including manually creating mappings

or automatically finding and creating mappings through mapping discovery. Mapping

discovery uses various algorithms to identify potential mappings including simple

name match, longest common subsequence algorithm, short-list mapping (select a

mapping destination data element from a short list of elements derived based on

mappings from related origin elements or from parent data structure) and cross-

mapping (using existing A to B and B to C mappings to identify new A to C

mappings).

A map set contains a view of the mappings between two working data sets. You can

export one or more map sets to create a mapping specification; for example, for the

ETL developers. You can also create mapping reports that show mappings between

more than two working data sets to export for use by business analysts and others.

The following sections describe the italicized terms in more detail.

What is a Data Representation?

A data representation is a data model, such as an LDM or PDM, application data

model, or other data construct, such as a source data flat file, or list of requirements

used to represent how a related set of data or requirements is structured. A data

representation contains data structures such as entities, tables, or files and their

corresponding data elements such as attributes, columns, or fields, respectively. The




diagram below shows the two parts of a data representation (data structure and data

element) and examples of data representations.

A data representation may also contain subject areas, which are logical groupings of

data structures.

Data representations are imported into Teradata Mapping Manager to create working

data sets for mapping.

What is a Working Data Set?

A working data set is a view of an imported data representation that is configured

(displayed in a window, organized, sorted and filtered) to facilitate mapping. A

working data set is automatically created when you import a data representation. The

content of a working data set is displayed in a data set window as shown in the

following picture.

It is possible for multiple users to each have their own working data set “view” of an

imported data representation, each with their own set of columns displayed, sort

criteria and/or filter criteria, without the need to duplicate the data representation in

the metadata repository.

For example, a working data set for an imported LDM may be created and configured

to show selected columns (properties), such as Data Structure Name (entity name),

Data Element Name (attribute name), and Data Element Definition, in a specific order

with rows sorted by Data Structure Name and Data Element Name as shown in the

following picture.

What is a Map Set?

A map set contains a view of the individual repository mappings between two selected

working data sets. Each mapping relates two mapping objects, each of which can be a

data element, data structure, subject area, literal, or data representation. One or more




map sets and/or mapping reports could be exported to help create a mapping

specification.

The contents of a map set (properties of the origin and destination plus any custom

properties) are displayed in a map set window as shown below.

What are Custom and System Properties?

Properties include names, descriptions, and other types of information about the data

representations, subject areas, data structures, data elements, map sets, and other

objects stored in the repository. Properties are either system (defined by Teradata

Mapping Manager) or custom (defined by you). System properties are categorized as,

required or optional.

For example, a data structure has a required system property of Data Structure Name

and optional system properties of Subject Area Name, Data Structure Type Code, and

others. These are shown in the following picture of the Working Data Set Properties

dialog box.

Source System A Data Mode

Data Set A

Logical Model Subset Working Data Set A1

Logical Model Subset Working Data Set B1

Source System B Data Model

Data Set B

Mapping Set A Mapping Specification for Source A

Mapping Set B Mapping Specification for Source B

Origin Destination

Source System A Data Model

Working

Data Set A

Logical Data Model

Logical Data Model Source System B

Data Model Working

Data Set B

Working Data Set C

Mapping A1

Mapping A2

Mapping A3

Map Set A to C

Map Set B-C Mapping B1

Mapping B2 Mapping B3 Working

Data Set C




You can create custom properties for data representations, data structures, data

elements, and mappings to store relevant information to assist in creating and reusing

mappings. Following are some examples of how you could use custom properties.

For a logical data model you are importing, you could create a custom property

in the corresponding data representation import file called Structure Action

Status to indicate the status of each entity (Required, Not Required).

For the same logical data model you are importing, you could create a custom

property for categories used to group related logical data model attributes. You

could then use these categories along with criteria filters in the tool to facilitate

mapping.

What is Mapping Discovery?

Mapping discovery is a feature of Teradata Mapping Manager that finds potential

mappings between two data representations based on several algorithms, including

simple name matching between selected properties of the data representations. For

example, when mapping one version of a logical data model (LDM) to another to trace

lineage, many of the entity and attribute names may be exactly the same in both

versions. Teradata Mapping Manager can find these matches and then give you the

option to create those mappings or discard them. There is also a Best Match algorithm

that finds the closest property value matches between data structures and data

elements in two data representations.




What is Cross-mapping?

Cross-mapping is the process of generating mappings between two working data sets

not linked directly to each other using intermediate mappings. For example, if A is

mapped to B and B is mapped to C, then Teradata Mapping Manager can use cross-

mapping to map A to C.

In Teradata Mapping Manager, cross-mapping is one of the methods used by the

mapping discovery feature.


Uninstalling the Software


Uninstalling the Software

Uninstall Teradata Mapping Manager

Run the uninstall from either of the following locations:

Windows Start menu > All Programs > Teradata Mapping Manager >

Uninstall Teradata Mapping Manager

Windows Control Panel

Uninstall Teradata Express

If you want to archive a copy of the Teradata Mapping Manager repository for future

use, back up the database before you uninstall Teradata Express. You can follow the

steps in Uninstall Previous Versions of Teradata Express earlier in this document for

instructions on uninstalling the current version as well.


Support


Support

Teradata Mapping Manager Help System

If you have questions about how to perform certain tasks in Teradata Mapping

Manager or are looking for best practices or mapping scenarios, refer to the Teradata

Mapping Manager help system or tutorial:

Select Help menu > Help Topics.

Select Help menu > Tutorial.

Known Problems and Workarounds

Problem: Nothing happens when you try to start Teradata Mapping Manager.

Workaround: See Appendix B “How to Debug Problems Starting TMM” for

suggested fixes and workarounds.

Problem: The default Java libraries ignore carriage return (0x0D, ASCII code

13) when rendering grids and/or text edit boxes. Also, a multi-line text string

using new-line (aka line feed, 0x0A, ASCII code 10) as line separator is not

fully rendered (only first line is rendered) in a grid cell unless auto-wrap is

turned on, although it is properly rendered in the multi-line grid edit dialog

box. It is believed that all other non-whitespace, non-printable characters will

be rendered as a square symbol in the user interface.

Workaround: For carriage return, there is no method to detect this character

using the Teradata Mapping Manager user interface, although the character is

properly stored in the metadata repository on import and is properly exported.

For new-line, you can do one of the following:

Hover your cursor over the grid cell containing a new-line, the tool-tip should

appear showing all lines of the grid cell.

Enable the “auto-wrap” option: open Tools > Preferences > Other and check

the option:

Enable word-wrap and auto-fit for all grid cells.

Double-click on the grid cell to open a grid edit dialog, which will properly

render the new-lines.

Problem: When copying NULL values from Excel, paste does not work

properly in all cases.


Support


Workaround: If you are copying a range of cells from Excel, and if the

bottom row has all blank/NULL values, then you paste this range of cells into a

Teradata Mapping Manager grid, the NULL row(s) at the bottom of the range

may be ignored. This appears to be a bug in the Java Runtime Environment so

there is no estimated fix date. The problem can occur if the range is a single

column wide or multiple columns wide. The workaround is to only copy ranges

from Excel that do not have all blanks cells in the bottom row.

Problem: When using ERwin Report Builder (ERwin 7.x) to export a data

element import file when the model has entities/tables with no

attributes/columns, the report output file will have row(s) with blank data

element name (required import field).

Workaround: 1) Use the Query Tool reports that are also provided with the Teradata

Mapping Manager installation OR

2) Either delete these rows from the import file or ignore the associated errors

generated by the import wizard. For more details, see the Help topic the help

topic “Using ERwin Report Builder to Create Data Representation Import

Files” under “Importing and Exporting > Using ERwin Reports to Create

Import Files”.

Problem: When using ERwin Report Builder (ERwin 7.x) to export a data

structure to subject area import file when the model has subject areas with no

entities/tables, the report output file will have row(s) with blank data structure

name (required import field).

Workaround: 1) Use the Query Tool reports that are also provided with the Teradata

Mapping Manager installation OR

2) Either delete these rows from the import file or ignore the associated errors

generated by the import wizard. See the help topic “Using ERwin Report

Builder to Create Data Representation Import Files” under “Importing and

Exporting > Using ERwin Reports to Create Import Files” for more details.

Problems Fixed

For a complete list of new features and problems fixed, see the What’s New in TMM

document online at:




Support


Contact Technical Support

For Teradata employees needing technical support with Teradata Mapping Manager,

send an email to:

TMM, Support (from Teradata internal address book)

For others, search topics or create a new topic on the Tools forum on Teradata

Developer Exchange to get help, report problems, and ask questions. Following is the

Tools forum Website:

http://forums.teradata.com/forum/tools

If you do not already have a Teradata-Pass (T-Pass) user authorization, you are asked

to register.

You may be asked for the version and build numbers of the software. See the

following sections for instructions on how to find the version numbers.

Note: Teradata Mapping Manager has been developed as a productivity tool for

Teradata Professional Services consultants, so we provide direct developer-level

support to them to ensure that they can get the appropriate level of urgent software

support when working on paid consulting engagements. We provide this tool to others

without a license fee but also without our normal support and maintenance offerings.

The Teradata Developer Exchange forum is the typical support channel for tools like

this that Teradata makes available without standard support and maintenance

offerings. If urgent software problem support is needed, you could ask your local

Teradata account team if you can hire Teradata professional services to provide this

support. The PS consultant will have direct developer-level support for problems that

cannot be solved without escalation.

Find Teradata Mapping Manager Version

To find the version of Teradata Mapping Manager you have installed, do one of the

following:

From the main window of the tool, click the About Teradata Mapping

Manager tool on the toolbar.

From the Help menu, choose About Teradata Mapping Manager.

Find Teradata Express Version

For Teradata Express, you need the version of the database and not the Teradata Tools

and Utilities (TTU), which may be different. If you are unsure which version of

Teradata Express you have, you can browse DBCInfoTbl, or search the systeminfo.log

file mentioned above for “Database Version” (search from end of systeminfo.log file

in the up-direction to find the version of the last database you accessed)..

Other Support Resources




Support


For Teradata Express for VMware User Guide, see this forum post if it is

still available:

http://developer.teradata.com/database/articles/teradata-express-14-0-for-

vmware-user-guide

Otherwise, Teradata Express development team indicates that users

should post support questions to the Cloud Computing forum on

Teradata Developer Exchange:

http://forums.teradata.com/forum

If you have problems finding the IP address for Teradata for VMware, and the tips in

this section of Appendix A did not help: Accessing Teradata from Host, then it is

recommended that you check the posts on this Cloud Computing community support

forum for Teradata Express for VMware and/or post your issue on that forum. Test

your connection problem using Teradata Studio and mention that application when

describing your connection issue.

http://developer.teradata.com/database/articles/teradata-express-14-0-for-vmware-user-guide


http://forums.teradata.com/forum


Appendix A: Installing and Using Teradata Express for VMware


Appendix A: Installing and Using Teradata

Express for VMware

This appendix contains instructions for installing and using the Teradata Express

13.10, 14.0, 14.10 or 15.0 for VMware. These instructions are targeted for Teradata

Mapping Manager (TMM) users who want to use Teradata Express (TDE) for

VMware on their local PC for the Teradata Mapping Manager repository.

Additional System Requirements for Teradata Express on

VMware

Following are the system requirements in addition to those specified in the section

“Minimum System Requirements” for running Teradata Mapping Manager with

Teradata Express for VMware.

CPU must support 64-bit operation and virtualization

VMware Player (free evaluation version available), VMware Workstation or

VMware Server

13GB disk space (minimum) for installation of 4GB version of Teradata

Express (14.0). Lesser amounts of disk space required for earlier versions.

4 GB minimum of system RAM for poor performance or 8 GB recommended

for decent performance. The 4GB minimum is based on our experience

running TDE 13.10 and 14.0 versions for VMware on a Windows 7 PC,

allocating 2GB to VMware. 8GB (4GB allocated to VMware) gives a

noticeable performance improvement, but is still a lot slower than using non-

VMware-based Teradata over a fast network connection.

See the following link for an introduction to Teradata Express for VMware Player:

http://developer.teradata.com/database/articles/introduction-to-teradata-express-for-

vmware-player

Here is the Teradata Express for VMware installation guide, on the Teradata

Developer Exchange:

http://developer.teradata.com/database/articles/teradata-express-14-0-for-vmware-

user-guide

Use this guide to download and install VMware Player and Teradata Express. In case

the user guide does not mention this, the vmware executable file has a “.vmx” file

extension.

For TMM usage, it is not required to read the following 3 sections of the user guide:

Using Viewpoint

Loading Data

Running Queries

http://developer.teradata.com/database/articles/introduction-to-teradata-express-for-vmware-player

http://developer.teradata.com/database/articles/introduction-to-teradata-express-for-vmware-player






Download and Install Tools and Utilities (TTU)

It appears that TTU 13.0 can co-exist with TTU 13.10 applications, but you may want

to use Add/Remove Programs to remove TTU 13.0 before installing TTU 13.10 or

14.0. As a rule, TTU applications of a given version can access older Teradata

versions (at least 2 point releases back, I think) along with the same Teradata version

but these TTU applications sometimes will not work with a newer version of Teradata

(without upgrading to the same version of TTU).

1. Go to Teradata Developer Exchange site (http://developer.teradata.com/) and

download the latest (non-beta) TTU package.

Click on Downloads on the right side of the results window, or download from

the following URL:

http://downloads.teradata.com/download/tools/teradata-tools-and-utilities-

windows-installation-package

2. Run the install package. It will take a while, but it is a silent installation so you do

not need to be present during installation.

3. Update any scripts you have that call TTU applications to use the correct path and

filename; for example, when upgrading from TTU 13.0 to 13.10, arcmain.exe and

bteq.exe have a similar path, with “13.0” changing to “13.10” in the pathname. If

you have any back/restore scripts using these applications, then you would either

need to edit the path in the scripts or use the filenames without a path and add a

high priority path in the Windows PATH environment variable that points to the

appropriate TTU folder(s).

Using TD Express/Linux Virtual Machine

1. Start VMware Player.

The first time you use a virtual machine you may need to open it using the Open

Virtual Machine option on the startup page.

Open the TDE 13.10, 14.0, 14.10 or 15.0 folder that you extracted under

C:\virtual-machines (or wherever).

After opening for the first time, the virtual machine is in a list on the left pane of

the startup page and you can just double-click on it.

2. If you are asked to upgrade VMware tools, I would recommend that you respond

“No”. They are not needed for basic TMM repository usage. If you decide to

upgrade, it is not a trivial exercise and you may need help from a VMware expert.

(Note: Backup readme v4.pdf or later versions have instructions in appendix A for

installing Vmware tools. This is required to allow copy/paste from Windows to

the Linux guest OS. This readme file is found under My Documents\Teradata

Mapping Manager\Backup after installing TMM.)

3. Enter “root” (without quotes) for both the login and password.

http://developer.teradata.com/

http://downloads.teradata.com/download/tools/teradata-tools-and-utilities-windows-installation-package

http://downloads.teradata.com/download/tools/teradata-tools-and-utilities-windows-installation-package




After a few minutes, you should see a desktop with a few folders and program

icons, including a Teradata Tools folder and a Gnome Terminal program icon.

(Some beta versions of Teradata Express do not have a graphical user interface

and only provide a command line interface. You can type the same commands in

this interface as mentioned below except that Gedit is not available. With this

interface, you will need to press CTRL+ALT keys simultaneously to return

control to the Windows host operating system. When Windows has control and

you want to activate the Linux guest OS command line window, which may be

completely blank, click in the middle of that window and press Enter to show the

command prompt.)

4. (First time only) If you have 4GB or more of system RAM, you may want to

increase the memory size used by the virtual machine to improve performance. To

do this, select Virtual Machine (top menu bar) > Virtual Machine Settings >

Hardware tab > Memory.

Move the slider bar on the right up to about 2GB if you have 4GB of system RAM

Move the slider bar on the right up to about 4GB if you have 8GB of system

RAM.

(If you have 8GB of RAM, this 4GB setting can improve performance quite a bit.

If you have 16GB, you may want to allocate 12GB to VMware)

Click OK.

Start Teradata

Teradata should start automatically when the virtual machine starts, but it may take a

minute or so. If it does not start, complete step 1 below. If you want to check the status

of Teradata to see if it has fully started, complete step 2.

1. Start Teradata manually as follows:

Double-click on the Teradata Tools folder to open a folder browser window.

Double-click on the Start Teradata program icon. Currently, there is no

automatic feedback on when Teradata has actually started, so you will need to

use the pdestate application (step 2).

2. To check the status of Teradata:

a. Double-click on Gnome Terminal to open it, if it is not already open.

(In some versions of Teradata Express for VMware, Gnome Terminal is not

default installed on the desktop. See Backup Readme v4.pdf or later, chapter

5, for instructions to place Gnome Terminal application icon on desktop.)

b. In the Gnome Terminal, type:

pdestate –a

Repeat this until you get a status of:

PDE state is RUN/STARTED




Logons are enabled...

You now should be able to access Teradata from the host (local PC) operating system.

If Teradata remains in the state DOWN/HARSTOP, then it is possible that Teradata

crashed or was manually stopped. Try the following command to start Teradata:

/etc/init.d/tpa start

If that does not work, then you may need to stop Teradata and remove a crash file

before restarting, as follows:

/etc/init.d/tpa stop

rm /var/opt/teradata/tdtemp/PanicLoopDetected

/etc/init.d/tpa start

Accessing Teradata from Host

Note: Do not change the VMware network configuration from the default NAT

option, unless you are a VMware networking expert who knows how to make things

work in the other configurations.

The default method for accessing Teradata from the host PC (i.e. Teradata Mapping

Manager running on Win 7 PC) is to use the “Teradata IP Address” and ODBC or

JDBC connection methods (TMM uses JDBC). In order for this connection method to

work properly, you must disconnect any local-PC VPN (virtual private network)

software.

At the time this was written, the Teradata Express user guide does not explain how to

find this Teradata IP Address and 60 minutes of searching the VMware web site did

not yield an answer either. It appears that the following procedure will show you the

Teradata IP Address for your installation of Teradata Express for VMware, although

Teradata Mapping Manager support does not have the expertise to debug your system

if this does not work for you:

Open the Teradata Express virtual machine and login to Linux. The default

username/password should be root/root. See section Using TD Express/Linux

Virtual Machine if you need instructions to do this.

Double-click on Gnome Terminal to open it, if not already open (or click in

the center of the virtual machine window and press Enter to see the Linux

command prompt if you have a version of Teradata Express without a

graphical (X-Windows) user interface). Click in that window and type the

following command (last character is a zero):

ifconfig eth0

This will display a short report of various network addresses.

The IP address following “inet addr:” is the Teradata IP Address.




The address is acquired from (or maybe derived from an acquired address) the DHCP

server for your network. It then becomes a static IP address. It is possible, although

probably a rare occurrence, that this IP address could change over time. For example,

if the network segment to which you are connected is physically reconfigured, then it

is possible that your PC’s IP address and this Teradata IP Address will change.

It is recommended that you first verify that you can access Teradata Express for

VMware using Teradata Administrator (or Teradata Studio) using this Teradata IP

Address. If you cannot connect to Teradata using Teradata Administrator then there is

no need to try to connect using Teradata Mapping Manager.

After the initial successful connection between Teradata Mapping Manager and

Teradata Express for VMware, if you ever have problems connecting again, your first

debug step should be to use Teradata Administrator to connect to this same instance of

Teradata and display the list of tables in the Teradata Mapping Manager repository

database.

If you cannot access Teradata, then see section Other Support Resources to get support

for Teradata Express. It is best to post your problem as a Teradata Studio + Teradata

Express connection problem rather than a Teradata Mapping Manager problem, as the

same engineering group owns Teradata Express and Teradata Studio (but not Teradata

Mapping Manager).

Note: If you are using VMware Workstation (not a free application) in place of

VMware Player (free), there is a feature to forward VMware ports but some users

were not able to get this feature to forward the local host port (127.0.0.1) to the

VMware virtual machine. The Teradata Mapping Manager support team cannot

provide support for using VMware port forwarding software, but this is a good feature

to use if you can get it to work as you do not have to disconnect from VPN in order to

access Teradata Express.

Stop Teradata/Virtual Machine

To stop the virtual machine and Teradata, double-click on the Gnome terminal icon in

the VMware window to open it, and then type the command “halt” in the Gnome

Terminal.

This will take a few minutes. Wait for the VMware window to close before shutting

down your PC.

As a quicker alternative, you can just close the VMware window (click on X in top-

right corner of window) and select Suspend option. When you reopen VMware, you

can click on the virtual machine name in the left pane and click on Play this virtual

machine in the right pane. The shut-down/startup time is much quicker doing this.


Appendix B: How to Debug Problems Starting Teradata Mapping Manager


Appendix B: How to Debug Problems Starting

Teradata Mapping Manager

This appendix describes some of the reasons that Teradata Mapping Manager may not

properly launch, along with possible solution(s) to these problems.

The following are hyperlinks to specific topics in this appendix.

Windows script host is missing on the client machine

You do not have write permission to the My Documents folder and subfolders

or the disk is full

Another instance of Teradata Mapping Manager is already running on the PC

Windows script host is missing on the client machine

We have written a VBS script to launch the TMM jar file in order to suppress the extra

command prompt window, which is opened with every Java based application. Our

VBS script require Microsoft Windows Script Host version 5.6 or above, which is

normally installed with every standard installation of Windows XP (SP2 and above) or

Windows 7. To verify the version or installation of Windows Script Host, perform the

following steps:

1. Select the Windows Start menu > Run, type “cmd” and press Enter. A command

prompt window opens.

2. In the command prompt window, type “CScript” and press Enter. If Windows

Script Host is installed on your PC, then it shows its version as illustrated below.

Windows Script Host Version


Appendix B: How to Debug Problems Starting Teradata Mapping Manager


If Windows Script Host 5.6 or above is not found and you are running Windows XP,

then you can download and install it from the following location:

http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-d896-482e-

a0d6-524e7e844d81&DisplayLang=en

As of this writing, Microsoft does not appear to have a support download of Windows

Script Host for Windows 7. It appears that Windows 7 does include this Script Host

software, however.

You do not have write permission to the My Documents folder

and subfolders or the disk is full

As part of the startup process for the Teradata Mapping Manager Java application, the

startup batch files open a log file under \My Documents\Teradata Mapping Manager

(Windows XP) or \Documents\Teradata Mapping Manager (Windows 7). This is the

location where all Teradata Mapping Manager run-time files will be created and

maintained. TMM users must have both read and write permissions for that folder and

its subfolders and there must be 100+ K-bytes of free disk space.

TMM checks for this condition on startup and reports the following error message if

found:

Error, cannot create log file under folder: <full path for LogFiles folder, as

installed on this PC>. Your disk may be full or you may not have write

permissions for this folder.

If the latter is the problem, then have a Windows administrative user give you full

read/write permissions to the \My Documents\Teradata Mapping Manager (Windows

XP) or \Documents\Teradata Mapping Manager (Windows 7) folders.

Use Windows Explorer to check and see if the hard drive where Teradata Mapping

Manager was installed is full. If so, then free up some disk space.

If Teradata Mapping Manager was installed on a PC by one user (perhaps an

administrator) but you are logged into Windows as another user, then Teradata

Mapping Manager will usually try to locate the run-time files folder based on the

username of the installer. If your user is not a Windows administrator, then this

situation will probably lead to this error. You can change the file system location for

Teradata Mapping Manager run-time files by opening Tools > Preferences to the

Startup tab and pressing the Change button. You must close and reopen Teradata

Mapping Manager before this change will take effect.

Another instance of Teradata Mapping Manager is already

running on the PC

The Teradata Mapping Manager startup program opens a debug log file for exclusive

access. Only one instance of Teradata Mapping Manager can have exclusive access on

a single PC, so the tool checks to see if another instance is running as part of the

startup process. If so, this error is reported in a command window. Either close the

other instance or use it instead of the instance that you are trying to create.

http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-d896-482e-a0d6-524e7e844d81&DisplayLang=en

http://www.microsoft.com/downloads/details.aspx?FamilyID=47809025-d896-482e-a0d6-524e7e844d81&DisplayLang=en


Glossary


Glossary

See the online help (Help menu, Help Topics option) for additional glossary terms

used in Teradata Mapping Manager.

business analyst – Understands the needs of business users and the data required to

implement a solution.

cross-mapping – Cross-mapping is the process of generating mappings between two

working data sets using intermediate mappings. For example, if A is mapped to B

and B is mapped to C, then Teradata Mapping Manager can use cross-mapping to

map A to C. Cross-mapping is one of the methods used by the mapping discovery

feature.

custom property – Many of the mapping objects in the repository, such as data

structures and data elements, have system properties, but can also be assigned

custom properties. These custom properties can be assigned using the Custom

Property Editor or as part of the import of a new data representation or mappings;

for example, where the input file has columns with the new custom property name

in the header and property values in the column. Custom properties provide

additional information that facilitates mapping or can be exported with mappings

for inclusion with a mapping specification.

data analyst – Responsible for analyzing data requirements for an organization.

data element – Generic term, used by Teradata Mapping Manager, to represent the

lowest level of data within a data representation. Data elements are grouped within

data structures, which are then grouped within a data representation. A data

element may be atomic data, derived data or a compound element. In a logical

data model, an attribute is a data element. In a physical data model, a column is a

data element. In a source data flat file, a field is a data element.

See Also: data representation

data model – A model of the data used by a business that formally describes the data

and how it is represented and accessed. A data model defines the data structures,

data elements and relationships between the data structures and elements for a

particular area of interest. Types of data models include logical, physical,

semantic, staging, and others.

data modeler – Analyzes and creates data objects and understands their relationships

to one another.

data representation – Generic term, used by Teradata Mapping Manager, for the

representation of a data model (such as a logical data model or application data

model) or other type of data framework (such as a source data flat file). A data

representation contains data structures such as entities, tables, and files and their

corresponding data elements such as attributes, columns, and fields,

respectively. The diagram below shows the two parts of a data representation, data

structure and data element, and different types of data representations.

http://sharepoint.teradata.com/ps/mappingmanager/TMM%20Glossary%20End%20User#datarep


Glossary


A data representation may also contain subject areas, which are logical groupings

of data structures.

Data representations are imported into Teradata Mapping Manager to create

working data sets for mapping.

data set window – A window within the task pane of Teradata Mapping Manager that

displays a single working data set and provides the interface for editing, viewing,

organizing, and exporting working data sets.

data structure – Generic term, used by Teradata Mapping Manager, for a data

construct that groups together a set of the lowest level data elements. In a logical

data model, an entity is a data structure. In a physical data model a table is a data

structure. In a source file a record, or possibly the file itself, is a data structure.


data transformation – Converts data from a source data format into a target data

format. Data transformation includes the mapping of source data elements to

target data elements with descriptions of the transformation that must occur as

well as the code generation that creates the actual transformation program.

Teradata Mapping Manager can be used to capture the mappings and

transformation notes and to create a mapping specification for code generation. It

also includes a SQL Generation feature that can generate INSERT SELECT

statements for each table that is the destination of one or more mappings, although

this function does not support any specific data transformation functions other

than selecting columns from more than one source table.

destination working data set – The working data set that is the ending point for a

specific mapping. Either working data set can be designated as the destination,

although, in some cases it makes sense to designate a specific working data set as

the destination; for example, in a source to target mapping, it is logical to assign

the target data model as the destination working data set.

See Also: working data set

ETL – Abbreviation for extract, transform, and load; part of the process of moving

data from one or more source systems to a database.

grid – Representation of information in a matrix (row and column) format. Data set

windows display information in either a tree or grid structure. Map set windows

display information only in a grid.

LDM – Abbreviation for logical data model.


Glossary


map set – A construct in Teradata Mapping Manager that contains a view of the

individual repository mappings between data representations, subject areas,

literals, data structures and data elements from two working data sets, one the

origin and the other, the destination. A map set can also show the unmapped data

elements in the origin or destination working data sets. One or more map sets or

map reports can be exported to help create a mapping specification.

map set window – A window within the task pane of Teradata Mapping Manager that

displays a map set and provides the interface for editing, viewing, organizing, and

exporting map sets.

mapping – A mapping is a linking of a data representation, subject area, literal, data

structure or element in an origin working data set to a corresponding mapping

object in a destination working data set.

mapping discovery – This is a feature of Teradata Mapping Manager that finds

potential mappings between two data representations based on simple name

matching between the properties of the data representations. For example, when

mapping one version of a logical data model (LDM) to another to trace lineage,

many of the entity and attribute names may be exactly the same in both versions.

Teradata Mapping Manager can find these matches and then give you the option

to create those mappings or discard them. There are also mapping discovery

algorithms for best name matching, cross-mapping and short-list mapping.

mapping object – Any object that can be the origin or destination of a mapping. A

mapping object can be a specific data element, data structure, subject area, literal,

or data representation.

mapping specification – Industry term defining a set of one or more mappings

between two or more data representations. A mapping specification is used to

define the required data transformations or to map requirements to data, for

example. In Teradata Mapping Manager, you can export one or more map sets or

mapping reports to create a mapping specification deliverable.

See Also: data transformation

metadata – Information that describes the data stored in the Teradata Mapping

Manager repository.

metadata object name – The concatenation of data representation name (optional),

data structure name and data element name using the period (.) character as a

separator .

object – In Teradata Mapping Manager, a generic term for working data set, map set,

and other items stored in the repository. Certain repository objects are displayed in

the Object Navigator and can be dragged to the task pane to view their details in a

task pane window.

Object Navigator – Tree structure displayed in the left pane of the Teradata Mapping

Manager window used to show the working data sets, map sets and other objects

available for a specific project.


Glossary


origin working data set – The working data set that is the starting point for a specific

mapping. Either working data set can be designated as the destination, although, in

some cases it makes sense to designate a specific working data set as the origin;

for example, in a source to target mapping, it is logical to assign the source data

model as the origin working data set.

See Also: working data set

PDM – Abbreviation for physical data model.

project – Used in Teradata Mapping Manager to group data representations and

mappings into an identifiable unit for use by a specified group of users. Users

are prompted to open a project when they start Teradata Mapping Manager. The

currently open project is displayed in the Object Navigator.

repository – An instance of the Teradata Mapping Manager relational metadata

database containing objects such as data representations, working data sets, map

sets, mappings, and properties that are stored, managed, and used by Teradata

Mapping Manager.

source data flat file – Any non-relational file external to the analytic

environment that is used as a source for analysis.

subject area – An optional grouping of data structures. Used primarily in logical data

models, but subject areas can be created for any type of data representation.


task pane – The right pane of the Teradata Mapping Manager window that serves as a

workspace where data set windows and map set windows are displayed and used.

tree – A hierarchical structure consisting of branch and leaf nodes, such as that used in

Windows Explorer. The Object Navigator is shown using a tree structure. Data set

windows can be viewed in either tree or grid view.

working data set – In Teradata Mapping Manager, a view of an imported data

representation that is configured (organized or filtered) to facilitate mapping. For

example, you can configure a working data set for an imported LDM (data

representation) to show selected columns for system properties such as Subject

Area Name, Data Structure Name, and Data Element Name as well as custom

properties in a specific order, and then filter it to show only one subject area.

Different users can create their own working data set “view” of the same data

representation. This allows them to individually change display columns, sort,

filter, and so on, their working data set without affecting the other user’s working

data set – all without the need to duplicate the data representation in the

repository.

Getting Started with Teradata Mapping Manager.pdf

Documents

Transcript of Getting Started with Teradata Mapping Manager.pdf