Teradata System Emulation Tool

Transcription

1 Teradata Tools and Utilities Teradata System Emulation Tool User Guide Release April 2018 B K

2 Copyright and Trademarks Copyright by Teradata. All Rights Reserved. All copyrights and trademarks used in Teradata documentation are the property of their respective owners. For more information, see Trademark Information. Product Safety Safety type NOTICE CAUTION WARNING Description Indicates a situation which, if not avoided, could result in damage to property, such as to equipment or data, but not related to personal injury. Indicates a hazardous situation which, if not avoided, could result in minor or moderate personal injury. Indicates a hazardous situation which, if not avoided, could result in death or serious personal injury. Warranty Disclaimer Except as may be provided in a separate written agreement with Teradata or required by applicable law, 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 noninfringement. 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. The information contained in this document may be changed or updated by Teradata at any time without notice. Teradata may also make changes in the products or services described in this information at any time without notice. Feedback To maintain the quality of our products and services, your comments on the accuracy, clarity, organization, and value of this document to: teradata-books@lists.teradata.com Any comments or materials (collectively referred to as "Feedback") sent to Teradata Corporation will be deemed nonconfidential. Without any payment or other obligation of any kind and without any restriction of any kind, Teradata and its affiliates are hereby free to (1) reproduce, distribute, provide access to, publish, transmit, publicly display, publicly perform, and create derivative works of, the Feedback, (2) use any ideas, concepts, know-how, and techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, and marketing products and services incorporating the Feedback, and (3) authorize others to do any or all of the above.

3 Contents Chapter 1: Features 5 Features 5 Prerequisites 5 Supported Releases 5 Key Benefits 5 Emulation-Process Overview 7 Support Tools 8 System Requirements 8 Privileges 9 Online Help 13 Chapter 2: Connection Methods 14 Connection Methods 14 ODBC Driver Setup 14 CLIv2 Setup 15 Verifying the Connection 16 Starting Teradata SET 16 Connect to a Teradata Database 17 Chapter 3: Menus and Toolbars 20 Menus and Toolbars 20 Main Window 20 Import Window 23 Chapter 4: Command-Line Interface 27 Command-Line Interface 27 Command-Line Switches 27 Command-Line Tasks 29 Chapter 5: Session Options 35 Session Options 35 Customization Options 35 Connectivity Options 39 Directory Options 39 Error-Handling Options 40 Chapter 6: Export Methods and Options 44 Export Methods and Options 44 Export by Query 44 Exporting by Database 53 Exporting by Workload 56 Export Options 58 Viewing the Estimated Export Time 70 Chapter 7: Import Methods and Options 72 Import Methods and Options 72 Importing to a Test System 72 Changing Import Options 76 Specifying Objects for Import 79 Guide, Release

4 Contents Changing the RAS Byte Order 80 Editing Import Information 81 Changing the Permanent Space 82 Retrying a Failed SQL Statement 85 Editing Information Offline 86 Saving Changed Information 87 Displaying Existing Databases 88 Renaming a Target Database 88 Undoing Target Database Renaming 90 Reordering Databases 91 Viewing Machine Configuration 91 Viewing Estimated Import Time 93 Chapter 8: Administrative Functions 94 Administrative Functions 94 Set TLE Parameters 94 MAP Emulation Configuration 100 Perform Query Testing 101 Perform a File Transfer 103 Undoing Imported Files 105 Deleting Exported Files 107 View Log Files and Summary Reports 109 Retrying Failed Import Operations 112 Manage Missing Access Privilege Errors 112 Disconnect and Close Teradata SET 114 Perform File Management 115 View Low Level Error Log 116 Appendix A: Additional Information 117 Guide, Release

