311845

Teradata Meta Data Services
Administrator Guide
Release 14.00
B035-3118-071A
November 2011
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, Active Enterprise Intelligence, Applications Within, Aprimo, Aprimo Marketing Studio, Aster, BYNET, Claraview, DecisionCast,
Gridscale, Managing the Business of Marketing, MyCommerce, Raising Intelligence, Smarter. Faster. Wins., SQL-MapReduce, Teradata Decision
Experts, Teradata Labs Logo, Teradata Raising Intelligence Logo, Teradata Source Experts, WebAnalyst, and Xkoto are trademarks or registered
trademarks of Teradata Corporation or its affiliates in the United States and other countries.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of Oracle.
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Intel, Pentium, and XEON are registered trademarks of Intel Corporation.
IBM, CICS, RACF, Tivoli, and z/OS are registered trademarks of International Business Machines Corporation.
Linux is a registered trademark of Linus Torvalds.
LSI is a registered trademark of LSI Corporation.
Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United
States and other countries.
NetVault is a trademark or registered trademark of Quest Software, Inc. in the United States and/or other countries.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
Oracle, Java, and Solaris are registered trademarks of Oracle and/or its affiliates.
QLogic and SANbox are trademarks or registered trademarks of QLogic Corporation.
SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.
SPARC is a registered trademark of SPARC International, Inc.
Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States
and other countries.
Unicode is a registered trademark of Unicode, Inc. in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN AS-IS BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION
MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
The information contained in this document may contain references or cross-references to features, functions, products, or services that are
not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features,
functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions,
products, or services available in your country.
Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated
without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any
time without notice.
To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this
document. Please email: teradata-books@lists.teradata.com.
Any comments or materials (collectively referred to as Feedback) sent to Teradata Corporation will be deemed non-confidential. Teradata
Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform,
create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata
Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including
developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright 1999-2011 by Teradata Corporation. All Rights Reserved.
Preface
Purpose
This book provides information about Teradata Meta Data Services, a Teradata Tools and
Utilities product. Teradata Tools and Utilities is a group of products designed to work with
Teradata Database.
This book supports the operational responsibilities of the Teradata Meta Data Services
administrator.
For detailed installation information, see the Teradata Tools and Utilities Installation Guide for
the appropriate operating system.
Programming information and descriptions of the Application Programming Interfaces
(APIs) included with MDS are provided in the Teradata Meta Data Services Programmer
Guide.
Audience
This book is intended for use by:
Teradata Meta Data Services Administrators
Teradata Professional Services Representatives
Supported Releases
This book supports the following releases:
Teradata Database 14.0, 13.10, 13.0, 12.0.x, and V2R6.2.x
Teradata Tools and Utilities 14.00
Teradata Meta Data Services 14.00
To locate detailed supported-release information:

1
Go to http://www.info.teradata.com/.
Under Online Publications, click General Search.
Type 3119 in the Publication Product ID box.
Under Sort By, select Date.
Click Search.
Teradata Meta Data Services Administrator Guide
Preface
Prerequisites
6
Open the version of the Teradata Tools and Utilities ##.##.## Supported Platforms and
Product Versions spreadsheet associated with this release.
The spreadsheet includes supported Teradata Database versions, platforms, and product
release numbers.
Prerequisites
The following prerequisite knowledge is required for this product:
Teradata Database
Teradata ODBC Driver
Microsoft Windows products
Linux
Changes to This Book

The following changes were made to this book in support of the current release. Changes are
marked with change bars. For a complete list of changes to the product, see the Teradata Tools
and Utilities Release Definition associated with this release.
Date and Release
Description
November 2011
Documented support of user-defined types (UDTs) and user-defined

functions (UDFs) in the Database Information Model (DIM).
14.00
Table 8 updated to show the Load Type as USER DEFINED TYPES/

FUNCTIONS instead of as USER DEFINED TYPES. Associated graphic
also modified.
Items 7 and 8 under Creating a Repository Class Property on page 97
clarified with additional information related to the SQL_DECIMAL, SQL_
NUMERIC, SQL_TIME, and SQL_TIMESTAMP data types.
Documented MDS support for Teradata 14.0 features and SQL syntax
changes to metacreate, metaload, and metamigrate. See relevant entries in
Chapter 6: MDS Utility Programs.
Documented MDS support added for global temporary tables in the DIM.
Documented MDS support for the SQL Array data type available in
Teradata 14.0.
Support for the NUMBER data type as a possible ColumnType value has
been added to MDS.
Updated version numbers.
Figure 8: MDS CWM_Metamodel layout on page 270 updated.
Preface
Additional Information
Additional information that supports this product and Teradata Tools and Utilities is available
at the web sites listed in the table that follows. In the table, mmyx represents the publication
date of a manual, where mm is the month, y is the last digit of the year, and x is an internal
publication code. Match the mmy of a related publication to the date on the cover of this book.
This ensures that the publication selected supports the same release.
Type of Information
Description
Access to Information
Release overview
Use the Release Definition for the following

information:
1 Go to http://www.info.teradata.com/.
Overview of all of the products in the

release
Information received too late to be
included in the manuals
Operating systems and Teradata
Database versions that are certified to
work with each product
Version numbers of each product and
the documentation for each product
Information about available training
and the support center
3 Type 2029 in the Publication Product ID box.
Late information
2 Under Online Publications, click General Search

4 Click Search.
5 Select the appropriate Release Definition from
the search results.
Preface
Type of Information
Description
Additional product
information
Use the Teradata Information Products

Publishing Library site to view or download
specific manuals that supply related or
additional information to this manual.
2 Under the Online Publications subcategory,
Browse by Category, click Data Warehousing.

3 Do one of the following:
For a list of Teradata Tools and Utilities

documents, click Teradata Tools and Utilities,
and then select an item under Releases or
Products.
Select a link to any of the data warehousing
publications categories listed.
Specific books related to Teradata Meta Data
Services, are as follows:
Teradata Meta Data Services Programmer Guide
B035-3047-mmyx
Teradata Tools and Utilities Installation Guide for
Microsoft Windows, B035-2407-mmyx
Red Hat Enterprise Linux
B035-3121-mmyx
SUSE Linux
B035-3122-mmyx
IBM s390x Linux
B035-3123-mmyx
HP-UX
B035-3124-mmyx
IBM AIX
B035-3125-mmyx
Oracle Solaris on AMD Opteron Systems
B035-3126-mmyx
Oracle Solaris on SPARC Systems
B035-3127-mmyx
IBM z/OS
B035-3128-mmyx
ODBC Driver for Teradata User Guide
B035-2509-mmyx
CD-ROM images
Access a link to a downloadable CD-ROM

image of all customer documentation for
this release. Customers are authorized to
create CD-ROMs for their use from this
image.
2 Under the Online Publications subcategory,
Browse by Category, click Data Warehousing.

3 Click CD-ROM Images.
4 Follow the ordering instructions.
Preface
Type of Information
Description
Ordering
information for
manuals
Use the Teradata Information Products

Publishing Library site to order printed
versions of manuals.
2 Under Print & CD Publications, click How to
Order.
3 Follow the ordering instructions.
General information
about Teradata
The Teradata home page provides links to

numerous sources of information about
Teradata. Links include:
1 Go to Teradata.com.
2 Select a link.
Executive reports, case studies of

