15.00 - DIP Scripts - Teradata Database

Teradata Database Utilities

Teradata Database
Release Number
Content Type
Publication ID
English (United States)
Last Update

DIP Scripts

The following table provides a summary of the different DIP scripts.


SQL Script File



  • Runs the access logging script.
  • Enables users with EXECUTE privilege on the DBC.AccLogRule macro to submit BEGIN LOGGING and END LOGGING statements, which enable and disable logging of privilege checking.

    Loads and Initializes the TD_ARRAY data type.


    Runs all DIP scripts that appear above DIPALL on the DIP menu screen.


    Initializes ANSI supported stored procedures.


    Creates the TD_ARRAY data type and corresponding functions.


    Provides infrastructure to support Data Stream Architecture (DSA) Backup And Recovery (BAR).


    Creates TD_SYSFNLIB database, if it does not already exist, and enables Teradata Database embedded services system functions, calendar views, and calendar macros.


    Installs the default client character sets for the system.

    Creates pre-defined translation tables for Unicode and non-English languages, including Japanese and various European languages. For more information on character sets, see International Character Set Support.


    Creates the database and views where crash dump information is stored.


    Creates all of the databases required by DIP scripts, and initializes the secondary indexes for DBC tables.


    Supports Database Extensibility Mechanisms that create the SYSLIB database and the supporting objects within it for managing user-created DEM objects.

    DEMs include stored procedures, UDFs, and UDTs distributed as packages that can be used to extend the capabilities of Teradata Database.

    Note: Successful creation of the stored procedures, external stored procedures, UDFs, and use of the created table functions requires a C compiler to be available on the Teradata system.


    Loads error message files for storing the text of messages that Teradata Database components, software, and client connections generate.


    Initializes the geospatial features of the Teradata Database, creating the SYSSPATIAL spatial_ref_sys database.


    Support functions for the JDBC API.


    Enables JSON functionality in Teradata Database.

    Note: This script is only available after JSON has been enabled by setting a DBS control flag.


    Enables global and persistent (GLOP) data support.

    GLOP data is a type of data available to external routines. The persistence in memory of GLOP data is based on specific boundaries, such as a user role or user account.

    For more information on GLOP data, see SQL External Routine Programming.

    Note: DIPGLOP is available only with appropriate licensing. If you require GLOP support, contact your Teradata representative.


    Runs the following 5 scripts in preparation for complete system migrations: DIPERR, DIPDB, DIPVIEWS, DIPVIEWSV, and DIPBAR.


    Initializes the Online Help Syntax.


    Initiates the default cost estimate statistics.

    Note: Other cost profiles should be used only under the direction of Teradata Support Center personnel.


    Initializes standalone patch versions. Automatically executed by PUT for all maintenance and efix upgrades.


    Initializes objects that have dependencies on other functions and procedures that were previously created by DIP.


    Creates a centralized repository for performance data, and infrastructure to support collection and reporting of performance data.


    Populates the DBC.PasswordRestrictions table with the list of words disallowed within a password.


    Finalizes the initialization of the DBC tables used for reconfiguration.


    Adds the ResUsage tables data columns. Allows logging of system performance statistics.


    Loads Resource Usage views and macros and enables report generation from data stored in the ResUsage system tables.

    Note: If your Teradata platform has co-existence nodes, during installation or upgrade, the identifiers for each node group should be defined in the CASE clauses of the appropriate view definitions in the diprum.bteq file.


    Enables Java-based external stored procedures.

    Note: Successful creation of the external stored procedures requires that there be a C compiler on the Teradata system.


    For more information, see Application Programming Reference.

    Note: This script should not be run independently. It is run automatically as part of the DIPALL script.


    Creates infrastructure to manage user installed files (UIFs). UIFs are text, binary, or script files (such as perl, python, or operating system shell scripts) that users can install in the database.

    Use the SCRIPT table operator to run these scripts, pass them arguments, and run operating system commands. For more information on the SCRIPT table operator, see SQL Functions, Operators, Expressions, and Predicates.


    Initializes the macros, procedures, and views that reside within the SystemFE database.


    Enables Teradata Database system functions and Embedded Services Functions.


    Creates or upgrades the database infrastructure for workload management and alerting.

    Note: DIPTDWM can also be started from the Linux command line by running /usr/tdbms/bin/tdwmdip. Running it in this way provides an interactive session that allows specification of various parameters, which cannot be specified when DIPTDWM is invoked from the DIP program.


    Initializes the infrastructure for creating UDT objects and Period Data Type objects.


    Creates the non-Unicode compliant views and macros for access to DBC objects.


    Creates the Unicode compliant views and macros for access to DBC objects, and populates all the comments for DBC system tables.


    Enables XML functionality in Teradata Database.

    Location of DIP Scripts

    DIP scripts are SQL code files with .bteq file extensions. To view the SQL code of a DIP script, you can inspect the script file itself. DIP scripts are located in the /usr/tdbms/etc directory on Teradata Database system nodes:

    Any output from running DIP scripts is captured to dipn.txt files, where n corresponds to the menu number of the DIP script. These output files are located in the /var/opt/teradata/tdtemp directory.


    The following example shows the DIP menu screen when the program is run interactively.

    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. DIPACR     - Access Rights
     8. DIPSYSFNC  - System Functions
     9. DIPRUM     - ResUsage Views/Macros
    10. DIPOLH     - Online Help
    11. DIPSYSFE   - System FE Macros
    12. DIPCRASH   - CrashDumps Database
    13. DIPCCS     - Client Character Sets
    14. DIPOCES    - Cost Profiles
    15. DIPPWRSTNS - Password Restrictions
    16. DIPUDT     - UDT Macros
    17. DIPARR     - ArrayVec Data Type
    18. DIPGEO     - Geospatial Data Type
    19. DIPXML     - XML Data Type
    20. DIPJSON    - JSON Data Type
    22. DIPCAL     - Calendar Tables/Views
    23. DIPSQLJ    - SQLJ Views/Procedures
    24. DIPSYSUIF  - SYSUIF Views/Procedures
    25. DIPJDBC    - JDBC Functions
    26. DIPRCO     - Reconfig
    27. DIPSTATS   - Automated Stats Mgmt
    28. DIPBAR     - BAR Databases/Views
    29. DIPPOST    - Post commands
    30. DIPTDWM    - TDWM Configuration
    31. DIPANSI    - ANSI Functions
    32. DIPALL     - All of the above
    33. DIPMIG     - Scripts for Migration
    34. DIPPDCR    - PDCR Tables/Views
    35. DIPACC     - Access Logging
    36. DIPPATCH   - Stand-alone patches

    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 Global Support Center.