15.00 - Import to a Test System - System Emulation Tool

Teradata System Emulation Tool User Guide

prodname
System Emulation Tool
vrm_release
15.00
category
User Guide
featnum
B035-2492-034K

Import to a Test System

The Import feature can be customized in a variety of ways to maximize the usefulness of the test system. An overview of the process follows:

1 Before importing data, connect to a Teradata Database. See “Connect to a Teradata Database” on page 31.

2 Select an export method. See Chapter 3 “Menus and Toolbars.”

3 Export the information needed to emulate the target environment on the test system. See Chapter 6 “Export Methods and Options”

4 Import the information to the test system, modifying the import options if necessary. See Chapter 7 “Import Methods and Options”

5 Manage the imported data:

  • Remove emulation information.
  • Delete files.
  • Email data to another location.
  • Troubleshoot the import and export processes.
  • See Chapter 8 “Administrative Functions.”

    An .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.

     

    Table 9: Default Import Locations 

    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

    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 “Change Import Options” on page 99.

    To change the location or target database where objects are created, use the Rename function in the Import window. See “Rename a Target Database” on page 112.

    To import emulation information to a test system

    Before proceeding, connect to a Teradata Database, and perform an export operation. See “Connect to a Teradata Database” on page 31 and Chapter 6 “Export Methods and Options”

    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.

    Note: 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.

    4 In the left pane, select objects to import, such as a table.

    Note: The Import menus and toolbar differ somewhat from those in the main window. See “Import Window” on page 38.

    5 [Optional] Perform any of the following procedures before completing the import:

  • “To change import options” on page 99
  • “To select objects for import” on page 103
  • “To change RAS byte order” on page 104
  • “To edit import information” on page 105
  • 6 Click .

    A confirmation message appears.

    7 Click Yes to start the import operation.

    Note: 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 “Retry Failed Import Operations” on page 138.

    8 [Optional] View a summary report of the import operation results.

    See “View a Summary Report” on page 136.

    9 [Optional] Perform query plan analysis on the test system.

    Note:  

  • To import C and C++ 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 UDFs cannot be imported with ODBC connectivity.
  • To import C and C++ UDF code files that reside on the Sever, files must be copied to the appropriate path, as specified in the CREATE FUNCTION DDL, on the Server. If a path is unspecified, the files must be copied to the default path. Refer to the Database Administration manual for default paths.
  • To import Java 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.