customer experiences with Teradata,
and thought leadership
Technical information, solutions, and
expert advice
Press releases, mentions, and media
resources
Preface
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Changes to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Chapter 1:
Teradata Meta Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
The MDS Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Application Information Metamodels (AIMs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Administration and Support Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MetaManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MetaSurf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MetaBrowse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Metacreate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Metaviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Metamigrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Metaload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MetaClient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Metadelete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MetaXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
28
28
28
29
29
29
29
29
30
30
Special Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Programming Interfaces (APIs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sample Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Versioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Retain Associated Business Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic DIM Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
XML Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SQL Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
30
30
31
31
32
32
32
33
Table of Contents
Chapter 2:
Configuration of Meta Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Teradata MDS Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Set the Workstation or Server Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Linux Workstations or Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Windows Workstations or Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Create the Meta Data Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Windows Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Linux Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Migrate the Meta Data Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Create A Virtual Directory or Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Chapter 3:
Administer MDS with MetaManager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Start MetaManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
MetaManager Main Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Tool Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
View Common Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
View Unique Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Teradata Database Systems and MetaManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Add Teradata Database Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Modify Teradata Database Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Delete a Teradata Database System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Teradata Databases and MetaManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Load Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Unload Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Resynchronize Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Get the DIM Update Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Set MetaLoad LoadTypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Set MDS Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Activity Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
Retain Associated Business Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
View or Delete MDS Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
10
Table of Contents
Chapter 4:
MetaBrowse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Start MetaBrowse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
MetaBrowse Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Tool Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Metamodels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
77
77
79
79
79
The Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Refresh Application Metamodels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Object Versioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Object Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Labels and Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Creating a Metamodel (AIM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Creating a Repository Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Creating a Repository Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Creating a Repository Class Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Creating a Derived Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Creating a Derived Class Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Modifying Repository Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying an AIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Repository Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Repository Relationship. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Repository Class Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Derived Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a Derived Class Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
102
103
103
104
104
104
104
Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Common Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unique Properties of a Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unique Properties of a Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unique Properties of a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unique Properties for the Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security Profile for the Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
View the Labels Applied to the Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
105
105
106
106
107
108
108
109
Finding Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Get Class Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Get Class Objects by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Get Object Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
109
110
112
114
11
Table of Contents
Class Objects and Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Add an Object to a Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Remove an Object from a Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Creating, Editing and Deleting Class Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Deleting Class Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Creating a Class Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Editing a Class Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Adding an Object to a Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Creating or Editing with the Create Repository Object Wizard . . . . . . . . . . . . . . . . . . . .118
Deleting Metamodels from the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Chapter 5:
Permissions, User Names, Passwords and Security Profiles . . .
123
MDS User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
Teradata MDS Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Changing MDS User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Accessing User Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Application Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Adding a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126
Delete Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127
Membership Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Managing Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Adding a User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Deleting Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
Security Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
Accessing Security Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
Adding a Security Profile/Editing a Security Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
Adding and Deleting Users and Application Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137
Assigning Security Profiles to Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Assigning AIM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Assigning Class Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Assigning Object Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
Chapter 6:
MDS Utility Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
mdsconfig (Linux only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
12
Table of Contents
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
metaclient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running metaclient from MetaBrowse or MetaManager . . . . . . . . . . . . . . . . . . . . . . . .
Command Line and Parameter File Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
144
144
144
145
145
145
147
150
150
metacreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
151
152
152
152
metaload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
152
152
153
156
157
metadelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
157
157
157
157
metaviews. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
metaxml . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running metaxml from MetaBrowse or MetaManager . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
158
158
158
159
159
159
prtconfig (Linux only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
metamigrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
161
161
161
162
13
Table of Contents
Chapter 7:
Automatic DIM Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Automatic DIM Update Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
Relay Services Gateway (RSG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
DDL Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
MDS Action Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
MDS Recovery Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164
Database Connection Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Out of Sync Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
Teradata Database System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
RSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
DDL Gateway Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Configuring Automatic DIM Update in MetaManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Adding a Teradata Database System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Adding Teradata Nodes to a Teradata Database System . . . . . . . . . . . . . . . . . . . . . . . . . .167
Loading Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168
Enabling Automatic DIM Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
Checking DIM Update Status with MetaManager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
Starting/Stopping the DDL Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
Starting/Stopping the MDS Action Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
Chapter 8:
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
Troubleshooting - Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173
Troubleshooting - Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
Appendix A:
Teradata Metadata - Database Information Metamodel . . . . .177
DIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
DIM Class Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
DIM Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
Database System Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
Database Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
Table Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Column Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
View Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
14
Table of Contents
View Column Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index Column Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Check Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reference Column Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Stored Procedures Parameter Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . .
Stored Procedures Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trigger Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Subject Area Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Business Entity Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Business Attribute Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Business Rule Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Valid Values Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FKReference Class Property Descriptions (Derived from Reference Column) . . . . . . .
Macro Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Macro Parameter Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hash Index Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Join Index Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MetaLoadTypes Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Function Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FunctionParameter Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Constant Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UDT Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UDTAttribute Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
186
187
187
188
188
188
189
189
189
190
191
191
191
192
192
192
193
193
194
194
195
195
196
197
198
199
DIM Relationship Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Appendix B:
Client Load Utility Metadata - Client Load Metamodel . . . . . . . 203
Client Load Metamodel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
CLM Class Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
CLM Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Script Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Source Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Source Field Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Target Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
205
205
206
206
207
CLM Relationship Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
15
Table of Contents
Appendix C:
SQL Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
MDS SQL Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209
meta_BusinessAttrColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
meta_BusinessAttributeRules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
meta_BusinessAttributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
meta_BusinessAttrViewCols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
meta_BusinessEntities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212
meta_BusinessEntityAttrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
meta_BusinessEntityTables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213
meta_BusinessEntityViews. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
meta_BusinessRules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
meta_BusinessRuleValues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214
meta_CheckConstraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
meta_ColumnHasTriggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
meta_Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216
meta_DatabaseBusEntities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
meta_DatabaseBusinessRules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .218
meta_DatabaseOwnsDatabases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
meta_Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
meta_DatabaseSubjectAreas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
meta_StoredProcedureMacros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
meta_FunctionParameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
meta_HashIndexIndices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222
meta_HashIndexTableColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223
meta_HashIndexTables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
meta_IndexColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
meta_Indexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225
meta_JoinIndexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226
meta_JoinIndexFunctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
meta_JoinIndexIndices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
meta_JoinIndexTableColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .228
meta_JoinIndexTables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229
meta_MacroHashIndexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229
meta_MacroJoinIndexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230
meta_MacroParameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230
meta_MacroReferencesMacros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232
16
Table of Contents
meta_Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
meta_MacroStoredProcedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
meta_MacroTableColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
meta_MacroTables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
meta_MacroTriggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
meta_MacroViewColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
meta_MacroViews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
meta_RefConstraintColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
meta_RefConstraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
meta_SPParameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
meta_StoredProcedureMacros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
meta_StoredProcedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
meta_StoredProcedureTables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
meta_StoredProcedureViews. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
meta_StoredProcHashIndexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
meta_StoredProcJoinIndexes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
meta_StoredProcRefsSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
meta_StoredProcTableColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
meta_StoredProcViewColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
meta_SubjectAreaEntities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
meta_SubjectAreas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
meta_SystemMetaloadTypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
meta_SystemNodes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
meta_TableColumns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
meta_TableHasTriggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
meta_Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
meta_TriggerMacros. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
meta_Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
meta_TriggerTables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
meta_TV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
meta_TVColumns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
meta_TVM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
meta_ValidValues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
meta_ViewColumnConstants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
meta_ViewColumnFunctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
meta_ViewColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
meta_ViewColumnTableColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
meta_ViewReferencesViews. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
17
Table of Contents
meta_Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
meta_ViewTableColumns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
meta_ErrorTables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
meta_ColumnUDTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
meta_MacroFunctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
meta_MacroParameterUDTs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
meta_SPParameterUDTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258
meta_TriggerFunctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
meta_TriggerUDTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259
meta_UDFFunctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
meta_UDFs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
meta_UDTAttributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
meta_UDTAttributeUDTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261
meta_UDTFunctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262
meta_UDTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262
meta_ViewColumnUDTs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263
meta_ViewFunctions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263
meta_ViewTables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263
Appendix D:
XML Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265
XML Bridge Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265
Supported tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266
How to Use XML Bridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267
OMG CWM to MDS CWM_Metamodel mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270
Current limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
Updates not supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
Not linking to DIM objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277
Technical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Importing XML via the GUIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278
Exporting from the MDS repository into the tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279
User Bridge Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283
18
List of Figures
Figure 1: Typical MDS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 2: Example Security Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Figure 3: Containment Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Figure 4: Processes Supporting Automatic DIM Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Figure 5: Database Information Metamodel (DIM) (Sheet 1 of 2) . . . . . . . . . . . . . . . . . . . . 177
Figure 6: Database Information Metamodel (DIM) (Sheet 2 of 2) . . . . . . . . . . . . . . . . . . . . 178
Figure 7: Client Load Metamodel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 8: MDS CWM_Metamodel layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
19
List of Figures
20
List of Tables
Table 1: Teradata MDS Configuration Linux Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Table 2: Logging Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 3: Tracing Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Table 4: MetaManager Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 5: MetaManager Tool Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Table 6: Common Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Table 7: Unique Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Table 8: Metaload Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Table 9: Audit Trail Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Table 10: Filter Box Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Table 11: MetaBrowse Menu Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Table 12: MetaBrowse Tool Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Table 13: Common Properties for Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Table 14: Unique Properties for Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Table 15: Unique Properties for Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 16: Unique Properties for Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Table 17: Unique Properties for Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 18: Security Profile for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 19: Common Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Table 20: Access Types for Security Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Table 21: Special Permission Types for Security Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Table 22: Teradata mdsconfig Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Table 23: metaclient Script Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Table 24: metaclient Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Table 25: Metaload Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Table 26: metadelete Input Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Table 27: metaxml Import Input Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Table 28: metaxml Export Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Table 29: metamigrate Input Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 30: DDL Gateway Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Table 31: Troubleshooting - Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Table 32: Troubleshooting - Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
21
List of Tables
Table 33: DIM Class Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Table 34: Database System Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
Table 35: Database Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
Table 36: Table Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Table 37: Column Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
Table 38: View Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Table 39: View Column Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
Table 40: Index Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Table 41: Index Column Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187
Table 42: Check Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Table 43: Reference Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Table 44: Reference Column Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
Table 45: Node Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Table 46: Stored Procedures Parameters Class Property Descriptions . . . . . . . . . . . . . . . . . .189
Table 47: Stored Procedures Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Table 48: Trigger Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190
Table 49: Subject Area Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
Table 50: Business Entity Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
Table 51: Business Attribute Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
Table 52: Business Rule Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Table 53: Valid Values Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Table 54: FKReference Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192
Table 55: Macro Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
Table 56: Macro Parameter Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193
Table 57: HashIndex Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
Table 58: JoinIndex Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194
Table 59: MetaLoadTypeClass Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Table 60: Function Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195
Table 61: FunctionParameter Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . .196
Table 62: Constant Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
Table 63: UDT Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198
Table 64: UDT Attribute Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
Table 65: DIM Relationship Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199
Table 66: CLM Class Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
Table 67: Script Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205
Table 68: Source Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206
22
List of Tables
Table 69: Source Field Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Table 70: Target Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Table 71: CLM Relationship Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Table 72: Columns and Data Types of the meta_BusinessAttriColumns View . . . . . . . . . . 210
Table 73: Columns and Data Types of the meta_BusinessAttributeRules View Descriptions . .
211
Table 74: Columns, Data Types, and Values of the meta_BusinessAttributes View . . . . . . 211
Table 75: Columns and Data Types of the meta_BusinessAttrViewCols View. . . . . . . . . . . 212
Table 76: Columns, Data Types, and Values of the meta_BusinessEntities View. . . . . . . . . 212
Table 77: Columns and Data Types of the meta_BusinessEntityAttrs View . . . . . . . . . . . . . 213
Table 78: Columns and Data Types of the meta_BusinessEntityTables View. . . . . . . . . . . . 213
Table 79: Columns and Data Types of the meta_BusinessViews View . . . . . . . . . . . . . . . . . 214
Table 80: Columns and Data Types of the meta_BusinessRules View. . . . . . . . . . . . . . . . . . 214
Table 81: Columns and Data Types of the meta_BusinessRuleValues View. . . . . . . . . . . . . 215
Table 82: Columns, Data Types, and Values of the meta_CheckConstraints View . . . . . . . 215
Table 83: Columns and Data Types of the meta_ColumnHasTriggers View . . . . . . . . . . . . 216
Table 84: Columns, Data Types, and Values of the meta_Columns View . . . . . . . . . . . . . . 216
Table 85: Columns, Data Types, and Values of the meta_DatabaseBusEntities View . . . . . 218
Table 86: Columns and Data Types of the DatabaseBusinessRules View . . . . . . . . . . . . . . . 218
Table 87: Columns and Data Types of the DatabaseBusinessRules View . . . . . . . . . . . . . . . 219
Table 88: Columns, Data Types, and Values of the meta_Databases View . . . . . . . . . . . . . . 219
Table 89: Columns and Data Types of the meta_DatabaseSubjectAreas View . . . . . . . . . . . 220
Table 90: Columns and Data Types of the meta_StoredProcedureMacros View . . . . . . . . . 221
Table 91: Columns and Data Types of the meta_FunctionParameters View . . . . . . . . . . . . 221
Table 92: Columns, Data Types, and Values of the meta_HashIndexIndices View . . . . . . . 223
Table 93: Columns and Data Types of the meta_HashIndexTableColumns View. . . . . . . . 223
Table 94: Columns and Data Types of the meta_HashIndexTables View . . . . . . . . . . . . . . . 224
Table 95: Columns and Data Types of the meta_IndexColumns View . . . . . . . . . . . . . . . . . 224
Table 96: Columns, Data Types, and Values of the meta_Indexes View . . . . . . . . . . . . . . . . 225
Table 97: Columns and Data Types of the meta_JoinIndexes View . . . . . . . . . . . . . . . . . . . 226
Table 98: Columns and Data Types of the meta_JoinIndexFunctions View. . . . . . . . . . . . . 227
Table 99: Columns, Data Types, and Values of the meta_JoinIndexIndices View . . . . . . . . 227
Table 100: Columns and Data Types of the meta_JoinIndexTableColumns View. . . . . . . . 228
Table 101: Columns and Data Types of the meta_JoinIndexTables View. . . . . . . . . . . . . . . 229
Table 102: Columns and Data Types of the meta_MacroHashIndexes View . . . . . . . . . . . . 229
Table 103: Columns and Data Types of the meta_MacroJoinIndexes View . . . . . . . . . . . . . 230
23
List of Tables
Table 104: Columns, Data Types, and Values of the meta_MacroParameters View . . . . . . .230
Table 105: Columns and Data Types of the meta_MacroReferencesMacros View . . . . . . . .232
Table 106: Columns and Data Types of the meta_Macros View . . . . . . . . . . . . . . . . . . . . . . .232
Table 107: Columns and Data Types of the meta_MacroStoredProcedures View . . . . . . . . .233
Table 108: Columns and Data Types of the meta_MacroTableColumns View . . . . . . . . . . .233
Table 109: Columns and Data Types of the meta_MacroTables View . . . . . . . . . . . . . . . . . .234
Table 110: Columns and Data Types of the meta_MacroTriggers View . . . . . . . . . . . . . . . . .234
Table 111: Columns and Data Types of the meta_MacroViewColumns View . . . . . . . . . . . .234
Table 112: Columns and Data Types of the meta_MacroViews View . . . . . . . . . . . . . . . . . . .235
Table 113: Columns and Data Types of the meta_RefConstraintColumns View. . . . . . . . . .235
Table 114: Columns and Data Types of the meta_RefConstraints View . . . . . . . . . . . . . . . . .236
Table 115: Columns, Data Types, and Values of the meta_SPParameters View. . . . . . . . . . .237
Table 116: Columns and Data Types of the meta_StoredProcedureMacros View . . . . . . . . .238
Table 117: Columns and Data Types of the meta_StoredProcedures View . . . . . . . . . . . . . .238
Table 118: Columns and Data Types of the meta_StoredProcedureTables View. . . . . . . . . .239
Table 119: Columns and Data Types of the meta_StoredProcedureViews View . . . . . . . . . .240
Table 120: Columns and Data Types of the meta_StoredProcHashIndexes View . . . . . . . . .240
Table 121: Columns and Data Types of the meta_StoredProcJoinIndexes View . . . . . . . . . .240
Table 122: Columns and Data Types of the meta_StoredProcRefsSPs View . . . . . . . . . . . . .241
Table 123: Columns and Data Types of the meta_StoredProcTableColumns View . . . . . . .241
Table 124: Columns and Data Types of the meta_StoredProcViewColumns View . . . . . . . .242
Table 125: Columns and Data Types of the meta_SubjectAreaEntities View . . . . . . . . . . . . .242
Table 126: Columns and Data Types of the meta_SubjectAreas View. . . . . . . . . . . . . . . . . . .243
Table 127: Columns and Data Types of the meta_SystemMetaloadTypes View . . . . . . . . . .243
Table 128: Columns and Data Types of the meta_SystemNodes View . . . . . . . . . . . . . . . . . .244
Table 129: Columns, Data Types, and Values of the meta_TableColumns View. . . . . . . . . .244
Table 130: Columns and Data Types of the meta_TableHasTriggers View . . . . . . . . . . . . . .246
Table 131: Columns and Data Types of the meta_Tables View . . . . . . . . . . . . . . . . . . . . . . . .246
Table 132: Columns and Data Types of the meta_TriggerMacros View . . . . . . . . . . . . . . . . .247
Table 133: Columns, Data Types, and Values of the meta_Triggers View . . . . . . . . . . . . . . .247
Table 134: Columns and Data Types of the meta_TriggerTables View . . . . . . . . . . . . . . . . . .248
Table 135: Columns and Data Types of the meta_TV View . . . . . . . . . . . . . . . . . . . . . . . . . . .249
Table 136: Columns and Data Types of the meta_TVColumns View . . . . . . . . . . . . . . . . . . .249
Table 137: Columns and Data Types of the meta_TVM View . . . . . . . . . . . . . . . . . . . . . . . . .250
Table 138: Columns and Data Types of the meta_ValidValues View . . . . . . . . . . . . . . . . . . .251
Table 139: Columns, Data Types, and Values of the meta_ViewColumnConstants View . .251
24
List of Tables
Table 140: Columns and Data Types of the meta_ViewColumnFunctions View. . . . . . . . . 253
Table 141: Columns, Data Types, and Values of the meta_ViewColumns View . . . . . . . . . 253
Table 142: Columns and Data Types of the meta_ViewColumnTableColumns View. . . . . 255
Table 143: Columns and Data Types of the meta_ViewReferencesViews View . . . . . . . . . . 255
Table 144: Columns and Data Types of the meta_Views View . . . . . . . . . . . . . . . . . . . . . . . 256
Table 145: Columns and Data Types of the meta_ViewTableColumns View. . . . . . . . . . . . 256
Table 146: Columns and Data Types of the meta_ErrorTables View . . . . . . . . . . . . . . . . . . 257
Table 147: Columns and Data Types of the meta_ColumnUDTs View . . . . . . . . . . . . . . . . 257
Table 148: Columns and Data Types of the meta_MacroFunctions View . . . . . . . . . . . . . . 258
Table 149: Columns and Data Types of the meta_MacroParameterUDTs View . . . . . . . . . 258
Table 150: Columns and Data Types of the meta_SPParameterUDTs View . . . . . . . . . . . . 258
Table 151: Columns and Data Types of the meta_TriggerFunctions View . . . . . . . . . . . . . . 259
Table 152: Columns and Data Types of the meta_TriggerUDTs View . . . . . . . . . . . . . . . . . 259
Table 153: Columns and Data Types of the meta_UDFFunctions View . . . . . . . . . . . . . . . . 260
Table 154: Columns and Data Types of the meta_UDFs View. . . . . . . . . . . . . . . . . . . . . . . . 260
Table 155: Columns and Data Types of the meta_UDTAttributes View. . . . . . . . . . . . . . . . 261
Table 157: Columns and Data Types of the meta_UDTFunctions View. . . . . . . . . . . . . . . . 262
Table 158: Columns and Data Types of the meta_UDTs View . . . . . . . . . . . . . . . . . . . . . . . 262
Table 160: Columns and Data Types of the meta_ViewFunctions View. . . . . . . . . . . . . . . . 263
Table 161: Columns and Data Types of the meta_ViewTables View. . . . . . . . . . . . . . . . . . . 264
Table 162: Tools supported by XML Bridge. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Table 163: Mapping OMG CWM to MDS CWM_Metamodel . . . . . . . . . . . . . . . . . . . . . . . 271
25
List of Tables
26
CHAPTER 1
Teradata Meta Data Services
Teradata Meta Data Services (MDS) provides an infrastructure for managing Teradata data
warehouse metadata and for creating tools to interchange metadata with external operational
systems, Extraction Transformation and Load (ETL) tools, Business Intelligence tools,
Database Modeling tools, and any other metadata sources.
Components of Teradata MDS include:
A repository database where metadata is stored in Teradata tables
Three predefined Application Information Metamodels (AIMs)
Tools and utilities to:
Define entirely new AIMs
Extend existing AIMs
Build metadata interchange bridges
Administrative and support tools and features for managing metadata.
The MDS Repository

The MDS repository is a collection of tables, views and macros stored in a Teradata Database.
These tables are used to store metadata. The macros and views are used internally by MDS.
The Teradata ODBC Driver is used for database access.
The MDS software performs services to persist and retrieve metadata from the repository
database and controls access to the repository and its objects. Access to the repository is
controlled by database security permissions. Access to objects within the repository is
controlled by MDS security permissions.
Application Information Metamodels (AIMs)

How metadata is stored in the repository is defined by Application Information Metamodels
(AIMs).
An AIM consists of
Classes, which are types of metadata objects
Properties, which are data fields associates with a particular class
Relationships, which are associations between two classes
27
Chapter 1: Teradata Meta Data Services

Administration and Support Tools
The three AIMs supplied with Teradata MDS are:
The Teradata Database Information Metamodel (DIM) is a predefined AIM for storing the
Teradata Data Dictionary information from Teradata databases and associated business
data.
The Client Load Metamodel (CLM) is a predefined AIM for storing the information
obtained from Teradata client FastLoad, MultiLoad and TPump utility scripts and output
files.
The Common Warehouse Metamodel (CWM) is a predefined AIM for storing

information obtained from supported business intelligence tools.
These AIMs can be extended or entirely new AIMs can be created to store other metadata in
the MDS repository.

Teradata MDS provides a number of different Administrative and Support tools and utilities
to create, modify and manage metadata in the MDS repository. This section provides a brief
description of these tools and utilities.
MetaManager
MetaManager is a Windows based Graphical User Interface (GUI) program for performing
administrative tasks including:
Loading, unloading, or synchronizing Teradata Database metadata
Defining users and groups of users
Defining and assigning security restrictions
Setting a variety of configuration options
Viewing logs
Starting the MetaXML or MetaClient utility
MetaSurf
Use MetaSurf s HTML files and Active Server Pages (ASP) scripts to set up a powerful Webbased application for viewing, navigating and analyzing Business and Technical metadata
stored in the MDS repository.
Access is based on the users role whether it be business, technical, or administrator through a
standard web browser.
Metasurf also provides the ability to edit metadata stored in the repository.
MetaBrowse
MetaBrowse is a Windows based GUI program for performing such tasks as:
28
Browsing and searching the repository

Creating new AIMs
Extending existing AIMs by creating new classes, properties and relationships
Editing or manually adding data in the repository
Deleting objects from the repository
Starting the MetaXML or MetaClient Utility
Metacreate
The metacreate program creates the initial MDS repository.
Metaviews
The metaviews program installs a set of MDS views into the DBC database. If installed, the
metaload program will use the views to access the DBC tables when loading the data
dictionary information into the repository. Although not required, it is strongly
recommended that the MDS views be installed for all Teradata systems to be tracked in the
MDS repository.
If the Automatic DIM Update feature is enabled on a system, the MDS views must be installed
on any system that does not support Unicode. See Automatic DIM Update on page 32 for
more information.
Metamigrate
The metamigrate program migrates an existing repository to a newer MDS repository version.
Metaload
The metaload program is a command line alternative and the program MetaManager uses for
loading, unloading or resynchronizing databases. The metaload program loads the Teradata
metadata into the MDS repository Database Information Metamodel (DIM). The metaload
program is Unicode-enabled. It will attempt to make a UTF-16 session character set
connection to Teradata databases.
If the program can establish a UTF-16 connection, the program does not require that the
MDS views be installed into the DBC database with the metaviews program.
If the program cannot establish a UTF-16 connection, it will run in a mode that requires that
the MDS views be installed into the DBC database with the metaviews program.
Beginning with MDS 13.0, metaload offers the ability to limit the database objects that will have
metadata extracted and loaded into the repository. Limiting the metadata can improve load
time and decrease the amount of disk space required by the repository but it can also result in
incomplete information. See Set MetaLoad LoadTypes on page 61 for more information.
MetaClient
The metaclient program loads CLM information into the repository. It can be run by any
MDS user from either the command line, through MetaManager, or MetaBrowse.
29

Special Features
Beginning with MDS 13.0, metaclient versions multiple instances of a client load script's
executions if versioning is enabled in the MDS repository.
Metadelete
The metadelete program drops all MDS repository tables, views, and macros in the MDS
repository database, effectively deleting the MDS repository.
MetaXML
The metaxml program imports data from an XML file into the repository or exports
metamodel definitions and object data to an XML file.
Special Features
In addition to the administrative support tools and utilities discussed above, Teradata MDS
also provides some special features that allow for highly customized metadata solutions.
Application Programming Interfaces (APIs)

Using the MDS supplied APIs programmers can create, modify and delete the metadata
objects and the application information metamodels in the MDS Repository. They can also
import and export metadata in the repository. MDS provides the following APIs:
C++
Microsoft Component Object Model (COM)
XML
Java
Samples for loading data through the APIs are also included. For additional information on
the APIs refer to theTeradata Meta Data Services Programmer Guide.
Sample Files
Teradata MDS also provides a number of different sample files that enable you to further
customize and configure your metadata solution.
Some of the sample files include:
Macros for use with Microsoft Excel
Sample code for use with the C++, COM and Java interfaces
Sample ASP scripts for use with MetaSurf
Sample XML scripts to load or update the repository
All of the sample files are located in individual directories below the sample directory with a
explanatory readme.txt file. Sample files are only installed if the MDS Development Kit is
installed.
30

Special Features
Versioning
Teradata MDS provides the ability to retain historical copies of data objects within classes or
data versioning.
The historical copies provide the ability to see the progression of changes made to an object
after its initial creation. Applications and users will only be allowed to modify the latest
version of an object, but the earlier versions will be viewable, within the restrictions of the
applicable security profile.
Versioning applies to data objects within classes. It cannot be used with the definitions of
models, classes, relationships, properties, users, or security profiles.
If versioning is enabled for a repository, AIM or class, MDS internally tracks two types of
versions:
Published
Inactive
The published version of an object is the 'currently visible' version.

An inactive version of an object is an historical version. Inactive versions exist in the
repository, but cannot be updated and they are only visible to users with read permission to
the version.
By default, a new MDS repository will not have versioning enabled.
You can enable or disable versioning for:
The whole repository
Specific metamodels
Specific classes
A repository with versioning enabled will require more PERM and SPOOL space on the
Teradata Database than the same repository created without versioning enabled.
Retain Associated Business Information

Teradata MDS provides the ability to retain specific types of DIM objects in a dormant state
after they have been deleted. Such objects will not be removed from the repository but they
will not be viewable until they are reactivated. When reactivated the business definitions and
other relationships defined before the object was deleted will also be reactivated.
Retain Associated Business Information support applies to tables, views and their component
objects. Retain Associated Business Information support does not apply to any other objects
in the DIM or other AIMs.
If custom descriptions or business definitions have been added to tables and columns, they are
lost on a subsequent resynchronization of the repository metadata when the tables are
dropped and re-created as part of the load process. Setting the Retain Associated Business
31

Special Features
Information option prevents this from happening and ensures that MDS reassociates any
custom descriptions and business information previously defined.
By default, a new MDS repository or a pre-12.0 repository being migrated to the current
release will not have Retain Associated Business Information enabled.
A repository with Retain Associated Business Information support enabled will require more
PERM and SPOOL space on the Teradata Database than the same repository created without
Retain Associated Business Information support enabled.
Automatic DIM Update

Because the Teradata Database meta data is a central part of the Teradata MDS repository, it is
vital to the use of MDS that the information be kept up to date and dynamically reflect any
changes in the Teradata active data warehouse.
The Automatic DIM Update feature is an optional component that, when enabled and
configured, dynamically keeps the MDS repository synchronized with the Teradata Database
Systems it describes.
Beginning with MDS 13.0, the MDS DDL Gateway (which is part of the Automatic DIM
Update feature) is Unicode-enabled. If the Automatic DIM Update feature is enabled for a
Teradata system, the DDL Gateway resynchronization process will attempt to make a UTF-16
session character set connection to the databases on that system.
If the DDL Gateway resynchronization process can establish a UTF-16 connection, it does not
require that MDS views be installed into the DBC database on that system with the metaviews
program.
If the DDL Gateway resynchronization process cannot establish a UTF-16 connection, it will
run in a mode that requires that MDS views be installed into the DBC database on that system
with the metaviews program.
XML Bridge
XML Bridge supports the exchange of metadata between MDS repository and select businessintelligence (BI), analytic, and modeling tools. Such tools must comply with the Object
Management Group (OMG) Common Warehouse Metamodel (CWM) XML Metadata
Interchange (XMI) format. For more information, see Appendix D: XML Bridge.
SQL Views
Teradata MDS now provides SQL views for observing the relationships between tables,
macros, views, and so on, as defined in the repository.
Each view provides data on some relationship, generally organized by system and database
names. For example, the view meta_ViewTables returns the columns System, TableDatabase,
TableName, ViewDatabase, and ViewName. The view meta_MacroTables returns similar info
for macros, and so on for the other types that reference tables. For details about each view, see
Appendix C SQL Views on page 209.
32

Special Features
Logging
Teradata MDS provides several different types of log files.
The Teradata MDS Audit Trail is a table in the MDS repository that contains an audit trail of
changes to the Teradata metadata. Entries are written to the table by the metaload utility.
Entries are also written to the table by the MDS DDL Gateway Integrity Servers if the
Automatic DIM Update feature is enabled. For each update to the DIM, an entry is inserted
into the audit trail table when audit logging is enabled.
The Teradata MDS Activity Log is a table in the MDS repository that, when activity logging is
enabled, tracks user access (reads, writes, deletes) of objects in the repository. The log also
indicates when access to an object is rejected because of permission conflicts. The Activity
Log, unlike the Audit Trail, is not limited to only tracking changes to the DIM.
You can view the contents of both the Activity log and the Audit Trail through MetaSurf (while
logged on as an Administrator) or by using SQL directly. The Audit Trail can be accessed
through the metaauditlog table or the mdsauditlog view. The Activity Log can be accessed
directly through the metaactivitylog table.
MDS Logs track error messages, warnings, and debug information on individual machines
where the MDS software is installed. The MDS Logs can be viewed through MetaManager.
33

Special Features
34
CHAPTER 2
Configuration of Meta Data Services
This chapter includes the following topics:
Teradata MDS Configuration Overview
Set the Workstation or Server Configuration Parameters
Create the Meta Data Repository
Migrate the Meta Data Repository
Create A Virtual Directory or Web Application
Teradata MDS Configuration Overview

Figure 1 on page 36 illustrates a typical Teradata MDS configuration consisting of:
A Teradata Database System containing a Teradata MDS repository
One or more workstations accessing the Teradata MDS repository with a web browser
An Active Server Pages (ASP) compliant web server with MetaSurf installed
A Windows based workstation configured to administer the MDS repository
Your system may also contain one or more workstations that will be used to develop or run
MDS applications and, if the Teradata MDS Automatic DIM Update feature is to be installed,
a designated DIM Update server.
35
Chapter 2: Configuration of Meta Data Services

Figure 1: Typical MDS Installation
Client Web Browser
Workstation/Laptop/Etc
with Supported Browsers
ASP
Page
HT40
2EQUEST
HT-,
0AGE
MetaManager/
MetaBrowse
(Windows PC)
*
Metasurf
Intranet
or
Internet
Active
Server
Engine
MDS
Com
Interface
+
Engine
MDS
Engine
HTML
Page
ODBC
ODBC
Teradata
Database
MDS
Repository
3118B001
Windows
Web
Server
* MDS Installed
Teradata Server
Set the Workstation or Server Configuration

Parameters
After the appropriate software is installed on your workstation or server, set the MDS
configuration parameters for each workstation or server.
Linux Workstations or Servers

On Linux workstations the local configuration parameters are set using the mdsconfig
program. You must be logged on as root to run mdsconfig.
36

The DSN name specified with mdsconfig for the location of the MDS repository should have
been added to the odbc.ini file on the Linux workstation or server.
Command-line Syntax
The parameters for the mdsconfig program are as follows:
mdsconfig -h <metahome> -o <DSNname> -u <dbuser> -p <dbpasswd> -l
<loglevel> -t <tracelevel> -s <numISvr>
Use mdsconfig H to get help for the mdsconfig program.

Table 1: Teradata MDS Configuration Linux Parameters
Parameter
Description
-h <metahome>
The MDS Installation folder.

It is highly recommended that the default location of /opt/teradata/mds
not be changed.
-o <DSN name>
Default ODBC Data Source Name (DSN) that MDS uses to connect to
the Teradata Database System containing the MDS repository.
-u <dbuser>
Database User Name that MDS uses to log on to the Teradata Database
System to access the MDS repository.
-p <dbpasswd>
Database User Password that MDS uses to log on to the Teradata

Database System to access the MDS repository.
-l <loglevel>
Error Log level (0-5). Where 0 is the least amount of logging and 5 is
the greatest amount.
-t <tracelevel>
Trace level (0-5) to be used for Application debugging. Where 0 is the

least amount of tracing and 5 is the greatest amount of tracing.
-s <numIntSvr>
Number of Integrity Servers for the MDS Data Definition Language

(DDL) Gateway to start. Defaults to 5.
-H
Displays option list.
If you will be installing and using the Automatic DIM Update, refer to Chapter 7: Automatic
DIM Updates, for additional installation and configuration tasks.
Windows Workstations or Servers

On Windows, the local MDS configuration parameters are stored in the Windows Registry. To
change the settings, you must be logged onto the Windows system as a user who has
permission to update the Windows Registry.
Note: On Windows, users who are only members of the Guests group will not be able to
change the settings.
Display the MDS Configuration tab of the Teradata Meta Data Services Configuration dialog box
by:
Clicking MDS Configuration from the Windows Control Panel.
37

Clicking Start>Programs>Teradata Meta Data Services>MetaManager to display The

Teradata Meta Data Services MetaManager Logon dialog box. Then click Configure.
Note: If you did not accept the default name as your choice during installation, you must
find your specified name for the MDS program group to launch MetaManager.
For more information, see the following:
Set the Database Connection Information on page 38
Setting Logging and Trace Levels on page 40
Log Files Manager on page 41
Set the Database Connection Information

During installation, the MDS Database connection information is specified. This information
resides in the local client system registry files, not in the repository. The MDS engine uses this
information to connect to the MDS repository.
The settings can be changed before making the connection, using the Teradata Meta Data
Services Configuration dialog box.
38

In the Data Source Name box enter the ODBC system Data Source Name (DSN) to use to
connect to the Teradata Database System containing the MDS repository.
In the Database User Name box enter the user name that MDS will use to log onto the Teradata
Database System. The user must have permissions to access the MDS database tables.
If the MDS users on the local system are browsing the MDS repository, the user needs SELECT
privileges to the database containing the MDS repository.
If any user loads or updates the MDS repository, INSERT, UPDATE and DELETE privileges
are also required.
To create an Application Information Metamodel, CREATE TABLE privileges are needed.
If this user will be creating the MDS repository, GRANT ALL PRIVILEGES to the user on the
database.
In the Database User Password box enter the password that MDS will use to log onto the
Teradata Database System.
In the Database Name box enter the name of the Teradata Database within the Teradata
Database System where the MDS repository is stored. This can be the same as the Database
User Name.
If omitted, the Database Name will default to the default Database Name in the ODBC DSN
for that Teradata Database System where the database is housed.
39

Note: If the DSN does not have a default Database Name, the connection will be made to the
default database of the Database User.
Changes to these settings are saved in the registry when you click Apply or OK after making
changes.
Note: If you are connected to MetaManager when you make changes to these settings, they
will not take effect until the next time you run MetaManager.
Setting Logging and Trace Levels
From the Teradata Meta Data Services Configuration dialog box, choose the Logging tab to see
the log options.
The logging and tracing levels only apply to the local system, where an MDS application is
running. They can be changed at any time and changes are written to the local systems
registry immediately.
MDS applications only read the log and trace level settings on start up, therefore restart the
application for the new settings to take effect. To change the settings for MetaSurf, restart the
web server.
Logging Level
This choice controls the amount of log messages written to the MDS log file. The default is
Warning.
Table 2: Logging Levels
Level
Description
Critical
Logs Critical messages
Error
Logs Error and Critical messages
Warning
Logs Warning, Error and Critical messages. Warning is the default logging
level
Information
Logs Information, Warning, Error and Critical messages
All
Logs Debug, Information, Warning, Error and Critical messages
Tracing Level
This choice controls the type of messages traced and written to the standard error output. The
Tracing Level and error output are used primarily when writing an application using the MDS
APIs. The default is Disable.
Table 3: Tracing Levels
40
Level
Description
Disable
No messages are traced.
Critical
Traces Critical messages

Table 3: Tracing Levels (continued)
Level
Description
Error
Traces Error and Critical messages
Warning
Traces Warning, Error and Critical messages
Information
Traces Information, Warning, Error and Critical messages
All
Traces Debug, Information, Warning, Error and Critical messages
Log Filename
The Log filename is read-only. The filename is meta_yyyymmdd.txt (where yyyy = year, mm =
month, dd = day). The date contained in the log filename indicates the date the log entries
were written.
MDS creates a new log file each day. The log does not wrap. Old log files should be deleted by
the MDS Administrator.
Log Files Manager
Click Log Files Manager to see previously generated log files - their names, and file sizes in
bytes.
View or delete the logs in this window.

The following instructions assume that the system does not have an existing MDS repository
created from an earlier version of MDS. If you have such a repository refer to Migrate the
Meta Data Repository on page 42 for information on migrating the existing MDS repository
to the current software version.
After installing the MDS software, the next step is to create the MDS repository.
Windows Workstation
Use this procedures to create the MDS Repository from a Windows workstation.
To create the MDS Repository

1
Click Start>Programs.
Click Teradata Meta Data Services (or the Program Group name you specified during
installation).
Click Create MDS Repository.

Click Create without versioning to create a repository without versioning enabled. This is
the default choice.
41

This runs the metacreate program and creates an MDS repository without versioning
support.
Click Create with versioning to create a repository with versioning enabled.
This runs the metacreate program and creates an MDS repository with versioning
support.
Linux Workstation
Use this procedure to create an MDS Repository from a Linux workstation.
To create the MDS Repository

1
Log onto the workstation as root.
Run the /opt/teradata/mds/bin/metacreate program to create an MDS repository without

versioning support or
Run the /opt/teradata/mds/bin/metacreate -v on program to create an MDS repository
with versioning support.

The process of migrating an MDS repository involves the following:
Upgrade a client to a new version of MDS first.
Migrate the MDS repository to the same version as the upgraded client.
Note: In the case of multiple environments (for example, Production, Staging, and Test)
remember that the version of MDS installed on any clients that access a given environment
must match the version of the MDS repository in that environment.
Upgrade remaining clients to the new version of MDS.
The specific procedures for Windows and Linux workstations follow.
Windows Workstation
The system must have an existing Teradata Meta Data Services (MDS) repository.
42
As a precaution, Teradata recommends that you create a backup of the Teradata database
containing the Teradata MDS repository before proceeding. If you are upgrading Teradata,
you must create a backup in Step 2.
If necessary, upgrade from an earlier version of Teradata Database.

a
Create a backup of the Teradata database containing the Teradata MDS repository, if
you have not already done so.
Upgrade the Teradata Database.

c
Caution:
Restore the Teradata MDS repository database.
Install the most recent Teradata MDS software components on a client that needs to access
the MDS repository in that environment.
Migrate the Teradata MDS repository to the same version as the client.
a
Click Start>Programs.
Click Teradata Meta Data Services (or the Program Group name specified during
installation).
Click Migrate MDS Repository.
Click Migrate without versioning to invoke the metamigrate program in an MSDOS window and migrate without versioning enabled. This is the default choice.
Click Migrate with versioning to invoke the metamigrate program in an MS-DOS

window and migrate a repository with versioning enabled.
If migrating a versioned repository to a non-versioned repository, only the latest version of

each object is migrated. All previous versions are removed and cannot be recovered.
d
Enter the MDS Administrator username and password (unless changed, it is metasu).
Migrating a repository takes several minutes.
Install the most recent MDS software components on any additional clients that need to
access the MDS repository.
Linux Workstation
The system must have an existing Teradata Meta Data Services (MDS) repository.
1
As a precaution, Teradata recommends that you create a backup of the Teradata Database
containing the Teradata MDS repository before proceeding. If you are upgrading Teradata,
you must create a backup in Step 2.
If necessary, upgrade from an earlier version of Teradata Database.

a
Create a backup of the Teradata database containing the Teradata MDS repository, if
you have not already done so.
Upgrade the Teradata Database.
Restore the Teradata MDS repository database.
Install the most recent Teradata MDS software components on a client that needs to access
the MDS repository in that environment.
Use the metamigrate utility to migrate the Teradata MDS repository to the same version as
the client.
Migrating a repository takes several minutes.
Install the most recent MDS software components on any additional clients that need to
access the MDS repository.
43


After installation of MetaSurf, define a virtual directory or web application for MetaSurf on
the web server.
When creating the virtual directory or web application, select an alias name for MetaSurf, for
example:
http://www.<yourhostname>/<mds> or http://<yourhostname>/<mds>
Where yourhostname is the name of the system and mds is the virtual name assigned to
MetaSurf.
Note: When changes are made to the Teradata ODBC DSN or MDS configuration, web
services may need to be restarted for the change to take effect.
For complete information on setting up the web server, starting and stopping web services,
and using IIS manager to create a virtual directory or web applications, refer to the web server
documentation. Additional information is also included in Section 9 of the MDS Readme.txt
file.
The appearance of the MetaSurf Web pages can be altered by:
modifying the style sheets used
defining new style sheets and incorporating them into MetaSurf
Style sheets, defined by the World Wide Web Consortium (W3C), allow you to describe the
appearance of individual HTML tags. The style sheet tags describe the font, color, paragraph
alignment, and other attributes for common HTML tags such as headings, paragraphs, lists,
and tables. Style sheets separate the style and layout of HTML from the informational content.
44
CHAPTER 3
Administer MDS with MetaManager
This chapter provides information on using MetaManager to perform such administrative

tasks as:
Adding, modifying, and deleting Teradata Database Systems
Configuring and viewing system audit logs
Loading, unloading, modifying, deleting and resynchronizing databases
Each Teradata Database System that will have database information loaded into the MDS
repository must be configured in MDS before its information can be loaded into the MDS
Repository. Use the MetaManager program to add and configure each Teradata Database
system.
Start MetaManager
When the MDS core files are installed, MetaManager will be installed on the system. The
Program group containing the shortcut to start MetaManager is determined during
installation. For detailed installation information, see the Teradata Tools and Utilities
Installation Guide for the appropriate operating system.
By default the MetaManager shortcut is in the Teradata Meta Data Services Program group
from the Windows Start>Programs menu. Click Teradata Meta Data Services>MetaManager.
The Teradata Meta Data Services Manager Logon dialog box appears.
45
Chapter 3: Administer MDS with MetaManager

MetaManager Main Window
An MDS administrative logon must be used to logon to MetaManager. The default MDS
Administrator name is metasu. The default password is metasu. For security purposes, change
the password immediately.
After entering the username and password, the MetaManager Main Window appears.
To run MetaManager from the command line:

Select Start>Run and enter metamgr mds_user mds_pwd
where mds_user and mds_pwd are the MDS Username and MDS Password parameters for the
system.
If MetaManager detects these two parameters, it will bypass the logon dialog box and attempt
to connect to the repository using the value of the parameters given. If MetaManager cannot
connect to the repository, a logon failure message will appear.

The MetaManager Main Window displays a:
Menu Bar
Tool Bar
Status Bar
Tree View of systems and nodes
Menu Bar
Table 4: MetaManager Menu Bar
Menu
Command
File
Exit
Exits Meta Data Services (MDS) MetaManager.
View
Audit Log
Views the audit log to see the audit trail of changes to the Teradata
metadata contained in the DIM.
Refresh
Refreshes the tree view to match the data in the MDS Repository.
Status Bar
Displays a status bar when checked. The Status bar contains help
message information for menu and toolbar items.
Toolbar
Displays a toolbar at the top of the MetaManager window when checked.

The toolbar icons are also available through menu commands.
46
Subcommand
Description

Table 4: MetaManager Menu Bar (continued)
Menu
Command
System
Add System
Adds a system to the repository.
Delete
Deletes a system from the repository.
Edit
Modifies a system in the repository.
Teradata Database
Systems
Loads or unloads a Teradata Database into the repository, resyncs

databases, or checks on the DIM update status.
Add Node
Adds a node to an existing system.
DIM Update
Sets options for the Automatic DIM Update to keep the databases in
sync.
User Manager
Displays a dialog box to add, delete or modify users or application

groups.
Security Profile
Displays a dialog box to add, change or apply security profiles to objects

such as AIMs or classes.
Change Password
Displays the Change MDS User Password dialog box. The MDS
Administrator (metasu) can change anyones password -- the previous
password is not required to complete the change.
Tools
Import
Subcommand
Description
XML
Displays a Locate the XML file to import dialog box. The MetaXML utility
will use the file in a separate console window to make modifications to
repository metamodels or data. Refer to metaxml on page 158 for
more in the MetaXML utility.
MetaClient
Shows the MetaClient dialog box to run the MetaClient utility. Refer to
metaclient on page 144 for more in the MetaClient utility.
MDS Configurations
Views or modifies settings for the audit trail, activity log and retain
associated business information feature. The audit trail tracks changes to
the Teradata metadata. The activity log tracks user access to objects in
the MDS repository.
The retain associated business information feature provides the ability to
reactivate tables, views and their component objects after they have been
deleted.
Help
MDS Log Files
Views the current log and tracing levels.
MetaLoad Load
Types
Displays the Metaload LoadTypes Administrator dialog box that provides

the ability to create, modify and delete Metaload LoadType objects.
Help Topics
Displays the Topics window of online help.
About MDS
Manager
Displays the MetaManager About dialog box. The dialog box contains
copyright and version information for MDS MetaManager.
47

Tool Bar
The Tool Bar contains the following icons:
Table 5: MetaManager Tool Bar
Icon
Function
Performs the same function as the System menu
Add System command.
Add Node command.
Teradata Database Systems command.
DIM Update command.
Performs the same function as the View menu Audit
Log command.
Performs the same function as the Tools menu User
Manager command.
Performs the same functions as the Security Profiles
command.
Performs the same function as the Tools menu MDS
Configurations command.
Performs the same function as the Tools menu MDS
Log Files command.
Performs the same function as the Help menu Help
Topics MetaManager command.
Status Bar
The status bar across the bottom of the MetaManager Main Window offers information to the
user. For example, the status bar might tell you that MDS is Loading a database into the
selected system.
Tree View
Tree View shows the list of systems in the repository. It will also display a systems nodes if any
are defined.
Clicking on the + symbol expands a system and populates its node.
Clicking on the - symbol contracts the view.
48

View Common Properties
To view the properties of any system or node, use the shortcut menu and click Properties.
View Common Properties

You can look at the common properties for each:
System
Node
Group
User
There are different ways to view the properties of each element.
Right-click the element, and then click Properties
Press Shift+F10 and click Properties
Press the Context menu key (if available)
The common properties can be viewed through MetaManager; they cannot be changed in this
application. The Common Properties tab displays the values of the common properties of the
selected object.
Table 6: Common Properties
Text Box
Description
Name
Displays the Name of the selected object.
Object ID
Displays the ID assigned to the selected object. This ID is

unique in the MDS Repository database.
Global Unique ID
Displays the Global Unique ID (GUID) of the selected object.

A GUID is a 128-bit structure that is unique, no matter which
computer generates it.
Class
Displays the Name of the Class of the Object.
Date Created
Displays the Date and Time the selected object was created.
Date Updated
Displays the Date and Time the selected object was last
modified.
Description
Displays the Description of the selected object.
49

View Unique Properties
View Unique Properties

The unique properties for an object can be viewed in the Unique Properties tab; they cannot be
changed in this application.
Table 7: Unique Properties Tab
Group
Element
Description
Name
This column lists the unique properties for the object.
Value
This column displays the value associated with the property in

the name column.
Display of selected
property value
When a list of properties is displayed, it can be difficult to see

the entire value in the list display.
Highlighting the property name will display its value in this
larger box with scroll bars.
Change decimal
format display
If the selected property has a floating point value, you can

change the precision and format of the value.
Precision
Enter the number of digits to be displayed to the right of the

decimal point.
Fixed/
Scientific
Click either Fixed or Scientific to set the display format.
Apply
Click to see the values in the new format.
Teradata Database Systems and MetaManager

After logging onto MetaManager as described in Start MetaManager on page 45 you can
add, modify or delete Teradata Database Systems.
Add Teradata Database Systems

Click System>Add System. The Add System dialog box appears.
50

Type in the system information and click OK.
The System Name is limited to 30 characters and must be unique.

Each system usually represents a Teradata Database System which will have database
metadata loaded into the MDS repository.
In the Description box, enter or change a description of the system. The description is
limited to 1024 characters.
Choose or change the Security Profile for the System. For details, see Chapter 5:
Permissions, User Names, Passwords and Security Profiles,. Permissions, User Names,
Passwords and Security Profiles
Choose to apply the Security Profile by Database or Class by choosing the Security
Propagation Type. For details, see Modify Teradata Database Systems on page 52..
The Connection Information is used by the MDS metaload utility to connect to this
Teradata Database System to load or resynchronize database information in the MDS
repository. Every workstation that will load, unload or resynchronize Teradata Database
Systems will need connection information for each Teradata Database System.
The ODBC Data Source Name (DSN) is used to connect to this specific Teradata Database
System. The DSN name is limited to 30 characters.
Teradata user login name (limited to 30 characters).

The user login requires privileges to connect to the Teradata Database to load, unload, and
resync databases. There are two options for granting permissions.
Create the MDS views that reference the DBC tables.

Click Start>All Programs>Teradata Meta Data Services>Create MDS Views.
51

Or run the metaviews command line program.

If the MDS views are created, no Teradata privileges are required by the user on the
DBC tables for loading, unloading, and resyncing databases.
If the MDS views are not created, MDS will access the DBC tables and the user requires
SELECT privilege on DBC
The Teradata SELECT privilege on databases containing stored procedures is required

to load all information on stored procedures.
If Automatic DIM Update is configured on the Teradata system, the user login also
requires SELECT and DELETE privileges on the dbc.mdsrecoverytbl.
Teradata user password (limited to 30 characters).
See alsoModify Teradata Database Systems on page 52 and Delete a Teradata Database
System on page 53.
Modify Teradata Database Systems

After a Teradata Database System has been added and configured as discussed in Teradata
Database Systems and MetaManager on page 50, use MetaManager to modify it.
From the MetaManager main window, select the system to modify. Click System>Edit. The
Modify System dialog box appears.
The options are the same as when adding a system.
52

Teradata Databases and MetaManager
Delete a Teradata Database System

Use MetaManager to delete a Teradata Database System that has been added and configured as
discussed in Teradata Database Systems and MetaManager on page 50.
From the MetaManager main window, highlight the system icon to delete. Click
System>Delete. The following warning message appears.
When a system is deleted, all the objects in the system are also deleted.
A system with the Automatic DIM Update feature enabled cannot be deleted.
Deleting a system is not reversible and can be time consuming.

After a Teradata Database System has been added as directed in Teradata Database Systems
and MetaManager on page 50, use MetaManager to load some or all of its databases into the
MDS repository. The metadata (tables, views, columns, and other objects) of loaded databases
can be searched and viewed with repository applications such as MetaSurf or MetaBrowse.
By default, when a database is loaded into the repository the metadata for following database
objects and their related objects are loaded into the MDS repository:
Tables
Views
Columns
Macros
Triggers
Stored Procedures
Hash Indexes
Join Indexes
MDS 13.00 and later offers the ability to limit the database objects that will have metadata
extracted and loaded into the repository. Limiting the metadata can improve load time and
decrease the amount of disk space required by the repository but it can also result in
incomplete information. For more information, see Set MetaLoad LoadTypes on page 61.
In MetaManager, click System>Teradata Database Systems. The Teradata Database Systems
tab appears.
53

All systems defined in the repository are listed on the left, along with the date of the last load.
Selecting a system displays its list of databases that have been loaded into the repository.
Select the system with database(s) to administer, click Teradata Database Administration. The
Teradata Meta Data Services Administration dialog box displays tabs to load, unload or
resynchronize databases and a tab for the Automatic DIM Update Status.
Note: To go directly to the Teradata Meta Data Services Administration dialog box, from the
MetaManager main window, right click on the system with database(s) to administer, and
click Database Administration.
Load Databases
After invoking the Teradata Meta Data Services Administration dialog box, load databases from
the Load Databases tab.
Select Load All Available Databases or Select Databases to Load or Load All Databases Except
Those Selected. Click Add>> and <<Remove to select or deselect databases to load into the
repository.
Note: If the Teradata Database is Kanji enabled, all Kanji character sets that will be used
must be installed on the system running MetaManager. For detailed installation information,
see the Teradata Tools and Utilities Installation Guide for the appropriate operating system.
54

Click OK or Apply to load the database(s) chosen.

The MetaLoad LOAD request dialog box displays.
Load Databases Request Options
Use this dialog box to specify the Security Profile and LoadType for the databases to be loaded.
For a versioned repository, use this dialog box to apply a label to the databases to be loaded.
Under Metaload options:
Accept the default security profile or click the Security Profile arrow for a list of a available
security profiles to apply.
Accept the default Load Type or click the Load Type arrow for a list of a available Load
Type objects to apply.
Enter a label in the Apply label box. In a versioned repository, the label specified will be
applied by the metaload utility to all the objects affected by the load. The label must not
already exist in the repository as metaload will try to create it.
Refer to Security Profiles on page 133 for further information on security profiles. Metaload
will not change the Security Profile of any existing objects. Use the Security Profile dialog box
in MetaManager to assign new Security Profiles to objects.
Refer to Set MetaLoad LoadTypes on page 61 for further information on defining Metaload
types.
55

Refer to Labels and Repository Objects on page 85 for further information on labels.
Click Proceed to load the selected databases.

While the database(s) are loading, a Process Status screen appears.
If there is an error during loading, the Status frame of the Process Status screen will indicate
what error occurred. View the output of the load or the log for details on the error.
The time the system will take loading the database(s) into the MDS repository will vary,
depending on the size of the chosen database(s) and the Metalaod Loadtypes selected.
When the load process is complete, the following status dialog box appears.
56

Click View Log to view the log file for the current day. Click View Output to ensure that all
databases loaded successfully.
You can now view, browse, or drill down on the metadata in the MDS repository.
Aborting the Load
Click Abort on the Process Status screen while the load process is running and the following
dialog box appears:
Click Yes to terminate the load. The following message appears.
Click OK. The Process Status dialog appears. Click View Log to view the load log or click View
Output to view the output log to determine the point where the load was abnormally
terminated.
57

When you click View Output, the Tools Output window appears listing the progress of the load.
If multiple databases were being loaded, scroll to the end to see the databases that were loaded
successfully before the job aborted.
When you return to the Database Systems tab, the aborted system will be indicated in the
Systems pane.
Resync the aborted databases before reloading the aborted system, so that the load completes
properly.
Unload Databases
Unload databases using MetaManager.
58

In MetaManager, click System>Teradata Database Systems. The Teradata Database Systems

tab appears.
To go directly to the Teradata Meta Data Services Administration dialog box, from the
MetaManager main window, right click on the system with database(s) to administer, and
select Database Administration.
After invoking the Teradata Meta Data Services Administration dialog box, use the Unload
Databases tab to unload databases.
All systems defined in the repository are listed on the left, along with the date of the last load.
Selecting a system displays its list of databases that have been loaded. In the example, two
databases have been previously loaded.
Click the name of database(s) to unload from the Loaded Databases list. Click Add>> to move
the database to the Selected Databases list. If you add a database that you do not want to
unload, click the database name from the Selected Databases list and click <<Remove to move
the database back to the Loaded Databases list.
Click OK or Apply to unload the database(s) in the Selected Databases list from the MDS
repository.
59

Resynchronize Databases
After displaying the Teradata Meta Data Services Administration dialog box, use the Resync
Databases tab to resynchronize databases.
Resyncing databases runs the metaload program to manually resynchronize the Teradata
metadata in the MDS repository.
Note: The Resync Databases tab will be disabled if Automatic DIM Update is enabled for the
system. For systems with Automatic DIM Update enabled, use the DIM Update Status tab to
synchronize databases that are out of sync.
Use the options in this tab, to resync all loaded databases or select the databases to resync.
Click Add>> or <<Remove to select or deselect databases to resync.
Click OK to display the MetaLoad LOAD request dialog box.
Resynchronize Database Request Options
Use this dialog box specify the Security Profile and LoadType for the databases to be
resynchronized. For a versioned repository, use this dialog box to apply a label to the databases
to be resynchronized.
Under Metaload options:
60
Accept the default security profile or click the Security Profile arrow for a list of a available
security profiles to apply.

Set MetaLoad LoadTypes
Accept the default Load Type or click the Load Type arrow for a list of a available Load
Type objects to apply.
Enter a label in the Apply label box. In a versioned repository, the label specified will be
applied by the metaload utility to all the objects affected by the load. The label must not
already exist in the repository as metaload will try to create it.
Refer to Security Profiles on page 133 for further information on security profiles. Metaload
will not change the Security Profile of any existing objects. Use the Security Profile dialog box
in MetaManager to assign new Security Profiles to objects.
Refer to Set MetaLoad LoadTypes on page 61 for further information on defining Metaload
types.
Click Proceed to start the resync process.
Get the DIM Update Status

After invoking the Teradata Meta Data Services Administration dialog box, get the status of the
MDS DDL Gateway and determine if any databases are out of sync by clicking the DIM Update
Status tab. For more information about the DIM update feature, see the Teradata Tools and
Utilities Installation Guide for the appropriate operating system.

From the main menu bar of the Teradata Meta Data Services Manager window, click
Tools>MetaLoad Loadtypes.
61

The Load Types Administrator dialog appears.
Use this dialog box to:
Create
Edit
Remove
MetaLoad Types objects to define the amount and type of data to be loaded into the
repository for the selected databases being loaded. Each Load type listed loads only that type
data and the constituent parts of that type. Table 8 shows the data type and constituent parts
that will be loaded for each load type.
Table 8: Metaload Types
62
Load Type
Data Type And Constituent Parts Loaded
TABLES
Tables
Columns
Indexes
Constraints

Table 8: (continued)Metaload Types
Load Type
Data Type And Constituent Parts Loaded
VIEWS
Views
TRIGGERS
Triggers
MACROS
Macros
Macro Parameters
STORED PROCEDURES
Stored
Procedures
Stored Procedure
Parameters
HASH INDEXES
Hash Indexes
JOIN INDEXES
Join Indexes
USER DEFINED TYPES/

FUNCTIONS
User Defined
Types
View Columns
UDTAttributes
User Defined
Functionsa
USER DEFINED
FUNCTIONS
User Defined
Function
FunctionParameters
a. User-defined functions are always loaded when user-defined types are selected, regardless of
whether "USER DEFINED FUNCTIONS" are specifically selected. This is the default behavior of
the metaload utility.
If there are relationships between the types (or their components) selected that are not
included in the load types selected, that information will not be loaded and/or tracked in the
repository.
To create a new metaload type:

1
Select Create a new Load Type Object
Under Properties of the LoadType Object, enter a name and select one or more load types
from the Load Types list.
Click Create Object
To edit a metaload type

1
Select Edit an existing Load Type Object
Under Properties of the LoadType Object, select the name of the Load Type Object and
select one or more load types from the Load Types list.
Click Modify Object
63

Set MDS Configurations
To remove a metaload type:

1
Select Remove a Load Type Object
Under Properties of the LoadType Object, select the name of the Load Type Object.
Click Remove Object

From the main menu bar of the Teradata Meta Data Services Manager window, click
Tools>MDS Configurations.
The MDS Configurations dialog appears.
64

Use this dialog box to configure the following MDS configurations:
Audit Trail
Activity Log
Unlike the Logging and Trace level MDS configuration parameters, the Audit Trail, Activity
Log and Retain Associated Business Information configurations are MDS system-wide
parameters. Because these parameters are stored in the MDS repository, the repository must
be created before these parameters can be set.
Audit Trail
The Teradata MDS Audit Trail is a table in the MDS repository that contains an audit trail of
changes to the Teradata metadata. The MDS DDL Gateway Integrity Servers and the metaload
utility write entries to the table. For each update to the DIM, an entry is inserted into the audit
trail table when audit logging is enabled.
The contents of the Audit Trail can be viewed through MetaSurf (while logged on with the
Administrator Profile) or by using SQL directly. The Audit Trail can be accessed through the
metaauditlog table or the mdsauditlog view.
Entries to the Audit Trail can be viewed and deleted with MetaManager.
Under Audit Log Flag, turn the audit log flag on or off (the default is Off) by clicking On or Off.
65

Set the expiration for the audit trail entries by entering a value between 1 and 3,650 days in the
Expiration box The default is 7 days.
Enter a value in the Action Poll box to set how often the MDS Action Processor will look for
changes to the system-wide parameters and to the parameters configured for Automatic DIM
Update.
If the Automatic DIM Update feature is enabled, the MDS Action Processor purges expired
entries from the audit trail. The MDS Action Processor will poll the MDS Audit Trail every 24
hours at 1:30 a.m. local time.
Viewing/Deleting the Audit Trail Log Entries
Perform the following tasks to view the Audit Log.
1
Open MetaManager.
From the Windows task bar, click Start>Programs>Teradata Meta Data Services (or the
Program Group name that was designated during MDS installation) followed by
MetaManager.
After logging in, the Meta Data Services Manager main window appears.
Click View Audit Trail Log

or
Click View>Audit Log.
If there are entries in the Audit Log an Auditlog Filter dialog box will appear. If there are no
entries in the Audit log, the Auditlog Entries window appears.
66

From here:
Click on a column name to sort the list by the column name
Click Filter to display the Auditlog Filter dialog box
Click Refresh to update the window.
Click on audit log entries and click Delete to delete them.
Note: If filtering is used to display the AuditLog dialogs list-view and you select all the
items in the list-view for deletion, the delete function will use the WHERE clause derived
from the filter. This type of delete will typically complete in a matter of seconds regardless
of how many items are involved. If filtering is used and specific items are selected for
deletion, the filter will not be used and the deletion can take several minutes depending
upon the number of items selected.
The format for each entry in the log is:
Table 9: Audit Trail Format
Column
Description
Event
Change type (create, delete, update).
DDLAction
Identifies the Teradata DDL being processed that caused this entry
CREATE TABLE, ALTER TABLE, DELETE DATABASE, etc.
Name
Name of the object that has changed.
Class ID
Class of the changed object.
67

Table 9: Audit Trail Format (continued)
Column
Description
System
Teradata system of the changed object.
Database
Database where the changed object resides.
TVM Name
Database object the changed object is associated with.
Timestamp
Date and time when entry is added to log.
User
User making the Teradata DDL change.
A view is provided to the Audit Trail so that direct SQL can be performed on the table. The
view is located in the Teradata Database where the MDS repository is located and is called
mdsauditlog.
Filtering the Audit Trail Log
You can apply or remove a filter to the rows selected from the MDS repository MetaAuditLog
table, as displayed by the Auditlog Entries window by using the AuditLog Filter dialog box.
If the Audit log contains entries, the dialog box appears when you click View Audit Trail Log or
click View>Audit Log.
The dialog box also appears after clicking Filter in the Auditlog Entries window.
To view the Audit Log Trail without filtering, click Show all rows in the audit log table.
68

To view the Audit Log Trail with filtering, click Show only the rows in the audit log table based
on the filter below.
The following table shows the subsets of the columns in the MetaAuditLog table that can be
filtered.
Table 10: Filter Box Descriptions
List or Text Box
Description of Values
Event
Select the type of DDL Actions to be returned from the list:

Add objects -- DDL Actions: Create Table, Add Column, etc.
Filter: WHERE Event=0.
Update Objects -- DDL Actions: Alter Table, Replace Macro,
etc. Filter: WHERE Event=1.
Delete Objects -- DDL Actions: Drop Table, Drop Column,
etc. Filter: WHERE Event=2.
All Events: no filter is built in and all DDL Action types are
returned.
UserName
Filters based on text entered.

Teradata wildcard characters are permitted.
Filter: WHERE UserName LIKE 'xxxxxx.
If no text is entered no filter is created and all UserNames are
returned.
DatabaseName

Filter: WHERE DataBaseName LIKE 'xxxxxx.
If no text is entered no filter is created and all DataBaseNames
are returned.
TVM Name

Filter: WHERE TableName LIKE 'xxxxxx.
If no text is entered no filter is created and all TVM-names are
returned.
LogDate
Enter a start and/or end date in the format of yyyy-mm-dd to

select a range of audit log entries to be returned.
Filter: WHERE LogDate>=yyyy-mm-dd for the Starting On
box and Filter: WHERE LogDate<=yyyy-mm-dd for the
Ending On box.
The selected box values, if any, are all ANDd together using LIKE qualifiers.
To filter on text that contains single quotes, you must enter the single quote twice to get
properly quoted strings. For example to filter on users you must enter users in the box.
69

Click Update Row count to return a count of the number of rows selected with the current
filter settings.
Click Continue/Apply to:
1
Apply the filter settings to the audit log table.
Close this dialog box.
Execute a Refresh on the Auditlog Entries window to display the resulting rows.
This button is labeled Continue when the dialog box first comes up, and changes to Apply
when requested from the Auditlog window (when you click Filter).
Click Cancel to close the dialog box without applying any filter changes. The Auditlog Entries
window remains the same - a Refresh is not done since the selection criteria have not changed.
Click Help and a help page appears.
Note: If filtering is used to display the Auditlog Entries windows list-view and selecting all the
items in the list-view for deletion, the delete function will use the WHERE clause derived from
the filter. This type of delete will typically complete in a matter of seconds regardless of how
many items are involved. If filtering is used and specific items are selected for deletion, the
filter will not be used and the deletion can take several minutes depending upon the number
of items selected.
Activity Log
The Teradata MDS Activity Log is a table in the MDS repository. When activity logging is
enabled entries to the table track user access (reads, writes, deletes) to objects in the
repository. The log also indicates when access to an object is rejected because of permission
conflicts. The Activity Log, unlike the Audit Trail, is not limited to only tracking changes to
the DIM.
The contents of the Activity Log can be viewed through MetaSurf (while logged on with the
Administrator Profile) or by using SQL directly.The Activity Log can be accessed directly
through the metaactivitylog table.
Entries to the Activity Log cannot be viewed or deleted with MetaManager.
Entries to the Activity Log can be can deleted using bteq or SQL Assistant.
Under Activity Log click Activity Logging On or Activity Logging Off to turn the logging flag on
or off. The default is Off.

Teradata MDS provides the ability to retain tables, views and their component objects in a
dormant state after they have been deleted. The objects will not be removed from the
repository but they will not be viewable until they are reactivated. When reactivated the
business definitions and other relationships defined before the object was deleted will also be
reactivated.
Under Retain Associated Business Information, the Feature currently disabled option button
will be filled in by default. Click Enable this feature and OK to enable this option.
70

View or Delete MDS Log Files
When the feature is enabled, the option buttons will display as Feature currently enabled and
Disable this feature. Click Disable this feature and OK to disable the feature.
Note: Disabling the feature will permanently delete dormant objects and their associated
business information from the repository.
A repository with Retain Associated Business Information support enabled will require more
PERM and SPOOL space on the Teradata Database than the same repository created without
Retain Associated Business Information support enabled.

Teradata Meta Data Services creates a separate log file every day on local systems, where an
MDS application is running. The amount and type of information written to the logs varies
depending upon how the logging and trace levels are defined. See the Teradata Tools and
Utilities Installation Guide for the appropriate operating system for more information on
setting logging levels. Old log files should be deleted periodically.
To view or delete an MDS log:
1
Click MDS Configuration from the Windows control panel to display the Teradata Meta
Data Services Configuration dialog box.
Start MetaManager, then click Configure in the Teradata Meta Data Services Manager
Logon dialog box.
Click the Logging tab to see the log options.
71

72
Click View to see the current log file.
Click Log Files Manager to open the Log Files Manager window to see log files, their
names, and file sizes.

View or delete the logs in this window.
73

74
CHAPTER 4
MetaBrowse
Like MetaSurf, MetaBrowse can be used for browsing and searching the Teradata MDS
repository.
MetaBrowse enables you to:
Browse the metadata
Change user passwords
Create new metamodels (AIMs) in the MDS repository
Add new classes, properties or relationships to existing metamodels in the MDS repository
Create, edit and delete repository object data
Add and remove objects from collections
Search for class objects by name
Retrieve all class objects for a class
Search for objects by ID
Delete metamodels, classes, properties or relationships from the MDS repository
In versioned repositories, MetaBrowse also enables you to:
Apply version labels
Change versioning settings for metamodels and classes
View object versions
MetaBrowse is likely to be used by a more technical user, such as the MDS Administrator,
rather than a business user.
Start MetaBrowse
When the MDS core files are installed, MetaBrowse will be installed on the system. For
detailed installation information, see the Teradata Tools and Utilities Installation Guide for the
appropriate operating system.
If the default choice of where to place the MetaBrowse shortcut was selected during
installation, you will see the Teradata Meta Data Services Program group from the Windows
Start/Programs button. Choose MetaBrowse from the Teradata Meta Data Services Program
Group, and the MetaBrowse login screen appears.
75
Chapter 4: MetaBrowse
Start MetaBrowse
The first time MetaBrowse is run after installation and creation of a new MDS repository, you
will have to use the MDS Administrator password to open MetaBrowse. The default MDS
Administrator name is metasu, and the default password is metasu.
For security purposes, change the default password immediately. Validation of the user name
is not case-sensitive. However, the case of the password must match exactly.
After entering a valid user name and password, the opening screen of MetaBrowse appears.
To run MetaBrowse from the command line:

Select Start>Run and enter metabrowse mds_user mds_pwd
where mds_user and mds_pwd are the MDS Username and MDS Password parameters for the
system.
If MetaBrowse detects these two parameters, it will bypass the logon dialog box and attempt to
connect to the repository using the value of the parameters given. If MetaBrowse cannot
connect to the repository, a logon failure message will appear.
76
MetaBrowse Main Window

The MetaBrowse Main Window displays a:
Menu bar
Toolbar
Status bar
List of application models contained in the MDS repository
Menu Bar
Table 11: MetaBrowse Menu Bar
Menu
Command
File
Exit
Submenu
Description
Exits Meta Data Services (MDS) MetaBrowse.
77
Table 11: MetaBrowse Menu Bar (continued)
Menu
Command
View
Refresh Application
Metamodels
Refreshes the Application Metamodels to match the data in the

MDS repository. All other lists are cleared.
Get Class Objects
Displays a list of all of the objects of the selected class.
Get Class Objects

by Name
Displays a dialog box that allows searching for Class objects

using wildcards.
Toolbar
Displays a toolbar at the top of the MetaBrowse window when

checked. The icons in the toolbar are also available through
menu commands.
Status Bar
Displays a status bar when checked. The Status bar contains

help message information for menu and toolbar items.
Application
Metamodel
Creates a new metamodel, class or relationship. Deletes an

existing metamodel. Displays the properties of the selected
metamodel.
Class
Creates a new property or derived class. Deletes an existing

class. Displays the properties of the selected class.
Relationship
Deletes an existing relationship. Displays the properties of the

selected relationship.
Property
Deletes an existing property. Displays the properties of the

selected property.
Create Version
Label
Displays the Create Version Label dialog box to create a new

version label. Note: This menu item appears only if the
repository has versioning enabled.
Tools
Import
Options
Object Lookup
Ctrl+L
Submenu
Description
XML
Displays a Locate the XML file to import dialog box. In a

separate console window, the MetaXML utility will use the file
to make modifications to repository metamodels or data.
Refer to metaxml on page 158 for more in the MetaXML
utility.
MetaClient
Displays the MetaClient dialog box to run the MetaClient

utility. Refer to metaclient on page 144 for more in the
MetaClient utility.
Displays the Object Lookup dialog box to find an object using
its Object ID.
The Object ID is available in the Description dialog box.
Change Password
Ctrl+P
Window
Tree View
Ctrl+T
78
Displays the Change Password dialog box to changes a users

MDS password. The MDS Administrator (metasu) can change
anyones password.
Displays the tree view window from the root out to the
Application Metamodels, Classes, Properties, and
Relationships.
The Tree View
Table 11: MetaBrowse Menu Bar (continued)
Menu
Command
Submenu
Description
Help
Help Topics
Displays the Topics window of the online help.
About MetaBrowse
Displays the MetaBrowse About dialog box. The dialog box

contains copyright and version information for MDS
MetaBrowse.
The Tool Bar

The Tool bar contains the following icons:
Table 12: MetaBrowse Tool Bar
Icon
Function
Description
Performs the same function as

the Options menu Object
Lookup command.
Displays the Object Lookup dialog box to find an object using

its Object ID.

the Options menu Change
Password command.
Displays the Change Password dialog box to change a users

MDS password. The MDS Administrator (metasu) can change
anyones password.

the Windows menu Tree View
command.
Displays the Application Metamodels, Class, Properties, and

Relationships in the Tree View format.

the Help menu Help Topics
MetaBrowse command.
Displays the table of contents for online help.
Status bar
The Status bar across the bottom of the MetaBrowse Main Window offers current status
information. For example, the status bar might indicate that MDS is Loading Class Properties.
Application Metamodels
Select an application metamodel to populate and display its classes and relationships.
Each relationship also displays the origin class name and the destination class name.
Select a class to view the properties defined for the class.
The Tree View

The elements of the MDS repository can be displayed in a tree view.
In the MetaBrowse window, click Window>Tree View or click
displays:
. The Tree View window
79
The Tree View
Clicking on the + symbol expands and populates the application metamodels, classes,
properties, and relationships.
Clicking on the - symbol contracts the view back.

To view the properties of any item in the tree, right-click the item and click Properties to view
orHighlight the item, and click View>Properties.
Keep the following in mind when working in the Tree View window:
The root node is the MDS repository root object.
Under the root is the list of application metamodels.
Expanding a metamodel populates its root classes.
Expanding a class populates its objects.
Expanding an object populates its relationships.
Expanding a relationship populates its object collections.
Therepresents destination collections.
The represents origin collections.
To drill-down further levels, continue to expand objects and relationships.
80
Passwords
To to reload all Application metamodels in the repository click View>Refresh all.

To refresh only a selected part of the tree, highlight the part to refresh. Click View>Refresh
selection.
Passwords
The default password for the Teradata MDS Administrator is metasu. It should be changed as
soon as possible, for security reasons.
A password cannot have fewer than five or more than fourteen characters. Unlike user names,
passwords are case sensitive.
A user can change his or her own password. A user logged onto MetaBrowse as an MDS
Administrator can change any users password.
Click Options>Change Password.
The Change password dialog box appears.
Enter the old password in the Old Password box, the new password in the New Password and
the Confirm New Password boxes for confirmation.
Refresh Application Metamodels

Click View>Refresh Application Metamodels reloads all Application models in the repository.
81
Object Versioning
Object Versioning
By default, when versioning is turned on for a repository, all classes will support versioning of
data.
Turning on data versioning for a metamodel turns on versioning of all data objects for all
classes defined in the metamodel, provided versioning is enabled for the repository. Turning
off data versioning for a metamodel turns off versioning of all data objects for all classes
defined for the metamodel. If a class is used by two or more metamodels, the state of data
versioning for the class is determined by the last metamodel using the class that had its data
versioning changed.
Turning on data versioning for a class creates versions of all data objects in the class, provided
data versioning is enabled for the repository. Turning off versioning for a class disables
versioning of all objects in the class.
Modifying Versioning for MetaModel or Class

For a repository that is created, or migrated, with versioning enabled, all metadata objects will
be versioned by default (with the exception of objects from the MDSMetaModel metamodel).
However, this default behavior can be changed for any particular metamodel, or just one or
more of its classes, by using the Modify Versioning Setting dialog box.
When versioning is ON for a metamodel, all classes for it are created with versioning ON by
default, though any particular class can have its versioning turned OFF. When versioning is
OFF for a metamodel, all of its classes will also have versioning OFF, and cannot have any
selectively turned ON.
When versioning is ON for a class, all updates to its objects will cause a new version (with a
new object ID) to be created by the MDS engine. When versioning is OFF for a class, all object
updates/writes will re-write the published version of the object and no new version will be
created. (This is the same behavior as when versioning is not enabled for the repository.)
If a classs metamodel has versioning set to OFF versioning cannot be turned on for the class.
The versioning setting of a derived class cannot be changed.
Perform the following steps to modify the versioning setting for a metamodel or class:
82
Object Versioning
1
From the MetaBrowse main window select the metamodel or class whose versioning
setting you want to change.
Right-click on the metamodel name or class name to display the shortcut menu.
Click Versioning. The Modify Versioning Setting dialog box appears.
Click the appropriate option button to turn versioning ON or OFF.
If you are turning versioning OFF for the metamodel or class or it is currently OFF, the
Delete all previous versions of each object in every class of this metamodel. Only the latest
version of each object will remain check box will be checked.
Select this check box to:
Delete all non-published versions of all objects in all classes of the metamodel or all
objects in the selected class
83
Object Versioning
Set the surviving version of each object to 1
Clear this check box to delete no metamodel class objects or class objects.
6
Click OK to modify the versioning setting and exit.
Object Versions
This dialog box displays:
The object's currently published name in the title
A list of all versions of this object including the version's Name, Version number, Object Id
and Publish State
From this dialog box you can:
View a specific version's properties by selecting the version and click Properties. This
button is available only when exactly one object is currently selected.
Compare two object versions by selecting the versions to compare and click Compare. This
button is available only when exactly two objects are currently selected.
Delete versions of an object by selecting the versions you want to delete and click Delete.
This button is available only if one or more objects are currently selected.
Deleting all versions of an object effectively deletes the object from the repository. Also, the
currently published version of the object may be deleted--this will cause the next highest
84
Object Versioning
version of the object to become the current version. As always when deleting objects, or
object versions, from the repository, do so with care as this action cannot be undone.
Each version is a different object and therefore has a different object ID. The Publish State
can only be:
Current
Current/frozen
Inactive
Objects shown with a Current publish state are always the most current or active version.
Objects in this publish state can be modified.
Objects shown with a Current/frozen publish state are also the most current or active version
of an object but they cannot be modified because their destination or origin collections
contain earlier versions of other objects.
Objects shown with an Inactive publish state are earlier versions of an object. Objects in this
publish state cannot be modified.
Labels and Repository Objects

A label can be applied to the whole repository, to a specific metamodel, or to specific objects
within the repository. Only the currently published version of objects and classes can be
labeled. Applying a label to the whole repository or to a metamodel has an implicit
propagation to all objects within the repository or metamodel. Applying a label to a specific
class uses default propagation to all objects in the class. Applying a label to an individual
object uses default propagation to all objects accessed from that object through propagatedelete relationships.
Use this procedure to add a new label class to a repository that has versioning enabled.
To create a version label

Labels are simply repository objects applied or attached to versions of objects, to create a
specific set of object versions that have some special meaning. You might, for example, create
and apply a label that shows the date a particular database was loaded. That way you can track
changes and retrieve the set of object versions that represented the database system at the time
the database was loaded and the label was applied.
1
Click Tools>Create Version Label to create a new label.
After entering the information described below, click Create Label to create the class.
85
Object Versioning
Group
Box or Check Box
Description
Required Field
Name
Enter a name (up to 255 characters) to identify

the label. The name can then be applied to object
versions using the Apply Version Label dialog box.
Optional Fields
Description
Enter a full description of the purpose of the label.

The description is limited to 1024 characters.
Creator Name
Enter a string (up to 255 characters) to indicate

the creator of this label. If empty, the current
MDS user name will be used.
GUID
Enter the GUID. The GUID is a 16-byte string

used to uniquely identify the object, with a format
of {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx},
where the {} are required. If omitted or the string
is not in the correct format, MDS will generate
one for you.
Owner Name
Select a user from the Owner Name list. The default

is the MDS user.
Security Profile
Choose from the list of all the current security

profiles in the MDS repository. The default
selection is the MDSDefaultSecurityProfile.
After creating a label, you can apply or attach it to:
86
A metamodel
A class
Objects
Object Versioning
Applying a label to a metamodel also applies the label to all classes and objects in the
metamodel.
Applying a label to a class also applies the label to objects in the class.
Use this procedure to apply a label to a Metamodel.
To apply a label to a Metamodel

1
Right-click on the metamodel to be labeled to display the shortcut menu or press

Shift+F10 to bring up the context menu.
Click Apply Version Label to display the Apply Version Label dialog box.
From here select the label to be applied.
[Optional] If the label was applied to an earlier version of the metamodel, and you want it
to be applied to the current version, select the Move existing label check box to move the
label to the current version of the metamodel.
Click Apply.
This will cause the selected label to be applied (or attached) to all the objects in all the
classes of the selected metamodel.
Use this procedure to apply a label to apply a label to a Class.
87
Object Versioning
To apply a label to a Class

1
Click the metamodel containing the class to be labeled in the Application Metamodels pane
Right-click on the class to be labeled in the Classes pane to bring up the shortcut menu.
Right-click or click the properties key or press Shift+F10 to bring up the context menu.
Click Apply Version Label.
The Apply Version Label dialog box appears.
From the list, select the label to apply (or attach) to all the objects in all the class.
[Optional] Select the Propagate check box to apply this label to all destination objects of
the class objects.
[Optional] If the label was applied to an earlier version of the class, and you want it to be
applied to the current version, select the Move existing label check box to move the label to
the current version of the class.
Click Apply.
Applying a label to metamodel objects

A label can be applied to a metamodel object from:
The Get Class Objects dialog box
The Object Collections dialog box
88
Repository Objects
The Tree View window.

Perform the following steps to apply a label to a metamodel object:
1
Right-click on the object to be labeled to display the shortcut menu.
Click Apply Version Label.
The Apply Version Label dialog box appears.
Select a label from the list to apply (or attach) the label to the object.
[Optional] If the label was applied to an earlier version of the object, and you want it to be
applied to the current version, select the Move existing label check box to move the label to
the current version of the object.
[Optional] Select the Propagate check box to apply this label to all destination objects of
this object.
Click Apply.
Repository Objects
MetaBrowse allows you to create the following Repository Objects:
Metamodels (AIM)
Repository classes
Repository relationships
Repository class property
Derived class
Derived class property
Creating a Metamodel (AIM)

1
Right click on the metamodel name and select New and then AIM or, click
Tools>Application Metamodel>New>AIM. The Create Repository Meta Model dialog box
appears.
89
Repository Objects
90
Input the information as described below.
Model Name (required) - Enter a short name used to identify the metamodel. The
name is limited to 255 characters and must be unique to all metamodels in the
repository.
Model Description (required) - Enter a full description of the purpose of the

metamodel. The description is limited to 1024 characters.
Model GUID (optional) - Unless you are identifying an object coming from another
repository, it is best to leave this blank and let the MDS engine generate this value for
you. The GUID is a 16-byte string used to uniquely identify the object, with a format
of {xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx}, where the {} are required. If omitted or the
string is not in the correct format, MDS will generate one for you.
Model Owner - Choose from the drop-down list of all current users in the repository.
The default is the current logged-in user.
Model Security Profile - Choose from the drop-down list of all the current security
profiles in the MDS repository. The default selection is MDSDefaultSecurityProfile.
After entering the desired information, click Create Model to create the AIM.
Upon successful completion, a dialog box appears, allowing you to choose Done or
continue on with this metamodel by adding either Class or Relationship objects to the
AIM. You can add these objects now, add them later, or a combination of both.
Repository Objects
Creating a Repository Class

You can create a new class for a specific AIM.
91
Repository Objects
92
To create a new class in a particular metamodel, first make sure that metamodel name is
highlighted.
Right click on the metamodel name and click New>Class or click Tools>Application
Metamodel>New>Class. The Create Repository Class dialog box appears.
Under Required Fields, enter a short name in the Class Name box. The name will be used
to identify the class. The name is limited to 255 characters and must be unique to all
metamodels in the repository.
Under Required Fields, enter a full description of the purpose of the class in the Class
Description box. The description is limited to 1024 characters.
After entering the required information, you can make additional optional choices about
the class as described below or click Create Class to create the class.
Repository Objects
Class GUID - The GUID is a 16-byte string used to uniquely identify the object, with a
format of {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, where the {} are required. If
omitted or the string is not in the correct format, MDS will generate one for you.
Select Unique Names to have the names of objects within the class checked for
uniqueness. If it is cleared, the class will be allowed to have objects created within it
that have duplicate names.
Select Root Class to identify the class as a Root class of the metamodel. This means the
class is the highest class hierarchical level in the repository, and has no parent classes. A
root class needs to be defined to use the tree view in MetaBrowse.
The properties listed under Inheritance Properties are not required and should be used
after carefully considering whether they are needed for the class or metamodel being
created.
Select Abstract Class to create this class as an abstract class. An abstract class is a
class that does not have object instances. An abstract class can have properties and
can be the source or destination class in relationships. An abstract class is created to
enable subclasses of the class to inherit the properties and relationships of the
abstract class.
Select Super Class List to define the class that this class will inherit from. A class
that inherits from another class is called a subclass. The class that the subclass
inherits from is called a superclass. A subclass inherits the properties and
relationships of its superclasses. The list can have 0 or 1 superclasses.
Click Modify Class List to add or remove the super class for this class.
Select a current user from the Class Owner list. The list contains all current users in the
repository. The default is the AIMs owner.
Select a security profile from the Class Security Profile list. The list contains all the
current security profiles in the MDS repository. The default selection is the security
profile of the AIM that is adding the class.
Upon successful completion, a dialog box appears, allowing you to click Done or continue
on with this class by adding Properties to it. You can add Properties now, add them later,
or a combination of both.
93
Repository Objects
Super Class List

This dialog box allows you to add or remove a classs super class.
To specify the classs super class:
1
Under Repository AIM Classes, select a metamodel from the Model list. This list contains
all the models in the repository that the user has access to. The classes for the selected
metamodel will appear in the Model Classes list.
Select the class to be the super class for this class from the Model Class list. Currently a
class can have one superclass at most
Under Repository AIM Classes, click Add Class to the List to move the class from the Model
Class list to the Super Class List list under Current Super Class.
Click OK to save the changes made and return to the Create Repository Class dialog box
where the Super Class List under Inheritance Properties will be replaced with the one
created in this dialog box.
Clicking Cancel discards any changes made in this dialog box and returns to the Create
Repository Class dialog box.
To remove the classs super class:
94
Under Current Super Class, select the class from the Super Class List.
Click Remove Class from the List to remove the selected class from the Super Class List.
Click OK to save the changes made and return to the Create Repository Class dialog box
where the Super Class List will reflect the changes made in this dialog box.
Clicking Cancel discards any changes made in this dialog box and returns to the Create
Repository Class dialog box.
Repository Objects
Creating a Repository Relationship

You can create a new relationship between classes for a specific application information
metamodel (AIM).
Note: While a relationship is created within its metamodel, its Origin and Destination classes
can come from other AIMs.
1
To create a new relationship in a particular metamodel, first make sure that metamodel is
highlighted.
Right click on the metamodel name and click New>Relationship or click

Tools>Application Metamodel>New>Relationship. The Create Repository Relationship
dialog box appears.
Under Required Fields, enter a short name in the Relationship Name box. The name will be
used to identify the relationship. The name is limited to 255 characters and must be
unique to all relationships in the repository.
Under Required Fields, enter a full description of the purpose of the class in the
Relationship Description box. The description is limited to 1024 characters.
Under Origin and Destination Classes, select a metamodel from the Origin Model list.
Under Origin and Destination Classes, select a class from the Origin Class list.
Under Origin and Destination Classes, select a metamodel from the Destination Model list.
Under Origin and Destination Classes, select a class from the Destination Class list.
the relationship as described below or click Create Relation to create the relationship.
95
Repository Objects
96
Relationship GUID - The GUID is a 16-byte string used to uniquely identify the object,
with a format of {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, where the {} are required.
If omitted or the string is not in the correct format, MDS will generate one for you.
Select Propagate Delete to specify that when an object in the origin class is deleted all
objects in its destination collection will also be deleted.
Select Names to have the names of any classes added to this relationship checked for
unique names within the Relationship.
Select a current user from the Relationship Owner list. The list contains all the current
users in the repository. The default is the AIMs owner.
Select a security profile from the Relationship Security Profile list. The list contains all
the current security profiles in the MDS repository. The default selection is the security
profile of the AIM that is adding the relationship.
Repository Objects
Creating a Repository Class Property

You can create a new property of a class for a specific application information metamodel
(AIM).
1
To create a new property for a class, first make sure that a class is highlighted.
Right click on the class name and select New>Property or Tools>Class>New>Property. The
Create Repository Class Property dialog box appears.
Under Required Fields, enter a short name in the Property Name box to identify the
property. The name is limited to 255 characters and must be unique within the class.
Enter a full description of the purpose of the property in the Property Description box. The
description is limited to 1024 characters.
The value in the Relative Property ID box has a default value set to one greater than the
current largest one for the class. If you have a special relative numbering scheme for a
particular reason, use the default value. This ID can be any unique whole number greater
than 500.
97
Repository Objects
6
Under Property Data Information, select a datatype from the Data Type list. The list contains
all the various combinations of all the data types supported by the repository. The
selection includes both the SQL type and an associated variant type.
Under Property Data Information, if you have selected a SQL character or binary data type,
enter a size in the Size box. If you have selected a SQL_DECIMAL or SQL_NUMERIC
data type, enter a size in the Size box which will be the precision of the decimal/numeric
value. The total size of all Properties of a Class cannot exceed the Teradata maximum
column length (currently about 62,000 bytes).
Enter the digit setting in the Digits box if you have selected either SQL_DECIMAL or
SQL_NUMERIC data type from the Data Type list. This will be the scale of the decimal/
numeric value. If you have selected a SQL_TIME or SQL_TIMESTAMP data type, enter a
value in the Digits box, which will be the fraction-seconds precision of the value.
the property as described below or click Create Property to create the property.
Property GUID The GUID is a 16-byte string used to uniquely identify the object, with a
format of {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, where the {} are required. If
omitted or the string is not in the correct format, MDS will generate one for you.
Character Set For character properties, this designates the character set. The default is
set for the database by Teradata. (Some options are Latin, Unicode, etc.) See the
Teradata documentation for details on character sets. If you input an unrecognized
character set, an error will occur.
Select a property owner from the Property Owner list. The list contains all current users
in the repository. The default is the Class owner.
Select a security profile from the Property Security Profile list. The list contains all the
current security profiles in the MDS repository. The default selection is the security
profile of the Class that is adding the property.
Creating a Derived Class

Derived classes improve performance when searching for data in the MDS repository.
It allows you to create a logical class using properties that exist in already defined classes.
Derived class objects look like normal class objects to the APIs. However, only the class
definitions for a derived class are stored--there are no physical objects in a derived class.
You can create a new derived class for a specific application information metamodel (AIM).
98
Repository Objects
1
To create a new derived class from a base class, first make sure that base class is highlighted.
Right click on the base class name and select New>Derived Class or, from the
Tools>Class>New>Derived Class. The Create Derived Class dialog box appears.
Under Required Fields, the Base Class Name box displays the base class selected to derive
the new class. This box is read only.
Enter a short name in the Derived Class Name box. This name will be used to identify the
class. The name is limited to 255 characters and must be unique for all classes in the
metamodel.
Enter a full description of the purpose of the derived class in the Derived Class Description
box. The description is limited to 1024 characters.
99
Repository Objects
6
After entering the required information as described below, you can make additional
optional choices about the derived class or click Create Derived Class to create the derived
class.
Derived Class GUID - The GUID is a 16-byte string used to uniquely identify the object,
with a format of {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, where the {} are required.
If omitted or the string is not in the correct format, MDS will generate one for you.
Select a class owner from the Derived Class Owner list. The list contains all current
users in the repository. The default is the owner of the base class.
Select a security profile from the Derived Class Security Profile list. The list contains all
the current security profiles in the MDS repository. The default selection is the security
profile of the base class.
Upon successful completion, a dialog box appears that allows you to choose Done or
continue on with this class by adding Properties to it. You can add Properties now, add
them later, or a combination of both.
You can create a new derived class for a specific application information metamodel
(AIM).
Creating a Derived Class Property

You can create a new property of a derived class for a specific application information
metamodel (AIM).
100
To create a new property for a derived class, first make sure that the derived class is
highlighted.
Click Tools>Class>New>Property. The Create Derived Class Property dialog box appears.
Repository Objects
Under Required Fields, enter a short name in the Derived Property Name box to identify
the property. The name is limited to 255 characters and must be unique within the class.
Enter a full description of the purpose of the property in the Derived Property Description
box. The description is limited to 1024 characters.
The value in the Relative Property ID box has a default value set to one greater than the
current largest one for the class. If you have a special relative numbering scheme for a
particular reason, use the default value. This ID can be any unique whole number greater
than 500.
Under Base Property Information, select a property from the Base Property Name list. The
list contains all the properties in the base class.
Under Base Property Information, The Current Origin Relationships list contains the
current set of parent relationships of the current class. Select a relationship and Click >> to
add it to the Derived Property Relationships list.
101
Modifying Repository Objects
The Derived Property Relationships list contains the list of relationships starting from the
base class, leading to the class that contains the property to be derived from. Because the
list is in order, items can only be removed from the end of this list. Select the last item and
click << to move back down one in the relationship list. This re-populates the Current
Origin Relationships list and the Base Property Name list with the appropriate items.
Click Reset to reset the resets the values of the lists under Base Property Information back
to their starting state.
8
After entering the required information, you can make optional choices about the derived
property as described below or click Create Derived Property to create the derived class
property.
Derived Property GUID The GUID is a 16-byte string used to uniquely identify the
object, with a format of {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, where the {} are
required. If omitted or the string is not in the correct format, MDS will generate one
for you.
Select a property owner from the Derived Property Owner list. The list contains all
current users in the repository. The default is the Class owner.
Select a security profile from the Derived Property Security Profile list. The list contains
all the current security profiles in the MDS repository. The default selection is the
security profile of the Class that is adding the property.

Metabrowse allows you to modify the following existing Repository Objects:
102
Metamodels (AIM)
Repository classes
Repository relationships
Repository class property
Derived class
Derived class property
Modifying an AIM
1
Right-click on the metamodel name and select Modify or click Tools>Application

Metamodel>Modify. The Modify Repository Metamodel dialog box appears.
Change any of the fields enabled on the dialog box, and click Modify Model to update the
MDS repository with the changes. Click Cancel to exit the dialog box without making any
changes.
Upon successful completion, a dialog box appears. Click OK to exit the dialog box.
Modifying a Repository Class

1
To modify a class in a particular metamodel, first make sure that metamodel name is
highlighted.
Right-click on the class name and select Modify, or, Click Tools>Class>Modify. The Modify
Repository Class dialog box appears.
Change any of the fields enabled on the dialog box, and click Modify Class to update the
changes.
103
Modifying a Repository Relationship

1
To modify a relationship in a particular metamodel, first make sure that metamodel is

highlighted.
Right click on the relationship name and select Modify, or click Tools>Relationship>Modify.
The Modify Repository Relationship dialog box appears.
Change any of the fields enabled on the dialog box, and click Modify Relationship to update
the MDS repository with the changes. Click Cancel to exit the dialog box without making
any changes.
Modifying a Repository Class Property

1
To modify a property for a class, first make sure that a class is highlighted.
Right click on the property name and select Modify or click Tools>Property>Modify. The
Modify Repository Class Property dialog box appears.
Change any of the fields enabled on the dialog box, and click Modify Property to update the
changes.
Modifying a Derived Class

1
To modify a derived class from a base class, first make sure that base class is highlighted.
Right click on the derived class name and select Modify, or, click Tools>Class>Modify. The
Modify Derived Class dialog box appears.
Change any of the fields enabled on the dialog box, and click Modify Derived Class to
update the MDS repository with the changes. Click Cancel to exit the dialog box without
making any changes.
Modifying a Derived Class Property
104
To modify a property for a derived class, first make sure that the derived class is
highlighted.
Right click on the property class name and select Modify, or, click Tools>Property>Modify.
The Modify Derived Class Property dialog box appears.
Change any of the fields enabled on the dialog box, and click Modify Property to update the
changes.
Properties
Properties
You can look at the properties for each:
Application Metamodel
Class
Property
Relationship
Whether you can see common properties, unique properties or security profile, varies with
the element selected.
There are five different ways to view the properties of each element.
Double-click the name, or
Right-click the element, and click Properties, or
Press Shift+F10, and click Properties, or
Press the Context menu key (if available), or
Select the element, then choose the Tools menu. The element category (Application
Metamodel, Class, Property or Relationship) will become active, and you can choose it
from the menu.
Following is an example of using the Tools menu to obtain the properties for a Class.
Remember that you can only view and not change properties for any of the predefined
metamodels.
Common Properties
You can look at the common properties for each:
Application Metamodel
Class
Property
Relationship
105
Properties
Object
The Common Properties tab displays the values of the common properties of the selected
object.
Table 13: Common Properties for Objects
Text Box
Description
Name
Displays the Name of the selected object.
Object ID
Displays the ID assigned to the selected object. This ID is

unique in the MDS Repository database.
Global Unique ID
Displays the Global Unique ID (GUID) of the selected object.

A GUID is a 128-bit structure which is unique, no matter
which computer generates it.
Class
Date Created
Displays the Date and Time the selected object was created.
Date Updated
Displays the Date and Time the selected object was last
modified.
Description
Displays the Description of the selected object. The

description is limited to 1024 bytes.
Unique Properties of a Relationship

You can view the unique properties of a relationship, but you cannot change them.
Table 14: Unique Properties for Relationships
Group
Box or Checkbox
Description
Relationship Classes
Origin Class
Displays the Origin Class Name.
Destination Class
Displays the Destination Class Name.
Unique Name
If selected, MDS validates that all objects added to the

collection of this Relationship have a unique name.
Propagate Delete
If selected, children of the relationship will be deleted if the

origin object is deleted.
Relationship Attributes
Section
Unique Properties of a Property

You can view the unique properties of a property, but you cannot change them.
106
Properties
Table 15: Unique Properties for Properties
Group
Box or Checkbox
Description
Property Type
ODBC Type
Displays the SQL data type of the Property object.
Variant Type
Describes the COM type, which determines the format of the

field for MDS to use to get and set the field.
Size
Displays the Size, in bytes, of the Property object if a character

type or the number of digits, if size is a numeric type.
Digits
Displays the number of digits to the right of the decimal point

for a numeric Property object.
Relative ID
Displays the Relative Property ID assigned to the property

object.
Character Set
Displays the name of the character set assigned to the property

object.
Derived Property
If active, signals that this is a derived property.
Base Property Name
Displays the name of the property the property was derived

from.
Relationships to
Property
Explains how the derived property was obtained from the base
property.
Property Size
Property ID
Unique Properties of a Class

You can view the unique properties of a class, but you cannot change them.
Table 16: Unique Properties for Classes
Box or Checkbox
Description
Serial
Every time a property is added or removed from a class, the

serial of the class is incremented by 1. The initial serial of a
class is 1.
Unique Name
If checked, MDS validates that all the objects in the Class have
a unique name.
Derived Class
If checked, signals that this class is a derived class.
Base Class ID
If this is a derived class, displays the object ID for the class

from which this class was derived.
Abstract Class
If checked, signals that this is an abstract class.
Super Class List
Super classes are classes that the selected class inherits from.
Versioning
This property indicates the current version status of the class

objects; it appears only if the repository is versioned.
107
Properties
Unique Properties for the Object

You can view the unique properties for a Database System object, but you cannot change
them.
Table 17: Unique Properties for Objects
Group
Element
Description
Name
This column lists the unique properties for the object.
Value
This column displays the value associated with the property in

the name column.
Display of selected
property value
When a list of properties is displayed, it can be difficult to see

the entire value in the list display.
Highlighting the property name will display its value in this
larger box with scroll bars.
Change decimal
format display
If the selected property has a floating point value, you can

change the precision and format of the value.
Precision
Enter the number of digits to be displayed to the right of the

decimal point.
Fixed/Scientific
Click either Fixed or Scientific to set the display format.
Apply
Click to see the values in the new format.
Security Profile for the Object

A security profile defines who can access the object. One security profile is assigned to each
object in the repository. Access to the object is based on the access type permissions defined in
the assigned security profile.
Security profiles for objects can be viewed but not changed in MetaBrowse. Security profiles
are created, edited and assigned in MetaManager.
Table 18: Security Profile for an Object
108
Box
Description
Name
Displays the name of the object.
Owner
Displays the name of the owner of the object.
Security Profile
Displays the name of the security profile that has been

assigned to the object.
Name/Access Type
Displays the users and application groups and shows the access
type for each user or group.
Finding Objects
View the Labels Applied to the Object

If versioning is enabled for the repository, the list box on this page will display all the labels
applied to this version of the object. If the list box is empty, no labels have been applied to this
version of the object.
Finding Objects
Every object in the repository has an object ID number. You can find an object if you know its
Object ID number. An object ID is one of the Common Properties associated with every
object in the MDS repository.
For example, if you know that an objects ID is 10781, click Options>Object Lookup. The
Object Lookup dialog box appears.
Type in the Object ID Number, for example 10781 then click OK. The search result section will
display the object.
109
Finding Objects
By right-clicking the search results of Object ID Lookup, you will see your options for
continued searching.
You can also see the properties for any object that is contained in the results of the search.
Get Class Objects

To retrieve all Objects in a class:
1
Select the Class.
Click View>Get Class Objects.
or
1
Right-click the Class name to display the shortcut menu.
Click Get Class Objects.
The following window shows an example of a result of searching for Column Class Objects.
110
Finding Objects
The Get Class Objects dialog box appears and displays:
Application Metamodel name
The Class Name
The Objects
From Get Class Objects dialog box you can:
Create a new object by clicking New Object to start the Create Repository Wizard.
Edit an object by clicking Edit Object.
Delete an object by clicking Delete Object.
View the properties of an object by right-clicking the object and choosing Properties.
View the collection of an object by right-clicking the object and choosing Get Object
Collection.
If the repository has versioning enabled, you can also:
View the versions of an object by right-clicking the object and choosing Get Object
Versions
Apply a version label to the object by right-clicking the object and choosing Apply Version
Label
111
Finding Objects
Get Class Objects by Name

To retrieve Class Objects by name:
1
Select the Class name.
Click View>Get Class Objects by Name,
or
1
Right-click the Class name to display the shortcut menu.
Click Get Class Objects By Name.
The Find by Name dialog box appears.
Enter a search criteria in the Find box and click OK.

The following dialog box shows an example configuration for searching a class for all objects
with book in their names.
112
Finding Objects
The following screen shows the results of a search looking for class objects that contain the
term book.
The Get Class Objects by Name dialog box appears and displays
The Application Metamodel name
113
Finding Objects
The Class Name
The search criteria
A list of all of the Objects that matched the search.
From this window you can:
Create a new object by clicking New Object to start the Create Repository Wizard.
Edit an object by clicking Edit Object.
Delete an object by clicking Delete Object.
View the properties of an object by right-clicking the object and choosing Properties.
View the collection of an object by right-clicking the object and choosing Get Object
Collection.
If the repository has versioning enabled, you can also:
View the versions of an object by right-clicking the object and choosing Get Object
Versions
Apply a version label to the object by right-clicking the object and choosing Apply Version
Label
Get Object Collection

After an object has been retrieved, you can obtain the collections for the object.
1
Right-click an object in the Get Class Objects dialog box, the Object Look up search result
dialog box or the Get Class Objects by Name results dialog box to display the shortcut
menu.
Click Get Object Collections to display the object collection.
After the Object Collection or collections are retrieved, the Object Collections dialog box
appears.
114
Finding Objects
The top of this window shows:
The Application Metamodel name
The Class name
The Object name of the Collection.
The left pane of the window displays the Name, Origin and Destination of each relationship
listed.
In this pane you can:
Right-click on a Relationship Name to access its properties.
Highlight a Relationship Name to display a list of objects in the right pane of the window.
Highlighting an object listed in the right pane of the window allows you to:
Right-click the object and select Properties to access its properties
Right-click the object and select Get Object Collection to display a new Get Object
Collection dialog box for the object
Click Edit Object to modify the object
Click Delete Object to remove the object.

Note: Edit Object and Delete Object will be disabled when viewing objects from the builtin MDSMetaModel used internally by MDS.
If the repository has versioning enabled, highlighting an object listed in the right pane of
the window will also allow you to:
115
Class Objects and Relationships
Caution:
Right-click the object and select Get Object Versions to display the Object Versions dialog
box for the object.
Clicking Delete Object from this dialog box removes the object from the class and cannot be
undone.
Note: If an object is selected and Delete Object is disabled, this indicates that the object cannot
be deleted.
If an object is selected and Edit Object is disabled, this indicates that either the object cannot
be edited or that more than one object is selected.
Class Objects and Relationships

Relationships map or link one or more objects from one class to one or more objects in
another class. The resulting mapping or linking is called a collection. You can add or remove
class objects to a collection by performing the following steps:
1
In the Relationships pane of the main window, select the relationship that defines the
collection you want to add or remove a class object from.
Click Tools>Relationship>Add Object to Collection or Tools>Relationship>Remove Object

from Collection.
or
In the Relationships pane of the main window, right-click on the relationship that defines
the collection to add or remove a class object from.
Click Relationship Add Object to Collection or Remove Object from Collection.
The appropriate dialog box appears.
Add an Object to a Collection

This dialog box allows you to add one or more objects to the collection defined by the selected
relationship.
To add an object to a collection, perform the following steps:
1
Select an object from the Origin Class list.
Select an object from the Destination Class list that you want to connect (or link) the left
pane objects to.
Click Add Object.
MDS places no restrictions on the cardinality of the origin or destination collections. They
can be one-to-one, one-to-many or many-to-many. Any model-specific restriction
enforcements are your responsibility. Other restrictions such as not allowing duplicate named
objects in the collection can be specified for the relationship and enforced by MDS.
116
Creating, Editing and Deleting Class Objects
Remove an Object from a Collection

This dialog box allows you to remove one or more objects from the collection defined by the
selected relationship.
Click Origin Class to display the list of objects in the Origin class in the left pane of the
window.
Click Destination Class to display the list of objects in the Destination class in the left pane of
the window.
To remove an object from a collection, perform the following steps:
1
Select an object from the list in the left pane to display its associated object or objects in a
list in the right pane of the window.
From the right pane listing, select the object that you want to break the left pane object s
connection to.
Click Remove Object.
The logical connection between the two class objects will be severed unless an error message
indicates otherwise.

You can create, edit or delete class objects in a number of different ways depending upon
which tasks you are performing and the class whose objects you are trying to change.
Deleting Class Objects

You can delete class objects in the following ways:
Click Delete Object in the Get Class Objects dialog box
Click Delete Object in the Get Class Objects by Name dialog box
Click Delete Object in the Object Collections dialog box
Click Delete Object in the Object Lookup dialog box
Creating a Class Object

You can create class objects in the following ways:
Click New Object in the Get Class Objects dialog box
Click New Object in the Get Class Objects by Name dialog box
All of these actions invoke the Create Repository Object Wizard. Use the Create Repository
Object Wizard to create a new object in the named class to the Teradata MDS repository.
Editing a Class Object

You can edit class objects in the following ways:
117
Click Edit Object in the Get Class Objects dialog box.
Click Edit Object in the Get Class Objects by Name dialog box.
Click Edit Object in the Object Lookup dialog box
Click Edit Object in the Object Collections dialog box
Object Wizard to edit the object in the named class to the Teradata MDS repository.
Adding an Object to a Class

You can add class objects to a class in the following ways:
1
Right-click the name of the class to add an object of this class type.
Click New>Object Data
or
1
Select name of the class you want to add an object to.
Click Tools>New>Object Data
Because adding an object to a class is the same thing as creating a new class object, you can add
an object to a class in the following ways:
Click New Object in the Get Class Objects dialog box.
Click New Object in the Get Class Objects by Name dialog box.
Click New Object in the Object Lookup dialog box.
Object Wizard to create a new object in the named class to the Teradata MDS repository.
Creating or Editing with the Create Repository Object Wizard

After invoking the Create Repository Object Wizard to edit or create a new class object, you
will step through a series of dialog boxes that define the following for the object:
Common Properties
Unique Properties
Security Properties
Common Properties
This page of the wizard allows you to enter the common properties for the new object.
Table 19: Common Properties
Field
Description
Class

If you are creating a new object this field is Read Only.
If you are editing an existing object you can edit this field.
118
Table 19: Common Properties (continued)
Field
Description
Name
Required entry. Enter the name (up to 255 characters) to be

associated with this object. If you are editing an existing object
you can edit this field.
GUID
Optional entry. If left blank the repository engine will generate

one.
Description
Optional entry. Enter any descriptive text (up to 1024

characters) to be associated with this object.
If you are editing an existing object you can edit this field.
If you are creating a new object, click Next to go to the Unique Properties Page of the Wizard or
click Cancel to abort the creation of the new object.
If you are editing an existing object, after you have edited the desired fields, click OK or Apply
to apply the changes.
Note: Clicking OK exits the dialog box. Clicking Apply applies the changes and allows you to
step through the other tabs.
Click Cancel to abort changes to the object and exit the dialog box. If any changes are pending,
you will be asked if you want to discard them.
Unique Properties
This page of the wizard allows you to enter or specify the unique properties for the new object.
Change or set a unique property by performing the following steps:
1
Select the property from the Property/Value list box. The default value for each property is
NULL until set.
Enter the desired value in the Value[Type] box.
If you want the value of the property to be sent directly to the database without the MDS
engine surrounding the value with single quotes, check the Literal String check box. If you
do not want the value of the property to be sent directly to the database, omit this step and
proceed to step 4.
Click Set Value to change the value for the property. The Property /Value list will be
updated with your change.
Repeat these steps for each property to be assigned a value.
If you are creating a new object:
Click Back to return to the Common Properties Page of the wizard.
Click Next to continue to the Security Properties Page of the wizard.
Click Cancel to dismiss the wizard and abort the creation of a new object.
If you are editing an existing object, after you have edited the desired fields, click OK or Apply
to apply the changes.
119
Deleting Metamodels from the Repository
Security Properties
Use this page of the wizard to:
Identify the security profile to be associated with the object
Identify the owner of the object
Specify the security properties for the new object.

Field
Description
Name
Read Only. Displays the name of the object.
Owner
A drop down menu of all repository owners. The

logged on owner is the default value.
Security Profile
A drop down menu of all Security Profiles in the

repository. The default is the Security Profile for the
class.
Name/Access Type
Displays the users and application groups and shows

the access type for each user or group.
To select an owner or a Security Profile, use the drop down menus.

If creating a new object:
Click Back to return to the Unique Properties Page of the wizard.
Click Cancel to dismiss the wizard and abort the creation of a new object.
Click Finish to invoke a Confirm dialog box The new object will not be created until you
click OK in the Confirm dialog box. Clicking Cancel in the Confirm dialog box will return
you to the wizard.
If editing an existing object, edit the desired fields and click OK or Apply to apply the changes.

Deleting metamodel items should be done very carefully, if at all. Do not delete a metamodel
item if you are unsure as to whether it should be deleted.
120
When a metamodel item is deleted, it is completely removed from the MDS repository; there
is no undo or recovery of the metamodel item.
When a metamodel is deleted, all classes in that metamodel are also deleted.
When a class is deleted, that class and every object in that class is deleted.
When a property is deleted, it is removed from every object in that class.
When a relationship is deleted, it is completely removed.
To delete metamodel items from the repository:

1
Highlight the application information metamodel (AIM), Class, Relationship or

Property.
Right-click the object and select Delete.
or
1
From the Tools menu, choose AIM, Class, Relationship or Property.
Click Delete.
There may be a delay for deletion to be accomplished, depending on the number of

Metamodel items being deleted.
Note: The three pre-defined and loaded metamodels (Core, DatabaseModel, and
MDSMetamodel) cannot be deleted.
121
122
CHAPTER 5
Permissions, User Names, Passwords

and Security Profiles
This chapter contains information on working with Users, Groups, Permissions and Security
Profiles.
MDS User Accounts

Just as Linux and Windows have defined user accounts that determine which users have logon
privileges, MDS also has user accounts that define who can access the MDS repository.
In MDS, you need to understand the difference between the following:
Database user
MDS Administrator
MDS user
The Database user is the Teradata login used by MDS to connect to the repository database.
That login is identified by the user name and password set in the MDS Database
Configuration.
The MDS default Administrator is created when the MDS repository is created. Other MDS
Administrators can be created by an MDS Administrator using MetaManager.
The MDS default Administrator user name is metasu. The default password for the MDS
Administrator is also metasu.
Note: You cannot change the MDS Administrator user name, it is always metasu.
To maintain the integrity of the system, it is recommended that you change the MDS
Administrator password immediately after the installation.
MDS Users are added later by the MDS Administrator using MetaManager. The MDS
Administrator is responsible for adding other MDS users through the MDS MetaManager
dialog box.
MDS users created without MDS Administrator privileges are non-administrators. Their
access to data in the MDS repository database is based on ownership and permissions of the
objects in the MDS repository database, which is set using security profiles. These users can be
assigned to security profiles with different levels of access permission.
123
Chapter 5: Permissions, User Names, Passwords and Security Profiles

Teradata MDS Users and Groups
Teradata MDS Users and Groups

An MDS user name and password is required to connect to the MDS repository. When
connected, the metadata objects that can be viewed or modified by the user are determined by
the permissions in the security profile assigned to each metadata object stored in the MDS
repository. For more information on security profiles see Security Profiles on page 133.
If a specific object is requested and the user does not have permissions, a permission error is
returned. If a collection of objects is requested, MDS will return only the objects that the user
has permission to access.
Changing MDS User Passwords

To change the password of an MDS user, open MetaManager.
From the Windows task bar, select Start, then Programs, then Teradata Meta Data Services (or
the Program Group name that was designated during MDS installation), then MetaManager.
After logging in, the Teradata Meta Data Services Manager main screen appears.
In MetaManager, click Tools>Change Password.
Select the appropriate MDS User Name from the MDS User Name list.
Type the password into the New Password, and the Confirm New Password edit boxes.
Click OK to change the password in the repository, or Cancel to dismiss the dialog without any
change.
If it the password for metasu is being changed, you will be prompted to confirm the change
before it is completed.
Since the user for MetaManager is always an MDS administrator, this dialog does not require
entering the previous password before changing the password.
Note: The default password for the default MDS Administrator is metasu. It should be
changed as soon as possible for security reasons.
Accessing User Manager

To view or change Users and User Groups, open MetaManager.
From the Windows task bar, select Start, then Programs, then Teradata Meta Data Services (or
the Program Group name that was designated during MDS installation), then MetaManager.
After logging in, the Teradata Meta Data Services Manager main screen appears.
124

Accessing User Manager
To Access User Manager:
Click
or
click Tools>User Manager
The User Manager window will display.

In the User Manager window, you see
The application group(s), if any,
All users in the MDS repository.
125

Application Groups
Application Groups
The application group is a label for several users who have been logically grouped together
and given a name. An application group can have zero to many users. The application group is
a means for granting a subset of users permissions to a set of metadata objects.
A user may or may not be a member of an application group.
An application group does not have to have any members to exist.
Adding a Group
Open the User Manager window.
Click Add Group. The Add Application Group window appears.
Type in an Application Group Name and a description if you choose.
126

Application Groups
Click OK to add the group. The new group will now appear in User Manager.
Delete Group
To delete a group:
Highlight the name if the group you would like to delete, then click Delete Group, or
Right-click the group name in the Application Group list in User Manager.
127

Application Groups
To delete the application group, click Delete and the group will be removed.
Deleting an application group does not delete the users in that group.
Membership Option
You can change or view group memberships from either the group or the user perspective.
Adding or removing members from a group
The membership option for a group lets you:
Add one or more users to the group
Remove one or more users from the group
Set memberships for the group
To add or remove users from a group:
128
Select the group name in the Application group list and
Click Membership

Application Groups
or
Right-click the group name and click Membership option to display the Membership
window.
You can add or remove users by selecting the name and clicking Add>> or <<Remove.
Changing group memberships for users
The membership for a user lets you:
Add the user to one or more groups
Remove the user from one or more groups
Set memberships for the user
To add or remove a user from a group:

1
Select the group name in the All Users list and
Click Membership
or
Right-click the user name and select the Membership option
You can add or remove users by selecting the name and clicking Add>> or <<Remove.
To access the options for a user, right-click user name in the User Manager.
129

Managing Users
Managing Users
To view or change settings for individual users, open the User Manager window.
Adding a User
From the User Manager window click Add User. The Add User window appears.
130

Managing Users
Type in the User Name and User Password. You will have to type in the password twice for it to
be accepted. You can add a description of the user in the Description box, as in the example
shown.
If you want to create an MDS Administrator, check the MDS Administrator box.
Click OK to add the user. The new user will now appear in User Manager.
131

Managing Users
Deleting Users
To delete a user:
Highlight the name of the user you would like to delete and click Delete User.
or
Right-click the user to delete and click Delete from the options.
The user will be removed. A user cannot be deleted if the user is the owner of any objects in
the repository.
Deleting all the users in a group does not delete that application group.
132

Security Profiles
Security Profiles
A security profile contains permissions for a set of groups and users.
One and only one security profile is assigned to each object in the repository.
Access to the object is based on the access type permissions defined in the assigned security
profile.
One security profile can be assigned to many objects.
If an object is not given public read access, a user will not be able to see the object unless
specifically granted access as a user or as a member of an application group in the security
profile for that object.
Access to objects in MetaSurf, MetaBrowse or other MDS applications is based on the access
type in the Security Profile associated with the object. If an object is not given public read
access, a user will not be able to see the object unless specifically granted access as a user or as
a member of an application group in the Security Profile for that object.
In the example in Figure 2, Mary, Fred and all users in the Acct and Payroll Application
Groups have read permission to databases A and B. Fred and all the users in the Payroll
Application Group can update objects corresponding to databases A and B.
Lucy and all users in the Application Group Acct have read and write access to databases C and
D. No other users can view these databases.
Figure 2: Example Security Profiles
Security
Profile
User: Mary Rights: Read
Payroll
Group: Acct Rights: Read
Payroll
Acct
Database
User: Fred Rights: Full
Group: Payroll Rights: Full
User: Lucy Rights: Full

D
Acct
Group: Acct Rights: Full

3047B035
It is possible for a user to have multiple privileges defined in the profile. In the above example,
user Mary has been granted explicit Read rights. If Mary is also a member of the Payroll group,
she will also have Full rights. The user will be granted the highest level of rights (in this case,
Full rights).
There is a special term that can be used to define rights in a Security Profile. The term is
Everyone. Everyone specifies permissions for anyone connecting to the MDS repository.
133

Security Profiles
Accessing Security Profiles

Access Security Profiles by clicking Tools>Security Profile from MetaManager main window,
or
Click
The Security Profile dialog box appears.
Security Profile Tab
The first tab is the Security Profile.
You can view the list of Security Profiles that have been defined.
You can add a new Security Profile by clicking Add.
You can delete a Security Profile by highlighting it and clicking Delete.
Click Refresh List to update the display.
You can invoke the Objects Assigned to Security Profile to view the objects that have the
selected Security Profile by clicking the View Objects Using Profile. This operation may
take longer than expected since all associated class objects will be read.
You can view specifics about the Security Profile or change parameters by clicking View/
Edit Profile.
Note: You cannot delete a Security Profile if the Security Profile is currently assigned to one or
more objects in the repository are assigned to the Security Profile.
134

Security Profiles
Adding a Security Profile/Editing a Security Profile

In the Security Profile dialog, click Add or View/Edit Profile. The Add Security Profile dialog box
appears.
Enter the Name of the Security Profile. The name is limited to 255 characters and must be
unique.
Enter a Description of the Profile. The description is limited to 1024 characters.
Enter the Owner of the Profile.
View a list of users and application groups set in this Security Profile and their access type.
Add users or application groups to the Security Profile by clicking Add Names button that
displays a list of Users and Application Groups.
Change the type of access for the user or application group by highlighting the name(s)
and selecting the access type:
Table 20: Access Types for Security Profiles
Access Type
Description
Read
Grants read access to an object.

Read access is the only access type needed for users that only read
objects in the MDS repository. The remaining access types are used for
customizing the type of update privileges that can be applied to objects.
135

Security Profiles
Table 20: Access Types for Security Profiles (continued)
Access Type
Description
Collection
Grants read access to an object and the ability to add or remove the
object from a collection.
Collection permission is needed on an object if it is to be added to a
collection.
You would grant collection permission (without update permission) to
an object if you want to make it available to other users to add to
existing or new relationships. For example, collection permission is
needed on most objects in the DIM. Metaclient links the source in the
load script to the destination table or view object in the DIM. It also
links the source fields in the load script to the column and view column
objects in the DIM. For metaclient to set up these relationships, the
user running metaclient must have collection permission to all DIM
objects that will be linked to the client load objects.
To add or remove an object from a collection, the user must have
Collection permissions to the source, destination and relationship
description objects.
Update
Grants read, update and delete permission to the object and the ability
to add or remove the object from a collection.
Full
Grants read, update and delete permission to the object and the ability
to add or remove the object from a collection. Also when applied to a
class description, grants permission to create objects of the class.
There are some special permission types.
136

Security Profiles
Table 21: Special Permission Types for Security Profiles
Permission Type
Description
Object Owner
Is granted Full permission to the object.
AIM objects
Model Objects - only the owner can delete (updates are not allowed).
ClassDescription objects - only the owner can delete the class
description or add or remove Property Description objects. (updates
are not allowed).
RelationshipDescription objects - only the owner can delete (updates
are not allowed).
MDS
Administrators
Have Full permission on all objects.
Adding and Deleting Users and Application Groups

You can add Users and Groups to the Security Profile by highlighting the user or group name
and clicking Add>> or << Remove.
Delete users and application groups from the security profile by highlighting the name and
clicking Delete Names.
137

Assigning Security Profiles to Objects

The second, third and fourth tabs in the Security Profile dialog are for assigning security
profiles to AIMs, Classes, and Objects in the repository.
Assigning AIM Profiles

Use the AIM Profiles tab to assign security profiles to AIMS.
Here you can:
View or change the Security Profiles assigned to each metamodel in the repository.
Assign a new Security Profile for a metamodel by highlighting the model, then choosing a
new Security Profile from the list and clicking OK.
Select or Clear the Assign the Profile to all the Classes and Relationships in the Model check
box.
Assigning Class Profiles

Use the Class Profiles tab to assign security profiles to classes.
138

Here you can:
Select a metamodel from the list to view the classes.
Change the Security Profile assigned to a class by highlighting the class and then selecting a
new profile from the Security Profile list.
Select or clear the Assign the Profile to all Current Objects in the Class check box.
Assigning Object Profiles

Use the Object Profile tab to assign security profiles to objects.
139

Here you can:
Select the metamodel and class from the Select AIM and Select Class lists.
Change the Security Profile assigned to an object by highlighting the object and then
selecting a new Security Profile from the Security Profile list and click OK.
Select or clear the Assign the Profile to Related Objects check box.
Related objects are objects that are the destination objects in collections of relationships that
have delete propagation flag turned on.
A relationship that has delete propagation flag turned on is called a containment relationship.
Propagation will continue until a class object is reached that has no containment
relationships.
Most of the DIM relationships are containment relationships. See the following figure:
140

Figure 3: Containment Relationships
DatabaseOwnsDatabases
Setting the group

permissions here
DataBase
DatabaseHasTables
DatabaseHasViews
Table
TableHasCheckConstraints
Check
View
TableHasColumns
Column
TableHasIndices
Index
IndexContainsColumns
IndexColumn
ViewHasTableColumns
ViewHasColumns
ViewColumn
TableHasRefConstraints
Reference
ConstraintReferenceColumns
ReferenceColumn
Can set the group

permissions group in all
destination classes
3047A010
For example, if you change the security profile of a database named Customer and select the
Assign the Profile to Related Objects check box, the security profile will be set in the Customer
database object and all Tables, Columns, Views, etc. associated with that database.
141

142
CHAPTER 6
MDS Utility Programs
This chapter provides additional information on the following utility programs that can be
used by an MDS Administrator invoked through MetaManager or MetaBrowse. Most can be
used from a DOS or Linux command line.
mdsconfig (Linux only)
metaclient (see metaclient)
metacreate
metadelete
metaload
metamigrate
metaviews
metaxml (Windows only) (see metaxml)
prtconfig (Linux only)
mdsconfig (Linux only)

Purpose
The mdsconfig command line program is used to set configuration parameters on a Linux
workstation.
Requirement
Must be logged on as root to run mdsconfig.
Syntax
mdsconfig -h <metahome> -o <DSNname> -u <dbuser> -p <dbpasswd> -l
<loglevel> -t <tracelevel> -s <numISvr>
mdsconfig H
Table 22: Teradata mdsconfig Input Parameters
Parameter
Description
-h <metahome>
The MDS Installation folder.

It is highly recommended that the default location of /opt/teradata/mds not be
changed.
143
Chapter 6: MDS Utility Programs

metaclient
Table 22: Teradata mdsconfig Input Parameters (continued)
Parameter
Description
-o <DSN name>
Default ODBC Data Source Name (DSN) that MDS uses to connect to the
Teradata Database System containing the MDS repository.
-u <dbuser>
Database User Name that MDS uses to log on to the Teradata Database System
to access the MDS repository.
-p <dbpasswd>
Database User Password that MDS uses to log on to the Teradata Database
System to access the MDS repository.
-l <loglevel>
Error Log level (0-5). Where 0 is the least amount of logging and 5 is the
greatest amount.
-t <tracelevel>
Trace level (0-5) to be used for Application debugging. Where 0 is the least
amount of tracing and 5 is the greatest amount of tracing.
-s <numIntSvr>
Number of Integrity Servers for the MDS Data Definition Language (DDL)
Gateway to start. Defaults to 5.
-H
Displays option list.
metaclient
Purpose
The metaclient utility loads the Client Load metadata into the MDS repositorys Client Load
Metamodel (CLM).
Description
The metaclient utility uses scripts to load the Client Load metadata into the MDS repositorys
Client Load Metamodel (CLM).
The metaclient program supports non-unique client load script names. The scriptqualifier is
used in conjunction with the script name to attempt to uniquely identify each script.
Metaclient will version multiple instances of a client load script's executions if versioning is
enabled in the MDS repository.
If two scripts have the same name and identification information, the two scripts will be
judged to be multiple executions of the same script and the information for the current script
being processed will update (overwrite) the existing script information if versioning is not
enabled in the MDS repository.
If versioning is enabled in the MDS repository, the information for the current script being
processed will update the existing script information.
If a script ID mismatch occurs [a new script or a script whose ID information changes (i.e.,
the script is moved to a different location on the origin system)], the script information will
144

metaclient
be processed as a new script. There is currently no facility in the metaclient utility to delete old
script information.
No versioning of multiple instances of a client load script's executions are stored (although a
VersionID property is included in the CLM for future implementation of versioning).
Requirements
Before loading client load script metadata using metaclient, the associated databases, tables,
views, and other database objects must already loaded into the DIM. Otherwise metaclient
will fail when it attempts to set relationships between objects in the CLM and the associated
DIM objects.
You must have read permission on both the script file and optional output file.
The script file and optional output file must be on the system (Linux or Windows) where the
program is being run.
Since all script files and output files to be loaded must reside on the system where the
metaclient utility is run, transport (move or copy) all external script files and output files from
their original system(s) to the metaclient system prior to executing metaclient.
Restrictions
Client Load scripts can come from z/OS, Linux, or Windows platforms but the metaclient
utility will only run on Linux, and Windows platforms.
Client Load scripts from z/VM platforms are not supported.
Only ASCII formatted files are supported.
The extraction/load of metadata from interactive client load sessions or directly from tape is
not supported.
On Linux, the metaclient utility will only run as a command-line program.
Operating Considerations
Platform Considerations
Client Load scripts can come from z/OS, Linux or Windows platforms but the metaclient
utility will only execute on Linux and Windows platforms.
If a z/OS script/output file is being loaded into the MDS repository, it must be transported
from the z/OS system to a Linux/Windows system and the file format must be converted from
EBCDIC (Extended Binary Coded Decimal Interchange Code) format to ASCII format.
To transport the z/OS script/output file, use the FTP program and specify ASCII mode so that
the script/output file will automatically be converted to ASCII format during the transport.
Run the FTP program from either the z/OS or Linux or Windows system but generally it is
easier to start the FTP program on the z/OS mainframe and then transport the script/output
file to the Linux or Windows system.
145

metaclient
From z/OS platforms, the metaclient utility will only support those z/OS scripts that can be
converted from EBCDIC to ASCII. For instance, support will not be provided for EBCDIC
Katakana or Kanji scripts because conversion to ASCII may not always work.
From the Linux or Windows platforms, the metaclient utility will support all of the languages
and file formats that MDS currently supports.
Script Considerations
For all scripts the metaclient utility assumes that:
A script file contains only one script
An output file contains only the output from one script
The output contained in the output file was generated by the associated script file
If multiple INMOD routines are specified for a single data source, only the last INMOD
routine specified will be stored in the CLM.
Note: The metaclient utility performs minimal syntactic validation of the scripts and output
files because it assumes valid, working scripts whose execution generated the output files.
TPump reports the number of records read for each IMPORT task instead of for an individual
table/view. The metaclient utility extracts this value from the TPump output file and assigns
the same value to the NbrRecordsRead property of all the table(s) and/or view(s) covered by
an IMPORT task and prefixes a MINUS sign.
TPump reports the number of records sent to Teradata and the number of records in the error
table for each IMPORT task instead of for an individual table/view. So, values in the
NbrRecordsSentToTD and NbrErrorsTbl1 properties for each table and/or view covered
by an IMPORT task are assigned in a similar manner.
Table 23: metaclient Script Feature
Script Type
Feature
Level of Support
Fastload
Scripts in multifile job
Treated as single, individual script. Not

combined to create one large script.
Statistics in a multifile job
Generated only for the output file of the final
script.
MultiLoad
Multiple tasks
Not supported
Variable substitution with utility Not supported

variables
DELETE task
Linkage between the script and the DIM table is

supported.
Linkage between source and DIM table or
between SourceFields and DIM columns is not
supported.
TPump
146
Multiple tasks (such as BEGIN

LOAD statements)
Not supported

metaclient
Table 23: metaclient Script Feature (continued)
Script Type
Feature
Level of Support
Variable substitution with utility Not supported

variables
DELETE task
Linkage between the script and the DIM table is

supported.
Linkage between source and DIM table or
between SourceFields and DIM columns is not
supported.
Syntax
metaclient MDSUser MDSPassword scriptname [-q scriptqualifier] [-o
outputfilename][-s targetsystemname]
[-d targetdatabasename][-L Label]
Table 24 shows the metaclient utility input parameters. The Optional/Required column refers
to whether the utility needs the information and not whether the parameter must be provided
by the user. The table provides a detailed explanation of how the utility can obtain the
information for each parameter.
Table 24: metaclient Input Parameters
Parameter
Description
MDSUser
A valid Meta Data Services repository user

name.
Optional/
Required
Required
MDSPassword
The MDS User password.
Required
scriptname
The script name as it exists on the

metaclient system
Required
The full path on the system (where the

script is located) can be included but is
not required.
Explanation
metaclient can obtain the information from
user input through:
The command line parameter,
A parameter file, or
MetaManager or MetaBrowse when the
utility is run through those programs

user input through:
147

metaclient
Table 24: metaclient Input Parameters (continued)
Parameter
Description
[-q] script
qualifier
The scripts unique identification

information on the system of origin.
Optional/
Required
Optional
Explanation
user input through:
If no script qualifier is provided, the scripts
load path (as specified in the scriptname
parameter) becomes the default script
qualifier.
Use when moving the script from the

system of origin to the metaclient system
or when the script name exists on
multiple systems.
Additional text that uniquely identifies
the script can be added and can take any
format. Maintain the same format among
all scripts (such as by platform) so that a
text comparison correctly generates a
success or failure.
The additional text can include:
If the system of origin is on Linux or
Windows, the script name and a fully
qualified path where the script is
located on the system of origin.
If the system of origin is on a z/O
platform, a data set name, a member
name, or both, identifying where the
script is located
Any other information that can be
used to uniquely identify the script.
[-o] output
filename
The name of the scripts output file.

A parameter used to allow the metaclient
utility to extract certain status
information from the script's output file.
Format: [metaclientsystemname:] [path]
outputfilename
The script's output filename consists of:
[Optional] The metaclient system
name where the output file is loaded.
[Optional] The full path on the
metaclient system where the output
file is located.
[Required] The output filename on the
metaclient system.
148
Required

user input through:
If the output file is available, status
information is loaded into the CLM.
If the output file is not available or not
provided through any of these means no
status information is loaded into the CLM
and the metadata load fails.

metaclient
Table 24: metaclient Input Parameters (continued)
Parameter
Description
Optional/
Required
[-s] target
systemname
The name of the target system.
Required
If you specify the target systemname

parameter, metaclient will use the value
specified instead of information provided
in a script.
Explanation
user input through:
metaclient can also obtain the information
from the tpid specified in the LOGON
statement in a script.
If the target system name is not provided
through any of these means, then the target
database name is unknown and the
metadata load fails.
[-d] target
databasename
The name of the target database.
Required
An optional parameter the metaclient

utility can use to obtain the target
database name.

metaclient can also obtain the information
from:
If you specify the target databasename

parameter, metaclient will use the value
specified instead of information provided
in a script.
The order of precedence is:
The DATABASE statement of a scripta
1 Input parameter
The BEGIN statement of a scriptb
2 DATABASE statement
The LOGON statement of a scriptc

If the target database name is not provided
through any of these means, then the target
database name is unknown and the
metadata load fails.
3 BEGIN statement
4 User name
[-L] Label
The name of the Label to be associated

with the script Use this parameter used to
allow Metaclient to specify labelname for
a load script.

user input through:
Optional

user input through:
a. When the DATABASE statement in the script explicitly sets a default database.
b. When the BEGIN statement explicitly qualifies the table name with the database name
c. The utility assumes the user name is also the name of the default database and does not interrogate the target system to
find the users default database. If the users default database name is different from the user name, use one of the other
methods to specify the target database. Otherwise, the correct target table is not found and the metadata load fails.
149

metaclient
Running metaclient from MetaBrowse or MetaManager

To run metaclient from MetaBrowse or MetaManager
1
Click Tools>Import>MetaClient from the main window of MetaManager or MetaBrowse to

display the MetaClient dialog box.
Select the command-line parameters that will be passed to the utility and click Load. To
exit this dialog box without running the utility, click Cancel.
The required entries are:
Client Load Script Name where you can either enter (or Browse to) the name of the
script to load the data
Client Load Script Output File - Enter (or Browse to) the output file generated by the
load program. (Optional.)-
Target System - Enter the name of the MDS target system. (Optional.)
Target Database - Enter the name of database of the load program. (Optional.)
The only optional entry is the Client Load Script Qualifier - Use this for the optional script
qualifier string. This string plus the Load Script Name is used to uniquely identify the load
script.
Note: Optional/Required column refers to whether the metaclient utility needs the
information and not whether the parameter must be provided by the user. Table 24 on
page 147 shows the metaclient utility input parameters and provides detailed information on
how the utility can obtain the information for each parameter.
For more information, see the following:
Purpose
Description
Requirements
Restrictions
Operating Considerations
Syntax
Command Line and Parameter File Operation

The input parameters are the same as those shown in Table 24 on page 147. They can be:
Entered on the command line

If the command line option is used, there must be a space separating the optional
parameter ID (-q, -o, -s, -d) and the parameter value when specifying the optional
parameters. If a parameter value contains spaces or special characters, the entire parameter
value must be enclosed in double quotes (). Enclosing the parameter value in single
quotes () or no quotes will cause an error.
Contained in a parameter file

If the parameter file option is used:
150

metacreate
The name of the parameter file will be the only parameter when invoking metaclient as
shown in this example:
metaclient paramfilename
The parameter file can have any valid name and can be fully qualified.
The contents of the parameter file must include the required parameter information
and can include any or none of the optional parameter information.
Within the parameter file the parameter ordering must be maintained.
The parameter file must specify only one parameter value per line and the list of
parameters must be in the following order:
the MDS user name (required)
the MDS password (required)
the Client Load script name (required)
the Client Load script's script qualifier information (optional)
the Client Load script's output file name (required)
the name of the target system (required)
the name of the target database (required)
Note: Optional/Required column refers to whether the metaclient utility needs the
information and not whether the parameter must be provided by the user. Table 24 on
page 147 shows the metaclient utility input parameters and provides detailed
information on how the utility can obtain the information for each parameter.
If a parameter value in the parameter file contains spaces or special characters, the
parameter value does not need to be enclosed in quotes. The entire parameter value can be
enclosed in double quotes () without causing an error. Enclosing the parameter value in
single quotes () will cause an error.
If an optional parameter is not being specified in the parameter file, a blank line must be
inserted to maintain its position in the parameter list if a subsequent optional parameter is
specified. If one or more trailing optional parameters are not being specified, blank lines
are not required since the EOF will terminate the parameter list with the last specified
parameter and any missing optional parameters will not be processed.
An EOF will terminate the parameter list in the parameter file.
Do not include the optional parameter ID (such as the -q for the script qualifier
parameter) as part of the parameter value in the parameter file because the parameters
position in the parameter list will indicate which parameter is being specified.
metacreate
Purpose
The metacreate program creates the initial Teradata MDS repository in an existing Teradata
Database System. It loads the tables with the initial MDS data. It is run once.
151

metaload
Description
Under Linux, the metacreate program provides the only method to create the repository. You
must be logged on as root to run the program.
Under Windows, the initial Teradata MDS repository can be created by following the
procedures in Teradata Tools and Utilities Installation Guide for Microsoft Windows or by
running the metacreate program as a command-line program.
Restrictions
Regardless of the operating system in use, the program is run once.
If an MDS repository was created for a previous version of software, do not invoke the
metacreate program. Migrate the existing repository to work with the current software version
with metamigrate. Instructions on migrating the repository can be found in the Teradata Tools
and Utilities Installation Guide for the appropriate operating system.
Syntax
metacreate [-v on | -v off] [-bi on | -bi off] [-fb on | -fb off][-m] [h]
Parameter
Description
-v on
The repository is created with data versioning enabled.
-v off
The repository is created with data versioning disabled. This is the

default action.
-bi on
The repository is created with retention of objects with business

definitions enabled.
-bi off
The repository is created with retention of objects with business

definitions disabled. This is the default action.
-fb on
Indicates that all tables in the repository should be created with

FALLBACK
-fb off
Indicates that all tables in the repository should be created with NO

FALLBACK
-m
Prompts for a new metasu password
-h
Displays a message describing the metacreate syntax and then exits.
metaload
Purpose
The MDS metaload program provides a command line alternative to MetaManager when
loading, unloading or resyncing databases. The metaload program loads Teradata metadata
into the MDS repository Database Information Metamodel (DIM).
152

metaload
Note: If the Teradata Database is Kanji enabled, all Kanji character sets that will be used must
be installed.
Syntax
metaload -s systemname [-n dsn] [-l user] [-p password]
{-m metasu's password | -S superuser -P superuser password}
[-d database | -f file | -x file | -r | -u database | -U file]
[-L label] [-t loadtypesname] [-c profile] [-o] [-evalrels] [-h]
Table 25: Metaload Input Parameters
Required/
Optional
Parameter
Description
-s systemname
User-defined system name for this

Teradata Database System. Multiple
Teradata Databases can be loaded into
the MDS repository, each
distinguished by its system name.
Required
-n dsn
The ODBC System Data Source Name

(DSN) for MDS to use to connect to
the Teradata Database System to be
loaded.
Required
If the system object is not defined.
Optional
If the system object is already defined.
The Teradata user name for MDS to

use to connect to the Teradata
Database System to be loaded.
Required
If the system object is not already defined

Single Sign On (SSO) is not supported by the
ODBC driver and the Teradata Database
System
The MDSMETALOADUSER environment
variable is not set
Optional
If the system object is already defined

Single Sign On (SSO) is supported by the
System
The MDSMETALOADUSER environment
variable is set
N/A
Not needed for an unload.
-l user
If you specify the -l parameter,

metaload will use the value specified
in the command line parameter
instead of the environment variable
and system object settings.
Circumstances
153

metaload
Table 25: Metaload Input Parameters (continued)
Parameter
Description
-p password
The Teradata password for MDS to use

to connect to the Teradata Database to
be loaded.
If you specify the -p parameter,
metaload will use the value specified
in the command line parameter
instead of the environment variable
and system object settings.
-m metasus
password
Password of the MDS Administrator.
Required/
Optional
Circumstances
Required
If the system object is not already defined

Single Sign On (SSO) is not supported by the
System
The MDSMETALOADPWD environment
variable is not set
Optional
If the system object is already defined

Single Sign On (SSO) is supported by the
System.
The MDSMETALOADPWD environment
variable is set.
Note: Using the environment variable prevents
the password from being exposed to users
running the ps command on Linux while
metaload is running.
N/A
Not needed for an unload.
Required
If the -S and -P parameters are not provided

or
If the -S, -P, and -m parameters are all

provided the -m parameter is ignored.
If the password is not set in the environmental

variable MDSMETASUPWD
If you specify the -m parameter, and

the -S and -P parameters are not
provided metaload will use the value
specified in the command line and
ignore the environment variable.
Note: Using the environment variable prevents

the password from being exposed to users
running the ps command on Linux while
metaload is running.
Optional
If the -S and -P parameters are provided

or
If the password is set in the environmental
variable MDSMETASUPWD
-S superuser
-P superuser
password
154
Specifies the name of an MDS

Administrator. The -S parameter can
specify metasu.
Required
Specifies the password of the MDS

Administrator given by the -S
parameter.
Required
If the -m parameter information is not provided
Optional
If the -S parameter is provided.

metaload
Parameter
Description
-d database
Limits the load (or resync) to the

specified database.
Required/
Optional
Optional
If the database name contains special

characters, the database name must be
enclosed in double quotes.
-f file
Limits the load (or resync) to the

databases listed in the specified file.
The names of the databases to be
loaded (or resynchronized) are read
from the file.
Loads all databases except those

databases specified in the file.
If this is the initial load of the system and the -d

or -f options are not specified, all databases will
be loaded.
If this is a resync of the system and the -d or -f
options are not specified, all databases which
have previously been loaded will be synchronized
and all other databases will be loaded.
Optional
If this is the initial load of the system and the d

or f options are both omitted, all databases will
be loaded.
If this is a resync of the system and the d or f
options are omitted, all databases that have
previously been loaded will be synchronized and
all other databases will be loaded.
See File Formats for file format

information.
-x file
Circumstances
Optional
If a database name in the file has

already been loaded, it will be skipped
and a warning message will appear.
To unload a database you must use the
unload option.
information.
-r
Resyncs all databases that have

previously been loaded.
Optional
-u database
Unloads the specified database
Optional
-U file
Unloads the databases listed in the

specified file.
Optional

information.
-c profile
Specifies the security profile to assign

to the DIM objects being loaded.
Optional
-o
Use the override option to run

metaload to complete loading of a
previously aborted system load.
Optional
Metaload sets a loading flag to

prevent multiple metaload processes
from attempting to load the same
system simultaneously. If a running
metaload process is aborted, this flag is
not reset.
155

metaload
Required/
Optional
Parameter
Description
-L label
Specifies a label name to be applied to

the loaded system. The label should
not be currently defined. If the label is
currently defined, metaload verifies
that the label is not currently attached
to entries in the repository.
Optional
-t
loadtypesname
Provides the name of an entry in the

MetaloadLoadTypes class. The entry
defines the data types (tables, views,
macros, etc.) that will be loaded for
the system. If this parameter is used
with an existing system, and resync is
being done, it will replace the
loadtypes entry currently associated
with the system. If this parameter is
not present with a new system, then all
supported types will be loaded. If this
parameter is not present with an
existing system, i.e. a resync is being
done, then the system's currently
associated entry will be used. Note: a
system will always be associated with
an entry in the MetaloadLoadTypes
class
Optional
-evalrels
Specifies that on a resync the

relationships for all objects in the
loaded system should be re-evaluated,
even if the SynchronizationLevel for
the object is already set to 1.
Optional
-h
Displays a message describing the

metaload parameters and then exits.
N/A
Circumstances
File Formats
If the -f file, -x file, or -U file parameters are specified to load, resynchronize, or unload
databases as listed in a file, the required format of this file is:
<DB>
databasename
</DB>
<DB>
databasename
</DB>
The heading tag <DB> and the trailing tag </DB> must each be on a separate line. There is no
limit to the number of database names that can be included in the file. The special format is
used to enable specification of the special characters (such as a newline) that Teradata allows
156

metadelete
to be used in a database name. If the database name contains leading spaces these must be
included. Trailing spaces in the name are optional. Database names are not case sensitive but
special characters must match exactly.
Warning Messages
It is possible for Teradata to contain views that reference columns in tables that no longer
exist. If metaload detects this situation, it will log warnings into the MDS error log indicating
which views reference invalid columns.
It is not a requirement that all databases in a Teradata Database System be loaded into the
MDS repository. Because of this, you can get the following warning messages:
If the owner database of a database being loaded has not been loaded, you will get a
warning message similar to this:
Could not create the DBOwnsDB Collection for DB[metaadm] because the
OwnerDB[dbc] is not loaded in MDS
If a view in the database being loaded references a table located in a database that has not
been loaded, you will get a warning message similar to this:
Could not create the ViewHasTableColumn Collection for View [myview1]
because systemname:dbname.tablename is not loaded in MDS
If you run metaload again to resynchronize the database after the owner database or the
database with the view table columns has been loaded, MDS will set up these relationships.
metadelete
Purpose
The metadelete program drops all MDS repository tables, views and macros; that is, all tables,
views and macros that were created by MDS in the Teradata Database.
Restrictions
Metadelete can only be run as a command line program. Must be logged in as root to run
metadelete on Linux.
Syntax
metadelete superuser password [-F]-h
Table 26: metadelete Input Parameters
Parameter
Description
superuser
The name of an MDS Administrator
password
The password of an MDS Administrator
157

metaviews
Table 26: metadelete Input Parameters (continued)
Parameter
Description
-F
Deletes the repository even if it is not the current release
-h
Displays a message describing the metadelete parameters and then exits.

No changes are made to the repository.
metaviews
Purpose
The metaviews program eliminates the requirement that a Teradata Database user configured
for a system object must have SELECT privileges on the DBC tables by installing a set of MDS
views into the DBC database.
Description
The installed views reference the DBC tables and are used by the metaload program to load
the Teradata Database data dictionary information.
The program executes the SQL in the mdsviews.dat file located in the MDS installation\bin
directory. After the views are created, SELECT privilege is granted to PUBLIC on all of the
MDS views.
Metaviews runs on Windows and Linux.
The metaviews program prompts the MDS administrator for the ODBC Data Source Name,
user name and password to use to connect to Teradata to create the views. The user name
must have permissions to create views in the DBC database.
The metaviews program has no command line parameters.
metaxml
Purpose
The metaxml utility is used to import data from an XML formatted file into the MDS
repository or to export metamodels or meta data objects from the repository to an XML file.
The export of metadata objects is not intended to be used in a bulk operation mode. For a
source object or metamodel object collection with many hundreds (or thousands) of
destination objects, the request can run for a considerable amount of time.
Requirements
Be familiar with the XML specification. Refer to the following web site:
http://www.w3.org/TR/REC-xml
158

metaxml
If the Teradata MDS development kit is installed, there are sample XML files located in a
sample\xml subdirectory below the Teradata MDS Installation directory. For detailed
installation information, see the Teradata Tools and Utilities Installation Guide for the
For complete details on creating MDS XML files, see the Teradata Meta Data Services
Programmer Guide.
The metaxml utility requires the MSXML 4.0 or 6.0 parser. The parser can be downloaded
from the Microsoft web site:
http://www.microsoft.com/downloads/
To export an object collection, a supported version of the Java JRE must be installed, and have
its JVM DLL path added to the user's PATH environment variable through the Control Panel.
Supported JREs are from Sun Microsystems: 1.5.0 update 6 or later and 1.6.0 update 3 or later,
and from IBM (WebSphere/Eclipse): 1.5.0.
The Sun Microsystems JVM DLL is located in JRE_HOME\bin\client and the IBM JVM DLL
is in JRE_HOME\bin\j9vm. Any one of these three JREs can be used but the JVM DLL should
come from the selected JRE_HOME of whichever one is being used.
Running metaxml from MetaBrowse or MetaManager

To run metaxml from MetaBrowse or MetaManager
1
Click Tools> Import>MetaXML from the main window
The Locate the XML file to import dialog box appears. Use this dialog box to locate the file.
Select the file and click Open to import data from the XML file into the MDS repository.
Restrictions
The metaxml utility is available only on Windows and can be run by any MDS user.
When the metaxml utility is started through either MetaManager or MetaBrowse, only the
import function is available.
Examples
The following command line example shows the metaxml import usage.
metaxml import mds_user mds_password xml_file
Table 27: metaxml Import Input Parameters
Parameter
Description
import
The import command indicates that metaxml is to be used to import

(i.e., load) data into the repository from an XML file.
159

metaxml
Table 27: metaxml Import Input Parameters (continued)
Parameter
Description
mds_password
The password of the MDS user
mds_user
The name of a valid Meta Data Services repository user.
xml_file
The name of the XML file to be imported.
The following command line example shows the metaxml export usage to export metamodels
or meta data objects out of the repository.
metaxml export mdsUser mdsPassword {-ocoll <objectID> | -mcoll <AIM_name> -model <name>}ofile <XML output file> [-v] [-l <label>]
Table 28: metaxml Export Input Parameters
Parameter
Description
export
The export command indicates that metaxml is to be used to export a

metamodel definition (not metadata) from the repository into an
XML file.
mds_password
Password of the MDS user
mds_user
Name of a valid Meta Data Services repository user.
-ocoll objectID
Identifies the Object ID of the repository object from which to start

the export. This object, and all its destination collection objects, will
be included in the resulting XML file.
AIM_Name
Identifies the name of the AIM (metamodel) whose objects will

be exported. Every object from each class in the AIM will be
exported into the resulting XML file, and all object associations
will be identified.
Note: Object associations to/from classes within other
metamodels will be ignored with a warning displayed to that
effect.
-model name
Identifies the name of the meta model to export. All classes, class
properties and relationships of the named meta model will be
included in the resulting XML file
-ofile XML output

file
Identifies the XML file name into which the objects will be exported.
If the filename is not fully qualified, the file will be created in the
current directory.
If the file exists, it will be over-written without warning
-v
(Optional) Requests that the utility output more verbose information

to the console. The utility shows only a minimal amount of progress
information if not used.
Note: Parameter is ignored when exporting metamodels with the model parameter.
160

Table 28: metaxml Export Input Parameters (continued)
Parameter
Description
-l label
(Optional) Specifies the name of the label to use in finding the object
versions to export. When used, only the particular version of each
object in the destination collection which has the label applied, if any,
will be exported to the output file.
In a versioned repository, if the source object itself does not have the
label applied to any of its versions, no objects will be exported, and a
warning message will indicate this. When no label is specified, the
latest (or published) version of each object is exported.
Note: Parameter is ignored when exporting metamodels with the model parameter.

Purpose
The prtconfig command line program is used to display the current local MDS configuration
parameters on a Linux workstation There are no parameters for prtconfig.
metamigrate
Purpose
The metamigrate program migrates a previous version of the repository to the current MDS
repository format. It can also be used to change the versioning state of an existing MDS 14.0
repository. In addition, it can be used to enable or disable the retention of business
information, and turn on or off the table creation fallback option.
Description
The metamigrate program will add any new repository tables and will add the new
components of the Database Information Metamodel (DIM) and the Client Load Metamodel
(CLM).
Metamigrate can be run anytime after the repository has been created/migrated to change the
state of versioning in the repository.
If the repository is initially set up to not support versioning, run metamigrate with '-v on' to
turn on versioning for all models and classes in the repository.
If the repository is initially set up to support versioning, run metamigrate with '-v off ' to turn
off versioning for all models and classes in the repository; any objects in the repository with
multiple versions will be reduced to only the latest version and the object's version will be set
to one.
161

metamigrate
Customer defined extensions to the DIM will be preserved after a repository is migrated.
Syntax
metamigrate superuser password [-v on | -v off] [-bi on | -bi off] [-fb
on | -fb off] [-h]
Table 29: metamigrate Input Parameters
162
Parameter
Description
superuser
The name of an MDS Administrator.
Password
The password of an MDS Administrator.
-v on
The repository is to be migrated with data versioning enabled.
-v off
The repository is to be migrated with data versioning disabled. This is

the default action.
-bi on
The repository is migrated with retention of objects with business

definitions enabled.
-bi off
The repository is migrated with retention of objects with business

definitions disabled.
-fb on
Indicates that all existing tables in the repository should be modified to

specify FALLBACK and that all new tables will be created with
FALLBACK.
-fb off
Indicates that all existing tables in the repository should be modified to

specify NO FALLBACK and that all new tables will be created with NO
FALLBACK.
-h
Displays a message describing the metamigrate parameters and then

exits. No changes are made to the repository.
CHAPTER 7
Automatic DIM Updates
Because Teradata Database metadata is a central part of the Teradata MDS repository, it is vital
that the information be kept up to date and dynamically reflect any changes in the Teradata
archive data warehouse. Automatic DIM updates will dynamically keep the MDS repository
synchronized with the Teradata Database Systems it describes.
This chapter contains general information on the Automatic DIM update feature, and
information on configuration tasks required to implement and administer the feature.
Automatic DIM Update Process

The following illustration shows the processes supporting Automatic DIM updates.
Figure 4: Processes Supporting Automatic DIM Updates
/LQX[:LQGRZV
0'6 ''/ *DWHZD\

6HUYHU
&RPPXQLFDWLRQ
6\VWHP
7HUDGDWD
56* 9352&
&OLHQW
0'6 ,QWHJULW\
6HUYHUV
7HUDGDWD 5'%06
0'6 5HSRVLWRU\
'DWDEDVH
$
163
Chapter 7: Automatic DIM Updates

Automatic DIM Update Process
Relay Services Gateway (RSG)

The RSG is a Teradata VPROC that relays messages between Teradata and the MDS DDL
Gateway.
Whenever a Teradata Database System processes a Data Definition Language (DDL)
statement, it sends the DDL to the RSG, which sends it on to the MDS DDL Gateway. The
DDL Gateway then updates the metadata in the MDS repository. An example of a DDL is:
create table mytable (c1 int);
Every Teradata node of the Teradata Database System must have an RSG VPROC running.
The RSG communicates via TCP/IP with the MDS DDL Gateway.
DDL Gateway
The DDL Gateway consists of one client, one server, and one or more integrity server
processes that keep the metadata in the MDS repository synchronized with Teradata. MDS can
track changes to multiple Teradata systems. The DDL Gateway is also responsible for
maintaining the audit trail of the DIM changes for each processed DDL statement. If the Audit
Log Flag is set to On, an entry is inserted into the audit trail for each update to the DIM.
The DDL Gateway can be installed on an application node of the Teradata system or on a
separate Windows or Linux box. Only one instance of the DDL Gateway is allowed.
MDS Action Processor

The MDS Action Processor is responsible for polling the Audit Log for expired entries and
purging the expired entries. The MDS Action Processor is also responsible for sending
messages to the MDS DDL Gateway to initiate scheduled recovery.
The MDS Action Processor runs on Windows or Linux and only one MDS Action Processor
can be run.
The Action Poll Rate defined in the MetaManager System-Wide Parameters defines the
frequency that the MDS Action Processor will reread the MDS system settings to pick up
changes to the Audit Flag, Audit Trail Expiration Days, and DIM Update Recovery Schedule
for each Teradata System object. The default setting for the Action Poll Rate is 5 minutes. The
Action Poll Rate can be increased to a maximum of 1440 minutes (24 hours).
The MDS Action Processor will poll the MDS Audit Trail every 24 hours at 1:30 a.m. local
time to remove expired entries in the Audit Trail.
A Recovery Schedule is configured in MDS for each Teradata Database System. The MDS
Action Processor will monitor the schedule times for each Teradata system and send a message
to the MDS DDL Gateway server when scheduled recovery is to be performed on each system.
MDS Recovery Tables

For the Automatic DIM update feature to be enabled on each Teradata Database System
loaded into the MDS repository, an MDS Recovery Table must exist on each of the Teradata
Database Systems.
164

Out of Sync Recovery
Teradata Database Systems automatically contain an MDS Gateway MDS Recovery Table. The
table has a fixed name (mdsrecoverytbl) and location (DBC).
Database Connection Information

When creating a System with Automatic DIM Updates enabled, a DSN, user name and
password for the DDL Gateway to use to connect to the system are specified in MetaManager.
The Gateway Server process uses these settings to resync a database during recovery and to
access the MDS Recovery Table. The Gateway Integrity Servers use these settings to connect to
the system to get information from the DBC tables.
If the DDL Gateway is running on Linux, the Gateway uses the Teradata user name specified
in mdsconfig to connect to the MDS repository. The Gateway uses the Teradata user name
specified in MetaManagers system configuration to connect to other Teradata systems.
The DDL Gateway on Windows systems runs as a service. A service can run as the
LocalSystem Account or as a specified account name and password. If the MDS repository
Database Configuration is configured for Teradata Single Sign On (SSO) where no username
and password is specified, then the DDL Gateway Service MUST NOT be configured to run
with the LocalSystem Account. If the MDS repository Database configuration is configured
for SSO where no username and password is specified, there must be a Teradata user account
with the same name as the user account in which the Gateway is run.
Out of Sync Recovery

The MDS repository can be out of sync with a Teradata Database System for a number of
reasons:
A Teradata Database System, RSG and/or MDS DDL Gateway reset occurs.
An error occurs and an Integrity Server cannot commit a transaction to the repository.
The MDS DDL Gateway goes down and does not come back up right away. In this case
Teradata is processing DDLs and not forwarding them on to MDS but is writing the
database names to the MDS Recovery Table.
The Integrity Servers have a backlog of transactions that have not yet been processed.
When the Automatic DIM Update feature is enabled, the task of keeping track of the DDL
Transactions is divided among the three components: Teradata Database System, RSG, and
DDL Gateway Server.
Teradata Database System

When the MDS DDL Gateway is down, the Teradata Database System will process DDL
statements but will write the names of all Affected databases to the MDS Recovery Table.
There is one MDS Recovery Table per Teradata Database System. When the MDS DDL
Gateway Server comes up, if the Recovery on Startup flag is checked, it will read the MDS
Recovery Table and resynchronize the repository for each database name listed in the table.
165

Configuring Automatic DIM Update in MetaManager
RSG
The RSG keeps track of the in-progress Teradata DDL transactions. These are DDLs that the
Gateway Server has not yet captured in its log and has not responded to Teradata to complete
the transaction. When the RSG detects that the MDS DDL Gateway has gone down or receives
a reset message from the MDS DDL Gateway Server, the RSG will abort the in-progress
transactions with the Teradata Database System.
DDL Gateway Server

The MDS DDL Gateway Server will keep track of the database names of all DDL transactions
that it has received messages for. It will track the transaction in a backlog list and in a log file.
The log will be combined with the MDS Recovery Table to resync the repository. Only
databases that are out-of-sync will be resynced during recovery.
The DDL Gateway Server performs recovery:
On startup of the DDL Gateway. On startup, the Gateway Server looks in the MDS
Recovery Table and in its own log to determine which databases need recovery. If the
Teradata Database System is configured in MDS to have the Recovery On Startup flag
enabled, the Gateway will begin recovery for that system. If the flag is not set, recovery will
be deferred until the scheduled time.
When the DDL Gateway receives a Recover now message from the MDS Action
Processor. Scheduled recovery will only occur once per day for each Teradata Database
System based on the schedule configured for that system in MDS. The schedule
configuration also specifies the days of the week to perform scheduled recovery.
The Gateway Server performs the following steps when performing recovery:
1
The Gateway Server sends a message to the Teradata Database to stop sending DDLs to
RSG and to log Affected databases in the MDS Recovery Table.
The Gateway Server reads and deletes MDS Recovery Table entries, reads the backlog list
and compiles a list of database names to resync.
Calls the metaload utility to resync each database name.
Reads and deletes the MDS Recovery Table again to resync databases that may have been
affected by DDLs during the resync process.
Sends a message to the Teradata Database to start sending DDLs to RSG.
Configuring Automatic DIM Update in

MetaManager
Use MetaManager to enable Automatic DIM Update. The steps to be performed are:
166
Add a Teradata Database System.
Add all Teradata nodes to the Teradata Database System.
Load databases.

4
Enable DIM Update and optionally setting the Recovery on Startup flag and recovery
schedule.
Adding a Teradata Database System

For details on this, see Chapter 3: Administer MDS with MetaManager.
Adding Teradata Nodes to a Teradata Database System

Configuring Nodes
The Automatic DIM Update feature requires that Teradata nodes on the Teradata Database
System be configured.
Adding a Node
Nodes may be added to a system, edited or deleted. A node definition consists of a name and
the node status (Up or Down).
To add a node:
1
In MetaManager, select a system. In the example shown, the systems name is simca.
Click System>Add Node. The Add Node dialog box appears.
Type in the node name, choose the node status, and click OK.
The node names are not arbitrary. Each name must be the primary name (first name after
the IP address in an /etc/hosts file) for its IP address and not an alias. The node names must
be unique within the enterprise, not just within the Teradata Database System.
You will be asked if you would like to add another node. When you are finished adding
nodes, they will appear in MetaManager.
167

Editing a Node
1
In MetaManager, choose the node to edit, then right-click on it to display the shortcut
menu.
Click Edit, and an Edit node dialog box will appear.
You can change the node status to Up or Down.
The status of the node should be set Down if the node on the Teradata Database System is to
be removed for an extended period. This will prevent the MDS DDL Gateway from sending
messages to the RSG on the node when it is unavailable.
Loading Databases
MDS loads data dictionary information for each of the selected databases into the MDS
repository. The actual data in the databases tables is not loaded.
The option you use to load databases into the MDS repository determines what databases the
DDL Gateway keeps in sync. The difference is in how the DDL Gateway handles newly created
users and databases in the Teradata Database System.
168
If you load All databases, the DDL Gateway will automatically add new databases and
users that are created in the Teradata Database System to the MDS repository. In other

words, All indicates that you want the MDS repository to contain all databases in the
Teradata Database System.
If you load Selected databases, the DDL Gateway will NOT add new databases and users
that are created in the Teradata Database System to the MDS repository. The DDL Gateway
will maintain only those databases selectively loaded into the MDS repository.
If you load All but Selected databases the DDL Gateway will automatically add new
databases and users that are created in the Teradata Database System to the MDS
repository. It, however, maintains the list of those databases that were excluded on the
initial load and ignores all DDLs for those databases. Databases that were originally loaded
but are later unloaded are considered to be databases that are excluded.
For all other DDLs, the DDL Gateway will update the repository for loaded databases and will
ignore DDL for databases that are not loaded into the repository.
If you do not load any databases for a Teradata Database System, the MDS DDL Gateway will
not track that system even if Automatic DIM Update is enabled for the system.
Before enabling DIM Update, load all databases to be maintained. If there is a lengthy time
between the initial load of the databases and when DIM Update is enabled, resync all
databases before enabling DIM Update.
For details on this, see Resynchronize Databases in Chapter 3: Administer MDS with
MetaManager.Resynchronize Databases.
Enabling Automatic DIM Update

1
In MetaManager, choose the system for which to have Automatic DIM Update enabled,
then right-click it.
Click DIM Update, and the DIM Update dialog box appears.
Select the Enable DIM Update check box.
Click OK to exit the dialog box. From this dialog box you can also select the Recovery on
Startup check box or define the recovery schedule by clicking Schedule (both are optional).
The MDS Recovery Table keeps track of the database name for each DDL that occurs while the
DDL Gateway is down. If RSG detects that the Gateway is down, RSG notifies Teradata to
begin writing to the MDS Recovery Table. When the Gateway comes back up, it reads the
MDS Recovery Table and marks each of the databases in the MDS Recovery Table as out of
sync. The Gateway will resync each database if Recovery on Startup is selected or at a
scheduled recovery time.
The recovery database is always DBC and the MDS Recovery Table is mdsrecoverytbl.
The Teradata user specified in the System Object must have SELECT and DELETE privileges
to the MDS Recovery Table.
169

Checking DIM Update Status with MetaManager
Checking DIM Update Status with MetaManager

1
From MetaManager, click System>Database Systems.
In the Meta Data Services Administration window, highlight a system name, click Database
Administration. The Teradata Meta Data Services Administration dialog box appears.
To go directly to the Teradata Meta Data Services Administration dialog box, from the
MetaManager main window, right click on the system with database(s) that you want to
administer, and click Database Administration.
Click the Dim Update Status tab to determine if any databases are marked out of sync by
the DDL Gateway.
The DIM Update Status tab is disabled if Automatic DIM Update has not been enabled for
your system. Refer to Enabling Automatic DIM Update on page 169 for additional
information.
The DIM Update Status window shows:
System Name - Displays the system chosen
DIM Update Status - Displays the DIM Update status of the system. The status codes are:
UP - DIM Update is up and tracking changes to the system
DOWN - the DDL Gateway has not yet notified the Teradata Database System to begin
sending DDLs
STOPPED - DIM Update is disabled and not tracking changes to the system
RESYNC - The Gateway is currently running recovery (scheduled or on startup)
UNKNOWN - MetaManager could not contact the DDL Gateway to get the status or the
DDL Gateway does not know about the system
Database out of sync - the box displays the list of database names that the DDL Gateway
has marked out of sync including those that were in the MDS Recovery Table.
Refresh List - updates the display
Sync Now - sends a message to the DDL Gateway to immediately begin recovery to
synchronize the Out of Sync databases.
Starting/Stopping the DDL Gateway

The DDL Gateway is automatically started at system boot and stops at system shutdown. The
DDL Gateway starts as a service on Windows. The names of the DDL Gateway programs are:
Table 30: DDL Gateway Processes
170
Gateway Component
Linux Program Name
Windows Program Name
Gateway Server
gwserver
gwserver.exe
Gateway Client
gwclient
gwclient.exe

Table 30: DDL Gateway Processes (continued)
Gateway Component
Linux Program Name
Windows Program Name
Integrity Servers
iserver
iserver.exe
To manually start the DDL Gateway on Linux, execute:

/etc/init.d/mdsgwy start
To manually stop the DDL Gateway on Linux, execute:

/etc/init.d/mdsgwy stop
To manually start or stop the DDL Gateway on Windows, use the Services Administrative
Tool. The DDL Gateway service is called Meta Data Services DDL Gateway.
Note: The DDL Gateway processes are not started at installation.
Starting/Stopping the MDS Action Processor

The MDS Action Processor is automatically started at system boot and stops at system
shutdown. The MDS Action Processor starts as a service on Windows.
The name of the MDS Action Processor program is metaaction on Linux and metaaction.exe
on Windows.
To manually start the MDS Action Processor on Linux, execute:
/etc/init.d/mdsap start
To manually stop the MDS Action Processor on Linux, execute:

/etc/init.d/mdsap stop
To manually start or stop the MDS Action Processor in Windows, use the Services
Administrative Tool. The MDS Action Processor service is called Meta Data Services Action
Processor.
171

172
CHAPTER 8
Troubleshooting
This chapter provides the following topics:
Troubleshooting - Programming
Troubleshooting - Miscellaneous
Troubleshooting - Programming
The following is troubleshooting information regarding programming with the MDS APIs.
Table 31: Troubleshooting - Programming
Problem
Possible Fix
Internationalized functions
When an application needs the internationalized functions

working under _MBCS or _UNICODE settings, the
application developer must set the locale in the application.
You can set the locale dynamically in your application based
on the Windows locale setting as follows:
//*** Get User Locale Info.
lcid = GetUserDefaultLCID(); // get locale ID here
GetLocaleInfo(lcid, LOCALE_SABBREVLANGNAME,
m_lpszLangU, 4);
GetLocaleInfo(lcid, LOCALE_SENGLANGUAGE,
m_lpszLangEng, 20);
// setlocale(LC_ALL, "target_language");
setlocale(LC_ALL, m_lpszLangEng);
Windows program built using the MDS C++ APIs

terminates at the end of the program with an access
violation.
C++ Applications (console applications or DLLs) using the

MDS APIs must set the C/C++ Code Generation Category to
Use run-time library: Multithreaded DLL. If an executable is
built using the Multithreaded library instead of the
Multithreaded DLL library, an access violation will occur
during program termination.
173
Chapter 8: Troubleshooting
The following is troubleshooting information regarding other problems while running MDS.
Table 32: Troubleshooting - Other
Problem
Possible Fix
Multiple entries in the MDS error log appear that say

something like this: Could not match column 'xxxx in
list of column entries.
These entries are warnings and usually not errors. To determine

whether the View/Macro/Stored Procedure is missing
information and an error truly exists:
Cause: MDS tries loading all table meta data first and then
Views to make sure all base table information is already
loaded and available in the repository to meet
dependencies. But this does not guarantee that MDS will
be able to resolve all viewcolumn to column mappings
because a view may in turn reference another view. As a
result MDS makes multiple passes to parse and load view
information. So the first pass may generate the warning
but on a subsequent pass it will find the base table
information and nothing is logged in the error file.
Read the SynchronizationLevel property for the View/Macro/

Stored Procedure. When the SynchronizationLevel property has
a value = 0 then it means that MDS was not able to resolve all of
the references in the item.
The following error message is found in the MDS error log

after running metacreate to create the MDS repository:
Ignore these error messages. MDS logs all SQL statements that
return an error. The metacreate utility performs a SHOW
TABLE metalatesttx; to see if a MDS repository already exists. If
the table does not exist, metacreate proceeds to create the
repository tables.
05/03/00 17:26:52|PID-280|THREAD220|2|CDBAccess::DBODBCError: ODBC error

(connection, statement, return code, native error code)
(14357064, 14358104, -1, -3807) S0002
[Teradata][Teradata Database System] Table/view/trigger
'metalatesttx' does not exist.
05/03/00 17:26:52|PID-280|THREAD220|2|CDBAccess::DBRunSql: ODBC SQLExecDirect
error. Failed SQL=SHOW TABLE metalatesttx;
Non ASCII characters in the Error Log can appear
differently depending on the program you use to view the
log.
For example, the following entry viewed with Notepad on

Windows looks like:
05/11/00 15:23:05|PID-149|5|TXP::dump_new_msg : <||
gwsDDL: Node=BRONCOS1, Sid=[0 8665], Tid=16380 [7
54646], CREATE USER "FshinStr" FROM "DBC" AS
PERMANENT = 3000000 ,SPOOL = 80000000 ,DEFAULT
DATABASE = "FshinStr" ,NO FALLBACK,NO BEFORE
JOURNAL,NO AFTER JOURNAL; [len=160]
The same entry, viewed with VI on Linux looks like:
05/11/00 15:23:05|PID-149|5|TXP::dump_new_msg : <||
gwsDDL: Node=BRONCOS1, Sid=[0 8665], Tid=16380 [7
54646], CREATE USER "F\344shi\366nSt\346r" FROM "DBC"
AS PERMANENT = 3000000 ,SPOOL = 80000000 ,DEFAULT
DATABASE = "F\344shi\366nSt\346r" ,NO FALLBACK,NO
BEFORE JOURNAL,NO AFTER JOURNAL; [len=160]
174
Table 32: Troubleshooting - Other (continued)
Problem
Possible Fix
An AMP containing the MDS repository is down. A

message similar to the following will be found in the MDS
error log:
The MDS repository will be unavailable until the AMP is

restored. To save processing cycles, stop the MDS DDL Gateway
and Action Processor processes until the AMP is restored.
CDBAccess::DBODBCERROR: ODBC error (connection,

statement, return code, native error code) (15078056,
15079088, -1, -2642) S1000 [Teradata] [Teradata Database
System] AMP Down: the request against nonfallback
metarelation_204 cannot be done.
When attempting to load database information through
MetaManager or directly through Metaload, the following
is generated:
6701 An unknown character string translation was
requested.
For Kanji based systems, the necessary translation tables must be

installed. For detailed installation information, see the
Teradata Tools and Utilities Installation Guide for the
175
176
APPENDIX A
Teradata Metadata - Database

Information Metamodel
DIM
The Database Information Metamodel (DIM) represented in Figure 5 and Figure 6 provides
the base model in which to store database metadata in the MDS repository.
Figure 5: Database Information Metamodel (DIM) (Sheet 1 of 2)

'DWDEDVH6\VWHP
6 X E MH FW $
UH D
1RGH

0 H WD

'DWDEDVH

/RDG7
\SH
V( QW
% XV LQ HV
% XV LQ HV

LW\

V5 XO H

7U LJ J
H

9D OLG 9D OX

0DFU
R 3D U D
P H WH

U

% X VL Q H VV
0DFU
$ WW UL EX WH

9 LH Z & RO
XP Q

6 3 3D UD P

7D E OH

& R OX P

9 LH Z

5 H IH U
HQFH

H WH U
&KHF

5 H IH U
HQFH&
R OX P Q

UR
6 WR UH G 3
FH G X UH
-R LQ ,Q G H

,Q G H[

& R Q VW D Q
H[
+ D VK ,Q G

,Q G H[
& R OX P

W
(
177
Appendix A: Teradata Metadata - Database Information Metamodel

DIM
Figure 6: Database Information Metamodel (DIM) (Sheet 2 of 2)
Database
StoredProcedure
68
Macro
76
JoinIndex
75
74
View
84
Function
80
69
78
82
FunctionParameter
65
83
81
67
70
Column
UDT
66
MacroParameter
72
79
UDTAttribute
SPParameter
73
Trigger
77
ViewColumn
71
3047A060
Other warehouse applications can reference the Teradata metadata in the DIM instead of
maintaining the identical metadata in their own metadata. This will reduce metadata
redundancy and the number of places that a change must be made.
You can extend the DIM with new relationships, classes, or properties to meet your metadata
management needs.
A Teradata Database System is initially loaded into the MDS repository using the metaload
utility or MetaManager. Metadata elements loaded into the DIM are referred to as DIM
objects. DIM objects are readable by any MDS User that has the appropriate read permission.
Table 33 on page 179 and Table 65 on page 199 contain descriptions of the DIM classes and
relationships respectively.
178

DIM Class Descriptions
DIM Class Descriptions

The Table 33 describes the DIM classes.
Table 33: DIM Class Descriptions
Class Name
Description
BusinessAttribute
A Business Attribute is a characteristic of a Business Entity. This

commonly represents a logical column.
BusinessEntity
A Business Entity represents a set of objects that have common

characteristics. This commonly represents a logical table.
BusinessRule
A Business Rule defines any restrictions on what values can be

stored in a column.
Check
A check constraint on a Teradata table
Column
A column of a Teradata table
Constant
A constant value
Database
A Teradata Database
DatabaseSystem
Identifies a Teradata Database System
FKReference
A derived class to track foreign key reference information
Function
A Teradata built-in function or a user-defined function.
FunctionParameter
A parameter of a user-defined function
HashIndex
A Teradata hash index
Index
An index of a Teradata table
IndexColumn
A column of an index
JoinIndex
A Teradata join index
Macro
A Teradata macro
MacroParameter
A parameter of a Teradata macro
MetaLoadType
Defines the types of data (tables, views, etc.) that are loaded in
the repository for a system
Node
A node of a Teradata system
Reference
A reference constraint on a Teradata table
ReferenceColumn
A column of a reference constraint
SPParameter
The parameter of a Teradata stored procedure
StoredProcedure
A Teradata stored procedure
SubjectArea
A subject area is a set of data organized to reflect a specific area of

business.
179

DIM Class Property Descriptions
Table 33: DIM Class Descriptions (continued)
Class Name
Description
Table
A Teradata table
Trigger
A Teradata trigger
UDT
A user-defined type
UDTAttribute
An attribute of a UDT
ValidValue
The Valid Value defines the possible values associated with a

Business Rule.
View
A Teradata view
ViewColumn
A column of a Teradata view

Database System Class Property Descriptions
Table 34: Database System Class Property Descriptions
180
Property Name
Description
MetaloadDate
Date the last time metaload was run This field is set by the
metaload utility (command line or as called by the
MetaManager) each time the utility is run.

Table 34: Database System Class Property Descriptions (continued)
Property Name
Description
LoadFlag
Flag that indicates if none, all, or selected databases have been

loaded
0 = Not loaded
1 = All DB Loaded
2 = Selected DB Loaded
3 = All but excluded DB Loaded
The field is set by the metaload utility (command line or as
called by the MetaManager).
If no databases are specified on initial load or during a resync,
the flag is set to 1 (All). This flag tells the MDS DDL Gateway to
maintain updates on all databases in the system.
If selected databases are specified on the initial system load, the
flag is set to 2 (selected DB). This flag tells the MDS DDL
Gateway to maintain updates on only the selected DBs that
have been loaded into the MDS repository.
If load all but the excluded databases is specified on the initial
system load, the flag is set to 3 (Excluded DB). This flag tells the
MDS DDL Gateway to maintain updates on all the DBs except
those that have been excluded.
If the flag is set to 1 (All) and metaload is run to resync a
specific database or databases, the flag is not changed.
If the flag is set to 2 (Specific DB) or 3 (Excluded DB) and
metaload is run to load or resync all databases, the flag is
changed to 1 (All).
MetaLoadUserLogin
Teradata user name for the metaload utility to use to logon to

this Teradata system to resynchronize metadata from this
MetaloadUserPwd
Password for the Metaload User Login
MetaloadSystemDSN
ODBC DSN for the metaload utility to use to connect to the

Teradata Database System to resynchronize
RecoveryDatabase
Name of the database containing the MDS Recovery Table for

Automatic DIM updates
RecoveryTableName
Name of the MDS Recovery Table If the MDS DDL Gateway is

down, Teradata will write the names of databases in which DDL
occur to this table. When the Gateway restarts, it will
resynchronize all the database names in this table.
DIMUpdateEnabled
Indicates if the Automatic MDS DDL Gateway should

automatically keep the MDS repository in sync with this
Teradata system
Y = yes
N = no
RecoveryDays
Indicates the days of the week for the MDS DDL Gateway to
perform recovery
181

Table 34: Database System Class Property Descriptions (continued)
Property Name
Description
RecoveryTime
Indicates the time for the MDS DDL Gateway to perform

recovery
RecoverOnStartup
Indicates to the MDS DDL Gateway to perform recovery when

the Gateway is started
RDBMSType
Text containing the RDBMS type such as Teradata
SecurityPropagationType
Indicates the default security profile to assign to new objects

that are loaded If set to 0, the security profile assigned to the
database object will be used. If set to 1, the security profile
assigned to the class will be used.
Database Class Property Descriptions

Table 35: Database Class Property Descriptions
Property Name
Description
CommentString
The comment stored in Teradata for this database
CreatorName
The Teradata user that created the database
DatabaseID
Teradata assigned identifier for this database
DatabaseType
Teradata Database types:

U = the object is a Teradata User
D = the object is a Teradata Database
When data is loaded using the Meta Integration Model Bridges
(MIMB), you may see the following values:
A = the object is an MS Access database
B = the object is a DB2 database
I = the object is an Informix database
M = the object is an SQLServer database
O = the object is an Oracle database
R = the object is a Redbrick database
S = the object is a Sybase database
T = the object is a Teradata Database
SynchronizationLevel
Internal flag
1 = All relationships have been set up
-1 = Invalid references detected in the database
0 = Owning database is not loaded Teradata Database
182

Table Class Property Descriptions

Table 36: Table Class Property Descriptions
Property Name
Description
CommentString
The comment stored in Teradata for this table
CreatorName
The Teradata user that created the table
DatabaseID
Teradata assigned identifier for the database where this table

resides
IsErrorTable
Indicates if the table is the error table for another table.

Possible values are Y=Yes, N=No.
IsGlobalTemporary
Indicates if the table is a global temporary table rather than a

permanent table.
LastAlterTimeStamp
Time that Teradata last updated the object
PrimaryIndexDefined
Indicates if the table has a primary index.

Internal flag
TableID
Teradata assigned identifier for this table
Version
Indicates the version of this table in Teradata

Teradata increments the version each time the table is altered.
Column Class Property Descriptions

Table 37: Column Class Property Descriptions
Property Name
Description
CharType
Specifies the character set type of character fields.

Values can be:
1 Latin
2 Unicode
3 KanjiSJIS
4 Graphic
5 Kanji1
ColumnFormat
Display format for the column
ColumnID
Teradata assigned identifier for this column
ColumnLength
Maximum size of the column
ColumnTitle
Heading for displayed or printed results that is different from the

column name, which is used by default
183

Table 37: Column Class Property Descriptions (continued)
Property Name
Description
ColumnType
Data type of this column. Values can be:
184
A1 1-dimensional Array
AN n-dimensional Array
AT Time
BF Byte
BO BLOB
BV VarByte
CF Character
CO CLOB
CV VarCharacter
D Decimal
DA Date
DH Day To Hour
DM Day To Minute
DS Day To Second
DY Day
F Float
HM Hour To Minute
HR Hour
HS Hour To Second
I Integer
I1 ByteInt
I2 SmallInt
I8 BigInt
MI Minute
MO Month
MS Minute To Second
N Number
PD Period Date
PM Period Timestamp with Time Zone
PS Period Timestamp
PT Period Time
PZ Period Time with Time Zone
SC Second
SZ Timestamp with Time Zone
TS Timestamp
TZ ANSI Time with Time Zone
UT User-defined Type
YM Year To Month
YR Year

Table 37: Column Class Property Descriptions (continued)
Property Name
Description
CommentString
The comment stored in Teradata for this column
Compressible
Indicates if the column is to be compressed

If yes, column will be compressed to zero space if the data value
of the column is equal to the CompressValue.
C = compress
N = do not compress
CompressValue
If NULL is specified, NULLs are compressed. If one or more

constants are specified, NULLS and the values are compressed.
DatabaseID
Teradata assigned identifier for the database where this column

resides
DecimalFractDigits
Number of digits in the decimal portion of data types of

DECIMAL and NUMERIC
DecimalTotalDigits
Total number of digits for data types of DECIMAL and

NUMERIC
DefaultValue
Default value specified for this column
IDColType
If this is an identity column, this field contains the parameters

defined for the identity column.
Nullable
Indicates if NULL is an accepted value for this column. Y/N

Y = acceptable value
N = not acceptable value
TableID
Teradata assigned identifier for the table where this column

resides
UppercaseFlag
If a column is declared UPPERCASE, then the small-case letters

are converted and stored in their capital-case equivalents.
Y = small-case converted
N = small-case not converted
View Class Property Descriptions

Table 38: View Class Property Descriptions
Property Name
Description
CommentString
The comment stored in Teradata for this view
CreatorName
The Teradata user that created the view
DatabaseID
Teradata assigned identifier for the database where this view

resides
185

Table 38: View Class Property Descriptions (continued)
Property Name
Description
IsRecursive
Indicates if the view is a recursive view, i.e SELECTs from itself.

Values are Y=Yes, N=No.
This property is set by metaload and DIM Update when they
process a view. When an existing database in the DIM is being
processed by metaload, it automatically reevaluates any view that
has a NULL value for the property.
LastAlterTimeStamp
ReqText
The SQL string used to create the view
Internal flag
0 = Invalid references detected
ViewID
Teradata assigned identifier for this view
View Column Class Property Descriptions

Table 39: View Column Class Property Descriptions
186
Property Name
Description
CharType
Specifies the character set type of character fields
ColumnID
Teradata assigned identifier for this view column
ColumnLength
Length of the view column
ColumnTitle

column name, which is used by default
ColumnType
Data type of this view column
CommentString
The comment stored in Teradata for this view column
DatabaseID
Teradata assigned identifier for the database where this view

column resides
DecimalFractDigits
For data types of DECIMAL and NUMERIC this is the number

of digits in the decimal portion of the number.
DecimalTotalDigits
For data types of DECIMAL and NUMERIC this is the total

digits in the view column.
Nullable
Identifies whether the view column is nullable
ViewID
Teradata assigned identifier for the view where this view column
resides

Index Class Property Descriptions

Table 40: Index Class Property Descriptions
Property Name
Description
DatabaseID
Teradata assigned identifier for the database where this index

resides
IndexNumber
Teradata assigned identifier for this index.
IndexType
The IndexType field identifies the index type as:
P (Primary)
Q (Partitioned Primary Index)
S (Secondary)
M (Multi-Column Statistics)
D (Derived column partition statistics)
N (hash index)
K (primary key)
U (unique constraint)
V (value ordered secondary)
H (hash ordered ALL covering secondary)
O (valued ordered ALL covering secondary)
I (ordering column of a composite secondary index)
1 (field1 column of a join or hash index)
2 (field2 column of a join or hash index)
TableID
Teradata assigned identifier for the table where this index is built
UniqueFlag
The UniqueFlag field indicates if the index is unique:

Y = yes, meaning unique
N = no, meaning non-unique
Index Column Class Property Descriptions

Table 41: Index Column Class Property Descriptions
Property Name
Description
ColumnPosition
Identifies the position of the column within an index
DatabaseID
Teradata assigned identifier for the database where this index

resides
IndexNumber
Teradata assigned identifier for this index
TableID
Teradata assigned identifier for the table where this index is built
187

Check Class Property Descriptions

Table 42: Check Class Property Descriptions
Property Name
Description
CheckBool
The check <boolean> string for this check constraint
ConstraintType
C = Table level check constraint

Q = Partitioned primary index constraint
DatabaseID
Teradata assigned identifier for the database where this check

constraint resides
TableID
Teradata assigned identifier for the table where this check

constraint resides
Reference Class Property Descriptions

Table 43: Reference Class Property Descriptions
Property Name
Description
DatabaseID
Teradata assigned identifier for the database where this

constraint resides
RefDatabase
Database of reference table
ReferenceID
Teradata assigned identifier for this Reference constraint
RefTable
Table that constraint refers to
TableID
Teradata assigned identifier for the table the constraint is built

on
Reference Column Class Property Descriptions

Table 44: Reference Column Class Property Descriptions
188
Property Name
Description
DatabaseID
Teradata assigned identifier for the database where this

constraint resides
ForeignKeyColName
Name of foreign key column
ReferenceColName
Name of reference column
ReferenceID
Teradata assigned identifier for this Reference constraint
TableID
Teradata assigned identifier for the table the constraint is built

on

Node Class Property Descriptions

Table 45: Node Class Property Descriptions
Property Name
Description
NodeStatus
Status of the node

U = node is up
D = node is unavailable
Stored Procedures Parameter Class Property Descriptions

Table 46: Stored Procedures Parameters Class Property Descriptions
Property Name
Description
CharType
Specifies the character set type of character fields
CommentString
The comment stored in Teradata for this parameter
DatabaseID
Teradata assigned identifier for the database where this stored

procedure resides
ParameterID
Teradata assigned identifier for this stored procedure parameter
ParamLength
Contains the maximum length in bytes for the value of this

parameter
ParamType
Contains the data type of this parameter
ProcedureID
Teradata assigned identifier for this stored Procedure
RowTypeDatabaseName
The name of the database containing the table referenced by a

%ROWTYPE attribute
RowTypeTableName
The name of the table referenced by a %ROWTYPE attribute
SPParamType
Contains information on this parameters type

I = IN
O = OUT
B = IN/OUT
Stored Procedures Class Property Descriptions

Table 47: Stored Procedures Class Property Descriptions
Property Name
Description
CommentString
The comment stored in Teradata for this Stored Procedure
CreatorName
The Teradata user that created the stored procedure
DatabaseID
Teradata assigned identifier for the database where this stored

procedure resides
189

Table 47: Stored Procedures Class Property Descriptions (continued)
Property Name
Description
LastAlterTimeStamp
ProcedureID
Teradata assigned identifier for this stored procedure
SPText
Contains Stored Procedure text
Internal Flag
Trigger Class Property Descriptions

Table 48: Trigger Class Property Descriptions
Property Name
Description
ActionTime
Action time for the trigger:

A = After the trigger event
B = Before the trigger event
I = Instead of the trigger event
CommentString
The comment stored in Teradata for the trigger
CreatorName
The Teradata user that created the trigger
DatabaseId
Teradata assigned identifier for the database where this trigger

resides
Event
Type of SQL DML statement that causes trigger to fire:

D = Delete
I = Insert
U = Update
IsEnabled
Indicates whether the trigger is activated or not:

Y = Enabled
N= Disabled
Kind
Trigger kind as defined by the FOR EACH clause:

R = Row
S = Statement
LastAlterTimeStamp
OrderingPosition
When one or more triggers are defined on the same table,

ORDER allows you to determine the sequence for firing each
trigger.
RequestText
Contains the text that created the trigger
Internal Flag
190

Table 48: Trigger Class Property Descriptions (continued)
Property Name
Description
TriggerId
Teradata assigned identifier for this trigger
Subject Area Class Property Descriptions

Table 49: Subject Area Class Property Descriptions
Property Name
Description
BusinessDefinition
Business definition of the subject area
SubjectAreaID
ID Number of the subject area
Author
Name of the creator of the subject area
Business Entity Class Property Descriptions

Table 50: Business Entity Class Property Descriptions
Property Name
Description
BusinessDefinition
Business description of entity
BusinessNotes
Comment text
EntityID
ID Number of the entity
EntityType
Value that indicates the type of the Entity. Valid values are:
ET_DE = dependent
ET_DR = derived
ET_IE = independent
SourceFile
Name of the file the entity was loaded from (such as the name of
the ERwin file)
Business Attribute Class Property Descriptions

Table 51: Business Attribute Class Property Descriptions
Property Name
Description
BusinessDefinition
Business description of attribute
BusinessNotes
Comment text
AttributeID
ID Number of the attribute
191

Table 51: Business Attribute Class Property Descriptions (continued)
Property Name
Description
AttributeType
Attribute type
Valid values are:
AT_DR = derived column
AT_NK = nonkey
AT_PK = key
ColumnPosition
The ordered position of the Attribute at the logical level
RoleName
Describes the Attributes role as a foreign key
Business Rule Class Property Descriptions

Table 52: Business Rule Class Property Descriptions
Property Name
Description
RuleDefinition
Definition of the rule
RuleID
ID Number of the rule
MinimumValue
String that specifies the minimum value
MaximumValue
String that specifies the maximum value
Valid Values Class Property Descriptions

Table 53: Valid Values Class Property Descriptions
Property Name
Description
ValueDefinition
Definition of the value
DisplayValue
The screen display form of the value
SequenceNumber
Sequence number of the value in the list
FKReference Class Property Descriptions (Derived from Reference

Column)
Table 54: FKReference Class Property Descriptions
192
Property Name
Description
ForeignKeyColName
Name of foreign key element
ReferenceColName
Name of the reference column
DatabaseID
Assigned identifier for the database where this Foreign Key

reference resides

Table 54: FKReference Class Property Descriptions (continued)
Property Name
Description
TableID
Assigned identifier for the table where this Foreign Key reference
is built
ReferenceID
Assigned identifier for the Foreign Key reference
RefLoid
Object ID for the ReferenceConstraint
ChildTable
Name of the Child (Referencing) table in a Foreign Key reference
ParentTable
Name of the Parent (Referencing) table in a Foreign Key reference
Macro Class Property Descriptions

Table 55: Macro Class Property Descriptions
Property Name
Description
Comment String
The comment stored in Teradata for the macro
CreatorName
The Teradata user that created the macro
DatabaseID
Teradata assigned identifier for the database where the macro

resides
LastAlterTimeStamp
MacroID
Teradata assigned identifier for this macro
MacroText
Contains the text that created the macro
Internal flag
Macro Parameter Class Property Descriptions

Table 56: Macro Parameter Class Property Descriptions
Property Name
Description
CharType
Specifies the character set type for character parameters
CommentString
The comment stored in Teradata for this parameter
DatabaseID
Teradata assigned identifier for the database where the macro

resides
DataType
The data type for the parameter
DefaultValue
The value assigned to the parameter when no value is specified for

the parameter in the call of the macro
MacroID
Teradata assigned identifier for this macro
193

Table 56: Macro Parameter Class Property Descriptions (continued)
Property Name
Description
ParameterID
Teradata assigned identifier for this macro parameter
ParameterTitle

parameter name, which is used by default
ParamFormat
The format used when displaying or printing the parameter value
ParamLength
Contains the maximum length in bytes for the value of this

parameter
Hash Index Class Property Descriptions

Table 57: HashIndex Properties
Property Name
Description
CommentString
The comment stored in Teradata for the hash index
CreatorName
Name of the Teradata user that created the hash index
DatabaseID
Teradata assigned identifier for the database where the hash index
resides
HashIndexID
Teradata assigned identifier for the hash index
LastAlterTimeStamp
RequestText
The CREATE HASH INDEX statement that created the hash index
Internal Flag
Join Index Class Property Descriptions

Table 58: JoinIndex Properties
194
Property Name
Description
CommentString
The comment stored in Teradata for the join index
CreatorName
Name of the Teradata user that created the join index
DatabaseID
Teradata assigned identifier for the database where the join index
resides
JoinIndexID
Teradata assigned identifier for the join index
LastAlterTimeStamp
RequestText
The CREATE JOIN INDEX statement that created the join index

Table 58: JoinIndex Properties (continued)
Property Name
Description
Internal Flag
MetaLoadTypes Property Descriptions

Table 59: MetaLoadTypeClass Property Descriptions
Property Name
Description
LoadFlags
Binary array with flags indicating the data types that can be loaded
Function Class Property Descriptions

Table 60: Function Class Property Descriptions
Property Name
Description
FunctionID
Teradata assigned identifier for a non-built in function
DatabaseID
Teradata assigned identifier for the database
RequestText
The create text for a user-defined function
LastAlterTimestamp
CreatorName
Name of the Teradata user that created the function
CommentString
Comment stored in Teradata for the function
FunctionClass
Class for the Teradata function or the user defined function

Valid values are:
Function Call = an instance of a function call. The call
parameters are stored in the FunctionCallParameters property.
Teradata BuiltIn = Teradata built-in function
UDF = general user defined function
UDF: Method = user defined function that is defined within a
User Defined Type (UDT)
UDF: Aggregate = user defined aggregate function
UDF: Ordered analytical = user defined ordered analytic window
aggregate function
UDF: Table UDF = user defined table function
UDF: Teradata Internal = a UDF used internally by the Teradata
database
UDT: Constructor = a user defined function that is the
constructor for a UDT
FunctionAlias
Alias used for the function in an SQL statement
195

Table 60: Function Class Property Descriptions (continued)
Property Name
Description
FunctionReturnType
Return type for the function
Internal flag
FunctionSpecificName
The specific name for the user defined function
FunctionCallParameters The actual parameters passed to the function
The following notes apply to constants referenced by a view column and functions referenced
by view columns, stored procedures, macros, etc.
If a constant is used in an expression with a table column or function, the constant and
expression are not stored in the repository. Only the column or function are stored and
associated with the view column.
For example, when a view column references expressions (c1 + 10) and [sum(c1) + 10],
where c1 is a table column, 10 is a constant, and sum(c1) is a function, only table column
c1 and function sum(c1) are stored in the repository and associated with the view column.
The constant 10 and expressions (c1 + 10) and [sum(c1) + 10] are not.
If a function is used in combination with other functions, each individual function is

stored in the repository and associated with the view column, whereas the combination of
functions is not.
For example, when a view column references the expression [sum(c1) + avg (c1)], only the
functions sum(c1) and avg (c1) are stored in the repository and associated with the view
column.
FunctionParameter Class Property Descriptions

Table 61: FunctionParameter Class Property Descriptions
Property Name
Description
CharacterSet
Teradata assigned identifier for the character set of a CHAR/

VARCHAR/CLOB data type
CommentString
Comment stored in Teradata for the parameter
DataType
The data type for the parameter. See the ColumnType entry in Table
37: Column Class Property Descriptions on page 183 for
acceptable values. In addition, the DataType property can include
the following value: ++ TD_ANYTYPE.
ParameterId
The ID of the parameter in the function
ParamLength
The maximum length of the parameter value
RowTypeDatabaseName The name of the database containing the table referenced by a

%ROWTYPE attribute
RowTypeTableName
196
The name of the table referenced by a %ROWTYPE attribute

Constant Class Property Descriptions

Table 62: Constant Class Property Descriptions
Property Name
Description
ConstantType
The type of the constant

Valid values are:
ACCOUNT *
ACTIVITY_COUNT
ALL
ANSIDATE
ASCII
AUTOTEMP
BIGINT
BINARY
CHARSET_COLL
CHAR_SET_GRAPHIC
CURRDATE *
CURRENT_ROLE
CURRENT_USER
CURRTIME *
PROFILE *
CURRTIMESTAMP *
DATABASE *
ConstantValue
DATE *
DECIMAL
DEFAULT
DQUOTESTR
EBCDIC
FLOAT
HEXSTR
HIGH
HOST
INTEGER
INTEGERDATE
JIS_COLL
KANJI
KANJISJIS
LATIN1
LOCAL
LOW
MANUAL
MULTINATIONAL
MEDIUM
NAME
NEVER
NULL
OFF
PARMNAME
PREPARE_COUNT
ROLE *
SESSION *
SOURCE_TIME_ZONE
SQLCODE
SQLSTATE
SQUOTESTR
STAR
TEMPORAL_DATE
TEMPORAL_TIMESTAMP
TIME *
UNICODE
UNKNOWN
USER *
The value of the constant
197

Values marked with * in the table are converted from constants to functions before being
stored in the MDS repository, and become part of function class BI (built-in). Date, Time,
Timestamp and Interval literals are stored as constant type SQUOTESTR (single quoted
string).
The following notes apply to constants referenced by a view column and functions referenced
by view columns, stored procedures, macros, etc.:
If a constant is referenced as a standalone value or in combination with other constants in

an expression, the constant or expression is stored in the repository and associated with
the view column.
For example, when a view column references the standalone constant 10, or the expression
of constants 10 + 20, then 10 or 10 + 20 is stored in the repository and associated with the
view column.
When a constant is used as a function parameter, such as in the function log(5), the
constant and function are stored in the repository and associated with the view column.
If a view column references a table column in combination with another table column,
both columns are stored in the repository and associated with the view column.
For example if a view column references table columns c1 + c2, both c1 and c2 are stored
in the repository and associated with the view column.
Because operators are not stored in the repository, it is not possible to determine if a view
column has two associated table columns because of an arithmetic operator such as (+) or
a binary operator such as OR.
UDT Class Property Descriptions

Table 63: UDT Class Property Descriptions
Property Name
Description
CommentString
Comment stored in Teradata for the UDT
CreatorName
The Teradata user that issued the CREATE TYPE
DatabaseID
Teradata assigned identifier for the database containing the UDT
DistinctPredefinedType The data type on which a distinct UDT is based

IsStructured
Is this a structured or distinct type?

Values are: Y=structured UDT, N=distinct UDT
LastAlterTimestamp
The time when the UDT was last modified
NumberOfArrayDimen The number of array dimensions for a UDT defining an ARRAY type
sions
198
RequestText
The CREATE TYPE statement
TypeID
Teradata assigned identifier for the type

DIM Relationship Descriptions
UDTAttribute Class Property Descriptions

Table 64: UDT Attribute Class Property Descriptions
Property Name
Description
AttributeFormat
The format string for the attribute, such as 9(5)
AttributeId
The order of the attribute within the UDT
AttributeLength
The maximum length of the attribute
CharacterSet
Teradata assigned identifier for the character set of a CHAR/

VARCHAR/CLOB data type
CommentString
Comment stored in Teradata for the attribute
DataType
The data type for the attribute
DecimalFractDigits
N of DECIMAL(m,n)
DecimalTotalDigits
M of DECIMAL(m,n)
TypeID
Teradata assigned identifier for the UDT containing this attribute

Table 65 describes DIM relationships. The diagram numbers refer to Figure 5: Database
Information Metamodel (DIM) (Sheet 1 of 2) on page 177 and Figure 6: Database
Information Metamodel (DIM) (Sheet 2 of 2) on page 178.
Table 65: DIM Relationship Descriptions
Relationship Name
Number in
Diagram
Description
SystemHasDatabases
Associates databases with Teradata Database systems
SystemHasNodes
Associates nodes with Teradata Database systems
DatabaseHasTables
Associates tables with databases where they reside
DatabaseHasViews
Associates views with databases
DatabaseHasMacros
Associates macros with databases
DatabaseHasStoredProcedures
Associates stored procedures with databases
DatabaseHasTriggers
Associates triggers with databases
DatabaseHasSubjectAreas
Associates subject areas with databases
DatabaseHasEntities
Associates business entities with databases
DatabaseHasRules
10
Associates business rules with databases
199

Table 65: DIM Relationship Descriptions (continued)
Relationship Name
Number in
Diagram
Description
DatabaseOwnsDatabases
11
Associates databases with owner databases
BusEntityHasAttributes
12
Associates attributes with business entities
BusEntityTable
13
Associates tables with business entities
BusEntityView
14
Associates views with business entities
BusAttrViewColumn
15
Associates view columns with business attributes
BusAttrColumn
16
Associates columns with business attributes
BusAttrRules
17
Associates rules with business attributes
BusRuleValues
18
Associates valid values with business rules
SubjectAreaEntities
19
Associates business entities with subject areas
TableHasColumns
20
Associates columns with tables
TableHasIndices
21
Associates indexes with tables
IndexContainsColumns
22
Associates columns with indexes
TableHasCheckConstraints
23
Associates check constraints with tables
TableHasRefConstraints
24
Associates reference constraints with tables
ConstraintReferencesColumns
25
Associates referenced columns with constraints
TableHasTriggers
26
Associates triggers with tables
ColumnHasTriggers
27
Associates triggers with columns
ViewHasColumns
28
Associates columns with views
ViewHasTableColumns
29
Associates table columns with views
ViewReferencesViews
30
Associates referenced views with other views
ViewColReferencesTableCols
31
Associates referenced table columns with view columns
SPHasParameters
32
Associates parameters with stored procedures
SPReferencesTables
33
Associates referenced tables with stored procedures
SPReferencesViews
34
Associates referenced views with stored procedures
SPReferencesStoredProcedures
35
Associates referenced stored procedures with other stored

procedures
SPReferencesMacros
36
Associates referenced macros with stored procedures
SPRefencesTableColumns
37
Associates referenced table columns with stored procedures
SPReferencesViewColumns
38
Associates referenced view columns with stored procedures
TriggerReferencesMacros
39
Associates referenced macros with triggers
200

Relationship Name
Number in
Diagram
Description
MacroHasParameters
40
Associates parameters with macros
MacroReferencesTables
41
Associates referenced tables with macros
MacroReferencesViews
42
Associates referenced views with macros
MacroReferencesSPs
43
Associates referenced stored procedures with macros
MacroReferencesMacros
44
Associates referenced macros with other macros
MacroReferencesTriggers
45
Associates referenced triggers with macros
MacroReferencesTableColumns
46
Associates referenced table columns with macros
MacroReferencesViewColumn
47
Associates referenced view columns with macros
DatabaseHasHashIndexes
48
Associates hash indexes with databases
DatabaseHasJoinIndexes
49
Associates join indexes with databases
JoinIndexHasIndices
50
Associates indexes with join indexes
HashIndexHasIndices
51
Associates indexes with hash indexes
JoinIndexReferencesTables
52
Associates referenced tables with join indexes
JoinIndexReferencesTableColumns
53
Associates referenced table columns with join indexes
HashIndexReferencesTables
54
Associates referenced tables with hash indexes
SPReferencesJoinIndexes
55
Associates referenced join indexes with stored procedures
MacroReferencesJoinIndexes
56
Associates referenced join indexes with macros
SystemHasMetaLoadTypes
57
Associates Metaload types with database systems
ViewReferencesTables
58
Associates referenced tables with views
TableHasErrorTable
59
Associates tables with their error tables
ViewColumnReferencesConstants
60
Associates referenced constants with view columns
TriggerReferencesTables
61
Associates referenced tables with triggers
HashIndexReferencesTableColumns
62
Associates referenced table columns with hash indexes
MacroReferencesHashIndexes
63
Associates referenced hash indexes with macros
SPReferencesHashIndexes
64
Associates referenced hash indexes with stored procedures
DatabaseHasUDTs
65
Associates UDTs with databases
UDTHasAttributes
66
Associates UDT attributes with UDTs
UDTHasFunctions
67
Associates functions with UDTs
DatabaseHasFunctions
68
Associates functions with databases
201

Relationship Name
Number in
Diagram
Description
FunctionHasParameters
69
Associates function parameters with functions
ColumnHasUDT
70
Associates UDTs with table columns
ViewColumnHasUDT
71
Associates UDTs with view columns
MacroParameterHasUDT
72
Associates UDTs with macro parameters
SPParameterHasUDT
73
Associates UDTs with SP parameters
JoinIndexReferencesFunctions
74
Associates referenced functions with join indexes
MacroReferencesFunctions
75
Associates referenced functions with macros
SPReferencesFunctions
76
Associates referenced functions with stored procedures
TriggerReferencesUDTs
77
Associates referenced UDTs with triggers
TriggerReferencesFunctions
78
Associates referenced functions with triggers
UDTAttributeHasUDT
79
Associates UDTs with UDT attributes
ViewColumnReferencesFunctions
80
Associates referenced functions with view columns
FunctionParameterHasUDT
81
Associates UDTs with function parameters
FunctionCallUsesUDF
82
Associates a function object that defines a call to a function with a

referenced function
FunctionReferencesFunctions
83
Associates a function with another function
ViewReferencesFunctions
84
Associates a view with functions
202
APPENDIX B
Client Load Utility Metadata - Client Load

Metamodel
Client Load Metamodel
MDS loads the Teradata Client Load Utility information (load script and output file) into the
MDS repository using the Client Load Metamodel.
The Client Load Metamodel (CLM) is a MDS defined metamodel for the TeradataClient Load
Utilities. The CLM stores metadata information about loading data into the Teradata system
through the use of MutliLoad, FastLoad and T-Pump scripts.
This metadata information includes information about a load script and its execution status,
information about the data source(s) that are used by the load script, and information about
the target table(s) and the view(s) that are loaded by the load script.
The CLM is linked to the Database Information Metamodel (DIM) at both the Table/View
level (Script and Source objects to the DIM Table class objects) and the Column/ViewColumn
level (SourceField objects to the DIM Column class objects). These linkages will allow a user
to traverse through both models regardless of which model he started with. The MDS utilities
metacreate and metamigrate automatically create the CLM in the MDS repository. The
metaclient program is used to load the Client Load metadata information into the CLM.
The CLM is represented by the following figure.
203
Appendix B: Client Load Utility Metadata - Client Load Metamodel

Figure 7: Client Load Metamodel

Script
VersionID
ScriptQualifier
OutputFileName
LoadUtility
SessCharSet
ScriptLevelDDLUsed
ProcessorTime
HighestReturnCode
CompletionStatus
StartTime
StartDate
EndTime
EndDate
ScriptHasSources
Source
SourceType
INMODRoutine
StartRecordRange
EndRecordRange
RecordFormat
IndicatorBits
ScriptHasTargets
Target
ScriptLoadsDIMViews
ScriptLoadsDIMTables
TargetType
TargetSystemName
TargetDatabaseName
TargetLevelDDLUsed
TargetLevelDMLUsed
NbrRecsSentToTD
NbrRecordsRead
NbrRecordsDeleted
NbrRecordsInserted
NbrRecordsSkipped
NbrRecordsUpdated
NbrErrorsTbl1
NbrErrorsTbl2
SourceLoadsDIMTables
Table
SourceUpdatesDIMViews
View
Database
Information
Model
SourceHasSourceFields
ScriptField
DataType
DataLenght
RecLayoutName
SourceFieldUpdatesDIMColumns
SourceFieldUpdatesDIMViewColumns
Column
ViewColumn
3047A013
204

CLM Class Descriptions
CLM Class Descriptions

The following table defines the CLM class descriptions.
Table 66: CLM Class Descriptions
Class Name
Description
Script
A Client Load script
Source
A data source used in the Client Load script
SourceField
A data field defined in the Source input record
Target
A target where the Source data is loaded into
The names of all objects in the CLM classes are limited to 255 characters.
CLM Class Property Descriptions

Script Class Property Descriptions
Table 67: Script Class Property Descriptions
Property Name
Description
VersionID
ID identifying a particular instance of the execution of this Client

Load script
ScriptQualifier
Identification information for this script on the origin system
OutputFileName
Name of this scripts output file
LoadUtility
Client Load Utility that this script is for
SessCharSet
The character set used by this script session
ScriptLevelDDLUsed
String list of non-Target related DDL statements executed in the

script
ProcessorTime
Amount of processor time used during the execution of this script
HighestReturnCode
The highest return code produced during the execution of this

script
CompletionStatus
Status of the scripts execution
StartTime
Time when the execution of the script started (HH:MM:SS)
StartDate
Date when the execution of the script started (YYYY-MM-DD)
EndTime
Time when the execution of the script ended (HH:MM:SS)
EndDate
Date when the execution of the script ended (YYYY-MM-DD)
205

Source Class Property Descriptions

Table 68: Source Class Property Descriptions
Property Name
Description
SourceType
Type of the input data source
INMODRoutine
Name of the INMOD routine that is preprocessing the input data

from this source
StartRecordRange
Record number of the 1st input record to be processed
EndRecordRange
Record number of the last input record to be processed
RecordFormat
Format of the input records
IndicatorBits
Indicates whether Indicator Bits are present in the input records
Source Field Class Property Descriptions

Table 69: Source Field Class Property Descriptions
206
Property Name
Description
DataType
Data type of the source field
DataLength
Data length of the source field
RecLayoutName
Name of the record layout definition where this source field is

defined

Target Class Property Descriptions

Table 70: Target Class Property Descriptions
Property Name
Description
TargetType
Type of the target For example, table or view
TargetSystemName
Name of the target system
TargetDatabaseName
Name of the target database
TargetLevelDDLUsed
String list of DDL statements executed against the target table
TargetLevelDMLUsed
String list of DML statements executed against the target table
NbrRecordsRead
Number of input records read
NbrRecsSentToTD
Number of input records sent to the Teradata Database
NbrRecordsDeleted
Number of records deleted from the target table
NbrRecordsInserted
Number of records inserted into the target table
NbrRecordsSkipped
Number of input records skipped
NbrRecordsUpdated
Number of records updated in the target table
NbrErrorsTbl1
Number of error records in error table #1
NbrErrorsTbl2
Number of error records in error table #2
207

CLM Relationship Descriptions
CLM Relationship Descriptions

The following table defines the CLM relationship descriptions.
Table 71: CLM Relationship Descriptions
208
Relationship Name
Description
ScriptHasSources
Associates Client Load scripts with their input data

sources
ScriptLoadsDIMTables
Associates Client Load scripts with the DIM tables

that they load
ScriptLoadsDIMViews
Associates Client Load scripts with the DIM views

that they load
ScriptHasTargets
Associates Client Load scripts with the targets that

they load
SourceHasSourceFields
Associates data sources with the data fields defined

in their input records
SourceUpdatesDIMTables
Associates data sources with the DIM tables that

they load
SourceUpdatesDIMViews
Associates data sources with the DIM views that they

load
SourceFieldUpdatesDIMColumns
Associates data fields with the DIM Table Columns

that they load
SourceFieldUpdatesDIMViewColumns
Associates data fields with the DIM View Columns

that they load
APPENDIX C
SQL Views
This appendix is a quick reference to the views providing read access into the Teradata Meta
Data Services repository.
This document is intended for the following users:
Teradata MDS end users
Teradata MDS administrators
Teradata Database administrators
MDS SQL Views

The Teradata MDS Views are part of MDS and reside in the space assigned for the MDS
repository database on Teradata. These pre-defined views provide users with a way to retrieve
frequently used data from underlying MDS repository tables.
The following views provide access to the metadata in the Database Information Metamodel
(DIM) through the use of standard SQL.
meta_BusinessAttrColumns
meta_JoinIndexFunctions
meta_StoredProcTableColumns
meta_BusinessAttributeRules
meta_JoinIndexIndices
meta_StoredProcViewColumns
meta_BusinessAttributes
meta_JoinIndexTableColumns
meta_SubjectAreaEntities
meta_BusinessAttrViewCols
meta_JoinIndexTables
meta_SubjectAreas
meta_BusinessEntities
meta_MacroHashIndexes
meta_SystemMetaloadTypes
meta_BusinessEntityAttrs
meta_MacroJoinIndexes
meta_SystemNodes
meta_BusinessEntityTables
meta_MacroParameters
meta_TableColumns
meta_BusinessEntityViews
meta_MacroReferencesMacros
meta_TableHasTriggers
meta_BusinessRules
meta_Macros
meta_Tables
meta_BusinessRuleValues
meta_MacroStoredProcedures
meta_TriggerMacros
meta_CheckConstraints
meta_MacroTableColumns
meta_Triggers
meta_ColumnHasTriggers
meta_MacroTables
meta_TriggerTables
meta_Columns
meta_MacroTriggers
meta_TV
209
Appendix C: SQL Views

meta_DatabaseBusEntities
meta_MacroViewColumns
meta_TVColumns
meta_DatabaseBusinessRules
meta_MacroViews
meta_TVM
meta_DatabaseOwnsDatabases
meta_RefConstraintColumns
meta_ValidValues
meta_Databases
meta_RefConstraints
meta_ViewColumnConstants
meta_DatabaseSubjectAreas
meta_SPParameters
meta_ViewColumnFunctions
meta_FunctionParameters
meta_StoredProcedureMacros
meta_ViewColumns
meta_HashIndexIndices
meta_StoredProcedures
meta_ViewColumnTableColumns
meta_HashIndexTableColumns
meta_StoredProcedureTables
meta_ViewReferencesViews
meta_HashIndexTables
meta_StoredProcedureViews
meta_Views
meta_IndexColumns
meta_StoredProcHashIndexes
meta_ViewTableColumns
meta_Indexes
meta_StoredProcJoinIndexes
meta_ErrorTables
meta_JoinIndexes
meta_StoredProcRefsSPs
meta_ColumnUDTs
meta_MacroFunctions
meta_MacroParameterUDTs
meta_SPParameterUDTs
meta_TriggerFunctions
meta_TriggerUDTs
meta_UDFFunctions
meta_UDFs
meta_UDTAttributes
meta_UDTAttributeUDTs
meta_UDTFunctions
meta_UDTs
meta_ViewColumnUDTs
meta_ViewFunctions
meta_ViewTables
Returns the current table columns in the repository systems that have defined Business
Attributes. Corresponds to the relationship BusAttrColumn.
Table 72: Columns and Data Types of the meta_BusinessAttriColumns View
210
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
AttributeName
VARCHAR(128)
ColumnLoid
INTEGER
AttributeLoid
INTEGER

Returns the Business Rules associated with each Business Attribute in the repository.
Corresponds to the relationship BusAttrRules.
Table 73: Columns and Data Types of the meta_BusinessAttributeRules View Descriptions
Column
Data Type
AttributeName
VARCHAR(128)
RuleName
VARCHAR(128)
RuleID
INTEGER
RuleDefinition
VARCHAR(12500)
AttributeLoid
INTEGER
RuleLoid
INTEGER
meta_BusinessAttributes
Returns the current Business Attributes defined in the repository.
Table 74: Columns, Data Types, and Values of the meta_BusinessAttributes View
Column
Data Type
AttributeName
VARCHAR(128)
AttributeID
INTEGER
AttributeType
VARCHAR(6)
Rolename
VARCHAR(12500)
ColumnPosition
INTEGER
BusinessDefinition
VARCHAR(12500)
BusinessNotes
VARCHAR(12500)
AttributeLoid
INTEGER
Values
AT_DR = Derived Column

AT_NK = Nonkey
AT_PK = Key
211

Returns the current view columns in the repository systems that have defined Business
Attributes. Corresponds to the relationship BusAttrViewColumn.
Table 75: Columns and Data Types of the meta_BusinessAttrViewCols View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ViewColumnName
VARCHAR(128)
AttributeName
VARCHAR(128)
ViewColumnLoid
INTEGER
AttributeLoid
INTEGER
meta_BusinessEntities
Returns the current Business Entities defined in the repository.
Table 76: Columns, Data Types, and Values of the meta_BusinessEntities View
212
Column
Data Type
EntityName
VARCHAR(128)
EntityType
VARCHAR(6)
EntityID
INTEGER
SourceFile
VARCHAR(255)
BusinessDefinition
VARCHAR(12500)
BusinessNotes
VARCHAR(12500)
EntityLoid
INTEGER
Values
ET_DE = Dependent
ET_DR = Derived
ET_IE = Independent

Returns the Business Attributes comprising each Business Entity in the repository.
Corresponds to the relationship BusEntityHasAttributes.
Table 77: Columns and Data Types of the meta_BusinessEntityAttrs View
Column
Data Type
EntityName
VARCHAR(128)
AttributeName
VARCHAR(128)
AttributeID
INTEGER
AttributeType
VARCHAR(6)
AttributeRolename
VARCHAR(255)
AttributeColumnPosition
INTEGER
AttributeBusinessDefinition
VARCHAR(12500)
AttributeBusinessNotes
VARCHAR(12500)
EntityLoid
INTEGER
AttributeLoid
INTEGER
meta_BusinessEntityTables
Returns the current tables in the repository systems that have defined Business Entities.
Corresponds to the relationship BusEntityTables.
Table 78: Columns and Data Types of the meta_BusinessEntityTables View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
EntityName
VARCHAR(128)
TableLoid
INTEGER
EntityLoid
INTEGER
213

Returns the current views in the repository systems that have defined Business Entities.
Corresponds to the relationship BusEntityViews.
Table 79: Columns and Data Types of the meta_BusinessViews View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
EntityName
VARCHAR(128)
ViewLoid
INTEGER
EntityLoid
INTEGER
meta_BusinessRules
Returns the Business Rules defined in the repository.
Table 80: Columns and Data Types of the meta_BusinessRules View
Column
Data Type
RuleName
VARCHAR(128)
RuleID
INTEGER
RuleDefinition
VARCHAR(12500)
MinimumValue
VARCHAR(255)
MaximumValue
VARCHAR(255)
RuleLoid
INTEGER
meta_BusinessRuleValues
Returns the Valid Values defined for each Business Rule in the repository. Corresponds to the
relationship BusRuleValues.
214

Table 81: Columns and Data Types of the meta_BusinessRuleValues View
Column
Data Type
RuleName
VARCHAR(128)
ValueName
VARCHAR(128)
ValueSequenceNumber
INTEGER
ValueDefinition
VARCHAR(12500)
RuleLoid
INTEGER
ValueLoid
INTEGER
Returns the current CHECK constraints for the tables in the repository systems. Corresponds
to the relationship TableHasCheckConstraints.
Table 82: Columns, Data Types, and Values of the meta_CheckConstraints View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
CheckName
VARCHAR(128)
CheckLoid
INTEGER
CheckType
CHAR(1)
CheckTypeA
VARCHAR(18)
CheckBool
VARCHAR(8192)
Values
Constraint Check
Partitioning Check
meta_ColumnHasTriggers
Returns the table column names comprising the triggers in the repository systems.
Corresponds to the relationship ColumnHasTriggers.
215

meta_Columns
Table 83: Columns and Data Types of the meta_ColumnHasTriggers View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
TriggerDatabaseName
VARCHAR(128)
TriggerName
VARCHAR(128)
ColumnLoid
INTEGER
TriggerLoid
INTEGER
meta_Columns
Returns the columns for the tables, views, macros, and stored procedures defined in the
repository systems. The TVType fields returns 'T' for a table, 'V ' for a view, 'M' for a macro,
and 'P' for a stored procedure.
Table 84: Columns, Data Types, and Values of the meta_Columns View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TVType
VARCHAR(2)
Values
T = Table
V = View
M = Macro
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
ColumnID
SMALLINT
ColumnLoid
INTEGER
ColumnType
CHAR(2)
216
P = Stored Procedure

meta_Columns
Table 84: Columns, Data Types, and Values of the meta_Columns View (continued)
Column
Data Type
Values
ColumnTypeA
VARCHAR(29)
ColumnLength
INTEGER
CharType
SMALLINT
CharacterSet
VARCHAR(8)
DecimalTotalDigits
SMALLINT
DecimalFractionalDigits
SMALLINT
UppercaseFlag
VARCHAR(3)
Nullable
VARCHAR(3)
DefaultValue
VARCHAR(1024)
Compressible
VARCHAR(3)
CompressValue
VARCHAR(8192)
IDColType
VARCHAR(164)
1-dimensional Array
ANSI Time
BLOB
VARBYTE
CLOB
Decimal
Day
Day to Minute
Date Tag
Hour
Hour To Second
Byte Integer
BIGINT
Month
NUMBER
PERIOD(DATE)
PERIOD(TIME)w/TimeZone
PERIOD(TIMESTAMP)w/
TimeZone
Timestamp w/ TimeZone
ANSI Timestamp w/
TimeZone
Unicode Fixed Character
Year
Graphic
Latin
Unicode
n-dimensional Array
Binary Fixed
Binary String
Character Fixed
VARCHAR
Date
Day To Hour
Day to Second
Real/Float
Hour To Minute
Integer
Short Integer
Minute
Minute To Second
PERIOD(TIME)
PERIOD(TIMESTAMP)
Second
Timestamp
User Defined Type
Unicode VARCHAR
Year To Month
Kanji1
ShiftJIS
Other
217

Table 84: Columns, Data Types, and Values of the meta_Columns View (continued)
Column
Data Type
SPParameterType
VARCHAR(1)
ColumnTitle
VARCHAR(256)
CommentString
VARCHAR(255)
ColumnUDTName
VARCHAR(128)
Values
Returns the Business Entities defined for the current databases in the repository systems.
Corresponds to the relationship DatabaseHasEntities.
Table 85: Columns, Data Types, and Values of the meta_DatabaseBusEntities View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
EntityName
VARCHAR(128)
EntityType
VARCHAR(6)
DatabaseLoid
INTEGER
EntityLoid
INTEGER
Values
ET_DE = Dependent
ET_DR = Derived
ET_IE = Independent
meta_DatabaseBusinessRules
Returns the Business Rules defined for the current databases in the repository systems.
Corresponds to the relationship DatabaseHasRules.
Table 86: Columns and Data Types of the DatabaseBusinessRules View
218
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
RuleName
VARCHAR(128)
RuleId
INTEGER

Table 86: Columns and Data Types of the DatabaseBusinessRules View (continued)
Column
Data Type
RuleDefinition
VARCHAR(12500)
DBLoid
INTEGER
RuleLoid
INTEGER
Returns the names of the databases owned by another database or user. Corresponds to the
relationship DatabaseOwnsDatabases.
Table 87: Columns and Data Types of the DatabaseBusinessRules View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
OwnedDatabaseName
VARCHAR(128)
OwnerLoid
INTEGER
OwnedLoid
INTEGER
meta_Databases
Returns the current databases by systems in the repository. Corresponds to the relationship
SystemHasDatabases.
Table 88: Columns, Data Types, and Values of the meta_Databases View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
Values
219

Table 88: Columns, Data Types, and Values of the meta_Databases View (continued)
Column
Data Type
Values
DBType
VARCHAR(8)
USER = Teradata User

DATABASE = Teradata
Database
A = MS Access Database
B = DB2 Database
I = Informix Database
M = SQLServer Database
O = Oracle Database
R = Redbrick Database
S = Sybase Database
T = Teradata Database from
MIMB load
DBCreatorName
VARCHAR(128)
IsSynchronized
VARCHAR(45)
DBLoid
INTEGER
Returns the Subject Areas defined for the current databases in the repository systems.
Corresponds to the relationship DatabaseHasSubjectAreas.
Table 89: Columns and Data Types of the meta_DatabaseSubjectAreas View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
SubjectAreaName
VARCHAR(128)
DatabaseLoid
INTEGER
SubjectAreaLoid
INTEGER
Returns the macros referenced by the current stored procedures in the repository systems.
Corresponds to the relationship SPReferencesMacros.
220

Table 90: Columns and Data Types of the meta_StoredProcedureMacros View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
MacroDatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
SPLoid
INTEGER
MacroLoid
INTEGER
Returns the parameters for the current functions in the systems in the repository.
Corresponds to the relationship FunctionHasParameters.
Table 91: Columns and Data Types of the meta_FunctionParameters View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
FunctionName
VARCHAR(128)
ParameterName
VARCHAR(128)
ParameterDataType
CHAR(2)
Values
221

Table 91: Columns and Data Types of the meta_FunctionParameters View (continued)
Column
Data Type
ParameterDataTypeA
VARCHAR(29)
Values
CharType
SMALLINT
CharacterSet
VARCHAR(8)
RowTypeDatabaseName
VARCHAR(128)
RowTypeTableName
VARCHAR(128)
FunctionLoid
INTEGER
ParameterLoid
INTEGER
1-dimensional Array
ANSI Time
BLOB
VARBYTE
CLOB
Decimal
Day
Day to Minute
Date Tag
Hour
Hour To Second
Byte Integer
BIGINT
Month
PERIOD(DATE)
PERIOD(TIME)w/
TimeZone
PERIOD(TIMESTAMP)w/
TimeZone
ANSI Timestamp w/
TimeZone
User Defined Type
n-dimensional Array
Binary Fixed
Binary String
Character Fixed
VARCHAR
Date
Day To Hour
Day to Second
Real/Float
Hour To Minute
Integer
Short Integer
Minute
Minute To Second
PERIOD(TIME)
PERIOD(TIMESTAMP)
Second
Timestamp
Year
NUMBER
TD_ANYTYPE
Returns the sub-indexes of the current Hash indexes by system and database in the repository.
Corresponds to the HashIndexHasIndices relationship.
222

Table 92: Columns, Data Types, and Values of the meta_HashIndexIndices View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
HashIndexName
VARCHAR(128)
IndexName
VARCHAR(128)
IndexType
CHAR(1)
IndexTypeA
VARCHAR(35)
Values
IsUnique
VARCHAR(3)
IndexNumber
SMALLINT
HashIndexLoid
INTEGER
IndexLoid
INTEGER
Primary
Partition Primary
Secondary
Join
Hash
Primary Key
Unique Constraint
Value ordered secondary
Hash ordered ALL secondary
Value ordered ALL
secondary
Ordering column
Multi-column statistics
Derived column partition
statistics
Field1 of hash
Field2 of hash
Returns the table columns referenced by the current hash indexes in the repository systems.
Corresponds to the relationship HashIndexReferencesTableColumns.
Table 93: Columns and Data Types of the meta_HashIndexTableColumns View
Column
Data Type
SystemName
VARCHAR(256)
223

Table 93: Columns and Data Types of the meta_HashIndexTableColumns View (continued)
Column
Data Type
DatabaseName
VARCHAR(128)
HashIndexName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
HashIndexLoid
INTEGER
ColumnLoid
INTEGER
Returns the tables referenced by the current hash indexes in the repository systems.
Corresponds to the relationship HashIndexReferencesTables.
Table 94: Columns and Data Types of the meta_HashIndexTables View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
HashIndexName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
HashIndexLoid
INTEGER
TableLoid
INTEGER
meta_IndexColumns
Returns the table columns comprising the indexes defined for the repository systems.
Corresponds to the relationship IndexHasColumns.
Table 95: Columns and Data Types of the meta_IndexColumns View
224
Column
Data Type
SystemName
VARCHAR(256)

meta_Indexes
Table 95: Columns and Data Types of the meta_IndexColumns View (continued)
Column
Data Type
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
ColunmLoid
INTEGER
ColumnPosition
SMALLINT
IndexNumber
SMALLINT
meta_Indexes
Returns the indices (primary, secondary, hash, join, etc.) defined for the current tables in the
repository. Corresponds to the relationships TableHasIndexes, DatabaseHasHashIndexes, and
DatabaseHasJoinIndexes.
Table 96: Columns, Data Types, and Values of the meta_Indexes View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
IndexName
VARCHAR(128)
IndexLOID
INTEGER
IndexType
CHAR(1)
Values
225

meta_JoinIndexes
Table 96: Columns, Data Types, and Values of the meta_Indexes View (continued)
Column
Data Type
Values
IndexTypeA
VARCHAR(35)
IsUnique
VARCHAR(3)
IndexNumber
SMALLINT
Primary
Partition Primary
Secondary
Join
Hash
Primary Key
Unique Constraint
Value ordered ALL
secondary
Ordering column
statistics
Field1 of hash/join
Field2 of hash/join
meta_JoinIndexes
Returns the current join indexes by system and database in the repository. Corresponds to the
SystemHasJoinIndexes relationship.
Table 97: Columns and Data Types of the meta_JoinIndexes View
226
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
JoinIndexName
VARCHAR(128)
IsSynchronized
VARCHAR(6)
LastAlterTimestamp
TIMESTAMP
RequestText
VARCHAR(12500)
CreatorName
VARCHAR(128)
JoinIndexLoid
INTEGER

Returns the Functions referenced by the current join indexes in the repository systems.
Corresponds to the relationship JoinIndexReferencesFunctions.
Table 98: Columns and Data Types of the meta_JoinIndexFunctions View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
JoinIndexName
VARCHAR(128)
FunctionName
VARCHAR(128)
JoinIndexLoid
INTEGER
FunctionLoid
INTEGER
meta_JoinIndexIndices
Returns the sub-indexes of the current Join indexes by system and database in the repository.
Corresponds to the JoinIndexHasIndices relationship.
Table 99: Columns, Data Types, and Values of the meta_JoinIndexIndices View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
JoinIndexName
VARCHAR(128)
IndexName
VARCHAR(128)
IndexType
CHAR(1)
Values
227

Table 99: Columns, Data Types, and Values of the meta_JoinIndexIndices View (continued)
Column
Data Type
Values
IndexTypeA
VARCHAR(35)
IsUnique
VARCHAR(3)
IndexNumber
SMALLINT
JoinIndexLoid
INTEGER
IndexLoid
INTEGER
Primary
Partition Primary
Secondary
Join
Hash
Primary Key
Unique Constraint
Value ordered ALL
secondary
Ordering column
statistics
Field1 of join
Field2 of join
Returns the table columns referenced by the current join indexes in the repository systems.
Corresponds to the relationship JoinIndexReferencesTableColumns.
Table 100: Columns and Data Types of the meta_JoinIndexTableColumns View
228
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
JoinIndexName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)

Table 100: Columns and Data Types of the meta_JoinIndexTableColumns View (continued)
Column
Data Type
JoinIndexLoid
INTEGER
ColumnLoid
INTEGER
Returns the tables referenced by the current join indexes in the repository systems.
Corresponds to the relationship JoinIndexReferencesTables.
Table 101: Columns and Data Types of the meta_JoinIndexTables View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
JoinIndexName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
JoinIndexLoid
INTEGER
TableLoid
INTEGER
meta_MacroHashIndexes
Returns the hash indexes referenced by the current macros in the repository systems.
Corresponds to the relationship MacroReferencesHashIndexes.
Table 102: Columns and Data Types of the meta_MacroHashIndexes View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
HashIndexDatabaseName
VARCHAR(128)
HashIndexName
VARCHAR(128)
MacroLoid
INTEGER
229

Table 102: Columns and Data Types of the meta_MacroHashIndexes View (continued)
Column
Data Type
HashIndexLoid
INTEGER
Returns the join indexes referenced by the current macros in the repository systems.
Corresponds to the relationship MacroReferencesJoinIndexes.
Table 103: Columns and Data Types of the meta_MacroJoinIndexes View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
JoinIndexDatabaseName
VARCHAR(128)
JoinIndexName
VARCHAR(128)
MacroLoid
INTEGER
JoinIndexLoid
INTEGER
Returns the parameters defined for the current macros in the repository systems. Corresponds
to the relationship MacroHasParameters.
Table 104: Columns, Data Types, and Values of the meta_MacroParameters View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
ParameterName
VARCHAR(128)
ParameterPositionID
SMALLINT
ParameterDataType
CHAR(2)
230
Values

Table 104: Columns, Data Types, and Values of the meta_MacroParameters View (continued)
Column
Data Type
Values
ParameterDataTypeA
VARCHAR(29)
1-dimensional Array
ANSI Time
BLOB
VARBYTE
CLOB
Decimal
Day
Day to Minute
Date Tag
Hour
Hour To Second
Byte Integer
BIGINT
Month
NUMBER
PERIOD(DATE)
PERIOD(TIMESTAMP)w/
TimeZone
ANSI Timestamp w/
TimeZone
User Defined Type
ParameterLength
INTEGER
CharType
SMALLINT
CharacterSet
VARCHAR(8)
Graphic
Latin
Unicode
Kanji1
ShiftJIS
Other
DefaultValue
VARCHAR(1024)
ParameterTitle
VARCHAR(256)
ParameterComment
VARCHAR(255)
MacroLoid
INTEGER
ParameterLoid
INTEGER
n-dimensional Array
Binary Fixed
Binary String
Character Fixed
VARCHAR
Date
Day To Hour
Day to Second
Real/Float
Hour To Minute
Integer
Short Integer
Minute
Minute To Second
PERIOD(TIME)
PERIOD(TIMESTAMP)
Second
Timestamp
Year
231

Returns the macros referenced by the current macros in the repository systems. Corresponds
to the relationship MacroReferencesMacros.
Table 105: Columns and Data Types of the meta_MacroReferencesMacros View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
RefdDatabaseName
VARCHAR(128)
RefdMacroName
VARCHAR(128)
MacroLoid
INTEGER
RefdMacroLoid
INTEGER
meta_Macros
Returns the current macros by database in the systems in the repository. Corresponds to the
relationship DatabaseHasMacros.
Table 106: Columns and Data Types of the meta_Macros View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
IsSynchronized
VARCHAR(6)
LastAlterTimestamp
TIMESTAMP
CreatorName
VARCHAR(128)
MacroLoid
INTEGER
meta_MacroStoredProcedures
Returns the Stored Procedures referenced by the current macros in the repository systems.
Corresponds to the relationship MacroReferencesSPs.
232

Table 107: Columns and Data Types of the meta_MacroStoredProcedures View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
SPDatabaseName
VARCHAR(128)
SPName
VARCHAR(128)
MacroLoid
INTEGER
SPLoid
INTEGER
Returns the table columns referenced by the current macros in the repository systems.
Corresponds to the relationship MacroReferencesTableColumns.
Table 108: Columns and Data Types of the meta_MacroTableColumns View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
MacroLoid
INTEGER
ColumnLoid
INTEGER
meta_MacroTables
Returns the tables referenced by the current macros in the repository systems. Corresponds to
the relationship MacroReferencesTables.
233

meta_MacroTriggers
Table 109: Columns and Data Types of the meta_MacroTables View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
MacroLoid
INTEGER
TableLoid
INTEGER
meta_MacroTriggers
Returns the triggers referenced by the current macros in the repository systems. Corresponds
to the relationship MacroReferencesTriggers.
Table 110: Columns and Data Types of the meta_MacroTriggers View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
TriggerDatabaseName
VARCHAR(128)
TriggerName
VARCHAR(128)
MacroLoid
INTEGER
TriggerLoid
INTEGER
meta_MacroViewColumns
Returns the view columns referenced by the current macros in the repository systems.
Corresponds to the relationship MacroReferencesViewColumns.
Table 111: Columns and Data Types of the meta_MacroViewColumns View
234
Column
Data Type
SystemName
VARCHAR(256)

meta_MacroViews
Table 111: Columns and Data Types of the meta_MacroViewColumns View (continued)
Column
Data Type
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
ViewDatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ColumnName
VARCHAR(128)
MacroLoid
INTEGER
ColumnLoid
INTEGER
meta_MacroViews
Returns the views referenced by the current Macros in the repository systems. Corresponds to
the MacroReferencesViews relationship.
Table 112: Columns and Data Types of the meta_MacroViews View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
ViewDatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
MacroLoid
INTEGER
ViewLoid
INTEGER
meta_RefConstraintColumns
Returns the table columns comprising the current REFERENCE constraints in the repository
systems. Corresponds to the relationship ConstraintReferencesColumns.
Table 113: Columns and Data Types of the meta_RefConstraintColumns View
Column
Data Type
SystemName
VARCHAR(256)
235

meta_RefConstraints
Table 113: Columns and Data Types of the meta_RefConstraintColumns View (continued)
Column
Data Type
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ReferenceId
SMALLINT
ReferenceName
VARCHAR(128)
ForeignKeyColumnName
VARCHAR(128)
ReferencedDatabaseName
VARCHAR(128)
ReferencedTableName
VARCHAR(128)
ReferencedColumnName
VARCHAR(128)
meta_RefConstraints
Returns the current REFERENCE constraints for the tables in the repository systems.
Corresponds to the relationship TableHasRefConstraints.
Table 114: Columns and Data Types of the meta_RefConstraints View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ReferenceName
VARCHAR(128)
ReferenceLoid
INTEGER
ReferenceID
SMALLINT
ReferencedDatabase
VARCHAR(128)
ReferencedTable
VARCHAR(128)
meta_SPParameters
Returns the parameters defined for the current stored procedures in the repository systems.
Corresponds to the relationship SPHasParameters.
236

meta_SPParameters
Table 115: Columns, Data Types, and Values of the meta_SPParameters View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
ParameterName
VARCHAR(128)
ParameterPositionID
SMALLINT
ParameterType
VARCHAR(12)
ParameterDataType
CHAR(2)
ParameterDataTypeA
VARCHAR(29)
Values
Input
Output
Input/Output
ParameterLength
INTEGER
CharType
SMALLINT
1-dimensional Array
ANSI Time
BLOB
VARBYTE
CLOB
Decimal
Day
Day to Minute
Date Tag
Hour
Hour To Second
Byte Integer
BIGINT
Month
NUMBER
PERIOD(DATE)
PERIOD(TIMESTAMP)w/
TimeZone
ANSI Timestamp w/
TimeZone
User Defined Type
Year To Month
n-dimensional Array
Binary Fixed
Binary String
Character Fixed
VARCHAR
Date
Day To Hour
Day to Second
Real/Float
Hour To Minute
Integer
Short Integer
Minute
Minute To Second
PERIOD(TIME)
PERIOD(TIMESTAMP)
Second
Timestamp
Year
237

Table 115: Columns, Data Types, and Values of the meta_SPParameters View (continued)
Column
Data Type
Values
CharacterSet
VARCHAR(8)
Graphic
Latin
Unicode
ParameterComment
VARCHAR(255)
SPLoid
INTEGER
ParameterLoid
INTEGER
RowTypeDatabaseName
VARCHAR(128)
RowTypeTableName
VARCHAR(128)
Kanji1
ShiftJIS
Other
Returns the macros referenced by the current stored procedures in the repository systems.
Corresponds to the relationship SPReferencesMacros.
Table 116: Columns and Data Types of the meta_StoredProcedureMacros View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
MacroDatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
SPLoid
INTEGER
MacroLoid
INTEGER
meta_StoredProcedures
Returns the current stored procedures in the databases of the repository systems. Corresponds
to the relationship DatabaseHasStoredProcedures.
Table 117: Columns and Data Types of the meta_StoredProcedures View
238
Column
Data Type
SystemName
VARCHAR(256)

Table 117: Columns and Data Types of the meta_StoredProcedures View (continued)
Column
Data Type
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
SPLastAlterTS
TIMESTAMP
IsSynchronized
VARCHAR(6)
SPComment
VARCHAR(255)
SPText
VARCHAR(12500)
CreatorName
VARCHAR(128)
SPLoid
INTEGER
Returns the tables referenced by the current stored procedures in the repository systems.
Corresponds to the relationship SPReferencesTables.
Table 118: Columns and Data Types of the meta_StoredProcedureTables View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
SPLoid
INTEGER
TableLoid
INTEGER
meta_StoredProcedureViews
Returns the views referenced by the current stored procedures in the repository systems.
Corresponds to the relationship SPReferencesViews.
239

Table 119: Columns and Data Types of the meta_StoredProcedureViews View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
ViewDatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
SPLoid
INTEGER
ViewLoid
INTEGER
Returns the hash indexes referenced by the current stored procedures in the repository
systems. Corresponds to the relationship SPReferencesHashIndexes.
Table 120: Columns and Data Types of the meta_StoredProcHashIndexes View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
HashIndexDatabaseName
VARCHAR(128)
HashIndexName
VARCHAR(128)
StoredProcedureLoid
INTEGER
HashIndexLoid
INTEGER
meta_StoredProcJoinIndexes
Returns the join indexes referenced by the current stored procedures in the repository systems.
Corresponds to the relationship SPReferencesJoinIndexes.
Table 121: Columns and Data Types of the meta_StoredProcJoinIndexes View
240
Column
Data Type
SystemName
VARCHAR(256)

Table 121: Columns and Data Types of the meta_StoredProcJoinIndexes View (continued)
Column
Data Type
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
JoinIndexDatabaseName
VARCHAR(128)
JoinIndexName
VARCHAR(128)
StoredProcedureLoid
INTEGER
JoinIndexLoid
INTEGER
Returns the stored procedures referenced by the current stored procedures in the repository
systems. Corresponds to the relationship SPReferencesStoredProcedures.
Table 122: Columns and Data Types of the meta_StoredProcRefsSPs View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
RefdStoredProcedureDatabase
VARCHAR(128)
RefdStoredProcedureName
VARCHAR(128)
SPLoid
INTEGER
RefdSPLoid
INTEGER
meta_StoredProcTableColumns
Returns the table columns referenced by the current stored procedures in the repository
systems. Corresponds to the relationship SPReferencesTableColumns.
Table 123: Columns and Data Types of the meta_StoredProcTableColumns View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
241

Table 123: Columns and Data Types of the meta_StoredProcTableColumns View (continued)
Column
Data Type
StoredProcedureName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
StoredProcedureLoid
INTEGER
ColumnLoid
INTEGER
Returns the view columns referenced by the current stored procedures in the repository
systems. Corresponds to the relationship SPReferencesViewColumns.
Table 124: Columns and Data Types of the meta_StoredProcViewColumns View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
ViewDatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ColumnName
VARCHAR(128)
StoredProcedureLoid
INTEGER
ColumnLoid
INTEGER
meta_SubjectAreaEntities
Returns the Business Entities comprising each Subject Area in the repository. Corresponds to
relationship SubjectAreaEntities.
Table 125: Columns and Data Types of the meta_SubjectAreaEntities View
242
Column
Data Type
SubjectAreaName
VARCHAR(128)

meta_SubjectAreas
Table 125: Columns and Data Types of the meta_SubjectAreaEntities View (continued)
Column
Data Type
EntityName
VARCHAR(128)
EntityType
VARCHAR(6)
SubjectAreaLoid
INTEGER
EntityLoid
INTEGER
meta_SubjectAreas
Returns the current Subject Areas defined in the repository.
Table 126: Columns and Data Types of the meta_SubjectAreas View
Column
Data Type
SubjectAreaName
VARCHAR(128)
SubjectAreaID
INTEGER
BusinessDefinition
VARCHAR(2048)
Author
VARCHAR(255)
SubjectAreaLoid
INTEGER
meta_SystemMetaloadTypes
Returns the MetaloadTypes entries for the current systems in the repository. Corresponds to
SystemHasMetaloadTypes.
Table 127: Columns and Data Types of the meta_SystemMetaloadTypes View
Column
Data Type
SystemName
VARCHAR(256)
TypeName
VARCHAR(128)
SystemLoid
INTEGER
TypeLoid
INTEGER
243

meta_SystemNodes
meta_SystemNodes
Returns the name of the nodes comprising the systems in the repository. Corresponds to the
relationship SystemHasNodes.
Table 128: Columns and Data Types of the meta_SystemNodes View
Column
Data Type
SystemName
VARCHAR(256)
NodeName
VARCHAR(256)
SystemLoid
INTEGER
NodeLoid
INTEGER
meta_TableColumns
Returns the columns for the current tables of the systems in the repository. Corresponds to the
relationship TableHasColumns.
Table 129: Columns, Data Types, and Values of the meta_TableColumns View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
ColumnId
SMALLINT
ColumnLoid
INTEGER
ColumnType
CHAR(2)
244
Values

meta_TableColumns
Table 129: Columns, Data Types, and Values of the meta_TableColumns View (continued)
Column
Data Type
Values
ColumnTypeA
VARCHAR(29)
ColumnLength
INTEGER
CharType
SMALLINT
CharacterSet
VARCHAR(8)
DecimalTotalDigits
SMALLINT
DecimalFractDigits
SMALLINT
UppercaseFlag
VARCHAR(3)
Nullable
VARCHAR(3)
DefaultValue
VARCHAR(1024)
Compressible
VARCHAR(3)
CompressValue
VARCHAR(8192)
IDColType
VARCHAR(164)
1-dimensional Array
ANSI Time
BLOB
VARBYTE
CLOB
Decimal
Day
Day to Minute
Date Tag
Hour
Hour To Second
Byte Integer
BIGINT
Month
NUMBER
PERIOD(DATE)
PERIOD(TIMESTAMP)w/
TimeZone
ANSI Timestamp w/
TimeZone
Year
Graphic
Latin
Unicode
n-dimensional Array
Binary Fixed
Binary String
Character Fixed
VARCHAR
Date
Day To Hour
Day to Second
Real/Float
Hour To Minute
Integer
Short Integer
Minute
Minute To Second
PERIOD(TIME)
PERIOD(TIMESTAMP)
Second
Timestamp
User Defined Type
Unicode VARCHAR
Year To Month
Kanji1
ShiftJIS
Other
245

Table 129: Columns, Data Types, and Values of the meta_TableColumns View (continued)
Column
Data Type
ColumnTitle
VARCHAR(256)
CommentString
VARCHAR(255)
Values
Returns the tables in the repository systems for which triggers are defined. Corresponds to the
relationship TableHasTriggers.
Table 130: Columns and Data Types of the meta_TableHasTriggers View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
TriggerDatabaseName
VARCHAR(128)
TriggerName
VARCHAR(128)
TableLoid
INTEGER
TriggerLoid
INTEGER
meta_Tables
Returns the current tables by system and database in the repository. Corresponds to the
DatabaseHasTables relationship.
Table 131: Columns and Data Types of the meta_Tables View
246
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
TableLoid
INTEGER
TableVersion
SMALLINT
IsSynchronized
VARCHAR(6)

meta_TriggerMacros
Table 131: Columns and Data Types of the meta_Tables View (continued)
Column
Data Type
LastAlterTimestamp
TIMESTAMP
CreatorName
VARCHAR(128)
meta_TriggerMacros
Returns the macros referenced by the current triggers in the repository systems. Corresponds
to the relationship TriggerReferencesMacros.
Table 132: Columns and Data Types of the meta_TriggerMacros View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TriggerName
VARCHAR(128)
MacroDatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
TriggerLoid
INTEGER
MacroLoid
INTEGER
meta_Triggers
Returns the current triggers defined for the repository systems. Corresponds to the
relationship DatabaseHasTriggers.
Table 133: Columns, Data Types, and Values of the meta_Triggers View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TriggerName
VARCHAR(128)
IsSynchronized
VARCHAR(6)
TriggerComment
VARCHAR(255)
TriggerEnabled
VARCHAR(3)
Values
247

meta_TriggerTables
Table 133: Columns, Data Types, and Values of the meta_Triggers View (continued)
Column
Data Type
Values
TriggerKind
VARCHAR(14)
Each Row
Each Statement
TriggerEvent
VARCHAR(6)
Delete
Insert
Update
TriggerActionTime
VARCHAR(12)
Before Event
After Event
TriggerOrder
SMALLINT
TriggerCreateTime
TIMESTAMP
TriggerLastEnableDisableTS
TIMESTAMP
CreatorName
VARCHAR(128)
TriggerText
VARCHAR(12500)
TriggerLoid
INTEGER
meta_TriggerTables
Returns the tables referenced by the current triggers in the repository systems. Corresponds to
the relationship TriggerReferencesTables.
Table 134: Columns and Data Types of the meta_TriggerTables View
248
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TriggerName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
TriggerLoid
INTEGER
TableLoid
INTEGER

meta_TV
meta_TV
Returns the tables and views defined in the repository systems. The TVType field returns 'T'
for a table and 'V' for a view.
Table 135: Columns and Data Types of the meta_TV View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TVType
VARCHAR(2)
TableName
VARCHAR(128)
TableLoid
INTEGER
IsSynchronized
VARCHAR(6)
LastAlterTimestamp
TIMESTAMP
CreatorName
VARCHAR(128)
meta_TVColumns
Returns the columns for the tables and views defined in the repository systems. The TVType
fields returns 'T' for a table and 'V ' for a view.
Table 136: Columns and Data Types of the meta_TVColumns View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TVType
VARCHAR(2)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
ColumnID
SMALLINT
ColumnLoid
INTEGER
ColumnType
CHAR(2)
ColumnLength
INTEGER
CharType
SMALLINT
249

meta_TVM
Table 136: Columns and Data Types of the meta_TVColumns View (continued)
Column
Data Type
DecimalTotalDigits
SMALLINT
DecimalFractionalDigits
SMALLINT
UppercaseFlag
VARCHAR(3)
Nullable
VARCHAR(3)
DefaultValue
VARCHAR(1024)
Compressible
VARCHAR(3)
CompressValue
VARCHAR(8192)
IDColType
VARCHAR(164)
SPParameterType
VARCHAR(1)
ColumnTitle
VARCHAR(256)
CommentString
VARCHAR(255)
ColumnUDTName
VARCHAR(128)
meta_TVM
Returns the tables, views, triggers, macros, procedures, hash indexes, and join indexes defined
in the repository systems. The TVType field returns 'T' (table), 'V' (view), 'G' (trigger), 'P'
(procedure), 'HI' (hash index), and 'JI' (join index).
Table 137: Columns and Data Types of the meta_TVM View
250
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TVType
VARCHAR(2)
TVName
VARCHAR(128)
TVLoid
INTEGER
IsSynchronized
VARCHAR(6)
LastAlterTimestamp
TIMESTAMP
CreatorName
VARCHAR(128)

meta_ValidValues
meta_ValidValues
Returns the current ValidValue definitions in the repository.
Table 138: Columns and Data Types of the meta_ValidValues View
Column
Data Type
ValueName
VARCHAR(128)
ValueDefinition
VARCHAR(12500)
DisplayValue
VARCHAR(255)
ValueSequenceNumber
INTEGER
ValueLoid
INTEGER
meta_ViewColumnConstants
Returns the Constants referenced by the current view columns in the repository systems.
Corresponds to the relationship ViewColumnReferencesConstants.
Table 139: Columns, Data Types, and Values of the meta_ViewColumnConstants View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ViewColumnName
VARCHAR(128)
Values
251

Table 139: Columns, Data Types, and Values of the meta_ViewColumnConstants View (continued)
Column
Data Type
Values
ConstantType
VARCHAR(128)
ConstantValue
VARCHAR(1024)
ColumnLoid
INTEGER
ConstantLoid
INTEGER
ACCOUNT
ACTIVITY_COUNT
ALL
ANSIDATE
ASCII
AUTOTEMP
BIGINT
BINARY
CHAR_SET_GRAPHIC
CHARSET_COLL
CURRENT_ROLE
CURRENT_USER
CURRDATE
CURRTIME
CURRTIMESTAMP
DATABASE
DATE
DECIMAL
DEFAULT
DQUOTESTR
EBCDIC
FLOAT
HEXSTR
HIGH
HOST
INTEGER
INTEGERDATE
JIS_COLL
KANJI
KANJISJIS
LATIN1
LOCAL
LOW
MANUAL
MEDIUM
MULTINATIONAL
NAME
NEVER
OFF
NULL
PARMNAME
PREPARE_COUNT
PROFILE
ROLE
SESSION
SOURCE TIME ZONE
SQLCODE
SQLSTATE
SQUOTESTR
STAR
TEMPORAL_DATE
TEMPORAL_TIMESTAMP
TIME
UNICODE
UNKNOWN
USER
Returns the Functions referenced by the current view columns in the repository systems.
Corresponds to the relationship ViewColumnReferencesFunctions.
252

meta_ViewColumns
Table 140: Columns and Data Types of the meta_ViewColumnFunctions View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ViewColumnName
VARCHAR(128)
FunctionName
VARCHAR(128)
ColumnLoid
INTEGER
FunctionLoid
INTEGER
meta_ViewColumns
Returns the columns for the current views in the systems in the repository. Corresponds to the
relationship ViewHasColumns.
Table 141: Columns, Data Types, and Values of the meta_ViewColumns View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ColumnName
VARCHAR(128)
ColumnID
SMALLINT
ColumnLoid
INTEGER
ColumnType
CHAR(2)
Values
253

meta_ViewColumns
Table 141: Columns, Data Types, and Values of the meta_ViewColumns View (continued)
Column
Data Type
Values
ColumnTypeA
VARCHAR(29)
ColumnLength
INTEGER
CharType
SMALLINT
CharacterSet
VARCHAR(8)
DecimalTotalDigits
SMALLINT
DecimalFractDigits
SMALLINT
Nullable
VARCHAR(3)
ColumnTitle
VARCHAR(256)
CommentString
VARCHAR(255)
254
1-dimensional Array
ANSI Time
BLOB
VARBYTE
CLOB
Decimal
Day
Day to Minute
Date Tag
Hour
Hour To Second
Byte Integer
BIGINT
Month
NUMBER
PERIOD(DATE)
PERIOD(TIMESTAMP)w/
TimeZone
ANSI Timestamp w/
TimeZone
Year
Graphic
Latin
Unicode
n-dimensional Array
Binary Fixed
Binary String
Character Fixed
VARCHAR
Date
Day To Hour
Day to Second
Real/Float
Hour To Minute
Integer
Short Integer
Minute
Minute To Second
PERIOD(TIME)
PERIOD(TIMESTAMP)
Second
Timestamp
User Defined Type
Unicode VARCHAR
Year To Month
Kanji1
ShiftJIS
Other

Returns the table columns referenced by the current view columns in the repository systems.
Corresponds to the relationship ViewColReferencesTableCols.
Table 142: Columns and Data Types of the meta_ViewColumnTableColumns View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ViewColumnName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
ViewColumnLoid
INTEGER
ColumnLoid
INTEGER
meta_ViewReferencesViews
Returns the views referenced by a view. Corresponds to the relationship ViewReferencesViews.
Table 143: Columns and Data Types of the meta_ViewReferencesViews View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
RefdViewDatabaseName
VARCHAR(128)
RefdViewName
VARCHAR(128)
ViewLoid
INTEGER
RefViewLoid
INTEGER
255

meta_Views
meta_Views
Returns the current views by database in the systems in the repository. Corresponds to the
relationship DatabaseHasViews.
Table 144: Columns and Data Types of the meta_Views View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ViewLoid
INTEGER
IsSynchronized
VARCHAR(6)
LastAlterTimestamp
TIMESTAMP
CreatorName
VARCHAR(128)
meta_ViewTableColumns
Returns the table columns referenced by the current views in the repository systems.
Corresponds to the relationship ViewHasTableColumns.
Table 145: Columns and Data Types of the meta_ViewTableColumns View
256
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
ColumnLoid
INTEGER
ViewLoid
INTEGER

meta_ErrorTables
meta_ErrorTables
Returns the tables using error tables.
Table 146: Columns and Data Types of the meta_ErrorTables View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ErrrorTableDatabaseName
VARCHAR(128)
ErrrorTableName
VARCHAR(128)
TableLoid
INTEGER
ErrorTableLoid
INTEGER
meta_ColumnUDTs
Returns the UDT referenced by a table column.
Table 147: Columns and Data Types of the meta_ColumnUDTs View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ColumnName
VARCHAR(128)
UDTName
VARCHAR(128)
ColumnLoid
INTEGER
UDTLoid
INTEGER
meta_MacroFunctions
Returns the functions referenced by a macro.
257

Table 148: Columns and Data Types of the meta_MacroFunctions View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
FunctionDatabaseName
VARCHAR(128)
FunctionName
VARCHAR(128)
MacroLoid
INTEGER
FunctionLoid
INTEGER
Returns the UDT referenced by a MacroParameter.
Table 149: Columns and Data Types of the meta_MacroParameterUDTs View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
MacroName
VARCHAR(128)
ParameterName
VARCHAR(128)
UDTName
VARCHAR(128)
ParameterPosition
Short
ParameterLoid
INTEGER
UDTLoid
INTEGER
meta_SPParameterUDTs
Returns the UDT referenced by an SPParameter.
Table 150: Columns and Data Types of the meta_SPParameterUDTs View
258
Column
Data Type
SystemName
VARCHAR(256)

Table 150: Columns and Data Types of the meta_SPParameterUDTs View (continued)
Column
Data Type
DatabaseName
VARCHAR(128)
StoredProcedureName
VARCHAR(128)
ParameterName
VARCHAR(128)
UDTName
VARCHAR(128)
ParameterPosition
Short
ParameterLoid
INTEGER
UDTLoid
INTEGER
Returns the functions referenced by a trigger.
Table 151: Columns and Data Types of the meta_TriggerFunctions View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
TriggerName
VARCHAR(128)
VARCHAR(128)
FunctionName
VARCHAR(128)
TriggerLoid
INTEGER
FunctionLoid
INTEGER
meta_TriggerUDTs
Returns the UDTs referenced by a trigger.
Table 152: Columns and Data Types of the meta_TriggerUDTs View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
259

meta_UDFFunctions
Table 152: Columns and Data Types of the meta_TriggerUDTs View (continued)
Column
Data Type
TriggerName
VARCHAR(128)
UDTDatabaseName
VARCHAR(128)
UDTName
VARCHAR(128)
TriggerLoid
INTEGER
UDTLoid
INTEGER
meta_UDFFunctions
Returns the functions referenced by functions (UDFs) in the repository systems. Corresponds
to the relationship FunctionReferencesFunctions.
Table 153: Columns and Data Types of the meta_UDFFunctions View
Column
Data Type
SystemName
VARCHAR(128)
DatabaseName
VARCHAR(128)
UDFName
VARCHAR(128)
VARCHAR(128)
FunctionName
VARCHAR(128)
UDFLoid
INTEGER
FunctionLoid
INTEGER
meta_UDFs
Returns the current user-defined functions.
Table 154: Columns and Data Types of the meta_UDFs View
260
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
UDFName
VARCHAR(128)
IsSynchronized
VARCHAR(6)

meta_UDTAttributes
Table 154: Columns and Data Types of the meta_UDFs View (continued)
Column
Data Type
LastAlterTimestamp
Timestamp
CreatorName
VARCHAR(128)
UDFLoid
INTEGER
meta_UDTAttributes
Returns the UDTAttributes comprising a UDT.
Table 155: Columns and Data Types of the meta_UDTAttributes View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
UDTName
VARCHAR(128)
AttributeName
VARCHAR(128)
DataType
CHAR(2)
DataTypeA
VARCHAR(29)
CharacterSet
VARCHAR(8)
AttributeLoid
INTEGER
meta_UDTAttributeUDTs
Returns the UDTs associated with UDTattributes.
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
UDTName
VARCHAR(128)
AttributeName
VARCHAR(128)
RefdUDTName
VARCHAR(128)
261

meta_UDTFunctions
Table 156: Columns and Data Types of the meta_ViewTableColumns View (continued)
Column
Data Type
AttributeLoid
INTEGER
RefdUDTLoid
INTEGER
meta_UDTFunctions
Returns the functions defined for a UDT.
Table 157: Columns and Data Types of the meta_UDTFunctions View
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
UDTName
VARCHAR(128)
FunctionName
VARCHAR(128)
UDTLoid
INTEGER
FunctionLoid
INTEGER
meta_UDTs
Returns the UDTs for a database system.
Table 158: Columns and Data Types of the meta_UDTs View
262
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
UDTName
VARCHAR(128)
UDTLoid
Integer
LastAlterTimestamp
Timestamp
CreatorName
VARCHAR(128)
IsSynchronized
VARCHAR(6)

meta_ViewColumnUDTs
meta_ViewColumnUDTs
Returns the UDT comprising a ViewColumn.
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
ViewColumnName
VARCHAR(128)
UDTName
VARCHAR(128)
ColumnLoid
INTEGER
UDTLoid
INTEGER
meta_ViewFunctions
Returns the functions referenced by views in the repository systems. Corresponds to the
relationship ViewReferencesFunction.
Table 160: Columns and Data Types of the meta_ViewFunctions View
Column
Data Type
SystemName
VARCHAR(128)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
VARCHAR(128)
FunctionName
VARCHAR(128)
ViewLoid
INTEGER
FunctionLoid
INTEGER
meta_ViewTables
Returns the tables referenced by the current views in the repository systems. The relationship
is ViewReferencesTables.
263

meta_ViewTables
Table 161: Columns and Data Types of the meta_ViewTables View
264
Column
Data Type
SystemName
VARCHAR(256)
DatabaseName
VARCHAR(128)
ViewName
VARCHAR(128)
TableDatabaseName
VARCHAR(128)
TableName
VARCHAR(128)
ViewLoid
INTEGER
TableLoid
INTEGER
APPENDIX D
XML Bridge
This appendix describes XML Bridge, a tool that supports the exchange of information
between MDS repository and select business-intelligence (BI), analytic, and modeling tools.
This appendix is intended for the following audience:
Teradata MDS end users
Teradata MDS administrators
Teradata Database administrators
It is divided into the following sections:
XML Bridge Overview on page 265 describes why a customer would need XML Bridge
and a brief introduction to how it works.
Supported tools on page 266 lists tools that have been verified to work with XML Bridge.
Requirements on page 266 lists XML Bridge requirements.
How to Use XML Bridge on page 267 provides procedures on how to exchange tool
metadata with MDS Repository.
OMG CWM to MDS CWM_Metamodel mapping on page 270 describes the MDS
CWM_Metamodel that represents OMG CWM in MDS Repository. Contains the current
diagram of the CWM_Metamodel and describes how CWM class packages map to its
classes.
Technical Details on page 278 provides information for developers and professional
services that may need specific, detailed information on the bridge mechanism. Has
sections on the export of metadata from MDS Repository into the tool and how to extend
the bridge to work with user-defined translation files and metamodels.
Current limitations on page 277 lists current limitations of the implementation.
FAQ on page 280 contains questions and answers concerning bridge details.
For more information on the MDS MetaXML utility, see Chapter 6 MDS Utility Programs
on page 143 of this guide, and MetaXML Scripting Interface of the Teradata Meta Data
Services Programmer Guide.
XML Bridge Overview

Customers often find it useful to move information (metadata) from an application/tool into
a metadata repository for additional analysis of the metadata, often in concert with other
metadata in the repository. Such an exchange of data is not usually possible since neither the
265
Appendix D: XML Bridge

Supported tools
tool nor repository exports (or imports) metadata in a way that can be understood by the
other. However, procedures and/or software may be developed to bridge the data path
between the tool and repository, allowing the data exchange.
To achieve this goal, XML Bridge combines the use of MDS software and Common
Warehouse Metamodel/XML Metadata Interchange eXtensible Markup Language (CWM/
XMI XML) from the Object Management Group (OMG). If a tool or application can export
its metadata in CWM/XMI XML format, then XML Bridge can transform it into MetaXML
schema format, so the MetaXML utility can import it into MDS Repository.
The translation from the XMI schema to the MDS XML schema is accomplished by an
eXtensible Stylesheet Language Transformation (XSLT) file provided by MDS. MDS also
provides a repository metamodel to represent the OMG CWM. For more information, see
FAQ on page 280 and Technical Details on page 278.
Supported tools
Table 162 summarizes the tools supporting CWM/XMI XML format that are
compatible with XML Bridge.

Table 162: Tools supported by XML Bridge
Vendor
Product
Version
Interface
Business Objects
Data Integrator
11.5.2
ETL (Source and Target Data Stores)

via CWM XMI File.
Cognos
Framework Manager
8.2
BI Design (RDBMS Source, OLAP

Source, Dimensional Target,
Expression Conversion) via CWM
XMI File.
CA
AllFusion ERwin Data

Modeler r7
7.2
Data Store (Physical and Logical Data

Model) via CWM XMI File.
SAS
SAS Data Integration

Studio
9.1.3
ETL (Source and Target Data Stores)

via CWM XMI File.
Informatica
PowerCenter Repository
Manager
8.6
ETL (source and Target Data stores)

via CWM XMI file.
Requirements
The only requirement to import tool metadata is the same as that required by the MetaXML
utility, namely the MSXML 4.0 parser or MSXML 6.0 parser. In addition, the MetaXML
export functionality requires a Java JRE. See the MetaXML section of the MDS Release
Notes for more information.
266

How to Use XML Bridge

The import of XML CWM or CWM/XMI formatted metadata via XML Bridge is a simple
process that can be done using either MetaBrowse or MetaManager. The work done by XML
Bridge is transparent to the user.
To import CWM or CWM/XMI formatted metadata via XML Bridge

1
Select a supported tool from which you want to import metadata into an MDS repository.
See Supported tools on page 266.
From the selected tool, open a file you want to import into MDS, and then execute the
appropriate menu-items to export the file into XML CWM or CWM/XMI format.
Using MetaBrowse or MetaManager, choose Tools>Import>XML to start the process of

importing the XML file into the MDS Repository. The following figure illustrates this step
using MetaBrowse.
MetaBrowse calls XML Import, and a standard Windows Locate the File to Import dialog
box appears.
4
Navigate through the directories to the file you want to import. Select the file, and then
click Open.
If the CWM_Metamodel has already been created, go to step 8.
If the CWM_Metamodel has not yet been created in the MDS repository, XML Import
prompts you to create it.
267

Click Yes to continue.

A console window opens and a series of processing messages appear while the MetaXML
utility creates the CWM_metamodel, which will hold CWM metadata. When processing is
finished, you are prompted to press Enter.
After complying, the console window closes and the MDS tool reappears, ready to import
the metadata from the transformed XML file.
From either MetaBrowse or MetaManager, again choose Tools>Import>XML.

A Locate the File to Import dialog box reappears.
Re-select the CWM XML file and click Open.
XML import software opens the file and determines that the CWM/XMI XML needs
processing by XML Bridge. As part of its routine, XML Bridge creates a transformed XML
file in MetaXML schema format, assigning it the same name as the file selected for import,
prepended by t_. For example, if you choose to import a file named sas.xml, XML Bridge
creates a file named t_sas.xml.
You are then prompted to import the transformed XML file.
Click Yes to continue.

When MetaXML is finished importing the file, youre prompted to press Enter. After
complying, the console window closes.
9
Choose View>Refresh Application Metamodels.

The tool refreshes, displaying the newly created metamodel and metadata of the imported
XML file, similar to that shown in the following figure.
268

MDS also provides functionality to export metadata from the MDS repository and back
into a supported tool. There is no GUI interface for such exports, however. For more
information, see Technical Details on page 278 and FAQ on page 280.
269

OMG CWM to MDS CWM_Metamodel mapping

The layout of the MDS CWM_Metamodel is shown in Figure 8.
Figure 8: MDS CWM_Metamodel layout
CWMRDB_SQLSimpleType
CWMRDB_Catalog
CWMRDB_Catalog
CWMTFM_TransformationTask
CWMTFM_TransformationTask
CWM_Model
CWM_Model
CWMRDB_SQLDistinctType
CWMRDB_Schema
CWMRDB_View
CWMRDB_Table
CWM_Description
CWMRDB_Column
CWMRDB_UniqueConstraint
CWMRDB_PrimaryKey
CWMOLAP_Schema
CWMOLAP_Cube
CWMOLAP_Measure
CWMOLAP_CubeRegion
CWMOLAP_CubeDimensionAssociation
CWM_DataType
CWM_Package
CWMTFM_Transformation
CWMTFM_DataObjectSet
CWM_Association
CWM_AssociationEnd
CWM_Multiplicity
CWMOLAP_Dimension
CWM_Class
CWMOLAP_Level
CWM_Attribute
CWM_StructuralFeature
CWMOLAP_Hierarchy
CWM_TaggedValue
CWM_KeyRelationship
CWMOLAP_HierarchyLevelAssociation
CWMRDB_ForeignKey
CWMTFM_TransformationMap
CWMRDB_SQLIndex
CWMTFM_ClassifierMap
CWMRDB_SQLIndexColumn
CWMTFM_FeatureMap
CWMRDB_Trigger
CWMTFM_ClassifierMapSource
CWMRDB_Procedure
CWMTFM_ClassifierMapTarget
CWMRDB_SQLParameter
3118A002
The MDS CWM_Metamodel holds CWM/XMI metadata imported by XML Bridge. The
metamodel classes are mostly a subset of the Core, Relational, Keys and Indexes, OLAP, and
Transformation packages found in OMG CWM.
Abstract classes Core_ModelElement and Ref_Core_ModelElement are used by the
CWM_Metamodel to hold properties common to their subclasses. The remaining classes in
the CWM_Metamodel have names resembling their CWM/XMI names that map back to the
OMG CWM class-package names.
The following table shows the mapping of the CWM Package classes to the MDS
CWM_Metamodel classes. Some of the more prominent attributes for the classes are listed.
For a complete list of all MDS CWM_Metamodel classes and their properties, including
descriptions, see the metamodel as defined in the XML file, or as viewed in MetaBrowse.
270

CWM_Metamodel Relationships (not shown here) are the natural result of the containment
associations found in the CWM.
Table 163: Mapping OMG CWM to MDS CWM_Metamodel
CWM Package:Class
MDS CWM_Metamodel Class
CWMRDB:Catalog
CWMRDB_Catalog
XMI.exporter
XMI.exporterVersion
Contains elements comprising relational and
OLAP models.
exporter
exporterVersion
xmlFileName
exporter and exporterVersion show information
related to source XML.
Note: This class typically holds the root object of

the metadata of the tool. See also CWM:Model
on page 276 and CWM:Package on page 276.
xmlFileName holds the name of the file used to

import the object and its descendents.
CWMRDB:Schema
CWMRDB_Schema
Contains elements comprising a relational

model.
catalogName
catalogName is a derived property value for
storing the name of the catalog owning the
schema.
CWMRDB:SQLSimpleType
CWMRDB_SQLSimpleType
characterMaximumLength
typeNumber
Data type used with a SQL column. Examples are
Integer, Varchar, LOB, CLOB, etc.
charLength
typeNumber
charLength shows the maximum length of
character data type associated with table
columns, view columns, SQL parameters, etc.
Data types in a catalog are assigned unique
typeNumber values. This is how Column,
SQLParameter, and Measure reference their
associated data types.
CWMRDB:Table
CWMRDB_Table
A materialized Column set.
RDBSchemaName
RDBSchemaName is a derived property value to
store the name of the schema owning this table.
271

Table 163: Mapping OMG CWM to MDS CWM_Metamodel (continued)
CWM Package:Class
CWMRDB:Column
CWMRDB_Column
owner
type
Column in a result set, a view, or a table.
ownerName
SQLSimpleTypeName
SQLSimpleTypeID
ownerType
SQLDistinctTypeID
SQLSimpleTypeName
SQLDistinctTypeID
ownerName will show the name of associated
element owning this column. (For example: table,
view, etc.)
SQLSimpleTypeName/SQLDistinctTypeName will
show the Column data type.
ownerType: either table or view. This is in place to
aid in searches, as it is derived from existing
information.
CWMRDB:View
CWMRDB_View
CWM:Expression.body
A view is a virtual table that doesn't store
information itself, but pulls it out of one or more
existing tables.
queryExpression
queryExpressionID
queryExpression shows the DML/DDL for the
View object.
CWMRDB:Procedure
CWMRDB_Procedure
Relational DBMS Stored procedures and

functions.
procedureExpression
Stores the expression body of a procedure.
CWMRDB:SQLParameter
CWMRDB_SQLParameter
Relational DBMS stored procedures and

functions.
procedureName
SQLSimpleTypeName
SQLSimpleTypeID
SQLDistinctTypeName
SQLDistinctTypeID
kind
SQLSimpleTypeName/SQLDistinctTypeName
show the Parameter data type name.
behavioralFeature
type
Parameters of stored procedures.
Kind specifies the type of SQLParameter. Valid

values are in, out, inout and return.
272

CWM Package:Class
CWMRDB:SQLIndex
CWMRDB_SQLIndex
spannedClass
isUnique
An index on a table.
refTableName
refTableID
uniqueFlag
refTableName shows the name of the table
referenced by the index.
CWMRDB: SQLIndexColumn
CWMRDB_SQLIndexColumn
feature
index
Columns that constitute the index.
refColumnName
refColumnID
SQLIndexName
SQLIndexID
refColumnName shows the name of the column
referenced by the indexColumn.
CWMRDB:PrimaryKey
CWMRDB_PrimaryKey
feature
keyRelationship
Stores the uniqueness information of the table.
columnName
keyRelationshipName
columnName shows the name of the column that
constitutes this key. If more than one, they are
stored in the PrimaryKeyHasStructuralFeatures
collection.
keyRelationshipName shows the name of the
constraint referring to the primary key. If more
than one, they are stored in the
PrimaryKeyHasKeyRelationships collection.
CWMRDB:ForeignKey
CWMRDB_ForeignKey
uniqueKey
feature
Stores the association of a table with columns of
another table.
parentColumnName
parentTableName
refPrimaryKeyName
childColumnName
parentColumnName shows the name of the
referenced column.
parentTableName shows the name of the parent
(referenced) Table.
refPrimaryKeyName shows the name of the
primary key referenced by the foreign key.
CWMRDB:UniqueConstraint
CWMRDB_UniqueConstraint
Stores conditions that define the uniqueness of

rows in a table.
CWMRDB:Trigger
CWMRDB_Trigger
Stores an event-based action defined for the table.
273

CWM Package:Class
CWMRDB:SQLDistinctType
CWMRDB_SQLDistinctType
Distinct datatype used with an SQL column.
SQLSimpleTypeName
typeNumber
SQLSimpleType holds the name of the simple
data type referenced by the distinct data type.
Data types in a catalog are assigned a unique
typeNumber value so that column,
SQLParameter, and Measure can reference their
associated data types.
CWMOLAP:Schema
CWMOLAP_Schema
Contains all elements comprising an OLAP

model.
CWMOLAP:Dimension
CWMOLAP_Dimension
An ordinate within a multidimensional structure,

which shares a common semantic meaning
within the domain being modeled.
Typical Dimensions are: Time, Product,
Geography, Scenario, etc.
CWMOLAP:HierarchyLevelAssociation
CWMOLAP_HierarchyLevelAssociation
currentLevel
Stores mapping of level/hierarchy-oriented
dimension attributes to one or more physical
deployments.
levelName
CWMOLAP:Level
CWMOLAP_Level
dimension
Stores assignment information for each member
of a dimension to a specific hierarchical level
within the dimension.
dimensionID
CWMOLAP:LevelBasedHierarchy
CWMOLAP_Hierarchy
Organizational structure that imposes a parent/

child ordering on the members of a dimension
and describes relationships between specific
levels of a dimension.
CWMOLAP:Cube
CWMOLAP_Cube
A collection of analytic values sharing the same

dimensionality.
CWMOLAP: CubeDimensionAssociation
CWMOLAP_CubeDimensionAssociation
Relates a cube to the dimensions that define it.
274

CWM Package:Class
CWMOLAP:CubeRegion
CWMOLAP_CubeRegion
Models a sub-unit of a cube of the same

dimensionality as the cube, with each dimension
optionally sub-set in its list of members. A cube
may or may not have CubeRegions.
cube
Identifies associated cube xmi.id value
CWMOLAP:Measure
CWMOLAP_Measure
Subclass of the CWM Attribute class,

representing dimension measures such as sales,
quantity, or weight.
owner
SQLDistinctTypeName
SQLSimpleTypeName
owner shows the xmi.id of the Cube class that
owns the measure.
SQLSimpleTypeName and
SQLDistinctTypeName hold the data type for the
measure.
CWMTFM:TransformationMap
CWMTFM_TransformationMap
Represents a specialized transformation

consisting of a group of ClassifierMaps, that map
from a set of sources to a set of targets.
CWMTFM:ClassifierMap
CWMTFM_ClassifierMap
transformationMap
Represents a mapping of source classifiers to
target classifiers. A ClassifierMap may consist of a
group of FeatureMaps.
transformationMapID
CWMTFM:FeatureMap
CWMTFM_FeatureMap
classifierMap
source (CWM:Feature)
target (CWM:Feature)
Represents a mapping of source features to target
features.
classifierMapID
sourceName
targetName
CWMTFM_ClassifierMapSource
source (CWM:Classifier)
Source classifiers of ClassifierMap.
xmi.idref
xmi.idref refers to the source of ClassifierMap.
CWMTFM_ClassifierMapTarget
target (CWM:Classifier)
Target classifiers of ClassifierMap.
xmi.idref
xmi.idref refers to the target of ClassifierMap.
UML:TaggedValue
CWM_TaggedValue
modelElement
Allows information to be attached to any model
element in the form of a tagged value pair (i.e.,
name = value).
modelElementName
modelElementID
275

CWM Package:Class
CWM:Model
CWM_Model
exporter
A view of the physical system (e.g. an analysis
model, design model, or implementation model). exporterVersion
Note: When a tool exports its model metadata
xmlFileName
only, its root element is likely to end up in this
exporter and exporterVersion show information
class.
related to source XML.
xmlFileName holds the name of the file used to
import the object and its descendents).
CWM:Package
CWM_Package
A grouping of model elements such as objects

from the Package and Classifier classes.
namespace
namespace holds the owner xmi.id of the
package.
Note: If the export is an OLAP model, the root

object may be in this class. MDS, however, will
translate this object into the CWMRDB_Catalog
class, and form all relationships from that class
object. (That is, it retains its root-object status
but in the Catalog repository class.)
CWM:Class
CWM_Class
Namespace for contained elements.
CWM:Association
CWM_Association
Declaration of a semantic relationship between

objects in the Classifier class.
CWM:AssociationEnd
CWM_AssociationEnd
Specifies the connection of an association to

another classifier.
className
associationName
Holds the values of class and association names.
CWM:Multiplicity
CWM_Multiplicity
Defines a non-empty set of non-negative

integers.
CWM:DataType
CWM_DataType
packageName
namespace
packageName
multiplicityRangeID
lower
upper
Instances of primitive values of data types, such

as integers and strings.
276
CWM:StructuralFeature
CWM_StructuralFeature
xmi.idref
Instances of the StructuralFeature class map
PrimaryKey instances to the Class(es) that
constitute the key.
xmi.idref
xmi.idref stores the xmi.id of the referenced
column.

Current limitations
CWM Package:Class
CWM:KeyRelationship
CWM_KeyRelationship
xmi.idref
Stores the identity of other related instances. Acts
similarly to the relational model concept of
foreign key and the object model concept of a
reference.
xmi.idref
xmi.idref stores the xmi.id of the key constraint
referring to the primary key.
CWM:Description
CWM_Description
modelElement
Stores business or technical descriptions of the
Tables and Columns classes.
modelElementName
modelElementID
modelElementName stores the name of the
object for which the description is defined.
CWM:Attribute
CWM_Attribute
type
owner
A named slot within a classifier feature that may
hold a value.
type
ownerName
ownerScope
type identifies the associated DataType xmi.id for
an object from the Attribute class.
ownerScope specifies whether the feature appears
in every instance of the classifier or only once for
the entire classifier.
Current limitations
The following subsections describe the current XML Bridge limitations.
Updates not supported

The metadata from the transformed file run by MetaXML is added to the repository, i.e. the
action attribute of the MetaXML XML is set to add. This means that if the user exports the
*same* metadata from the tool a second time, the MDS repository metadata objects should be
removed before the new (updated) XML is imported into the MDS repository. Deleting the
top-most object is the easiest way to accomplish this (this object is in either the
CWMRDB_Catalog or CWM_Model class).
The issue here is that objects from the tool must somehow be linked to MDS repository
objects. The ability to accomplish this will depend on the specific capabilities provided by each
tool and at this time, no tool provides the needed information to accomplish this.
Not linking to DIM objects

The imported XML currently is not linked to objects in the MDS DIM, as this would require a
significant amount of user input. (This is a candidate for a future enhancement.)
277

Technical Details
Technical Details
The information in this section is provided for those who wish to better understand the
mechanisms which MDS uses to perform the bridge operations, and for developers or
professional services who may wish to extend the bridge for their own specific use. This
information is not necessary to understand if one simply wishes to use the bridge.
The ability to exchange metadata with a tool is provided by either using the MDS GUI
interface or, in a batch environment, by using a VBScript file. Each method uses the MDS
XSLT file developed for the tools XML. The XSLT file transforms the tools CWM/XMI into
MetaXML schema-formatted XML.
If MDS has not certified a tools exported XML, that XML will not be able to be imported into
the MDS repository. See the Supported Tools section for the current list of tools that have
been certified. However, it is possible for the user to develop and include his own bridge,
which can be used in the same way by the GUI to transform and import XML into the
repository as described below. See the User Bridge Development section below.
Importing XML via the GUIs

To use one of the MDS GUIs to import XML, the user needs to start MetaBrowse or
MetaManager, and from the Tools -> Import -> XML... menu item select an XML file from
the file-open dialog. Prior to the 12.0 release, this action would send the XML file directly to
the MetaXML utility, which requires XML in MetaXML schema format. Now, the
implementation will first check the name of the root node in the XML. If the root node is
METAXML, the XML in this file is supposed to already be in MetaXML schema format, and
so it is sent to MetaXML as usual.
However, if the root node is not METAXML, the implementation will look to see if there is
an XSLT file available to translate the source XML into MetaXML XML. It does this by
checking the metatools_cfg.xml file in the %METAHOME% tools directory. This file contains
a <Bridge> element, as a child of the <Import><XML> elements, for each bridge supported.
Currently there is just the one for CWM/XMI Bridge.
Each <Bridge> element has a rootnode attribute. This attribute contains the name of the
XML root node for the source XML file, i.e. the one to be transformed. For the CWM/XMI
Bridge it is XMI. So, the implementation reads the metatools_cfg.xml file, looking for a
<Bridge> rootnode attribute which matches the root node of the XML it is trying to import.
If it finds a match, it will then get the rest of the information for this bridge from the child
<Bridge>elements: namely, the XSLT file name, found in the <XSLTFile> child element; the
metamodel name, found in the <AIMName> child element; and the XML file for the
metamodel, found in the < AIMXMLFile> child element.
If it does not find a root node to match the source XML, it will display an error message saying
that the XML is not in MetaXML scheme format, and that there is no translation file available.
But if a match of the root node is made, the implementation will next look for the presence of
the necessary metamodel in the MDS repository. For CWM/XMI XML, this is the
CWM_Metamodel. If it is not already in the repository, the implementation will display a
278

Technical Details
message saying so, and asking the user for permission to create it. If the user OKs this, it will
import the XML of the <AIMXMLFile>. For the CWM/XMI XML, this is
CWM_Metamodel.xml. It expects this file to also be in the tools directory.
If the metamodel is present, the implementation will apply the XSLT identified in the
<XSLTFile> element to the source XML. For the CWM/XLI XML, this is the
CWM_MetaXML.xslt file, which it again expects to find in the tools directory.
If the XSLT has been properly worked out, the result will be the original XML transformed
into MetaXML schema XML. The implementation will then save this in a file in the same
directory as the source XML, with a t_ prepended to its name.
Finally, the implementation will launch the MetaXML utility to import the transformed XML
into the MDS repository.
Batch XML transformation via the VBScript file
A batch process can be used for importing a tools XML instead of the GUI method. After the
CWM/XMI XML has been exported from a tool, there is a simple two-step process that can be
used to transform and import it into the MDS repository. It involves using an MDS provided
VBScript file to transform a tools XML, and the MetaXML utility to do the import.
This VBScript file is called bridge.vbs and is located in the MDS installation directory in the
tools folder. This script needs the name of the source XML file (exported from the tool) and
the name of the XSLT file to do the transformation. To transform a CWM/XMI XML, use the
CWM_MetaXML.xslt file also found in the tools folder.
If successful, it will produce a transformed XML file with the same name as the source file but
with a t_ prepended to it. This XML is now in MetaXML schema format, and it so is ready
to be imported by the MetaXML utility into the MDS repository.
Note: The CWM_Metamodel must already be installed in the repository as this batch
procedure will assume it is there.

See the Purpose section in the bridge.vbs file for more details it can be viewed in any text
editor.
Exporting from the MDS repository into the tool

The user may modify imported metadata, and then export it out of the MDS repository
using the MetaXML utilitys export functionality. MDS provides another XSLT file to then
transform this XML back into CWM/XMI schema (it is the MetaXML_CWM.xslt file in the
tools directory). The user would apply this XSLT to the exported XML to get CWM/XMI
XML, which could then be imported back into the tool. Note that since the top-most object is
placed in the CWMRDB_Catalog or CWM_Model class of the CWM_Metamodel, the user
should identify this object as the one for the export out of the MDS repository.
Currently MDS does not provide a GUI interface for this procedure, so you must use the steps
above to accomplish this task. (This is a candidate for a future enhancement.)
See the Teradata Meta Data Services Programmer Guide (the MetaXML Scripting Interface
chapter) for more information about exporting objects out of the repository using MetaXML.
279

FAQ
User Bridge Development

If the user (or professional services) desires, a customer-specific bridge can be developed and
used the same as is describe in the Importing via the GUIs section above.
To accomplish this, the user will need to develop an XSLT file to translate their XML into
MetaXML schema, the same as the CWM_MetaXML.xslt does. Also, an MDS metamodel
must be identified as the target of the import. This metamodel may be one already pre-defined
by MDS (e.g. the DatabaseModel or the ClientLoadModel). However, if the XML will be
bridged into a metamodel not already pre-defined by MDS, this metamodel will need to be
developed by the user, and made available in XML format. (One easy way to do this is to create
the metamodel via MetaBrowse, and then use MetaXML to export it out of the repository.)
The XSLT file and the metamodel XML file (if necessary), must be placed in the MDS
installation tools folder the with the other bridge files.
Finally, the user must modify the metatools_cfg.xml and add a <Bridge> element as a child of
the <Import><XML> element, the same as the CWM/XMI <Bridge> element. The proper
values for the rootnode attribute and all the <Bridge> child elements must be included also.
(Note that even if the metamodel is already installed in the repository, so an XML file is not
needed for it, you must still include an empty AIMXMLFile element or the parse of the
metatools_cfg.xml file will fail.)
Once this is completed, the user will be able to point their MDS GUI XMLImport
request at their XML file, and have it translated and imported, just the same as for a CWM/
XML XML file.
FAQ
Q: Why use OMG CWM and XMI XML?
A: OMG CWM/XMI XML was chosen for MDS as it is a standards-based effort whose stated
purpose is to enable easy interchange of metadata between data warehousing tools and
metadata repositories in distributed heterogeneous environments. All serious tools should
provide an XML export using CWM/XMI even if they continue to use proprietary export
formats.
Q: Where do imported objects go?
A: All objects go into classes of the MDS CWM_Metamodel. The one-and-only root or toplevel object is imported into either the CWMRDB_Catalog class or CWM_Model class. All
other objects in the import can be found as destination objects of the root object.
Q: The MDS MetaXML utility only recognizes XML in its native schema format, so how is it
importing CWM/XMI XML?
A: MetaXML is not directly importing CWM/XMI XML. A transformation file is applied first,
creating a new XML file (designated as the t_ file in the confirm-import message). The
transformed file is in MetaXML schema format and is handed over to MetaXML to import.
For more information, see Technical Details on page 278.
280

FAQ
Q: The import does not identify which tool the metadata comes from. What if I want to
include this information for the MDS import?
A: Consider adding user-defined properties to the CWMRDB_Catalog class using
MetaBrowse or MetaXML. After the import, you can use MetaBrowse to update the
appropriate CWMRDB_Catalog object and add values to its user-defined properties.
To track a set of imported objects, consider using an MDS label. After the import, use
MetaBrowse to choose the appropriate CWMRDB_Catalog object from the import and apply
an MDS label with propagation. The label is then applied to all imported objects.
Note: When you add user-defined properties to a CWM_Metamodel class, use MetaXML to
export the metamodel to a file, thereby saving your changes for future reference.
Q: Can I export tool objects from MDS repository into my tool (referred to as a roundtrip)?
A: Yes, provided your tool can import CWM/XMI XML. All tools listed in Table 162 on
page 266provide import functionality. However, there is no GUI interface for the MDS part of
this task. See Technical Details on page 278 for information on performing an MDS export
and the steps for generating CWM/XMI XML for the tools.
Q: Can I modify imported metadata?
A: Yes. Imported objects are like other metadata objects in the MDS repository. Updates are
permitted as long as you have the proper privileges.
Q: If I change imported metadata, are the changes reflected when I round-trip back to my
tool?
A: That depends. All MDS objects have several common properties that are not part of the
CWM, for example the Description property. If you add descriptions to imported MDS
objects and then export them, your Description text appears in the exported XML. However,
the XSLT that converts the MDS XML back to CWM/XMI XML format does not use the
Description field, so your descriptions will be lost during that step of the process.
On the other hand, if you modify the value of a property from the original CWM/XMI XML,
the MetaXML export will reflect the change, and the XSLT will preserve it, allowing the tool to
import the change. It is your responsibility to make sure that your change does not break the
tools expectations or internal rules. Otherwise, the tool import may fail, the tool execution
may produce errors, or your data may merely be inconsistent).
Q: What happens to the XML file exported from my tool and the resulting transformed
XML file?
A: Nothing. The original file is used in read-only mode and is never altered. The transformed
file is placed in the same directory as the original file and not touched after the import. You
may delete either or neither file as desired. You may also re-import the transformed or original
file.
Q: Can an MDS CWM_Metamodel be created before doing a CWM import?
A: Yes. The file containing the metamodel definition is a regular XML representation using a
schema native to MetaXML. It can be imported by MetaXML at any time, the same as any
281

FAQ
other XML file. It is located in the tools folder of the MDS installation and is named
CWM_Metamodel.xml.
Q: What if I import the same CWM RDBMS::Catalog a second time?
A: You get a new set of objects, regardless of whether you deleted the first import. This
behavior is consistent with current MetaXML behavior when the action is add, which is
how the transformed XML is created.
Q: Why can I not export all the metadata out of my tool?
A: You can export whatever the tool allows. However, unless the tool exports its metadata in
CWM/XMI format, MDS will not be able to load it. The XML Bridge is based on the CWM/
XMI standard provided by the OMG, so metadata exported in non-standard format cannot be
imported.
Note: A tool may not allow an export of its proprietary metadata in a standards-based format.
Q: What metadata is exported from a tool and imported into MDS? What tool metadata
does MDS support?
A: XML Bridge imports all tool metadata from an exported CWM/XMI file and has no
control of what metadata a tool chooses to export in that format. Consult your tool vendor for
specifics on what is exported by their tool.
Q: I have XML files not in CWM/XMI format, but for which I can produce XSLT to
transform them into MetaXML schema. Can I use XML Bridge to import them as well?
A: Yes. See Technical Details on page 278.
Q: I have a batch environment I would like to use to do XML Bridge imports into MDS. Is
that possible?
A: Yes, at least from the MDS side of the exchange. Once you have exported the tools CWM/
XMI XML to a file, MDS provides a simple batch way to transform the XML into MetaXML
schema. For the details, see Technical Details on page 278.
282
Index
A
activity log
and SQL 33
metaactivitylog table 33, 70
setting flag 70
application groups
access types
changing 135
adding 126
deleting 128
memberships
changing 128
audit trail 65
and SQL 33
metaauditlog table 33, 65
metaauditlog view 33, 65
Automatic DIM Update
action processor
starting/stopping 171
and RSG 164
and Teradata Database System 165
DDL Gateway 164
database connection information 165
server 166
starting/stopping 170
MDS Action Processor 164
MDS Recovery Table 165
nodes
configuring 167
processes 164
B
BusinessAttribute class property descriptions 191
BusinessEntity class property descriptions 191
BusinessRule class property descriptions 192
C
Check class property descriptions 188
class objects
getting 110
getting by name 112
class property
creating 97
classes
security profiles
assigning 138
client load metamodel See CLM
CLM 205
CLM classes
descriptions 205
property descriptions 205
Script property descriptions 205
Source class property descriptions 206
SourceField property descriptions 206
Target class property descriptions 207
CLM relationship descriptions 208
Column class property descriptions 183
command-line syntax
mdsconfig 37, 143
metaclient 147
metadelete 157
metaload 152, 153
metaxml 160
prtconfig 161
Common Warehouse Metamodel 32
Constant class
containment relationship 140
CWM class packages 265
CWM metamodel 28
CWM_Metamodel 265
CWM/XMI 267
CWM/XMI XML 266
D
Data Definition Language See DDL
data versioning 31
Database class property descriptions 182
database information metamodel See DIM
databases
aborting load 57
loading 54
resynchronizing 60
unloading 58
DatabaseSystem class property descriptions 180
derived class
creating 98
property creating 100
DIM
class descriptions 179
class property descriptions 180
283
Index
DIM classes
BusinessAttribute class property descriptions 191
BusinessEntity class property descriptions 191
BusinessRule class property descriptions 192
Check class property descriptions 188
Column class property descriptions 183
Database class property descriptions 182
DatabaseSystem class property descriptions 180
Index class property descriptions 187
IndexColumn property descriptions 187
Node class property descriptions 189
Reference class property descriptions 188
ReferenceColumn class property descriptions 188
StoredProceduresParameter class property descriptions
189
SubjectArea class property descriptions 191
Table property descriptions 183
Trigger class property descriptions 189
ValidValues class property descriptions 192
View class property descriptions 185
ViewColumn class property descriptions 186
DIM relationship descriptions 199
dormant object support
PERM space 71
SPOOL space 71
tables 47, 70
views 31, 47, 70
dormant objects
and MDS 31, 70
PERM space 32
SPOOL space 32
tables 31
E
export
metaxml 160
F
FastLoad 28
Function class
property descriptions 195, 196, 198, 199
I
inactive
version type 31
Index class property descriptions 187
IndexColumn property descriptions 187
L
labels
applying to classes 87
284
applying to metamodels 87
applying to objects 89
creating 85
M
MDS
application groups
permissions 126
data
initial load
and metacreate 151
MetaSurf files 28
objects
security profile permissions 124
security profiles assigning 138
passwords 123
permissions 123
repository
creating
on Linux 42, 152
on Windows 41
with metacreate 151
migrating 161
security profiles
accessing 134
adding 135
adding users 137
permissions 133
setting configuration parameters
on Linux 36
on Windows 38
user groups 124
user names 123
users
adding 130
and application groups 126
changing memberships 129
deleting 132
managing 124
object permissions 124
utility programs 143
MDS administrative logon
metasu 46
MDS Administrator
default user name 46, 123
mdsconfig 158
command-line syntax 37, 143
metaactivitylog table
activity log 33, 70
metaauditlog table
audit trail 33, 65
metaauditlog view
audit trail 33, 65
Index
MetaBrowse 28
application metamodels
reloading 81
viewing properties 105
class property
creating 97
default password 76
derived class
creating 98
property creating 100
initial login 75
label
creating 85
label applied to objects
viewing 109
MDS Administrator name, default 76
metamodels
creating 89, 103
deleting 121
objects
finding 109
Options menu
Object Lookup 109
properties
viewing 105
repository class
creating 91
repository relationship
creating 95
security profile for objects
viewing 108
technical user and 75
Tools menu 85, 89, 92, 95, 99, 100, 103, 104, 105, 121
version label
creating 85
View menu
Get Class Objects 110
Get Class Objects by Name 112
Refresh Application Metamodels 81
metaclient
and Repository Versioning 145
command-line syntax 147
metacreate
MDS repositiory
creating 151
creating on Linux 42, 152
metadelete 157
metaload
command-line syntax 152, 153
warning messages 157
MetaLoadType class
MetaManager 28
access types
changing 135
activity log
setting flag 70
application groups
adding 126
deleting 128
options 128
audit trail
setting parameters 65
classes
security profiles
assigning 138
databases
aborting load 57
loading 54
resynchronizing 60
unloading 58
dialog boxes
Add Groups & Users 137
Add Security Profile 135
icons
security profile 134
user manager 125
initial login 45
MDS system configuration, modifying 64
MetaLoad LoadTypes, modifying 61
metasu 46
nodes
adding 167
objects
security profiles, assigning 138
security profiles
accessing 134
adding 135
adding users 137
system
deleting a Teradata database 53
Tools menu 124, 126, 128, 129, 130, 132, 134, 135, 137
user groups
managing 124
User Manager window 126, 130, 132
users
adding 130
deleting 132
managing 124
options 129
metamigrate 161
metamodels
creating 89, 103
deleting 121
exporting 158
metasu 154
MDS Administrator
285
Index
default user name 46

MDS Administrator password 47
MetaSurf
ASP compliant web server 35
virtual directory 44
metaviews
and data dictionary 29, 158
and MDS views 29, 158
and metaload 29, 158
and ODBC 29, 158
and SELECT privileges 29, 158
installing 29, 158
metaxml 158
export 160
exporting metamodels 158
exporting objects 158
importing data 158
MultiLoad 28
N
Node class property descriptions 189
nodes
adding 167
configuring for Automatic DIM Update 167
O
Object Management Group 32
objects
exporting 158
finding 109
getting by name 112
labels, viewing 109
security profiles, viewing 108
OMG CWM 265, 266
P
passwords
changing metasu 47
passwords and metaload 154
PERM space
and dormant object support 71
and dormant objects 32
and retain associated business information 32
and versioning 31
permissions 123
product version numbers 3
prtconfig 158
published
version type 31
286
R
Reference class property descriptions 188
ReferenceColumn class property descriptions 188
Relay Services Gateway See RSG
repository class
creating 91
repository relationship
creating 95
retain associated business information
PERM space 32
SPOOL space 32
retain associated business information See dormant objects
S
Script property descriptions 205
security profiles
adding 135
adding users 137
permissions 133
SELECT privileges
and metaviews 29, 158
software releases
supported 3
Source class property descriptions 206
SourceField property descriptions 206
SPOOL space
and dormant object support 71
and dormant objects 32
and retain associated business information 32
and versioning 31
SQL
and activity log 33
and audit trail 33
StoredProceduresParameter class property descriptions 189
SubjectArea class property descriptions 191
system configuration, modifying MDS 64
system, deleting a Teradata database 53
T
Table property descriptions 183
tables
dormant objects 31
metaactivitylog 33, 70
metaauditlog 33, 65
Target class property descriptions 207
and Automatic DIM Update 165
Teradata meta data tables 27
TPump 28
Trigger class property descriptions 189
troubleshooting
miscellaneous 174
Index
programming 173
U
User Manager window
MetaManager 126, 130, 132
users
access types 135
V
ValidValues class property descriptions 192
version numbers 3
versioning
classes 88
labels 85
metamodels 87
modifying 82
PERM space 31
SPOOL space 31
types
inactive 31
published 31
versioning of new MDS repository
default is no versioning 31
View class property descriptions 185
ViewColumn class property descriptions 186
views
dormant object support 31, 47, 70
metaauditlog 33, 65
X
XML CWM 267
XML Metadata Interchange 32
287
Index
288

311845

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

311845

Hochgeladen von

Copyright:

Verfügbare Formate

Teradata Meta Data Services

Teradata Meta Data Services Administrators

Teradata Professional Services Representatives

Teradata Database 14.0, 13.10, 13.0, 12.0.x, and V2R6.2.x

Teradata Tools and Utilities 14.00

Teradata Meta Data Services 14.00

To locate detailed supported-release information:

Under Online Publications, click General Search.

Type 3119 in the Publication Product ID box.

Under Sort By, select Date.

Teradata Meta Data Services Administrator Guide

Teradata ODBC Driver

Microsoft Windows products

Changes to This Book

Documented support of user-defined types (UDTs) and user-defined

Table 8 updated to show the Load Type as USER DEFINED TYPES/

Teradata Meta Data Services Administrator Guide

Use the Release Definition for the following

Overview of all of the products in the

3 Type 2029 in the Publication Product ID box.

Teradata Meta Data Services Administrator Guide

2 Under Online Publications, click General Search

the search results.

Use the Teradata Information Products

Browse by Category, click Data Warehousing.

For a list of Teradata Tools and Utilities

Access a link to a downloadable CD-ROM

Browse by Category, click Data Warehousing.

Teradata Meta Data Services Administrator Guide

Use the Teradata Information Products

The Teradata home page provides links to

Executive reports, case studies of

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

The Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Teradata Meta Data Services Administrator Guide

Class Objects and Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Teradata Meta Data Services Administrator Guide

prtconfig (Linux only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

View Column Class Property Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DIM Relationship Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

CLM Relationship Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Figure 1: Typical MDS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Table 1: Teradata MDS Configuration Linux Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Teradata Meta Data Services Administrator Guide

Table 33: DIM Class Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

Teradata Meta Data Services Administrator Guide

Table 69: Source Field Class Property Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services Administrator Guide

Teradata Meta Data Services

A repository database where metadata is stored in Teradata tables