Undo Imported Files - System Emulation Tool

Teradata System Emulation Tool User Guide

Product
System Emulation Tool
Release Number
15.00
Language
English (United States)
Last Update
2018-09-28
dita:id
B035-2492
lifecycle
previous
Product Category
Teradata Tools and Utilities

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

Note: If objects are cleaned up once using the associated .undo file, they cannot be cleaned up again using the same .undo file.

To undo an import

1 Connect to the same system used to create the .undo file.

See “Connect to a Teradata Database”on page 31.

2 From the main window, click .

The Open dialog box appears and displays the available .mcf files.

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.

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”on page 57.

8 Click Undo Import.

The selected .undo file undoes the import, and the Undo Import File dialog box is closed.

Note: 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 “View a Log File”on page 135.

9 View a summary report for the results.

See “View a Summary Report”on page 136.