16.10 - Running DIP - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
zll1480972831047.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval

There are two ways to run DIP:

  • Interactively
    1. Type start dip from the Supervisor window of CNS or just dip from the Linux command line.

      The DIP utility presents a numbered list of available DIP scripts.

    2. Type the number or name of the script to be executed, and press Enter.

      Depending on what script you selected, a message similar to the following appears:

      Executing DIPERR at Tue Feb 20 13:04:29 2001
      Please wait...
      DIPERR is complete at Tue Feb 20 13:04:46 2001
      Please review the results in /tmp/dip1.txt on node 1- 4
      The results of the script are saved into a text file, which is named using DIP and the number of the script.
    3. To run another script, type Y and press Enter, then continue as above. To exit DIP, type N and press Enter.
  • Non-interactively

    If you know the menu number of the DIP script, you can run DIP with a single-line command from the Supervisor window of Database Window (or any interface to the console subsystem (CNS), such as the cnsterm command-line utility). Use the following syntax:



    dbc_password
    The password for user DBC.

    If the password contains the # character, enclose the dbc_password within quotes or apostrophes: "our#dbc#password"

    -h
    Displays DIP online help information.
    -s list_of_scripts
    Displays a list of script numbers or names separated by spaces to be executed in that order.

    For example:

    • 1 2 5 6
    • DIPERR DIPDB DIPVIEWS DIPVIEWSV
    script_name
    The DIP menu name of the script to be run, for example, DIPALL or DIPVIEWS.
    script_number
    The DIP menu number of the script to be run.

Example: DIP menu screen

The following example shows the DIP menu screen when the program is run interactively. Some menu choices appear only if you have licensed related Teradata Database optional features.

Select one of the following DIP SQL scripts to execute:
        (Press the Enter key to quit)

 1. DIPERR     - Error Messages
 2. DIPDB      - System Databases
 3. DIPDEM     - UDF/UDT/XSP/SPL Macros
 4. DIPRSS     - ResUsage Tables
 5. DIPVIEWS   - Legacy System Views
 6. DIPVIEWSV  - Unicode System Views
 7. DIPDBCCMT  - DBC Table Comments
 8. DIPACR     - Access Rights
 9. DIPSYSFNC  - System Functions
10. DIPRUM     - ResUsage Views/Macros
11. DIPOLH     - Online Help
12. DIPSYSFE   - System FE Macros
13. DIPCRASH   - CrashDumps Database
14. DIPCCS     - Client Character Sets
15. DIPOCES    - Cost Profiles
16. DIPPWRSTNS - Password Restrictions
17. DIPUDT     - UDT Macros
18. DIPARR     - ArrayVec Data Type
19. DIPGEO     - Geospatial Data Type
20. DIPXML     - XML Data Type
21. DIPJSON    - JSON Data Type
22. DIPDATASET - DATASET Data Type
24. DIPCAL     - Calendar Tables/Views
25. DIPSQLJ    - SQLJ Views/Procedures
26. DIPSYSUIF  - SYSUIF Views/Procedures
27. DIPJDBC    - JDBC Functions
28. DIPRCO     - Reconfig
29. DIPSTATS   - Automated Stats Mgmt
30. DIPBAR     - BAR Databases/Views
31. DIPPOST    - Post commands
32. DIPSZVIEWS - Secure Zones Legacy System Views
33. DIPSZVIEWSV - Secure Zones Unicode System Views
34. DIPMAPS    - Multiple Hash Maps
35. DIPTDWM    - TDWM Configuration
36. DIPANSI    - ANSI Functions
37. DIPALL     - All of the above
38. DIPMIG     - Scripts for Migration
39. DIPPDCR    - PDCR Tables/Views
40. DIPACC     - Access Logging
41. DIPPATCH   - Stand-alone patches
42. DIPGLOP    - GLOP Tables/Procedures
43. DIPRTBLOP  - R Table Operator
44. DIPCDC     - Unity Change Data Capture

Usage Notes

The DIPALL script executes all DIP scripts that appear in the menu above it. It is normally run as part of Teradata Database installation, so running the scripts above it individually is not normally necessary.

Scripts that appear below DIPALL in the menu are for special purposes, and should generally only be run with guidance from the Teradata Support Center.