15.00 - Starting and Running DUL/DULTAPE - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
15.00
Content Type
Configuration
Publication ID
B035-1102-015K
Language
English (United States)
Last Update
2018-09-25

Starting and Running DUL/DULTAPE

Because dul and dultape are used to move large amounts of data, these operations are usually performed in batch mode.

  • On Linux, dul and dultape run in either batch or interactive mode in the following environments:
  • SUSE Linux Enterprise 9 (EM64T)
  • SUSE Linux Enterprise 10 (EM64T)
  • Starting DUL and DULTAPE on Linux

    Note: The default password for the crashdumps logon is crashdumps. Verify whether your System Administrator has changed the password or is still using the default.

    You can start and exit dul and dultape interactively from the command line.

    To start dul interactively, do the following:

    1 At the command prompt, type the following and press Enter:

    dul

    Dul prompts you for your logon:

    Dump Unload/Load - Enter your logon:

    2 Type:

    .logon crashdumps

    and press Enter.

    The password for the crashdumps logon is crashdumps.

    To start dultape interactively, do the following:

    1 At the command prompt, type the following and press Enter:

    dultape

    Dultape prompts you for the tape drive path:

    Dump Unload/Load to Tape - Please insert tape and input tape device name:

    2 Insert the tape, type the tape drive path, and press Enter. For example:

    /dev/rmt/c0t3d0s0

    Dultape prompts you for your logon:

    Dump Unload/Load to Tape - Enter your logon:

    3 Type:

    .logon crashdumps

    and press Enter.

    The password for the crashdumps logon is crashdumps.

    To log off the Teradata Database and exit dul or dultape, do the following:

    ✔ At the command prompt, type one of the following and press Enter:

  • LOGOFF;
  • END;
  • QUIT;
  • Space Requirements

    The following sections discuss the space requirements for the Teradata Database and hosts.

    Crashdumps Database

    The Crashdumps database is used to store system dumps. Because system dumps take up disk space, you should periodically clear old or unwanted dump tables from the Crashdumps database.

    If the space available in the Crashdumps database is exceeded, a message is displayed on the system console every hour until you make space available for the dump to be saved. To make more room for new dumps, examine the existing dumps and delete the ones that you no longer need.

    If you still need the existing dumps, then copy them to removable media. Once the Teradata Support Center has received and evaluated a dump, you can delete the tables.

    Database Space Allocation

    The proper size for the Crashdumps database depends on the following configuration information:

  • Number of nodes on the system
  • Number of dumps you want to have available online at any one time (minimum of one dump)
  • The size of the dump for any given node depends on several unpredictable variables. To calculate the approximate size of the Crashdumps database that you need for your system, use the following formula:

    number of DBS nodes  x  number of dumps  x  100 MB

    At least 100 MB of space should be allowed per dump, although Teradata recommends larger multiples.

    Privileges

    For Dump/Unload Operations

    Before you can perform a dump/unload operation, your username specified in the logon ID must have the following:

  • CREATE, DROP, and SELECT privileges on the tables in the Crashdumps database
  • SELECT privileges on the DBC.SW_EVENT_LOG system table
  • For Load Operations

    Before you can perform a load operation, your username specified in the logon ID must have CREATE, DROP, and SELECT privileges on the DataBase Computer (DBC) tables of the Teradata Database.

    If the username you specify when you invoke dul does not have the appropriate privileges, then the Teradata Database returns an error message, and the operation is cancelled.

    For detailed information on access privileges, see Database Administration or consult your system administrator.