5 1 Features Features This is an introduction to Teradata System Emulation Tool (SET) features. Included is information about system requirements, privileges, and online help. Prerequisites The following prerequisite knowledge is required for this product: Teradata SQL Teradata Database Relational database management systems (RDBMS) Connectivity software, such as Open Database Connectivity (ODBC) or Call-Level Interface, Version 2 (CLIv2) Microsoft Windows 2000, Windows NT, Windows XP, Windows 7 operating systems Utilities that load and retrieve data Supported Releases This book supports the following releases: Teradata Database Teradata Tools and Utilities Teradata SET The most current information about supported operating systems, supported Teradata Database versions, and product version numbers for all Teradata Tool and Utilities is available (at in a single spreadsheet titled Teradata Tools and Utilities ##.# Supported Platforms and Product Versions (B ). Key Benefits Teradata SET imitates a target (production) system on a test system. System-level environmental data is captured from the target system, then stored in relational tables. The Teradata Query Optimizer (Optimizer) processes information from these tables, together with appropriate column and index statistics, to generate query plans on the test system as though the operation occurred in the production environment. Use Teradata SET to do the following: Guide, Release

6 1: Features Imitate the impact of environmental changes on Structured Query Language (SQL) statement performance. Determine the source of Optimizer-based query issues using imported environmental cost data and random AMP sample (RAS)-based statistical data. Teradata SET performs the following key functions: Works as a standalone application. Interfaces with a Teradata Database using CLIv2 or ODBC. Exports system information from a target system to a specified file on a workstation. Imports system information from the workstation to a test system. Displays the Query, Explain Text, Step Report, and Summary Information for queries in the Import window. Allows editing of object definitions, statistics, RAS, cost parameters, and cost profiles before import to a test system. Exports and imports data demographics of tables from one Query Capture Database (QCD) to another. Provides a summary report of the failures and successes of an import, export, or undo (cleanup) operation. Allows visual reordering of databases. Exports and imports workload recommendations. Allows other client applications to use Teradata SET functions. Uses Imported Data Capturing data from a target (production) system and applying it to a test system is a two-phase process: 1. Relevant data on the target system is read and then written to a staging area. 2. The staged data is imported to the test system and applied to the appropriate data tables. Imported data is used to do the following: Recreate the Optimizer performance characteristics of the target system. The Optimizer generates query execution plans based on many factors, such as available system resources, indexes, primary and secondary keys, and available statistics. All of these factors impact how the Optimizer creates the most effective execution plan. Generate query plans that emulate those created on the target system under a given set of conditions. A small test system can be used to generate query plans that emulate a much larger target system. Guide, Release

7 1: Features Perform what-if modeling. Test, diagnose, and solve Optimizer-related performance questions that might occur in the target system. Teradata SET also works with Teradata Visual Explain to emulate how a target system performs under specific conditions and workloads. Simplifies Data Capture Teradata SET provides an easy way to resolve Optimizer-related problems and discrepancies on a target system and to capture system information. Use Teradata SET to automate the process of exporting and importing system information for query-plan generation. The alternative is to use SQL statements which, unlike Teradata SET, requires knowledge of exactly what information to capture and which SQL statements to use. Using SQL statements is timeconsuming and prone to user-introduced errors. Ensures Data Integrity Teradata SET saves essential system information in specific file types based on the export options chosen. When system information is imported to the test system, it is automatically loaded in the correct format. Teradata SET also synchronizes all of the elements of a target environment. For example, all the configuration settings, databases, data models, and data dependencies maintain the correct relationships when exported and imported. In addition, database objects are duplicated on the test system. Tables, views, macros, triggers, join indexes, and stored procedures function just like they do on the target system. Use Teradata SET to thoroughly debug and optimize queries in a safe, but equivalent, emulated environment prior to introducing them into the production system. Emulation-Process Overview This section provides an overview of the typical Teradata SET emulation process. It is assumed that SystemFE.Opt_Cost_Table and SystemFE.Opt_RAS_Table exist on the target system. The process is as follows: 1. Connect to a Teradata Database using a Teradata Open Database Connectivity (ODBC) driver or Teradata Call-Level Interface, Version 2 (CLIv2). 2. Create a target system profile that defines the databases, tables, views, macros, and related environmental parameters or RAS to be captured and loaded onto the test system. 3. Perform an export operation from the target system to collect Optimizer cost parameters; RAS; and any necessary object definitions, statistics, and test queries from the target system. Then, place this emulation information on the system disk as data files that the test system can import. Guide, Release

8 1: Features 4. If the target and test systems are not connected to the same network, perform a pack operation to combine all the data files into one file. (Pack files also can be compressed using any standard compression method.) Transfer the files to the test system. 5. Perform an import operation to create the objects, emulate the statistics, and import the data into SystemFE.Opt_Cost_Table and SystemFE.Opt_RAS_Table on the test system. 6. Set emulation on the test system, and use the data to test and resolve any problems or discrepancies. The figure below shows the relationship between Teradata SET, the ODBC, and CLIv2 interfaces, target systems, and test systems. Teradata SET Architecture Target System Teradata Database Workstation Teradata SET Client Tool AMP Samples QCD Schema/DDL Statistics EXPORT SYSTEM INFORMATION CLIv2 ODBC Teradata SET Data Files GDO Cost Parameters IMPORT SYSTEM INFORMATION Test System Teradata Database QCD Statistics Tables AMP Samples GDO Cost Parameters Support Tools Teradata SET uses the following tools to emulate a target system on a test system: Query Capture Facility (QCF) SQL SHOW statement Target Level Emulation (TLE) Guide, Release

9 1: Features System Requirements The following topics describe the system requirements: Operating System Connectivity Compatibility Installation Operating System The most current information about supported operating systems, supported Teradata Database versions, and product version numbers for all Teradata Tool and Utilities is available (at in a single spreadsheet titled Teradata Tools and Utilities ##.# Supported Platforms and Product Versions (B ). Connectivity Connecting Teradata SET to a Teradata Database requires one of the following: ODBC Driver for Teradata Database Teradata CLIv2 for Network-Attached System Before retrieving system information from a target system, an ODBC driver or CLIv2 must be installed on the workstation. If an ODBC driver and CLIv2 are installed on the same system, the user-configured ODBC driver is used to connect to Teradata Database after the initial setup. Compatibility Teradata SET is certified to run with any Level-2-compliant, 32-bit ODBC driver. Teradata SET is also certified to run with CLIv2. For details on the compatible versions, refer to Teradata Tools and Utilities for Microsoft Windows Installation Guide (B ). Installation Install Teradata SET as a standalone application using the standard Microsoft Windows software installation instructions. For more information, refer to Teradata Tools and Utilities for Microsoft Windows Installation Guide (B ). Privileges To perform export, import, or undo import (cleanup) operations, establish all of the following: Guide, Release

10 1: Features Privileges to all database objects to be exported or imported A valid Teradata Database user ID A valid password for the user ID To learn more about privileges, refer to SQL Data Definition Language (B ). The following topics describe access rights: Export Rights Import Rights Estimate-Time Rights Undo-Import Rights Export Rights Set privileges prior to performing export operations. When exporting by query, the right to execute the SHOW QUALIFIED SQL statement and configuration data (RAS, statistics, object definitions) is required if only those objects returned from this statement can be exported. The table below lists the privileges required to export each type of information. Exported Information Cost parameters Execution plans Required Rights INSERT, SELECT, and DELETE on SystemFE.Opt_Cost_Table and SystemFE.Opt_DBSCtl_Table. For an existing plan: SELECT on the QCD tables or on the QCD EXECUTE on QCD macros For a new plan, sufficient rights to execute the DUMP EXPLAIN statement for the given query. For a new plan with demographics: Sufficient rights to execute the INSERT EXPLAIN statement for the given query EXECUTE on the QCD macros New plans can be generated only from the Export By Query dialog box. See Export by Query. Object definitions For join indexes, macros, tables, triggers, stored procedures, User Defined Functions (UDFs), and User-Defined Types (UDTs), sufficient rights to execute the corresponding SHOW statement for the database objects. To export object definitions for view, SELECT on the view in order to perform the SHOW QUALIFIED statement. To export by database, SELECT on DBC.Columns and DBC.Tables to export referenced UDTs. Guide, Release

11 1: Features Exported Information Machine configuration Required Rights MONRESOURCE privilege on V2R6.2 database. EXECUTE FUNCTION access to SYSLIB.MonitorVirtualConfig and EXECUTE FUNCTION access to SYSLIB.MonitorPhysicalConfig on Teradata Database 12.0 and later database versions. On a V2R6.2 database, this information is exported only when a CLIv2 connection is used. See Viewing Machine Configuration. RAS SELECT on the tables selected for export. INSERT, SELECT, and DELETE on SystemFE.Opt_RAS_Table. Statistics All rights required to execute the HELP STATISTICS statement on the table or join index referenced. SELECT on the DBC.IndexStats, DBC.ColumnStats, and DBC.MultiColumnStats views. Demographics SELECT on the data demographics table and corresponding views of the table, and sufficient rights to execute the COLLECT DEMOGRAPHICS statement. SELECT on QCD views. EXECUTE on QCD macros. This option is only available in export-by-database and export-by-query operations. QCD data SELECT on QCD tables and views. EXECUTE on QCD macros. This option is only available in export-by-database operations. Workloads SELECT on QCD tables and views. EXECUTE on QCD macros. This option is only available in export-by-workload operations. Cost profiles MH Maps SELECT on the DBC.CostProfiles_v and DBC.CostProfileValues_v views. SELECT on the tables selected for export. INSERT, SELECT, and DELETE on SystemFE.Opt_Map_Table and SystemFE.Opt_MapRel_Table Guide, Release

12 1: Features Import Rights Set privileges prior to performing import operations. The table below lists the privileges required to import each type of information. Imported Information Cost parameters Execution plans Object definitions Required Rights INSERT on SystemFE.Opt_Cost_Table and SystemFE.Opt_DBSCtl_Table. INSERT, SELECT, and UPDATE on QCD tables and views. CREATE on the user or database into which the information is imported. (Use to create database objects such as join indexes and stored procedures.) CREATE PROCEDURE WITH GRANT OPTION for the database in which stored procedures are created. CREATE EXTERNAL PROCEDURE WITH GRANT OPTION for the database in which external stored procedures are created. CREATE FUNCTION WITH GRANT OPTION for the database in which User Defined Functions are to be created. UDTTYPE on the SYSUDTLIB database, to create a UDT. UDTUSAGE, to include a UDT with a CREATE TABLE statement. RAS Statistics Demographics QCD data Workloads Cost profiles MH Maps INSERT on SystemFE.Opt_RAS_Table. All rights required to execute the COLLECT STATISTICS statement for the table or join index referenced. INSERT, SELECT, and UPDATE on the data demographics table and corresponding table views. EXECUTE for demographics macros. INSERT, SELECT, and UPDATE on QCD tables. SELECT on QCD views. INSERT, SELECT, and UPDATE on QCD tables. SELECT on QCD views. EXECUTE on the DBC.CreateNewCostProfile and DBC.InsertConstantValue macros. INSERT on SystemFE.Opt_Map_Table and SystemFE.Opt_MapRel_Table Estimate-Time Rights The following privileges are required to use the Estimate Time function when performing export and import operations: The corresponding rights listed in Export Rights and Import Rights. CREATE DATABASE on the default database. Guide, Release

13 1: Features Undo-Import Rights The table below lists the privileges required to restore the default test system environment (also known as undo-import or cleanup operations). Undo-Import Information Cost parameters Execution plans Object definitions RAS Statistics Demographics QCD data Workloads Cost profiles MH Maps Required Rights DELETE on SystemFE.Opt_Cost_Table and SystemFE.Opt_DBSCtl_Table or on SystemFE. DELETE on the QCD tables or on the QCD. EXECUTE on QCD macros. Sufficient DROP rights on the parent database or DELETE on the database object. DELETE on SystemFE.Opt_RAS_Table or on the SystemFE database. All rights required to execute the DROP STATISTICS statement for the table or join index referenced. DELETE on the data demographics table and corresponding views of the table. EXECUTE on demographics macros and QCD macros. DELETE on QCD tables and views. EXECUTE on QCD macros. DELETE on QCD tables and views. EXECUTE on QCD macros. EXECUTE on the DBC.DeleteCostProfile macro. DELETE on SystemFE.Opt_Map_Table and SystemFE.Opt_MapRel_Table or on the SystemFE Database Online Help Opening Online Help From the toolbar, click. The Help window opens. Use the tools available from the Help window to navigate to other topics. Opening Context-Sensitive Help From most windows and dialog boxes, press F1 to see context-sensitive help for the active window or dialog box. If F1 does not display context-sensitive help, press Shift+F1. Guide, Release

14 2 Connection Methods Connection Methods This chapter contains procedures for establishing a connection to a Teradata Database using either ODBC or CLIv2. Verify the connection before opening Teradata SET. ODBC Driver Setup Define a data source for each Teradata Database (target system and test system) prior to connecting with ODBC. Use the Microsoft ODBC Data Source Administrator to create ODBC data sources and to configure the drivers. Defining a Data Source 1. Open Microsoft ODBC Data Source Administrator by doing one of the following: From the Teradata System Emulation Tool window (main window), click Tools > Define Data Source. From the Windows desktop, click Start > All Programs > ODBC > 32- bit ODBC Administrator. The ODBC Data Source Administrator dialog box appears and displays the User DSN tab by default. 2. Click Add. 3. Under the Name column, select Teradata. 4. Click Finish. The ODBC Driver Setup for Teradata Database dialog box appears. Guide, Release

15 2: Connection Methods 5. Enter information in the boxes. For more information, refer to ODBC Driver for Teradata User Guide (B ). 6. Verify the connection before opening Teradata SET and connecting to a Teradata Database. See Verifying the Connection. CLIv2 Setup When using CLIv2, define an IP address and provide the name of the Teradata Database to use in the hosts file on the workstation. Unlike the ODBC connection, no data source must be defined prior to connecting to a Teradata Database. CLIv2 connections are defined from within Teradata SET. See Connect to a Teradata Database. Defining an IP Address and a Name for a Teradata Database 1. Use Windows Explorer to navigate to the hosts file. On systems running Windows NT or Windows 2000, the hosts file is located in the system32\drivers\etc subdirectory of the directory in which Windows is installed. 2. Double-click the hosts file. Guide, Release

16 2: Connection Methods The Open With dialog box appears. 3. Click NOTEPAD. 4. Click OK. The hosts file opens in a Notepad window. 5. At the bottom of the file, type: xxx.xxx.xxx.xxx ssscop1 where xxx.xxx.xxx.xxx is the functional IP address and sss is the Teradata Database name. 6. Click File > Save. 7. Click File > Exit to close Notepad and return to the Windows desktop. 8. Verify the connection before opening Teradata SET and connecting to a Teradata Database. Verifying the Connection Test the connection between the workstation and Teradata Database before starting Teradata SET. 1. From the Windows desktop, click Start > Run. 2. In the Open box, type PING followed by the name of the Teradata Database and the cop1 suffix: PING ssscop1 where sss is the Teradata Database name. 3. Teradata Database returns the following message: Reply from xxx.xxx.xx.xx where xxx.xxx.xx.xx is the Teradata Database IP Address. If Teradata Database does not respond to the PING command, contact the network administrator to determine the cause of the error. 4. Start Teradata SET. Guide, Release

17 2: Connection Methods Starting Teradata SET Prerequisite: Teradata SET must be installed and configured before connecting to a Teradata Database. To learn how to navigate Teradata SET, see Menus and Toolbars. This section explains how to start Teradata SET using Windows. The tool also can be started from the command line. See Command-Line Interface. From the Windows desktop, click Start > All Programs > Teradata System Emulation Tool number, where number is the version number. The main window opens. See Main Window for information on locating the Teradata SET version number. Connect to a Teradata Database Before using Teradata SET to export information, connect to a Teradata Database using ODBC or CLIv2. Connecting Using ODBC Prerequisite: Before connecting through ODBC, define a data source. See ODBC Driver Setup. For information on starting Teradata SET, see Starting Teradata SET. 1. From the Teradata SET main window, click. The Select a Data Source dialog box appears. 2. Select a data source. Refer to ODBC Driver for Teradata User Guide (B ) for assistance. 3. Click OK. Guide, Release

18 2: Connection Methods Connecting Using CLIv2 Prerequisite: An IP address and modifications to the hosts file are required prior to connecting with CLIv2. See CLIv2 Setup. For information on starting Teradata SET, see Starting Teradata SET. 1. From the main window, click Tools > Options. The Options dialog box appears. 2. Click the Connectivity tab. 3. Click CLIv2. 4. Click Apply. 5. Click OK. 6. Click. The Connect to Teradata Database dialog box appears. Connect to Teradata Database Please enter your logon information Teradata Database Name: panther User Name: DBC Password: Session Character Set: More >> OK Cancel 7. Enter the logon information in the dialog box. Logon Information Teradata Database Name User Name Password Session Character Set Description Select a Teradata Database from the list or type a valid Teradata Database name. The IP address of the server should be stored in the hosts file to use a host name. See the procedure Defining an IP Address and a Name for a Teradata Database. Select a user name from the list, or type a valid user name. The user name must be defined for the server. When using Single Sign On, ensure that the User Name and Password boxes are blank. Type the password for the user name in the User Name box. The password is concealed with asterisks in place of the characters as they are typed. [Optional] Select a session character set: ASCII KANJISJIS_0S Guide, Release

19 2: Connection Methods Logon Information Description UTF-16 UTF-8 More Authentication Mechanism Authentication Parameter Default Database Account String Less Click to view Advanced Options. Select a mechanism from the list. Security measures are specific to each Teradata site. Contact the Database Administrator or the security manager if no mechanisms are listed. Type the parameters required by the selected mechanism. The authentication parameter is concealed with asterisks in place of the characters as they are typed. Consult the Database Administrator for current authentication parameters. [Optional] Select the default database for the session. If no database is specified, the default database defined for the user is used. [Optional] Select the account string from the list or type the logon parameters that define the user group. Click to hide Advanced Options. 8. Click OK. Guide, Release

20 3 Menus and Toolbars Menus and Toolbars This topic provides information about the Teradata SET menus and toolbars. Use this information to navigate the main window (Teradata System Emulation Tool window) and the Import window. Main Window The main window contains menus, commands, and a toolbar that access Teradata SET primary functions and features. Use the options available in the main window to navigate the Teradata SET application. Main Window Menus, Commands, and Toolbar Buttons describes main window options. Version and Copyright Information explains the information available in the About Teradata System Emulation Tool dialog box, which is accessed from the dialog box Help menu. Main Window Menus, Commands, and Toolbar Buttons Menu Command Button Description File Connect Disconnect Log on to a Teradata Database. Log off from a Teradata Database. Exit None Close Teradata SET and return to the Windows desktop. View Log File Summary Report Open or close a log file. Open or close a report that summarizes the successes and failures of an import, export, or undo import (cleanup) operation. Guide, Release

21 3: Menus and Toolbars Menu Command Button Description Tools Font None Display the Font dialog box to change the font style, size, or color for text displayed in the main window. For example, change the font used when displaying the log file or summary report. Toolbar None Show or hide the main window toolbar. Status Bar None Show or hide the status bar in the Main and Import windows. Export Import Undo Import Customize Data Capture emulation information from a target system. Open the Import window, edit exported emulation information, and then import that information to a test system. Display the Open dialog box and select a single.undo file of imported information to remove it from a test system. Open the Import window, select an.mcf file, then edit emulation information without being connected to Teradata Database. This option is only available when not connected. Map Emulation Config.. Set TLE Reset TLE Delete Files Pack Unpack Define Data Source Execute SQL/SQL Assistant None None Displays the MAPS from the target system and the corresponding test system map for emulation. Facilitates user to manually select a MAP on the test system to emulate target system MAP. Refer to Perform Query Testing for details. Display the Set Target Level Emulation dialog box to define how RAS, cost parameters, cost profiles, and Dynamic (IPE) plans are emulated on the connected system. Display the Reset Target Level Emulation dialog box to reset RAS, cost parameters, and cost profiles to default values. Display the Delete dialog box to remove selected Teradata SET files. The.mcf files are read and, depending on the export options chosen, the corresponding file types (such as.ddl and.opt) are removed. See Perform File Management. Display the Pack dialog box to combine an.mcf file and its associated files into one file (.pack). The UDF code files specified (if any) in response to the Browse for UDF File Open Dialog during export are also packed in the same file. See Perform File Management. Display the Unpack dialog box to separate the files in a.pack file. See Perform File Management. Display the ODBC Database Administrator dialog box to define or edit ODBC data sources for a Teradata Database. Open a query editor (SQL Assistant or Execute SQL) to execute queries. Click Tools > Options to select an editor. Guide, Release

22 3: Menus and Toolbars Menu Command Button Description Help Options None Display the Options dialog box to customize Teradata SET features. See Customization Options. Help Topics About Teradata System Emulation Tool None Open online help. Display version and copyright information. From the main window, click Help > About Teradata System Emulation Tool. The About Teradata System Emulation Tool dialog box appears. See Version and Copyright Information. Toolbar button None None Toggle audible notification feature on or off. Control of this feature is also accessible from Tools > Options. Select the Customize tab. Version and Copyright Information The following table explains the information available in the About Teradata System Emulation Tool dialog box, which is accessed from the Help menu. Version and Copyright Information Information Description Version Date Created System Version number of the software installed. Date the installed version of software was created. System name of the current connection. This information appears only when connected to a Teradata Database. Connection Type Character Set The connectivity type is indicated as the following types: Connected-ODBC Connected to Teradata Database with ODBC connectivity. Connected-CLI Connected to Teradata Database with CLI connectivity. Not Connected Not connected to Teradata Database. Displays the session character set used to connect to Teradata Database. This information appears only when connected to a Teradata Database. Guide, Release

23 3: Menus and Toolbars Information User Description Name of the currently connected user. This information appears only when connected to a Teradata Database. Database Version Version number of the connected Teradata Database. This information appears only when connected to a Teradata Database. Database Release Release number of the connected Teradata Database. This information appears only when connected to a Teradata Database. Copyright Current copyright statement. Import Window The Teradata System Emulation Tool - Import window (hereafter referred to as the Import window) contains menus, commands, and a toolbar that access Teradata SET Import functions. Opening the Import Window 1. Click in the main window. Use the options available in the Import window to navigate the Import feature. The information that appears in the right pane of the Import window depends on what was imported. See Import Window Menus, Commands, and Toolbar Buttons for a description of all the menus, commands, and buttons. Guide, Release

24 3: Menus and Toolbars Import Window Menus, Commands, and Toolbar Buttons Menu Command Button Description File Save As Import Exit Display the Save As dialog box to rename an edited file. This option is only available if the emulation information has been edited or if the selections in the left pane (import tree) have changed. Import emulation information to a test system. Close the Import window and return to the main window. Edit Undo Undo the last edit. This option is only available in edit mode and only if the emulation information has been edited. Cut Move selected text to the Clipboard. This option is only available in edit mode and only when text is selected. Copy Copy selected text to the Clipboard. This option is only available in edit mode and only when text is selected. Paste Insert text from the Clipboard. This option is only available in edit mode. Find Display the Find dialog box to search for specified text in the left or right pane. The following options are available from the Find dialog box: Match whole word only. Select to search for whole words. Match case. Select to distinguish between uppercase and lowercase characters during the search. Search in all DDLs. Select to search all object definitions. Guide, Release

25 3: Menus and Toolbars Menu Command Button Description This option is available and included in the Find dialog box only when searching the Object Definitions Information pane. Replace Replace selected text. Select All None Select all of the text in an editable pane. Allow Edit Apply Changes Turn on the edit mode to modify object definitions, RAS, statistics, cost parameters, and cost profiles in the right pane of the Import window. Apply edits to the active object definition, RAS, statistic, cost parameter, or cost profile. This option is only available after making changes in edit mode. View Tool Bar None Show or hide the Import window toolbar. Status Bar None Show or hide the status bar in the main and Import windows. Font None Display the Font dialog box to change the font style, size, or color for text displayed under Object Definitions Information and Explain Text Information in the Import window. Source Machine Configuration Estimate Time Display the Source Machine Configuration dialog box to view the configuration characteristics of the system from which the emulation information is exported (the target system). Display the Estimated Time dialog box to view the estimated length of time needed for the import operation. Click Refresh to load the most current information. The Estimate Time function requires privileges. See Estimate- Time Rights. Options Existing Databases Display the Existing Databases dialog box to view a list of existing databases. This option is available when the export includes one of the following: Object definitions Execution plans Workloads QCD data Guide, Release

26 3: Menus and Toolbars Menu Command Button Description Import Options Order Database Set TLE Change PermSpace Display the Import Options dialog box to further define the databases and emulation information for an import operation. Allow the reordering of databases at the same level in the left pane (import tree) of the Import window. Display the Set Target Level Emulation dialog box to view a list of the RAS, cost parameters, cost profiles, and Dynamic (IPE) plans exported from a target system. Use the dialog box to define the emulation information imported to a test system. Display the Change PermSpace dialog box to specify different permanent space (permspace) than that calculated automatically by Teradata SET. Permanent space is required for importing objects on a target system. Help Help Topics About Teradata System Emulation Tool None Open online help. Display version and copyright information. From the main window, click Help > About Teradata System Emulation Tool. The About Teradata System Emulation Tool dialog box appears. See Version and Copyright Information. Toolbar buttons (no corresponding menu or commands) None None Rename the target database. None None Undo the renaming of a target database. Guide, Release

27 4 Command-Line Interface Command-Line Interface This chapter explains command-line switches and how to perform tasks from the command line. Export, import, and undo-import (cleanup) operations can be performed for the following items: Object definitions Statistics RAS Execution plans Optimizer cost parameters Cost profiles DBS Control information Demographics Workload information Multiple Hash Maps Command-Line Switches The following table describes the command-line switches for Teradata SET. Command-line switches are not case-sensitive. Switch am c dsp ed esr Task Set authentication mechanism and parameter for connecting to a database. Connect using ODBC. Capture execution plan information for a specific date when queries are added for export using the function CURRENT_DATE. The date must be specified with this switch in mm-ddyyyy format. For example, -dsp Export by database for the specified database name. Export table data used by query optimization. This function is available only when command-line switch p (execution plans) is specified in the export options. eqf eqt Export by query for the queries contained in the specified file. Export by query for the query specified on the command line. Guide, Release

28 4: Command-Line Interface Switch ewl ewr f i icf l lsr qcd scs u unx ux uxq xapp dbql tardbql x Task Export by workload for the specified workload name. Export specific recommendation tags during an export by workload. Save the exported information to the specified file. Import information from the specified file. Read the command switches from the specified file instead of the command line. Connect using CLIv2. Insert table data used by query optimization to tables on the test system. Export and import QCD-related information. Specify session character set. Clean up information using the specified file. Retrieve Data Dictionary information and QCD data using non-x views. Retrieve Data Dictionary information and QCD data using X views. Retrieve data from the QCD using X views. Keep the application open and connected following an export, import, or undo-import (cleanup) operation. By default, the application automatically disconnects and closes after the operation completes or an unsuccessful log on occurs. Export DBQL query specified on the command line using the parameters DBQL Database name and DBQL Query ID. Import DBQL XML Plans into the specified Target DBQL Database. The target DBQL Database name should be provided followed by the switch. Export execution plans in XML form for queries either entered manually (specified on the command line using switch eqt) or selected from file. The following table describes the command-line switches for export and import options. Options can be specified in any combination and in any order. For example, typing -drs or -d -s -r achieves the same result. If no option is specified, all options are considered. Switch d e g o p q r Task Export, import, and undo object definitions. Export, import, and undo cost profiles. Use 't' to export current cost profiles. Export, import, and undo demographics. Export, import, and undo Optimizer cost parameters and DBS Control information. Export, import, and undo execution plans. Import and undo import the DBQL XML Plans. Export, import, and undo RAS. Guide, Release

29 4: Command-Line Interface Switch s w m Task Export, import, and undo statistics. Export, import, and undo workload information, including workload definitions and index recommendations. Export, import and undo Maps. Command-Line Tasks Review the following topics before using the command line: Logging On Exporting Importing Undoing Imported Information Using the Input Command File Switch Logging On Use the Teradata SET command-line interface to log on to a Teradata Database using either ODBC or CLIv2 connectivity. Use the following command syntax to log on to a Teradata Database: tset [-c -l] <DSN_or_tdpid>\<username>\<password> [-am <Authentication Mechanism>\<Authentication Parameter>] [-scs <Session characterset>] Guide, Release

30 4: Command-Line Interface When only the log-on switch is specified in the command, the application remains open after a connection is established regardless of the xapp switch. The following examples demonstrate ways to log on from the command line. Syntax Example tset -c mydsn tset -c mydsn\jeff \padres tset -c mydsn \padres tset -l mytdpid \jeff tset -l mytdpid \jeff\padres Description Use ODBC to log on to the data source named mydsn. If the complete log-on information is not available in the DSN, the Teradata Database dialog box appears. Use ODBC to log on to the data source named mydsn with the user name jeff and password padres. Use ODBC to log on to the data source named mydsn with the password padres. If the user name is not available in the DSN, the Teradata Database dialog box appears. Display the Connect to Teradata Database dialog box and wait for a password. Then, use CLIv2 to connect to a Teradata Database named mytdpid with the user name jeff. Use CLIv2 to log on to a Teradata Database named mytdpid with the user name jeff and password padres. Exporting Use the command line interface to export information for a specified database. To export demographics, use the qcd switch to specify an existing QCD database. Exporting by Database Use the following command syntax to export by database: tset [-icf <commandfile>] [[-c -l] <DSN_or_tdpid>\<username>\<password> [-am <Authentication Mechanism>\<Authentication Parameter>] [-scs <Session characterset>] -ed <databasename> [-qcd <qcdname>] [-f <exportfile>] [-d -s -r -p -o -g -w -e -m] [-ux -unx] [-xapp]] The following examples demonstrate ways to export by database from the command line. Guide, Release

31 4: Command-Line Interface Syntax Example tset -l prod\dbc\dbc -ed db1 -dsro tset -l test\jeff -ed qcd - p -ux tset -c prod -ed dbc -o -f cost Description Export object definitions, statistics and RAS for the database dbl from the system prod. Cost parameters are also exported from the system. The exported data is saved to a file using the name prod. Export execution plans from the QCD database named qcd from the system test. Only plans captured by the user jeff are exported. The exported data is saved to a file named test. Export only cost parameters from the system prod. The exported data is saved to a file named cost. Exporting by Query Use the command line interface to export information for a specified query. Enter the query on the command line or specify a file name containing one or more queries. To export demographics, use the switch to specify an existing QCD database. If the qcd switch is not specified when exporting execution plans, then the name qcd is used by default. Use the following command syntax to export data by query: tset [-icf <commandfile>] [[-c -l] <DSN_or_tdpid>\<username>\<password> [-am <Authentication Mechanism>\<Authentication Parameter>] [-scs <Session characterset>] [-eqt <querytext> -eqf <queryfile>] [-dbql <DBQL DB Name DBQL Query ID>] [-qcd <qcdname>] [-f <exportfile>] [-d -s -r -p -o -g -w -e -m] [-ux -unx] [-esr] [-x] [-xapp]] The following examples demonstrate ways to export by query from the command line. Syntax Example tset -l prod\dbc\dbc -qcd myqcd -dsro -eqt "select * from orders" -f query1 tset -c prod -p -eqf query.txt -f queryplans Description Export object definitions, statistics and RAS for the objects referenced by the specified query from the system prod. Cost parameters are also exported. The execution plan for the query is exported using the QCD database named myqcd. The exported data is saved to a file named query1. Export the execution plans for all of the queries in the file query.txt from the system prod. The QCD database name qcd is used by default. The exported data is saved to a file named queryplans. Guide, Release

32 4: Command-Line Interface Syntax Example tset -c prod\dbc -eqt "sel * from dbc.dbcinfo;" -qcd "testqcd" -p -x tset -c prod\dbc -dbql "DBQATXML " -p Description Export the execution plan for the specified query by capturing the plan in XML form using INSERT EXPLAIN INTO testqcd IN XML query. Export the execution plan from DBQL Database DBQATXML with the specified Query ID. Exporting by Workload Use the command line interface to export information for a specified workload. This is useful for extracting the information required to perform an index analysis on a test system using Teradata Index Wizard. You must specify the workload name and the name of the QCD that contains the workload. Use the following command syntax to export by workload: tset [-icf <commandfile> ] [[-c -l] <DSN_or_tdpid>\<username>\<password> [-am <Authentication Mechanism>\<Authentication Parameter>] [-scs <Session characterset>] -qcd <qcdname> -ewl <workloadname> [-ewr <recommendationtag1> [-ewr <recommendationtag2>... ]] [-f <exportfile>] [-d -s -r -p -o -g -w -e -m] [-xapp]] The following example demonstrates how to export by workload from the command line. Type: tset -l prod\dbc\dbc -qcd qcd -ewl wl1 -dsrpow -f workload1 Object definitions, statistics, and RAS for the objects referenced by the queries of workload wl1 in the QCD named qcd from the system prod are exported. The execution plans for the queries, the workload definition, plus any index recommendations and cost parameters are also exported. This is all of the information needed to do an index analysis on a test system using Teradata Index Wizard. The exported data is saved to a file named workload1. Importing Use the command line interface to import information associated with a specified.mcf file onto a Teradata Database. If the requested information is not available in the file, then the switch is ignored. Use the following command syntax to perform an import: tset [-icf <commandfile>] [[-c -l] <DSN_or_tdpid>\<username>\<password> [-am <Authentication Mechanism>\<Authentication Parameter>] [-scs <Session characterset>] Guide, Release

33 4: Command-Line Interface [-i <importfile> [-tardbql <targetdbqlname>] [-d -s -r -p -o -g -w -e -q -m] [lsr] [-xapp]] The following examples demonstrate ways to import from the command line. Syntax Example tset -l test\dbc\dbc -i prod.mcf tset -c test -i cost.mcf -o -xapp tset -c prod\dbc -i <importfile> - tardbql dbqatxml -q Description Import all of the information available in the prod.mcf file onto a Teradata Database named test. Import cost parameters from the cost.mcf file into a Teradata Database named test. The application remains open after the import is completed. Import DBQL XML plans available in the import file to the specified target DBQL database DBQATXML Undoing Imported Information Use the command line interface to clean up or remove information previously imported onto a Teradata Database. If the requested information is not available to be cleaned up, then the switch is ignored. Use the following command syntax to clean up imported information: tset [-icf <commandfile>] [[-c -l] <DSN_or_tdpid>\<username>\<password> [-am <Authentication Mechanism>\<Authentication Parameter>] [-scs <Session characterset>] [-u <undofile>] [-d -s -r -p -o -g -w -e -q -m] [-xapp]] The following are examples of how to clean up imported information from the command line. Type: tset -c test -u prod.31-jul undo The information that was imported into a Teradata Database named test, as logged in the specific.undo file, is cleaned up. Type: tset -c test\dbc -u prod.31-jul undo -q The DBQL XML Plans that were imported into a Teradata Database named test, as logged in the specified.undo file, are cleaned up. Using the Input Command File Switch Use the input command file switch to read command options from a file. No other switch is allowed on the command line when the icf switch is specified. Guide, Release

34 4: Command-Line Interface Use the following command syntax to specify an input command file: tset [-icf <commandfile>] The following is an example of how to specify an input command file from the command line. Type: tset -icf command.txt where the file command.txt contains the following text: -c mydsn -ed db1 -dsro Command options are read from command.txt, and the command is executed. Guide, Release

35 5 Session Options Session Options Teradata SET sessions can be customized using the Options dialog box, which consists of the following tabs: Customize: Select options such as whether to create a log file. Connectivity: Choose the interface to use when connecting to a Teradata Database. Directory: Specify the directory in which exported emulation information is saved. Error Handling: Choose how errors are handled. Selections take effect immediately and remain in effect until they are changed. Customization Options Use the Customize tab to set options such as whether to create a log file. It is not necessary to connect to Teradata Database for this procedure. Setting Session Defaults 1. From the main window, select Tools > Options. The Options dialog box appears with the Customize tab selected by default. Guide, Release

36 5: Session Options Options Customize Connectivity Options Create log file Directory Error Handling Log SQL statements Display logon dialog at startup Provide Audible Notification Use X views (QCD only) Use X views (DBC and QCD) Use Multi-Threading Use SQL Assistant instead of tghe Execute SQL window with ODBC connectivity Export table data used by query optimization Import table data used by query optimization Capture date specific execution plan information Date (MM/DD/YYYY): 8/16/2016 Export Plans in XML Export Dynamic Plans Enable Object Use Count OK Cancel Apply 2. Select one or more of the check boxes under Options. Option Create log file Log SQL statements Display logon dialog at startup Provide Audible Notification Description Record all operations performed during an active Teradata SET session. Use the log file to research an operation. For example, research what occurred during an import operation when the import is partially successful. Create a log file of the SQL statements used in the export, import, and undo import (cleanup) processes. Connect automatically to the selected Teradata Database. The Teradata Database Connect dialog box appears. Emit a tone when an event is initiated; for example, when a file is exported. Click on the toolbar to toggle the audible notification on or off. Use X views (QCD only) Use X views (DBC and QCD) Retrieve data from the QCD using X views. See Creating Restricted Views for information on restricted views. Retrieve Data Dictionary information and QCD data using X views. See Creating Restricted Views for information on restricted views. Guide, Release

37 5: Session Options Option Use Multi- Threading Use SQL Assistant instead of the Execute SQL window with ODBC connectivity Description Speed up export and import operations with multiple connections. Use SQL Assistant instead of Execute SQL as the query editor when connected to the Teradata Database with ODBC connectivity. When using a CLIv2 connection, Execute SQL is used regardless of how this option is set. Export table data used by query optimization Export table data used by query optimization along with the execution plan. When this option is selected, table data used by query optimization is retrieved and stored in Teradata SET export files. Table data might be needed to accurately emulate a query plan if the source table of a join has a single-row access using a unique index because the Optimizer retrieves this row and uses the column values for cardinality estimations. Execution plans must be exported in order to use this function. See Export Options for more information on exporting execution plans. Import table data used by query optimization Capture date specific execution plan information Export Plans in XML Export Dynamic Plans Enable Object Use Count Insert table data used by query optimization to tables on the test system. Execution plan information is captured for a specific date when queries using the function CURRENT_DATE are added for export. The Date dropdown list is active when this option is selected. This option works when DUMP EXPLAIN or INSERT EXPLAIN SQL statements are used to capture the execution plan information. For queries entered by user, export execution plans in XML format by submitting INSERT EXPLAIN in XML. For queries entered by a user, export Dynamic Plans (IPE - Incremental Planning and Execution) captured into the SystemFE.Opt_XMLPlan_Table by submitting DIAGNOSTIC DUMP XMLPLAN SystemName REQUEST RequestName comment string ON FOR REQUEST; request; If 'Enable Object Use Count' option is checked, TSET, before importing statistics, will submit REPLACE QUERY LOGGING WITH USECOUNT ON 'DBNAME', where DBNAME is the Database being imported for which OUC information is captured while exporting statistics. And during undo import of statistics, TSET submits END QUERY LOGGING WITH USECOUNT ON 'DBNAME'. The 'Enable Object Use Count' is grayed out when TSET is connected to TD14.0 or earlier versions. Guide, Release

38 5: Session Options Export Plans in XML and Export Dynamic Plans are mutually exclusive options. Select either option for a manually entered query. Either a dynamic plan or a QCD XML plan can be captured. 3. Click Apply. 4. [Optional] To continue customizing a session, select another tab in the Options dialog box. 5. To return to the main window, click OK. Creating Restricted Views Restricted DBC database views can be created to limit access to information. Restricted DBC views are identified by the suffix X and are called X views. Teradata SET uses restricted views to restrict access to data dictionary information and QCD data the logged in user owns or has access to. Beginning with Teradata Database , each system view in the DBC database includes a view that supports Unicode. All Unicode system views are identified by a suffix, V or VX, when a restricted Unicode view is used. To learn more about X views, V views, and VX views, see Data Dictionary (B ) and Database Administration (B ). Additional restricted views required by Teradata SET must be created in Teradata Database. Teradata SET creates restricted views from a script file. There are five versions of the script file: DBCXViews62.bteq; used on Teradata Database V2R6.2, V2R6.1, or V2R6.0 DBCVXViews120.bteq; used on Teradata Database DBCVXViews130.bteq: used on Teradata Database and Teradata Database DBCVXViews140.bteq: used on Teradata Database 14.0 DBCVXViews141.bteq; used on Teradata Database and higher The script files are located in the Teradata installation folder; for example, C:\Program Files(x86)\Teradata\Client\16.20\bin\DBCVXViews141.bteq To create restricted views: 1. Start Teradata SET Select Tools > Options from the menu. The Options dialog box appears. 3. Select the Customize tab. 4. Select Use X views (DBC and QCD). 5. Connect to the database. A confirmation message appears. Guide, Release

39 5: Session Options 6. Click Yes to create the restricted views. Connectivity Options Use the Connectivity tab to choose the interface used to connect to a Teradata Database. It is not necessary to connect to Teradata Database for this procedure. Selecting a Connectivity Type 1. From the main window, click Tools > Options. The Options dialog box appears with the Customize tab selected by default. 2. Click the Connectivity tab. 3. Select a connection type: ODBC or CLIv2. 4. Click Apply. 5. [Optional] To continue customizing a session, select another tab in the Options dialog box. 6. To return to the main window, click OK. Directory Options Use the Directory tab to specify the directory and file in which exported emulation information is saved. It is not necessary to connect to Teradata Database for this procedure. Guide, Release

40 5: Session Options Selecting a Path for Saved Information 1. From the main window, click Tools > Options. The Options dialog box appears with the Customize tab selected by default. 2. Click the Directory tab. 3. To specify a folder in which to save exported information, do one of the following: a. Type a complete path name in the Path box. b. Select a folder from the Browse for Folder dialog box: Click Browse. Select a folder under Choose Folder. Click OK. 4. Click Apply. 5. [Optional] To continue customizing a session, select another tab in the Options dialog box. 6. To return to the main window, click OK. Error-Handling Options Use the Error Handling tab to specify how errors are handled. It is not necessary to connect to Teradata Database for this procedure. Setting Error-Handling Options 1. From the main window, click Tools > Options. The Options dialog box opens with the Customize tab selected by default. 2. Click the Error Handling tab. Guide, Release

41 5: Session Options 3. Select one or more of the check boxes in the Error Handling tab. Option Description General Applies to export, import, or undo import (cleanup) operations. Log only failures in Summary Report Ignore Teradata Database errors Log the failed operations into the summary report. View the log file to determine the cause of any failures. Prevent Teradata Database error messages from being displayed while performing export, import, or undo import (cleanup) operations. Review the log file for information about the errors. Automatically grant missing access privileges Revoke access privileges Automatically generate the SQL statement to grant the necessary privileges. If selected, the Grant access privilege dialog box is not displayed. Instead, the SQL statement required to grant the necessary privileges is automatically generated and submitted. To revoke the access privileges granted from TSET. Guide, Release

42 5: Session Options Option Grant access privileges on database Description TSET generates SQL statement to grant the necessary privileges on the required database instead of on a particular object reported on missing access privilege error message. Import Applies only to import operations. Depending on other settings selected under Import, some errors might display. For example, if the Display Object exists dialog check box is selected, an error appears if a table that is being imported already exists on the system. If this check box is not selected, all Teradata Database error messages appear. Display Failed SQL statement dialog Display the SQL Statement Failed dialog box. Use this dialog box to do one of the following: Abort the import. Ignore the error and continue importing. Enter SQL to correct insufficient privileges or permanent space errors and then retry the failed statement. Teradata Database errors that can be retried include: Clear the check box to prevent the SQL Statement Failed dialog box from appearing. These errors are automatically ignored during future import operations. See Retrying Failed Import Operations. Display Object exists dialog Display a message that the importing object already exists on the machine during import of object definitions and ask if the object should be overwritten using one of the following: Yes Yes To All No No To All Cancel Clear the check box to prevent the Display Object Exists dialog box from appearing and to make the Option box available. Automatic message responses are sent based on the option selection in the Option box. Option Set automatic message response. Automatic message responses are sent based on the option selected: Yes To All. Drop all existing objects, and recreate all exported objects. No To All. Do not drop existing objects, and continue with the import operation. Cancel. Automatically abort the import operation if any objects already exist. Guide, Release

43 5: Session Options Option Description Clear the Display Object exists dialog check box to prevent the Display Object Exists dialog box from appearing and to make the Option box available. Prompt to create nonexisting QCDs/DBQLs Receive a message prompt to create a QCD/DBQL database if the target QCD/DBQL database does not exist during import of QCD/ DBQL database related information. Display duplicate primary key error Clear this check box to automatically create a target QCD/DBQL database without being prompted. Applies only during import of RAS; workloads; or cost parameters, Database System (DBS) Control information, and cost profiles. Random AMP Samples Prompt with a dialog box that requests a new system name or RAS tag if a duplicate prime key error occurs while importing RAS. Clear this check box to cause the import operation to fail due to duplicate prime key errors if the rows already exist on the import system. Select the Use the new tag for the rest of the RAS import check box to use the new RAS tag if duplicate primary key errors occur in the rest of the import of the RAS rows. Clear the check box to display the same dialog box for all RAS tags when the duplicate primary key error occurs. Workloads Prompt with a dialog box that requests a new workload name if a duplicate prime key error occurs while importing workloads. Clear this check box to cause the import operation to fail due to duplicate prime key errors if a workload already exists in the target QCD. Cost Parameters, DBS Control and Cost Profile records Prompt with a dialog box that requests a new cost tag if a duplicate prime key error occurs while importing cost parameters, DBS Control information, and cost profiles. Clear this check box to cause the import operation to fail due to any duplicate prime key errors if rows already exist on the import system. Dynamic Plans Prompt with a dialog box that requests a new Request tag, if a secondary uniqueness violation condition occurs while importing a dynamic plan. Clear this check box to cause the import operation to fail due to any secondary index uniqueness violation, if a dynamic plan with the same system and request name exist on the import system. 4. Click Apply. 5. [Optional] To continue customizing a session, select another tab in the Options dialog box. 6. To return to the main window, click OK. Guide, Release

44 6 Export Methods and Options Export Methods and Options Teradata SET is used to quickly capture (export) emulation information, which can be edited, and then import the information to a test system in order to imitate the target system. For example, using system information exported from a target system with four nodes, cost parameters and execution plans can be analyzed on the test system as if it also has four nodes. See Import Methods and Options. The Export feature can be customized to ensure that the test system imitates the features of the target system being analyzed (see Export Options). The steps below provide an overview of the export process: 1. Before exporting emulation data, connect to a Teradata Database. See Connect to a Teradata Database. 2. Select an export method: Query: To identify database objects for export using one or more data manipulation language (DML) statements. See Export by Query. Database: To select database objects for individual export. See Exporting by Database. Workload: To identify database objects for export based on an existing workload definition. See Exporting by Workload. 3. Customize the export operation. See Export Options. 4. Export the information needed to emulate the target environment on the test system. The following topics explain how to use Teradata SET to capture information from a target system: Export by Query Exporting by Database Exporting by Workload Export Options Viewing the Estimated Export Time Export by Query This export method uses DML statements to identify database objects to export. The export-byquery operation uses the SHOW QUALIFIED statement; therefore, use only DML statements as input. In other words, do not use Data Definition Language (DDL) statements. TSET is enhanced to support queries calling stored procedures in the release. TSET parses the queries entered in Export by Query interface to determine if there are any queries calling stored procedures. Such queries are separated out and SHOW QUALIFIED is not submitted for those queries. Objects referred to in the Stored Procedures are retrieved by submitting SHOW PROCEDURE. For more Guide, Release

45 6: Export Methods and Options information about the SHOW statement and restrictions, refer to SQL Data Definition Language (B ). Exporting by Query 1. From the main window, click. The Export from Teradata Database dialog box appears. 2. Click Query. 3. In the File name box, type a file name for the exported emulation information. By default, the File Name box displays the name of the target system specified when connecting. See Connect to a Teradata Database. 4. Specify a path to the folder in which to save the file by doing one of the following:. Type a path in the In folder box Click Browse to locate a destination folder using Windows Explorer. By default, the In Folder box displays the path specified in the Options dialog box. See Directory Options. 5. Click OK. The Export By Query dialog box appears. 6. Define the default database for running queries by doing one of the following: Type the name of the database in the Default Database box. Click to select a database from the list. Guide, Release

46 6: Export Methods and Options If adding a query and the database, tables, and view names in the new query are fully qualified, it is not necessary to select a database. 7. In the QCD Name box, do one of the following: Type the database name. Click to select a database from the list. 8. Select queries using any of the following options: Typing a Query Manually Loading a Query from a File Loading a Query from a QCD Loading a Query from DBQL Loading a Query from IPE Plans List 9. In Export Options, select the appropriate check boxes to define the exported information. See Export Options. 10. [Optional] To further define the selected export options for the query, click Options. The Export Options dialog box appears. The options available in the dialog box depend on the selections made under Export Options in the Export By Query dialog box. See Export Options. If a selected query contains a problem, clicking Options displays a Warnings dialog box. To resolve the warning, change the query or remove it from Selected Queries. 11. [Optional] To customize the headings under Selected Queries: a. Right-click on the heading row. b. Select a command from the shortcut menu. Selected Queries Default Database EDW EDW EDW Copy Find... Hide/Show Columns... e Query Text SELECT L_RETURNFLAG [FORMAT 2 x[1 SELECT S_ACCTBAL, S_NAME [FORMA SELECT L_ORDERKEY, SUM[L_EXTENS Select All Clear All Export Options All Objec Save As... Print... Samples Execution Plans Statistics Cost Parameters Demographics Cost Profiles Options [Optional] Click Estimate Time to view an estimate of the time needed to export each object. See Estimate-Time Rights and Viewing the Estimated Export Time. 13. Click to begin the export process. Guide, Release

47 6: Export Methods and Options The export-by-query operation uses the SHOW QUALIFIED statement. To avoid errors, only input DML statements, not DDL statements. If there is an error, a Warning dialog box appears. Modify the statement before restarting the export operation. After the export operation completes, a summary report of the export operation results appears. See Viewing a Summary Report. Queries which call stored procedures are separated out before submitting SHOW QUALIFIED. The separated queries (calling Stored Procedures) are parsed to get the Stored Procedure object and SHOW PROCEDURE is submitted to retrieve the Stored Procedure Object Definition. Nested Stored Procedures are also captured. Typing a Query Manually 1. In the Query box, type a valid query. See Perform Query Testing. 2. Click Add to move the query to Selected Queries. To remove a query, select the query and click Remove. 3. [Optional] To enter another query: a. Click Clear to erase the text in the Query box. b. Type another query. c. Click Add. 4. Under Export Options, select check boxes to define the exported information. See Export Options. Loading a Query from a File 1. Click Open Query. The Open dialog box appears. Guide, Release

48 6: Export Methods and Options 2. Select a file. 3. Click Open. All of the queries in the selected file are added under Selected Queries in the Export By Query dialog box. To remove a query, select the query and click Remove. 4. Under Export Options, select check boxes to define the exported information. See Export Options. Loading a Query from a QCD 1. Click Browse QCD. The Query Capture Database dialog box appears. Guide, Release

49 6: Export Methods and Options 2. Select one or more queries by doing one of the following: Select one query. Hold Shift or Ctrl while selecting multiple queries. Click Select All to select all of the queries. 3. Click OK. All of the selected queries are added under Selected Queries in the Export By Query dialog box. To remove a query, select the query and click Remove. 4. Under Export Options, select check boxes to define the exported information. Query text is retrieved from the QCD specified in the QCD Name box. If the Execution Plans check box is selected, the query plan also is retrieved from the database named in the QCD Name box. See Export Options. Loading a Query from DBQL 1. Click DBQL Plans. The DBQL Plans dialog box appears. Guide, Release

50 6: Export Methods and Options 2. In the Selection box, do one of the following. Select DBQL (default) to browse XML queries from the DBQL. Select External Database to browse XML queries from an external database. 3. [Optional] Click DBQL Filter Options. The Select Criteria dialog box appears. 4. Enter data in the Select Criteria dialog box. Option Step Count Description The minimum number of steps for the queries received from the DBQL. Guide, Release

51 6: Export Methods and Options Option Result Rows Select Users and Accounts Description The minimum number of rows returned for the queries retrieved from the DBQL. Click to open the Select Users and Accounts dialog box and browse queries submitted by a set of users or accounts. To select a user, enter the user name in the Select User box and then click Add. You can also click List Users to list all users in the Select User list box. Select a name and then click Add. To select an account, enter an account in the Select Account box and then click Add. You can also click List Accounts to list all the accounts. Select an account and click Add. To remove users or account names from the lists, select the user or account name in the list, and then click Remove. Select Criteria Start Date End Date Start Time End Time Enter the date in the MM/DD/YYYY format to search for queries started on or after the specified date. If no start date is specified, all statements from the DBQL are loaded. Enter the date in the MM/DD/YYYY format to search for queries ending on or before the specified date. If a start date is specified but no end date is specified, all statements from the DBQL beginning on the start date and ending on the current date are loaded. Enter the time in the HH:MM:SS format to search for queries on or after the specified start time. If no start time is specified, the default start time of 00:00:00 is used. Enter the time in the HH:MM:SS format to search for queries on or before the specified end time. If no end time is specified, the default end time of 13:59:59 is used. Select QueryBand Name Value List Names Add Rem Name-Value Filter The name of a Query Band Name-Value pair. For more information about SET QUERY_BAND, refer to SQL Data Definition Language (B ). The value of a Query Band Name-Value pair. Click to list all the Query Band Names in the Name-Value list. Click to add the selected Query Band Name-Value pair to the Name-Value list. Click to remove the selected Query Band Name-Value pair from the Name- Value list. The combination of the Name and Value entries (Name-Value pair). Click to filter out some of the Query Band Name-Value pairs. 5. Click OK to close the Select Criteria dialog box and return to the DBQL Plans dialog box. 6. Click Browse DBQL to load the XML queries from DBQL to add to the Query List. 7. Select one or more queries by doing one of the following: Guide, Release

52 6: Export Methods and Options Select one query. Hold Shift or Ctrl while selecting multiple queries. Click Select All to select all of the queries. 8. Click OK to add the XML queries to the Select Queries list in the Export by Query dialog. 9. Under Export Options, select check boxes to define the exported information. See Export Options. Loading a Query from IPE Plans List 1. Click IPE Plans. The Dynamic Plans dialog box appears. 2. Select one or more queries by using one of the following options: Select one query. Hold Shiftor Ctrl while selecting multiple queries. Click Select All to select all queries. 3. Click OK. All selected queries are added under Selected Queries in the Export by Query dialog box. To remove a query, select the query and click Remove. 4. Under Export Options, select check boxes to define the exported information. Query text is retrieved from the XML Plan document available in SystemFE.Opt_XMLPlan_Table. See Export Options. Guide, Release

53 6: Export Methods and Options Specifying USING Clause Values For queries that the user inputs manually or selects from a file, TSET submits a DUMP EXPLAIN or INSERT EXPLAIN query to export execution plan information. If the query includes the USING clause, TSET displays the Input using values to capture specific plan screen. Input Using Values to Capture Specific Plan Use this screen to specify values for the USING clause shown for each selected query. The Using Variables fields display data in the Name field and Datatype field. 1. Enter data values in the Value column for each query listed in the Using Query edit box. 2. Choose one of the following: Click OK to export specific execution plans that contain values for the USINGclause. Click Ignore to capture generic execution plans. Click Ignore All to capture generic plans for all other export queries containing the USING clause. Exporting by Database Use the export-by-database method to select database objects for individual export and to define the information to export. 1. From the main window, click. The Export from Teradata Database dialog box appears. 2. Click Database. 3. In the File name box, type a file name for the exported emulation information. Guide, Release

54 6: Export Methods and Options By default, the File name box displays the name of the target system specified when connecting. See Connect to a Teradata Database. 4. Specify a path to the folder in which to save the file. By default, the In Folder box displays the path specified in the Options dialog box. See Directory Options. 5. Click OK. The Export By Database dialog box appears. 6. Define the export source by choosing one of the following: Choice Export from an entire database or from a user Action Do one of the following: Enter the name of the database or user in the Specify Export Database box. Click to select a database or user from the Specify Export Database list. The Execution Plans check box is unavailable, by default, unless a database in List of Objects pane is marked as a QCD, or a database is selected from the Specify Export Database list and the Query Capture Database check box is selected. Guide, Release

55 6: Export Methods and Options Choice Export from an individual database object Find a database object Action a. In the List of Objects pane, select the object. b. Click Add to move the object to the Selected List pane. c. Repeat the previous two steps until all of the required objects are in the Selected List pane. To find a database object, do the following: a. Click on an object in the List of Objects pane. b. To search in the selected list of objects, click on an object in the Selected Lists pane. c. Click Find Object. The Find dialog box appears. d. Enter an object name in the Find what field. e. Select any other find options on the dialog box, and then click Find Object. f. Click Add to move the object to the Selected List pane. To remove an object from the Selected List pane, select it and click Remove. Add multiple databases for export a. Specify the database or user in the Specify Export Database in either of the following ways: Enter the name of the database or user in the Specify Export Database box. Click the browse button to select a database or user from the Specify Export Database list. b. Click Add to move the object to the Selected List pane. If the Add button is not clicked, after specifying the database or user in the Specify Export Database box, only the database specified in the Specify Export Database box is available for export. Add multiple query-capture databases for export a. Select the check box Query Capture Database. b. Specify a query-capture database in the Specify Export Database box in either of the following ways: Enter the name of the query-capture database in the Specify Export Database box. Click the Browse button to select a query-capture database from the Specify Export Database list. c. Click Add to move the object to the Selected List pane. After selecting the Query Capture Database check box, and clicking the Browse button, only query-capture database names populate the Specify Export Database list. If the Query Capture Database check box is deselected and the Browse button is clicked, all database names populate the Specify Export Database list. If the Add button is not clicked after specifying a query-capture database in the Specify Export Database box, only the query-capture database names specified in the Specify Export Database box are available for export. 7. [Optional] Under Export Options, select check boxes to define the exported information. See Export Options. Guide, Release

56 6: Export Methods and Options 8. [Optional] To further define the selected export options, click Options. The Export Options dialog box appears. The options available in the dialog box depend on the selections made under Export Options on the Export By Database dialog box. 9. [Optional] To mark a database as a QCD, do the following: a. In the List of Objects pane, right-click the name of a database to display the shortcut menu. b. Click Mark as QCD. The Execution Plans check box under Export Options is available only when the database is marked as a QCD. 10. [Optional] Click Estimate Time to see the estimated time required to process the export request. See Estimate-Time Rights and Viewing the Estimated Export Time. 11. Click Export to begin the export process. After the export operation completes, a summary report of the export operation results appears. See Viewing a Summary Report. Exporting by Workload Use this export method to choose a QCD database and multiple workloads for export and to define the details for the specific emulation information to capture. 1. From the main window, click. The Export from Teradata Database dialog box appears. 2. Click Workload. 3. In the File name box, type a file name for the exported emulation information. By default, the File Name box displays the name of the target system specified when connecting. 4. Specify a path to the folder in which to save the file. By default, the In Folder box displays the path specified in the Options dialog box. See Directory Options. 5. Click OK. The Export By Workload dialog box appears. Guide, Release

57 6: Export Methods and Options 6. Select a QCD database to be the source of the workload information by doing one of the following: Type the name of the database in the QCD Database box. Click to select a database from the QCD Database list. 7. [Optional] To load index recommendations for the selected workload, do one of the following to specify the workload: Specify the workload by... a. Typing the workload name in the Workload box. b. Pressing Enter. Specify the workload by... Clicking the Workload arrow to select a workload from the list. 8. [Optional] To view the statements that make up a workload: a. Under Workload Information, right-click the workload name. b. Click View Workload. The View Workload dialog box appears. 9. [Optional] To move an index recommendation from Workload Information to Selected Workload: a. Under Workload Information, select a row. b. Right-click the row to display the shortcut menu. c. Click Add. 10. [Optional] To remove a workload from the export operation: a. Under Selected Workloads, select a row. Guide, Release

58 6: Export Methods and Options b. Click Remove. For a workload without any recommendations, the Index tag and Recommendation Time boxes are empty. 11. [Optional] To customize the headings under Workload Information or Selected Workload: a. Right-click the heading row. b. Click Hide/Show Columns. c. Select headings to hide or show. 12. [Optional] Under Export Options, select check boxes to define the exported information. See Export Options. 13. [Optional] To further define the selected export options, click Options. The Export Options dialog box appears. The options available in the dialog box depend on the selections made under Export Options on the Export By Workload dialog box. 14. [Optional] Click Estimate Time to see the estimated time required to process the export request. See Estimate-Time Rights and Viewing the Estimated Export Time. 15. Click Export to begin the export process. After the export operation completes, a summary report of the export operation results appears. See Viewing a Summary Report. The Partition Tag column in the workload information and selected workloads displays the partition recommendation tag name. When a partition recommendation tag is displayed, the Index Tag column is blank. When the Index Tag column displays an index tag, the Partition Tag column is blank. Export Options This section describes the purpose of each check box and explains how to use each option. Check boxes also can be used in combination. Select check boxes under Export Options, located in the export dialog boxes (Export By Query, Export By Database, and Export By Workload), to define the information exported from a target system. Availability of the check boxes varies according to the type of export selected. Guide, Release

59 6: Export Methods and Options When exporting by query and either typing a query manually or loading a query from a file, the execution plans are captured and exported depending on the options selected for Execution Plans, Export Plans in XML (Customization option), Export Dynamic Plans(Customization option), and Demographics as described below. Export Dynamic Plans Export Plans in XML Execution Plans Demographics Description Unchecked Checked Checked Unchecked INSERT EXPLAIN in XML captures the plan into a QCD database and deletes it after the export operation. Unchecked Unchecked Checked Unchecked DUMP EXPLAIN captures the plan. Unchecked Checked or Unchecked Checked Checked INSERT EXPLAIN captures the plan into a QCD database and deletes it after the export operation. Checked Unchecked Checked Irrelevant IPE Plan is captured in SystemFE.Opt_XMLPlan_Table. During an import operation, the QCD plans are imported into the database listed in the QCD Name box. The DBQL Plans are imported into the external DBQL Database. Dynamic Plans are imported into SystemFE.Opt_XMLPlan_Table. If the Execution Plans check box is selected and the Export table data used by query optimization check box is selected when customizing options (see Customization Options for more information), table data used by query optimization is captured. For more information, refer to SQL Request and Transaction Processing (B ). Click Options, when available, to display the Export Options dialog box and modify the default settings for the following: Cost parameters Cost profiles Demographics RAS After defining the options, Teradata SET can be used to estimate how long the export will take given the options selected. See Viewing the Estimated Export Time. For a description of each option, see the following sections. All Select the All check box to capture all of the elements listed in the dialog box except demographics. This option can be used to capture the TLE information (or black-box test environment) of specific, problem-causing queries to simulate the production environment on a test system for debugging. To include demographics, select the Demographics and All check boxes. See Changing the Demographics Export Options. Guide, Release

60 6: Export Methods and Options Changing the Cost Parameters Export Options Select the Cost Parameters check box to export the Optimizer environmental cost parameters and DBS Control information from a target system. Cost parameters are captured from the system Globally Distributed Object. 1. From an export dialog box, click Options. The Export Options dialog box appears. 2. [Optional] In the Cost tag box, type a new file name. By default, the Cost tag box displays the file name entered when choosing an export method in the Export from Teradata Database dialog box. 3. To capture cost data from specific rows, click Select Rows. The Export Cost Parameters dialog box appears. 4. Select a method for exporting cost parameters. Option Capture from Source Description Export cost parameters from SystemFE.Opt_Cost_Table for the selected rows. Cost parameters and related DBS Control information is exported after parameters are captured from the target system. Guide, Release

61 6: Export Methods and Options Option Capture Current Costs Set Costs Description Export the cost parameters and DBS Control information from the target system. A row is inserted into SystemFE.Opt_Cost_Table and SystemFe.Opt_DBSCtl_Table using the cost tag specified in the Cost tag column. The row is exported and then deleted from SystemFE.Opt_Cost_Table and SystemFe.Opt_DBSCtl_Table after the export process is complete. Set and then export the cost parameters for a given row. This option is available only when an entry exists in SystemFE.Opt_Cost_Table. Only one cost parameter can be set for a system. It ensures that the Optimizer ignores the current system parameters and uses the new parameters when generating an execution plan. Using this option is similar to using a DIAGNOSTIC SET COST statement. This option is available only when exporting by query. TLE must be turned on before setting cost parameters. Be aware that TLE might cause system performance degradation. For more information about TLE, refer to SQL Request and Transaction Processing (B ). 5. Click OK to close the Export Cost Parameters dialog box and return to the Export Options dialog box. 6. Click OK to close the Export Options dialog box. Changing the Cost Profiles Export Options Select the Cost Profiles check box to export cost profiles from a target system. 1. From an export dialog box, click Options. The Export Options dialog box appears. 2. [Optional] In the Profile Name box, type a new file name. By default, the Profile Name box displays the file name entered when choosing an export method in the Export from Teradata Database dialog box. 3. To capture specific cost profiles, click Select Rows. The Export Cost Profiles dialog box appears. Guide, Release

62 6: Export Methods and Options 4. Define the way that cost profiles are exported. Option Capture from Source Capture Current Cost Profile Set Cost Profile Description Export cost profiles from DBC.CostProfiles_v. This option exports cost profiles after capturing the profiles from the target system. Export the active cost profile from the target system. Set and then export the cost profile. Only one cost profile can be set for a system. Using this option is similar to using a DIAGNOSTIC SET PROFILE statement. This option is available only when exporting by query. TLE must be turned on before setting a cost profile. Be aware that TLE might cause system performance degradation. For more information about TLE, refer to SQL Request and Transaction Processing (B ). 5. Click OK to close the Export Cost Profiles dialog box and return to the Export Options dialog box. 6. Click OK to close the Export Options dialog box. Guide, Release

63 6: Export Methods and Options Changing the Demographics Export Options Select the Demographics check box to export information about tables (demographic data). Demographics can only be captured and imported when a QCD is specified during an export operation. Captured demographics are collected in the specified QCD. To export demographics information in addition to the information exported when All is selected, select the Demographics check box. Depending on the type of export operation performed, this feature either captures demographics of the tables and indexes referenced in a query or samples of all of the tables in a given database. 1. From an export dialog box, click Options. The Export Options dialog box appears. By default, the Demographics Source box displays the name of the active QCD. 2. Click Select Tables. The Export Demographics dialog box appears and displays a list of the tables selected for export. 3. Define the way that demographics are exported. Option Capture from QCD database Description Export demographic rows, if available, from the active QCD source for the elements (objects) specified in the Demographics Source box. If rows do not exist for the selected elements, current demographics are collected into the QCD source, exported, then deleted from the QCD source. Guide, Release

64 6: Export Methods and Options Option Capture Current Demographics Description Export current demographics into the QCD source that is specified in the Demographics Source box. If demographics for a table exist, the row is updated. If demographics for a table do not exist, the demographics inserted into the QCD are deleted after the row is exported. 4. [Optional] To view a graph or chart of the demographics for a selected table: a. Select a row under Select Rows. b. Click View Demographics. The Demographics interface opens. Use the interface to display demographic data in various formats. For more information about the Demographics interface, refer to Teradata Index Wizard User Guide (B ). 5. Click OK to close the Export Demographics dialog box and return to the Export Options dialog box. 6. Click OK to close the Export Options dialog box. Execution Plans Select the Execution Plans check box to export (in relational format) the Optimizer execution plans that are created for queries. A DUMP EXPLAIN script of the queries also is captured. Execution plans are selected for export based on the type of export operation: by query, by database, or by workload. When the Execution Plans check box is selected, Explain Text, Step Report, and Summary Information are also captured and displayed in the Import window. Exporting Execution Plans When Exporting by Query 1. From the Export by Query dialog box, click next to the QCD Name box. 2. Select a QCD from the QCD Name list. 3. Select the Execution Plans check box. Execution plans can only be exported and imported when a QCD is specified for the export operation and the Execution Plans and Demographics check boxes are selected. If selected, demographics information is collected in the QCD. An execution plan will not be captured for queries calling Stored Procedures. Guide, Release

65 6: Export Methods and Options Exporting Execution Plans When Exporting by Database When exporting by database, there are two ways to capture execution plans. 1. Specify a database: a. From the Export by Database dialog box, click next to the Specify Export Database box. b. Select a QCD database. c. Select the Query Capture Database and the Execution Plans check boxes. 2. Select a QCD database: a. From the Export by Database dialog box, select a QCD database from the List of Objects pane. b. Right-click the row to display a shortcut menu. c. Select Mark as QCD. d. Select the Execution Plans check box. Exporting Execution Plans When Exporting by Workload 1. From the Export by Workload dialog box, click next to the QCD Database box. 2. Select a QCD database. 3. Select the Execution Plans check box. Object Definitions Select the Object Definitions check box to export the data model and the DDL text of selected objects or the objects referenced by a given query. Use this option to export the details of the structure and instances of the objects used by a given query. Exported object definitions are used to create the tables, views, macros, triggers, indexes, stored procedures, User Defined Functions (UDFs), and UDTs on a test system. Object definitions are selected for export based on the type of export operation. When exporting by query, selecting the Object Definitions check box exports the UDFs and UDTs returned by the SHOW QUALIFIED statement on the query. When exporting by database, selecting the Object Definitions check box exports the UDTs referenced by objects added for export and the UDTs added manually for export. When exporting by workload, selecting the Object Definitions check box exports the UDFs and UDTs returned by the SHOW QUALIFIED statement on the queries. Guide, Release

66 6: Export Methods and Options While exporting XSP/UDFs, TSET retrieves only the CREATE/REPLACE PROCEDURE/ FUNCTION DDL, as TSET cannot retrieve XSP/UDF code files (source, header, or object). The user must supply the XSP/UDF code files. TSET displays the File Open Dialog screen for browsing the XSP/UDF code files during export. The screen title includes the XSP/UDF filename for C and C++ XSP/UDFs. For JAVA XSP/UDFs, the JAR_ID and Java ClassName are included in the screen title. The supplied XSP/UDF code filenames are copied to the Export path. If C and C++ XSP/UDF code files are not copied to the export path, the pack operation fails. If Java XSP/UDF code files are not copied to the export path, the pack operation does not fail, but the Java XSP/UDF code files must be moved manually from the production system to the test system. Missing code files are displayed at the end of the export operation, and before an import operation. QCD Data Select the QCD Data check box to export all execution plans, workloads, QCD statistics, and demographics from a QCD database. This option applies only to databases marked as QCD when defining the export-by-database operation. At least one database must be marked as QCD for this option to be available. This option applies only to QCD databases with QCF version or later. Random AMP Samples Select the Random AMP Samples check box to export the data distribution of a table on one or more randomly selected AMPs based on the type of export operation. When exporting by query, this option exports the RAS for the tables referenced by the specified queries. When exporting by database, this option exports the RAS of the tables selected for export. When exporting by workload, this option exports the RAS for the tables referenced by the workload queries. TLE must be turned on before setting RAS. Be aware that TLE might cause system performance degradation. For more information on TLE, refer to SQL Request and Transaction Processing (B ). Changing the RAS Export Options 1. From an export dialog box, click Options. Guide, Release

67 6: Export Methods and Options The Export Options dialog box appears. 2. [Optional] In the RAS tag box, type a new file name. By default, the RAS tag box displays the file name entered when choosing an export method in the Export from Teradata Database dialog box. No more than 128 tables can be selected in the current session. However, an unlimited number of rows can be exported from SystemFE.Opt_RAS_Table. 3. Click Select Tables. The Export Random AMP Samples (RAS) dialog box appears. 4. Under Select Table Names, do one of the following: Select the tables to export. Click Select All. 5. To define the way that RAS are exported, select an option. Guide, Release

68 6: Export Methods and Options Option Capture from Source Capture from AMPs Description Export RAS from SystemFE.Opt_RAS_Table and allow the use of RAS already added to SystemFE.Opt_RAS_Table. These samples can be added manually to SystemFE.Opt_RAS_Table using another tool, such as using the DIAGNOSTIC DUMP statement in Basic Teradata Query (BTEQ). Export samples from the target system. Use this option to export samples for the selected row directly from the AMPs. This option exports samples to SystemFE.Opt_RAS_Table using the RAS tag specified in the RAS tag box. The samples are deleted after the row is exported. If the row exists in SystemFE.Opt_RAS_Table, the Duplicate Random AMP Samples (RAS) dialog opens, enabling the user to select the required option. See Export Options for RAS Duplicate Keys. Set Samples Set the RAS for the selected row before exporting. This ensures that the Optimizer uses this set of samples when generating an execution plan. Only one RAS can be set for each table selected. This option is available only when exporting by query. 6. Click OK to close the Export Random AMP Samples (RAS) dialog box and return to the Export Options dialog box. 7. Click OK to close the Export Options dialog box. Export Options for RAS Duplicate Keys The screen below is referenced in the Capture from AMPs option in Changing the RAS Export Options. Duplicate Random AMP Sample Duplicate Random AMP Sample A RAS with SystemName hyvm20, DBName analysis, TableName t1 already Exists. Select an Option. Select Option Delete and Recollect Sample Export existing Sample from Opt_RAS_Table Ignore. Do not export this Sample OK Cancel Do not show this dialog again Guide, Release

69 6: Export Methods and Options Note that the option chosen is utilized for the remaining Duplicate Random AMP Sample. Option Delete and Recollect Sample Export existing Sample from Opt_RAS_Table Ignore. Do not export this sample Do not show this dialog again Description Deletes the existing stale Random AMP Sample (RAS), and exports RAS to SystemFE.Opt_RAS_Table. The row is deleted after export operation. Exports the existing sample. Skips the export of RAS for this tag. When checked, the Duplicate Random AMP Sample dialog box is not invoked for the remaining Duplicate RAS errors and the RAS export option chosen previously is used to resolve Duplicate RAS errors observed during the remaining export operation. Statistics Select the Statistics check box to export statistics based on the type of export operation. When exporting by query, this option exports the statistics that were collected (if any) for the database objects referenced in the selected list of queries. When exporting by database, this option exports the statistics of the database objects selected for the export, if any were collected. When exporting by workload, this option exports the statistics for the database objects referenced by the workload query. Workloads Select the Workload check box to export specific queries and recommendations for a workload. This option is available only when exporting by workload. See Exporting by Workload. MH Maps-Multiple Hash Maps Select the MH Maps check box to export Maps based on the type of export operation. TSET captures the Map information and exports it. When exporting by query, this option exports the Maps for the database objects referenced in the select list of queries. When exporting by database, this option exports the Maps of the database objects selected for the export. When exporting by workload, this option exports the Maps of the database objects referenced by the workload queries. Guide, Release

70 6: Export Methods and Options In addition to the Maps of the database objects, TSET captures the System and User Maps and exports them. The User Maps corresponding to the selection from the Original User drop-down combo are exported. Viewing the Estimated Export Time After an export is defined (see Export Options), Teradata SET can be used to estimate how long it will take to run the export operation. If the estimate is high, the export parameters can be defined or the operation can be run at a more convenient time. The estimate-time function is available for all export methods. Specific privileges and a connection to a Teradata Database are required. See Estimate-Time Rights. 1. Go to one of the following: Export by Query dialog box Exporting by Database dialog box Exporting by Workload dialog box 2. Click Estimate Time. The Estimated Time dialog box appears and displays time estimates for each object being exported plus a total estimated time for the export operation. Estimated Time: Total Estimated Time: 00:36:50:55 Estimated Time Breakdown Option Object Definitions Statistics Random AMP Samples Cost Parameters Object Type Table View Macro Join Index Estimated Time 00:22:04:80 00:07:04:12 00:07:41:00 00:00:00:63 Count OK Refresh 3. Click Refresh to view estimates of the time needed to export each object. 4. Click OK to close the Estimated Time dialog box. 5. [Optional] When exporting by query, a query can be removed or the estimated time for a selected query or queries can be viewed: a. Under Selected Queries, right-click the row. Guide, Release

71 6: Export Methods and Options b. Select a command from the shortcut menu. Guide, Release

72 7 Import Methods and Options Import Methods and Options Use the import function to import emulation information to a test system where query plan analysis can be performed. To prepare for an import operation: 1. Read or review this topic. 2. Connect to a Teradata Database. 3. Perform an export operation (see Export Methods and Options). The following topics explain Teradata SET import functions and options: Importing to a Test System Changing Import Options Specifying Objects for Import Changing the RAS Byte Order Editing Import Information Changing the Permanent Space Retrying a Failed SQL Statement Editing Information Offline Saving Changed Information Displaying Existing Databases Renaming a Target Database Undoing Target Database Renaming Reordering Databases Viewing Machine Configuration Viewing Estimated Import Time Importing to a Test System The Import feature can be customized in a variety of ways to maximize the usefulness of the test system. Overview 1. Before importing data, connect to a Teradata Database. 2. Select an export method. See Export Methods and Options. 3. Export the information needed to emulate the target environment on the test system. See Export Methods and Options. Guide, Release

73 7: Import Methods and Options 4. Import the information to the test system, modifying the import options if necessary. See Import Methods and Options. 5. Manage the imported data by doing the following (see Administrative Functions): Remove emulation information. Delete files. data to another location. Troubleshoot the import and export processes. A.mcf file is created when emulation information is exported from a target system. This file includes pointers to the raw data files that are also created during export. During an import operation, the data in these files is applied to the default location specified in the following table. Import Item Default Import Location Change Location Cost parameters SystemFE.Opt_Cost_Table and Opt_DBSCtl_Table No Cost profiles Data Dictionary No Demographics Export Demographics Source Yes Execution plans Export QCD Yes Object definitions Export database Yes RAS SystemFE.Opt_RAS_Table No Statistics Data Dictionary No Workload data Export QCD Yes Multiple Hash Maps SystemFE.Opt_Map_Table SystemFE.Opt_MapRel_Table No To change the owner of databases or users, use the Parent Database box in the Import Options dialog box. To change the QCD, use the Target QCD box in the Import Options dialog box. See Changing Import Options. To change the location or target database where objects are created, use the Rename function in the Import window. See Renaming a Target Database. Importing Emulation Information to a Test System Prerequisite: Before proceeding, connect to a Teradata Database, and perform an export operation. Note the following: Guide, Release

74 7: Import Methods and Options To import C and C++ XSP/UDF code files that reside on the Client, the code files (source, header, or object) must be available in the Import path. Object files must have been generated to be compatible with the compiler/linker of the Database Server. The client-side XSP/UDFs cannot be imported with ODBC connectivity. To import C and C++ XSP/UDF code files that reside on the Sever, files must be copied to the appropriate path, as specified in the CREATE/REPLACE PROCEDURE/FUNCTION DDL, on the Server. If a path is unspecified, the files must be copied to the default path. Refer to Database Administration (B ) for default paths. To import Java XSP/UDF code files, the JAR file, supplied by the user during the export operation, must be registered using the external stored procedure SQLJ.INSTALL_JAR(). Registering the JAR file with the JARID and ClassName specified in the CREATE FUNCTION DDL can be done outside Teradata SET using a BTEQ session. Missing files are displayed before the Import operation. 1. From the main window, click. 2. From the Open dialog box, select the.mcf file to use when importing information. The preview pane (right pane) displays information about the file such as source system information. To close the preview pane, clear the Show Preview check box. Open Look in: My Recent Documents Desktop data jsspc1.mcf Exported By Database Source: jsspc1 Release: V2R Version: Date: Options: Object Definitions Cost Parameters DBSControl Information My Documents My Computer My Network Places File name: jsspc1.mcf Open Files of type: Control Files [.mcf] Cancel Show Preview A confirmation message displays the name of any missing file along with a statement that the corresponding option cannot be imported. Close the message box to open the Import window. 3. Click Open. The Import window opens and displays the file name in the title bar. Guide, Release

75 7: Import Methods and Options 4. In the left pane, select objects to import, such as a table. The Import menus and toolbar differ somewhat from those in the main window. See Import Window. 5. [Optional] Perform any of the following procedures before completing the import: Changing Import Options Specifying Objects for Import Changing the RAS Byte Order Editing Import Information 6. Click. A confirmation message appears. 7. Click Yes to start the import operation. If a database being imported does not exist on the test system, it is created before the database objects are imported into the database. The main window displays the status of the import operation. The message Import completed appears in the main window after the operation is completed. If error messages appear while importing object definitions, see Retrying Failed Import Operations. Guide, Release

76 7: Import Methods and Options 8. [Optional] View a summary report of the import operation results. 9. [Optional] Perform query plan analysis on the test system. Changing Import Options The characteristics of an import can be changed prior to importing information to a test system. 1. From the Import window, click. The Import Options dialog box appears. Import Options Parent Database Info Parent Database: DBC External DBQL Selection Target DBQL: QCD Selection Target QCD: Source Version: Current Version: QCF QCF Object Definitions Random AMP Samples Execution Plans QCD Data Cost Profiles Statistics Demographics Workloads Cost Parameters DBQL Plans MAPS Miscellaneous Options Only synchronize version of created tables Import original statistics collection timestamp OK Error Handling... Option Description Parent Database Info Parent Database Specify a database name to be the owner for any database or user created during the import operation. This option is available only when importing object definitions, demographics, execution plans, and workloads. External DBQL Selection Guide, Release

77 7: Import Methods and Options Option Target DBQL Description Specify the DBQL listed as the destination DBQL for the import of XML plans. This option is only available when importing DBQL XML Plans. If a target DBQL is not selected, then the DBQL Database from which the plans are exported becomes the target DBQL. If the target DBQL is DBC, the import is terminated. If the Target DBQL database specified does not exist, Teradata SET either prompts for the creation of the DBQL, or it automatically creates the DBQL depending on the selected import error handling options. See Error- Handling Options. QCD Selection Target QCD Specify the QCD listed as the destination QCD for the import operation. This option is available only when importing execution plans, QCD data, demographics, or workloads. If no target QCD is specified, the information is imported into the QCD from which it was exported. If the database does not exist, Teradata SET either prompts for the creation of the QCD or automatically creates the QCD, depending on the import error handling options. See Error-Handling Options. Source Version Current Version Display the QCF version number of the export system. Display the QCF version number of the system to which Teradata SET is connected. Import Options Object Definitions Random AMP Samples Execution Plans Create or define the database objects. Import RAS into SystemFE.Opt_RAS_Table. Import execution plans into a QCD. It is possible to import execution plans to a later version of Teradata Database. However, to import execution plans to an earlier version requires that a compatible-version QCD exist on Teradata Database. QCD Data Import index recommendations, workload definitions, and execution plans to the QCD specified in the Target QCD box. Guide, Release

78 7: Import Methods and Options Option Description This check box is available only if an export-by-database operation was performed for one or more databases marked as QCDs and the QCD Data check box was selected. To import only execution plans, clear the QCD Data check box and select Execution Plans. If the Target QCD box is left blank, the system creates QCDs with the same names as those used during export. Data is then imported into these QCDs. See Error-Handling Options. Cost Profiles Statistics Demographics Import cost profiles into the Data Dictionary. Import the statistics into the Data Dictionary. Import table demographics to the QCD specified in the Target QCD box. If the Target QCD box is left blank, the system creates QCDs with the same names as those used during export. Data is then imported into these QCDs. Workloads Import the workload definitions and any index recommendations to the QCD specified in the Target QCD box during export. This check box is available when exporting by workload. If the Target QCD box is left blank, the system creates QCDs with the same names as those used during export. Data is then imported into these QCDs. Cost Parameters DBQL Plans Maps Import system cost parameters into SystemFE.Opt_Cost_Table and import DBS Control information associated with the cost parameters. Import DBQL XML Execution Plans into a DBQL. Imports MAP information into SystemFE.Opt_Map_Table and SystemFE.Opt_MapRel_Table Miscellaneous Options Only synchronize version of created tables Only synchronize the version with the tables successfully created by Teradata SET during the import operation. If the check box is not selected, the QCD.RELATION table is synchronized with the version in the DBC.TVM table for all tables referred to in the execution plan queries. This feature is available only when the Object Definitions and Execution Plans check boxes are selected. Import original statistics collection timestamp Use the original timestamp value for all statistics data in the current import operation. Guide, Release

79 7: Import Methods and Options Option Description If the check box is not selected, all statistics data in the current import operation is imported using the current timestamp value. 2. [Optional] In the Parent Database box, do one of the following: Type an owner name for any databases or users created during the import operation. Click to load the available databases and select one from the list. By default, the Parent Database box displays the database name established when logging on. 3. [Optional] In the Target QCD box, specify the destination QCD for the import by doing one of the following: Type a QCD name in the Target QCD box. Click to load the available QCDs and select one from the list. 4. [Optional] Under Import Options, clear check boxes to exclude items from the import. This results in a partial import. Options are available only if they were included in the export. 5. [Optional] See Error-Handling Options. 6. Click OK to close the dialog box and return to the Import window. A appears next to the object in the left pane that corresponds to a selection made under Import Options in the Import Options dialog box. 7. [Optional] See Saving Changed Information. 8. [Optional] Click to start the import operation. See Importing to a Test System. Specifying Objects for Import Specific objects can be selected for import. Typically this is done when performing a partial import. In the Import window the following panes are available: The left pane (import tree) features an expandable view of the database objects, object definitions, statistics, and RAS that can be imported. The right pane provides information about any object selected in the left pane. For example, see the figure below. When an object definition is selected in the left pane, the associated information appears in the right pane. Guide, Release

80 7: Import Methods and Options Importing Selected Objects 1. From the Import window, click next to each database object in the left pane to expand the view. 2. Select the objects to import. A check mark next to an object indicates that the object is selected for import. A check mark appears next to every item by default. If there is no check mark next to an object, it is not available for import. To import an object that is not included in the list of available objects, see Changing Import Options. 3. Clear the check box next to any database object that is not intended for import. Clearing a check box at the parent level automatically clears all check boxes at the child level. Check boxes at the same child level can be selected separately. 4. [Optional] Save the import options for a future import operation. 5. [Optional] Click to start the import operation. Changing the RAS Byte Order If RAS are imported to a hardware platform with dissimilar byte layout, the RAS byte order cannot be determined and must be changed. Failing to change the byte layout can lead to incorrect interpretation of the data. Guide, Release

81 7: Import Methods and Options To ensure the NumRows data is correctly interpreted, specify the byte order of the source and target machines before initiating the import operation. Important: Use this procedure only when importing to a hardware platform with dissimilar byte layout. 1. From the Import window, click next to RAS Tags in the left pane to expand the view. 2. Right-click a RAS node and select RAS Byte Order. The RAS Byte Order dialog box appears. If the byte order for one table changes, it changes for all of the tables. 3. In the Source Machine Byte Order box, select one of the following: Little-Endian Big-Endian 4. In the Target Machine Byte Order box, select one of the following: Little-Endian Big-Endian 5. Click OK. 6. Make sure the check box located next to the RAS tag is selected so it is included in the import. 7. [Optional] Click to start the import operation. Editing Import Information The Windows editing commands, such as Find, can be used in the Import window to edit the text and tables. Edits are made in the right pane of the Import window. The following information is editable: Cost parameters, including DBS Control information Object definitions RAS Statistics Cost profiles 1. From the Import window, select an object in the left pane to edit. Corresponding information is displayed in the right pane. 2. Click. 3. Edit the information by doing one of the following: Double-click the information in the right pane in order to edit: Statistics RAS Cost parameters Guide, Release

82 7: Import Methods and Options DBS Control information Cost profiles Click under Object Definitions Information to edit object definitions directly. 4. Click. 5. [Optional] See Saving Changed Information to save the changes to a different file name. 6. [Optional] Click to start the import operation. Changing the Permanent Space Prerequisite: Before proceeding, connect to a Teradata Database, and perform an export operation. See Connect to a Teradata Database and Export Methods and Options. Teradata SET uses a formula to automatically calculate the permanent space (also called permspace) required for creating a database. Permanent space calculations are based on the number of objects selected and the space required for creating child databases. However, the amount of space calculated can be more or less than the system can spare. Follow the permanent space messages to correct this situation. Permanent space requirements can be specified before importing objects from a target system. Change the permanent space allotment to avoid messages about permanent space. 1. From the Import window, click. The Change PermSpace dialog box appears. Guide, Release

83 7: Import Methods and Options Change PermSpace Information The following figures indicate the permspace with which databases will be created. You may specify space to suit your need in User Specified Space. This cell is disabled for existing databases. After making the changes use Recalculate to recalculate the space and check for any warnings. Databases with warnings are displayed in bold font. Click the rows to see the warnings. Warnings Scale Factor[KB]: 32 Databases Query Capture Databases 1 2 Calculated Space[KB] DBC edw Calculated Space[KB] DBC User Specified Space[KB] Available Space [Existing Databases] MaxPerm-CurrentPerm[KB] Parent Database Available or Required Parent Database Space [KB] Check user specified space against child database(s) space Check and update parent database(s) space Clear user specified space Import Parent Database[KB]: DBC Space Available [KB]: Space Required: 512 OK Cancel Recalculate Existing databases are highlighted in blue. Space cannot be specified for existing databases. The only editable box is Scale Factor(KB). The only editable column is User Specified Space(KB). Option Information Warnings Scale Factor(KB) Databases Query Capture Databases Description Information about using the dialog box. For rows shown in bold, warnings about the database or QCD. Integral number used to automatically calculate space required to create the objects in a database. Change Scale Factor(KB) to a number between 1 and 100. The default is 32. Scale Factor(KB) has an effect on the value displayed in the Calculated Space(KB) column. Space requirements for the databases in the left pane (import tree). Space requirements for the QCDs in the left pane (import tree). Guide, Release

84 7: Import Methods and Options Option Database Name or Query Capture Database Description Name of the database that will be created during the import operation. The column label (Database Name or Query Capture Database) is determined by whether Databases or Query Capture Databases is selected. Calculated Space(KB) Space required to create the database, based on the number of objects selected in the left pane (import tree), including the calculated or userspecified space of any child databases. The space requirements for each database are based on the number of tables and objects selected in the left pane (import tree) and the space required for creating child databases. An approximation of the deficit space, determined by comparing the calculated space and the available space, appears in this column. User Specified Space(KB) Calculated space for the new database. If entered, this number overrides the Calculated Space(KB) value. If a discrepancy is found, a warning appears recalculated. If specifying space for a child database, it is considered when calculating the space required for the parent database. Minimum value is 0 KB. Maximum value is 2,097,151 KB. Right-click in this field for more options. Space cannot be specified for an existing database. Available Space (Existing Databases) MaxPerm- CurrentPerm(KB) Parent Database Available or Required Parent Database Space(KB) Import Parent Database(KB) Space Available(KB) Space Required(KB) Available permanent space for the database if it already exists on the system. Existing databases are highlighted in blue. Immediate parent database of the database that will be created. If parent database does not exist, the projected space required to create the child databases and any objects within the parent database. If parent database exists, the available space (MaxPerm - CurrentPerm) for the parent database. Owner for the databases created during the import operation. This is specified in the Parent Database box of the Import Options dialog box. Available space (MaxPerm - CurrentPerm) for the import parent database. If Databases is selected, the space required to create the databases. If Query Capture Databases is selected, the space required to create the QCDs. Guide, Release

85 7: Import Methods and Options Selecting stored procedures in the left pane (import tree) does not affect the permanent space calculation. 2. [Optional] If Databases is selected, right-click in the User Specified Space(KB) column and choose a command from the shortcut menu. Command Check user specified space against child database(s) space Check and update parent database(s) space Clear user specified space Description Determine if the child databases can be accommodated in the userspecified space. Teradata SET displays a warning if space cannot be accommodated. Determine if the user-specified space for a database can be accommodated by each parent database. If the calculated space for the parent database cannot accommodate the space specified, Teradata SET attempts to update the parent database space. Teradata SET displays a message if either the existing parent or user-specified database space is insufficient. Clear the user-specified space for a database. 3. [Optional] If Query Capture Databases is selected, right-click in the User Specified Space(KB) column and choose a command from the shortcut menu. Command Check total QCD space against available Parent space Check user specified space against calculated space for QCD Clear user specified space for QCD Description Check if there is enough available space in the parent database to accommodate the creation of the QCDs. Check the user-specified space against the calculated space for a QCD. Clear the user-specified space for a QCD. 4. Click Recalculate to recalculate the space for each parent database. The recalculation is based on the amount in the User Specified Space(KB) column, the Calculated Space(KB) column of the child databases, and the current scale factor. 5. Do one of the following: Click Cancel to ignore changes and close the dialog box. Click OK to accept the changes and close the dialog box. 6. [Optional] Click to start the import operation. Retrying a Failed SQL Statement When importing object definitions, errors can occur (such as insufficient privileges or permanent space). Use the SQL Statement Failed dialog box to retry the failed statement. Guide, Release

86 7: Import Methods and Options This dialog box is available if the Display Failed SQL statement dialog option is selected in the Options dialog box, regardless of whether the Ignore Teradata Database errors check box is selected. The dialog box appears when there is an error. See Error-Handling Options. 1. When the SQL Statement Failed dialog box appears, do one of the following: Click Abort to automatically abort the import operation. Follow these steps to enter another SQL statement: a. Type a statement to grant the necessary privileges or increase the permanent space. b. Click Retry. Click Retry to retry the failed statement if the error has been corrected by other means. Click Ignore to ignore the error and proceed with the import of the remaining objects. 2. Click Hide Failed SQL to hide the Failed Statement pane. Editing Information Offline Teradata SET allows multiple versions of the emulation information to be saved in order to test different scenarios. While offline, the following tasks can be performed to modify the information and create multiple scenarios: Open and edit emulation information. Change import options. Select objects for import. Edit import information. An import cannot be performed without a connection to a Teradata Database. Use this procedure to create different versions of the emulation files to test multiple scenarios from one exported file. While offline, all functions are available except the database interactive settings, such as displaying existing databases, browsing on the Parent Database box in the Import Options dialog box, and browsing on the Target QCD box in the Import Options dialog box. 1. From the main window, click Tools > Customize Data. The Open dialog box appears and displays a list of available.mcf files. Guide, Release

87 7: Import Methods and Options Open Look in: My Recent Documents Desktop data jsspc1.mcf Exported By Database Source: jsspc1 Release: V2R Version: Date: Options: Object Definitions Cost Parameters DBSControl Information My Documents My Computer My Network Places File name: jsspc1.mcf Open Files of type: Control Files [.mcf] Cancel Show Preview 2. Select an.mcf file to be the source of the emulation information. The right pane displays information about the file, such as source system information, the exported options, and the export date. To close the right pane, clear the Show Preview check box. 3. Click Open. 4. [Optional] Perform one of the following procedures: Changing Import Options Specifying Objects for Import Editing Import Information 5. [Optional] See Saving Changed Information. 6. [Optional] Connect to a Teradata Database and start the import operation. Saving Changed Information Use the Save As feature to save changes made using the Import window and the Import Options dialog box. The Save As feature also saves any database name changes and any modifications made to the following: Object definitions Statistics RAS Cost parameters DBS Control information Cost profiles 1. After making changes, click. Guide, Release

88 7: Import Methods and Options The Save As dialog box appears. 2. In the File name box, type a name. Changes cannot be saved in the original file. 3. Click Save. A new.mcf file and corresponding data files are created containing the changes. Displaying Existing Databases To make renaming of a target database easier, use Teradata SET to view a list of existing databases and identify possible candidates. See Renaming a Target Database. From the Import window, click. The Existing Databases dialog box appears and displays a list of existing databases and database owners. Renaming a Target Database Use Teradata SET to rename a target database when the database already exists on the test system and must remain on the test system. The name change affects the following: Statistics RAS DDLs of the objects in the database DDLs of the objects that have dependencies on the renamed object Use the Replace dialog box to change the database name for all object definitions. This procedure can be performed offline or while connected to a Teradata Database. 1. Do one of the following: Guide, Release

89 7: Import Methods and Options When connected to a Teradata Database, click. When not connected to a Teradata Database, click. The Open dialog box appears and displays the available.mcf files. 2. Select an.mcf file. 3. Click Open. 4. From the Import window, select the target database to rename. 5. From the toolbar, click. 6. Type a new database name. 7. Press Enter. A confirmation message appears. Target Database You have changed the target database name for import. You must also change the database name in the object definitions. Do you want to proceed and update the database name in the object definitions? Yes No Don t ask this question again 8. [Optional] To prevent the message from appearing each time this procedure is performed, select the Don t ask this question again check box. 9. [Optional] To keep the original database name in the object definitions, click No. The status bar displays the following message: Target database has been changed from old name to new name The target database name is changed. The object definitions are not renamed. Skip the remaining steps in this procedure. 10. [Optional] To update the name change in the object definitions, click Yes. The Replace dialog box appears. 11. Define the search-and-replace operation using the options in the Replace dialog box. Option Find what Replace with Description Search for this database name. Replace the database name listed in the Find what box with this database name. Guide, Release

90 7: Import Methods and Options Option Match whole word only Match case Search in all DDLs Description Search for whole words. This check box is selected by default. Search for characters that match the case in the Find what box. Search all object definitions. This check box is selected by default. 12. Find and replace the database name in the object definitions: a. Click Find Next to find the next matching instance in the object definitions. b. Do one or more of the following: Click Replace to replace the selected instance in a single object definition. The import tree in the left pane expands, and the corresponding DDL is selected. Click Replace All to replace all instances of the database name in a single object definition. The total number of replacements appears at the bottom of the Replace dialog box. Click Replace in all DDLs to replace all instances of the database name in all object definitions. The total number of replacements appears at the bottom of the Replace dialog box. The first time Replace is clicked, the Allow Edit command becomes available on the Edit menu. When editing is allowed, object definitions, RAS, statistics, cost parameters, DBS Control information, and cost profiles can be modified in the right pane of the Import window. 13. After all of the intended replacements have been made, click Cancel to close the Replace dialog box. 14. To commit the name change, click. The status bar displays Changes applied. All changes must be committed and applied before conducting the import operation. The changes are applicable only to the next import operation. See Importing to a Test System. Undoing Target Database Renaming Use the renaming feature to restore the original name for the target database. For example, if a renaming was done in error, the original name can be restored. This procedure can be performed offline or while connected to a Teradata Database. 1. From the Import window, select the database that requires its name to be restored. 2. Click. Guide, Release

91 7: Import Methods and Options A message appears stating that the target database name has been restored and noting that any changes made to the object definitions must also be undone. 3. [Optional] To keep the new database name in the object definitions: a. Click No in response to the message in step 2. The object definitions are not renamed, and the status bar displays the following message: You have undone the change made to the target database name. You must also undo any change(s) made to the Object Definitions... b. Skip the remaining steps in this procedure. 4. [Optional] To reverse the name change in the object definitions: a. Click Yes in response to the message in step 2. The Replace dialog box appears. b. Perform step 9 through step 12 in Renaming a Target Database. Reordering Databases After performing an export operation, reorder the databases in the emulation information to resolve referential integrity dependencies during import. This procedure is performed in the Import window and can be performed while offline or while connected to a Teradata Database. 1. In the left pane of the Import window, select a database to reorder. 2. Click. 3. In the left pane (import tree), drag the database icons to change their order. Only database icons can be reordered and only with other database icons at the same level. 4. [Optional] Click to start the import operation. Viewing Machine Configuration After performing an export operation review the configuration of a source machine to estimate the import time. While preparing emulation information for import, it might be helpful to refer to the configuration of the target system in order to identify compatible systems. This procedure requires a connection to a Teradata Database. 1. From the Import window, click. The Source Machine Configuration dialog box appears and displays details about the machine from which the system information was exported. Guide, Release

92 7: Import Methods and Options Source Machine Configuration Machine Configuration Exported Option Version Date Time CharSet Machine Name Number of AMPs Number of PEs Number of Nodes Model By Database 13.10m :13:44 ASCII OTHER OK Row Name Exported Option Version Release Date Time CharSet Machine Name Description Type of export used (database, query, or workload) Teradata software version used Teradata software release used Date the system information was exported Time the system information was exported Character set used with the exported system information Name of the machine from which the system information was exported For a CLIv2 connection, the system name typed in the hosts file. For an ODBC connection, the name typed under Teradata Server Info in the ODBC Driver Setup for Teradata Database dialog box. See Connection Methods. Number of AMPs Number of PEs Number of Nodes Number of AMPs configured on the machine Number of parsing engines (PEs) present on the machine Number of nodes connected to the system A node is a hardware assembly that contains several tightly coupled CPUs. Model Model number of the machine Guide, Release

93 7: Import Methods and Options The physical configuration boxes (Number of AMPs, Number of PEs, Number of Nodes, and Model) are only available if the user has necessary access rights on the target system. See Export Rights. 2. [Optional] Click to start the import operation. Viewing Estimated Import Time This procedure requires a connection to a Teradata Database. The Estimate Time function requires privileges. See Estimate-Time Rights. Estimate import time before performing an import operation to optimize system management. 1. From the Import window, click. The Open dialog box appears. 2. Select an.mcf file into which to import information. 3. Click Open. 4. Click. The Estimated Time dialog box appears and displays time estimates for each element being imported along with a total estimated time for the import operation. Estimated Time: Total Estimated Time: 00:36:50:55 Estimated Time Breakdown Option Object Definitions Statistics Random AMP Samples Cost Parameters Object Type Table View Macro Join Index Estimated Time 00:22:04:80 00:07:04:12 00:07:41:00 00:00:00:63 Count OK Refresh 5. [Optional] Click Refresh to recalculate estimates for the current import. 6. Click OK to close the Estimated Time dialog box. 7. [Optional] Click to start the import operation. Guide, Release

94 8 Administrative Functions Administrative Functions Teradata SET includes many administrative functions to facilitate the export and import of data. Set TLE Parameters Set TLE parameters using the Set Target Level Emulation feature. Specifying RAS, cost parameters, cost profiles, and Maps at various levels for the connected test system allows the creation of multiple emulation scenarios that cover a wide range of testing possibilities on a single test system. When the analysis is complete, the test system defaults can be restored using the Reset Target Level Emulation dialog box. See Resetting TLE. Set TLE Overview Use the Set Target Level Emulation dialog box to define RAS, cost parameters, cost profiles, and Maps. The Set Target Level Emulation dialog box can be accessed from either the main window or from the Import window. This procedure explains the process of setting IFP and system levels for cost parameter emulation or cost profile emulation that can only be set by a DBC or SystemFE user. This limitation does not apply to setting RAS emulation. For more information, refer to SQL Request and Transaction Processing (B ). Use the TLE function at any time during export and import operations. The following scenario is typical: 1. Export emulation information from a target system to a client machine. 2. Import that emulation information to a test system. 3. Apply TLE using the Set Target Level Emulation feature in Teradata SET. 4. Capture query plans using Teradata Visual Explain. 5. Analyze the query plan. 6. Reset RAS, cost parameters, and cost profiles on the test system using the Reset feature in Teradata SET. Guide, Release

95 8: Administrative Functions Setting TLE Before using Teradata SET to control emulation, turn on the TLE feature for the test system. Using the DBS Control utility, set the general field 22 (Target Level Emulation) to TRUE. For a description of the DBS Control utility, refer to Utilities (B ). 1. From the main window or the Import window, click. The Set Target Level Emulation dialog box appears and displays the available emulation information on the current system. The Set RAS tab is selected by default. Set Target Level Emulation Set RAS Set Costs Set Cost Profile Set IPE Plan Set MAP Select Table Names Database Name Table Name RAS Tag Name 1 TESTDB TESTTABLE RAS_TAG Set RAS at level SESSION SYSTEM Select All OK Cancel 2. Do one of the following: Select the desired individual RAS tags. Click Select All to apply all of the listed RAS tags. 3. Select one of the following to define the level of the RAS emulation: Session System 4. Click the Set Costs tab. 5. Select individual cost tags. Only one cost tag can be set for each level. 6. Click the Set Cost Profile tab. 7. Select an individual cost profile. Guide, Release

96 8: Administrative Functions Only one cost profile tag can be set for each level. 8. Define the level of the cost emulation by selecting one of the following: Session IFP System 9. Click the Set IPE Plan tab. Select one IPE Plan based on the selected System Tag name and the Request name. Only one IPE Plan can be selected for Emulation. Unlike RAS and Cost parameters, IPE Plans can be emulated at SESSION (Request) level only. 10. When finished making changes, click OK. If TLE is set from the main window, Teradata SET performs the emulation request immediately and displays the results in the main window. If TLE is set from the Import window, Teradata SET performs the emulation request at the end of the import operation. 11. [Optional] See Viewing a Summary Report. 12. [Optional] See Perform Query Testing to analyze query plans that are emulated on the test system. 13. [Optional] See Resetting TLE to reset the original RAS and cost defaults on a test system. Set Map When the Set MAP tab is selected in the Set Target Level Emulation interface, the following GUI is displayed. Guide, Release

97 8: Administrative Functions Set Target Level Emulation Set RAS Set Costs Set Cost Profile Set IPE Plan Set MAP Select MAP Tag 1 Tag Name DatabaseName TableName SDLC8858 TESTDB TESTTABLE Map Emulation Type Global TLE Amp Count #AMPs 0 Set MAP at Level SESSION TLE Map SYSTEM Select All IFP OK Cancel Selecting the required Tag Name and TLE Map radio button emulates the target system as closely as possible. For each table selected, the complete map information of its TLE Map is used in query planning. When Global TLE Amp Count is used with the number of AMPs specified by the user, the pre- TD16.10 emulation approach is used. Resetting TLE Reset the test system TLE back to the system default values after importing RAS, cost parameters, cost profiles, and Maps. Before resetting the test system default values, turn on the TLE feature for the test system. Using the DBS Control utility, set the general field 22 (Target Level Emulation) to TRUE. For a description of the DBS Control utility, refer to Utilities (B ). 1. From the main window, click. The Reset Target Level Emulation dialog box appears with the Reset RAS tab selected by default. Emulation is turned on for the tables shown. Guide, Release

98 8: Administrative Functions 2. Do one of the following: Select individual RAS tags to be reset (turn off emulation). To select more than one level, hold Shift and click with the left mouse button. Click Select All to reset all of the listed RAS tags. A sample can be reset at both session and system levels. Drag the scroll box to the right to see the Level column, which contains the reset level of the samples. 3. [Optional] To reset the cost parameters, follow these steps: a. Click the Reset Costs tab to display the cost parameters currently in effect at the request (if set), session, IFP, and system levels. b. Select one or more cost tags to reset. To select more than one cost tag, hold Shift and click with the left mouse button. Guide, Release

99 8: Administrative Functions 4. [Optional] To reset cost profiles: a. Click the Reset Cost Profile tab to display the cost profiles currently in effect at the session, IFP, and system levels. b. Select one or more cost profiles to reset. To select more than one cost profile, hold Shift and click with the left mouse button. c. When finished making changes, click OK. 5. To Reset MAPS: a. Click the Reset MAP tab to display the current MAPs. Guide, Release

100 8: Administrative Functions b. Select one of the following options to reset: Select row(s) from the spread, select the TLE Map radio button and click OK. This resets the TLE Map set for the object. Select Global TLE Amp Count and click OK. This resets per the AMP based pre-td16.10 cost model. 6. Check the main window for verification that the reset was successful or for diagnostic information explaining why the reset was unsuccessful. MAP Emulation Configuration 1. Select a MAP from Emulation System (Test System) to emulate the Target System Map. The Target and Emulation MAPS dialog appears, displaying the Target System Map (TMAP) and the corresponding Emulation Map (EMAP) on the test system. It also displays the Target System Map Kind (TKIND), Emulation Map Kind (EKIND), the corresponding AMP counts (TAMPCNT, EAMPCNT), etc. Guide, Release

101 8: Administrative Functions Target and Emulation MAPS Map Emulation Configuration TMAP TD_GLOBALM TD_DATADIC TD_MAP1 EMAP TKIND EKIND TAMPCN TD_Map1 C C TD_Map1 C C TD_Map1 C C Change the Emulation Map Target MAP Emulation Map TD_DATADIC TD_DataDictio Rerun DefaultMapSimulation TD_DataDictionary TD_GlobalMap TD_Map1 TD1AmpSparseMa Change Map Close 2. To select an Emulation Map to emulate a Target System Map, choose the Target Map and Emulation Map from the Target MAP and Emulation MAP combo-boxes and click the Change Map button. The Map Emulation Configuration is updated with the changed configuration. 3. After finalizing the selection of Emulation Maps for the Target Maps, click Rerun DefaultMapSimulation to execute the Default Map Simulation macro. Perform Query Testing Use Teradata SET to execute SQL statements, using either Teradata SQL Assistant or the Execute SQL main window, to test queries before using them. Depending on how the query tool interface is set up and the connection mode, you test queries either in the Teradata SQL Assistant or in the Execute SQL main window. See Setting the Query Tool Interface. Setting the Query Tool Interface 1. From the main window, click Tools > Options. The Options dialog box appears with the Customize tab selected by default. 2. Do one of the following: Select the Use SQL Assistant rather than the Execute SQL window with ODBC connectivity check box to use Teradata SQL Assistant instead of Execute SQL as the query editor when connected to Teradata Database with ODBC connectivity. Clear the Use SQL Assistant rather than the Execute SQL window check box to use the Execute SQL window. Guide, Release

102 8: Administrative Functions When using a CLIv2 connection, Execute SQL is used regardless of how this option is set. 3. Click Apply. 4. Click OK to close the Options dialog box. Testing a Query Using Teradata SQL Assistant If you are using Teradata SQL Assistant, refer to Teradata SQL Assistant for Microsoft Windows User Guide (B ). Testing a New Query Using the Execute SQL Main Window 1. From the main window, click. The Execute SQL main window opens. 2. Do one of the following: Type the query to be tested in the Untitle window, which then becomes the Query window. If queries exist in the History window, click the cell under the Query column to select one. The query appears in the Query window. 3. Click. The results appear in the status bar at the bottom of the window. Testing an Existing Query Using the Execute SQL Main Window 1. From the main window, click. The Execute SQL main window opens. 2. Click. A Windows Explorer window opens. 3. Navigate to the query to be tested. 4. Click Open. The query appears in the Query window. 5. Remove heading information so just the query text exists. 6. Click. The results appear in the status bar at the bottom of the window. Inputting USING Values When a query containing the USING clause is submitted in the execute SQL window, the Input using values screen displays. Guide, Release

103 8: Administrative Functions Input USING values The Using Query display box shows the query containing the USING clause. The Using Variables display box shows the values for the Name and Datatype variables. 1. For the Value variable, enter the data values in the Value column. 2. Click one of the following: Click OK to pass the variable data to the query during execution. Click Cancel to prevent passing variable data to the query. Perform a File Transfer Use the Pack feature to simplify file transfer; for example, to send exported files to another location. The Pack feature combines all of the files associated with an export into a single file that can be sent in or transferred to an FTP site. Then, use the Unpack feature to separate the files after they have been packed. All pack files contain non-ascii characters, so use binary mode when transferring them using FTP. Packing Files 1. From the main window, click. The Pack dialog box appears. Guide, Release

104 8: Administrative Functions 2. Select the.mcf file to pack. The preview pane on the right displays information about the file such as source system information. To remove the preview pane, clear the Show Preview check box. The Undo Files box displays any.undo files associated with the selection. 3. [Optional] To include an.undo file, select the file. 4. Click Pack. The files associated with the selected.mcf file are combined into one file with a.pack extension. UDF code files specified in response to the Browse for UDF File Open Dialog during the Export operation are also included in the.pack file. 5. [Optional] Unpack the file. Unpacking Files Prerequisite: A pack file must be created to use this procedure. See Packing Files. 1. From the main window, click. The Unpack dialog box appears and displays all available.pack files. Guide, Release

105 8: Administrative Functions 2. Select the.pack file to unpack. The preview pane on the right displays information about the file such as source system information. To close the preview pane, clear the Show Preview check box. 3. Click Unpack. Undoing Imported Files After the query plan is analyzed, use the Teradata SET Undo Import feature to undo (cleanup) the imported information that is no longer needed. Every import creates a corresponding.undo file, which is used to keep the test system uncluttered. Multiple types of information can be removed from a single.undo file, but only one undo import operation is performed at a time. If objects are cleaned up once using the associated.undo file, they cannot be cleaned up again using the same.undo file. 1. Connect to the same system used to create the.undo file. See Connect to a Teradata Database. 2. From the main window, click. The Open dialog box appears and displays the available.mcf files. Guide, Release

106 8: Administrative Functions Open Look in: My Recent Documents Desktop data jsspc1.mcf Exported By Database Source: jsspc1 Release: V2R Version: Date: Options: Object Definitions Cost Parameters DBSControl Information My Documents My Computer My Network Places File name: jsspc1.mcf Open Files of type: Control Files [.mcf] Cancel Show Preview 3. Select an.mcf file that has an associated.undo file. The Undo Files box displays the.undo files associated with the selection. Open is available only if an.undo file exists. The preview pane on the right displays information about the file such as source system information. To close the preview pane, clear the Show Preview check box. 4. Select an.undo file. 5. Click Open. The Undo Import File dialog box appears and displays the.undo file name in the title bar. The.undo file is created during the import process and named using the following format: file name.current timestamp.undo. Guide, Release

107 8: Administrative Functions Undo Import File: sdlc8858.labs.teradata.com.07-mar undo Undo Import Parent Database: Select Target QCD Name: QCD Name: Workload Name: Undo Import Options Object Definitions Statistics Random AMP Samples Demographics Execution Plans Workloads QCD Data Cost Parameters Cost Profiles Data was exported from Teradata Database Imported Machine Version Release Date Time Character Set Machine Name Number of AMPs Number of PEs Number of Nodes Model Name Exported Option sdlc8858.labs.teradata 16.10j j :42:58 UTF16 sdlc8858.labs.teradata C Export By Query DBQL Plans MAPs Undo Import Set TLE... Error Handling... Cancel 6. Under Undo Import Options, select the check boxes for the information to undo (clean up) in the database. 7. Click Error Handling to change how errors are handled during the undo-import (cleanup) operation. See Error-Handling Options. 8. Click Undo Import. The selected.undo file undoes the import, and the Undo Import Filedialog box is closed. If the undo-import (cleanup) operation is only partially successful, an error message appears. If this occurs, open the log file for the operation to diagnose the problem. See Viewing the Log File for the Current Session. 9. View a summary report for the results. See Viewing a Summary Report. Guide, Release

108 8: Administrative Functions Deleting Exported Files After performing a query plan analysis, use the Delete Files feature to delete individual export files that are no longer needed. Depending on the export options selected, a number of files are created when emulation information is exported from a target system to a test system. The Delete Files feature reads the.mcf file and, depending on the export options chosen, removes the corresponding files:.ddl 130.col.dem.log.opt.pack.qcd.ras.rpt.sql.undo.mcf If necessary, the deleted files can be restored from the Recycle Bin. The files are automatically restored to the appropriate directory. 1. From the main window, click. The Delete Files dialog box appears and displays the available.mcf files. 2. Select the.mcf file to delete. The preview pane on the right displays information about the file such as source system information. To close the preview pane, clear the Show Preview check box. Only.mcf files appear in the list. However, deleting the.mcf file deletes all associated files, with the exception of the.pack file. To delete the.pack file, go to the next step. XSP/UDF code files specified in response to the Browse for XSP/UDF File Open Dialog during the Export operation are also deleted. 3. [Optional] To remove the.pack file during the delete operation, select the Delete Pack File check box. Guide, Release

109 8: Administrative Functions 4. Click Delete. A confirmation message appears. 5. Click Yes to remove the files. During the Unpack and Delete File Operation, the user is prompted to confirm overwriting or deletion of the XSP/UDF code files. The XSP/UDF files are also displayed with the normal Teradata SET files, such as.mcf,.log,.ddl, and so on. View Log Files and Summary Reports To troubleshoot an export, import, or undo-import (cleanup) operation, use the log file to view the events in the current Teradata SET session and find the required information. View the summary report for a summary of the failed and successful operations. Viewing the Log File for the Current Session Review the log file to see the actions taken during the current Teradata SET session. 1. From the main window, click. The Open dialog box appears and displays the available log file. The File name box displays the name of the most recently used log file, by default. Guide, Release

110 8: Administrative Functions 2. Select a log file for review. 3. Click Open. The log appears in the main window. 4. To close the log file, click. Guide, Release

111 8: Administrative Functions Viewing a Summary Report View the summary report for a summary of the failed and successful import, export, or undo-import (cleanup) operations. Reports are stored in the text-file format with the extension.rpt. To restrict the summary report to logging only failed operations, change the error handling options. See Error-Handling Options. 1. Perform an import, export, or undo-import (cleanup) operation. 2. Click. The Open dialog box appears. 3. Select the corresponding.rpt file. 4. Click Open. The report appears and displays a summary of the corresponding operation. Guide, Release

112 8: Administrative Functions 5. To close the report, click. 6. For detailed information about the operation, view the log file. See Viewing the Log File for the Current Session. Retrying Failed Import Operations When importing object definitions, certain errors such as insufficient privileges or permanent space can occur. Use the SQL Statement Failed dialog box to retry the failed statement. This dialog box appears only if the Display Failed SQL Statement dialog check box is selected on the Options dialog box, regardless of the state of the Ignore Teradata Database errors check box. See Error-Handling Options. 1. When the SQL Statement Failed dialog box appears, do one of the following: Click Abort to automatically abort the import operation. Grant the required rights before retrying: a. Enter another SQL statement to grant the necessary privileges or increase the permanent space. b. Click Retry. Click Retry to retry the failed statement if the error has been corrected by other means. Click Ignore to ignore the error and proceed with the import of the remaining objects. 2. Click Hide Failed SQL to close the Failed Statement pane. Guide, Release

113 8: Administrative Functions Manage Missing Access Privilege Errors Teradata SET export, import, and undo operations might be unsuccessful if the logged-on user has insufficient access privileges. Use the Grant access privilege dialog box to manage a missingaccess-privilege error. See Error-Handling Options for more information about the Options dialog box. When the Submit grant statement from administrator s session check box is selected, the check-box setting and the database session selected also apply the next time the Grant access privilege dialog box appears. Retrying a Failed Statement Use this procedure only if the logged-on user has permission to grant privileges or a System Administrator is present to grant privileges. See Ignoring Missing Access Privileges. 1. When the Grant access privilege dialog box appears, displaying the missing-access-privilege information, click Failed Statement to view the SQL causing the error. 2. Click Retry to retry the failed statement when the required access privileges have been granted using a application other than Teradata SET. 3. [Optional] In the Grant Statement box, enter the grant statement with the missing access privileges. If the Grant Statement box is left empty, Teradata SET automatically generates the grant statement with the required access privileges. Select the Grant missing access rights without prompting check box to grant further missing privileges without prompting the Grant access privilege dialog box. 4. Select the Submit grant statement from administrator s session check box. Guide, Release

114 8: Administrative Functions Grant access privilege Error Information ta Driver][Teradata Database] The user does not havce INSERT access to SystemFe.opt_cost_table. Failed Statement Grant Options Grant Statement Submit grant statement from administrator s session. Grant missing access rights without prompting. Grant Retry Ignore Ignore All Abort A dialog box appears, allowing entry of logon information. Which dialog box appears depends on the connectivity type in use. 5. Enter logon information: For ODBC connectivity, enter logon information in the Select a Data Source dialog box. For CLI connectivity, enter logon information in the Connect to Teradata Database dialog box. The user ID entered must have the right to grant access privileges. 6. Click OK. 7. Click Grant to grant the missing access privilege. Ignoring Missing Access Privileges The access privilege error can be ignored or the current operation can be aborted instead of granting the access privilege. To grant access privileges, see Retrying a Failed Statement. When the Grant access privilege dialog box appears, displaying the missing access privilege information, click one of the following: Ignore, to ignore the missing-access-privilege error Ignore All, to ignore all future missing-access-privilege errors Abort, to abort the current operation Disconnect and Close Teradata SET Disconnect from the current database before connecting to a different database. Close Teradata SET to end the session and disconnect from the current database. Guide, Release