15.00 - Error-Handling Options - System Emulation Tool

Teradata System Emulation Tool User Guide

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

Error‑Handling Options

Use the Error Handling tab to specify how errors are handled.

Note: It is not necessary to connect to Teradata Database for this procedure.

To set 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.

 

3 Select one or more of the check boxes in the Error Handling tab.

 

Option

Description

General

Note: Applies to export, import, or undo import (cleanup) operations.

Log only failures in Summary Report

Log the failed operations into the summary report.

View the log file to determine the cause of any failures.

Ignore Teradata Database errors

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

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.

Revoke access privileges

To revoke the access privileges granted from TSET.

Grant access privileges on database

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

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

  • 2644
  • 2843
  • 3250
  • 3523
  • 3524
  • Clear the check box to prevent the SQL Statement Failed dialog box from appearing. These errors are automatically ignored during future import operations. See “Retry Failed Import Operations” on page 138.

    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.
  • 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 non-existing 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.

    Clear this check box to automatically create a target QCD/DBQL database without being prompted.

    Display duplicate primary key error

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