The following table provides a summary of the different DIP scripts.
| SQL Script File | Purpose |
|---|---|
| DIPACC |
|
| DIPACR | Loads and Initializes the TD_ARRAY data type. |
| DIPAEXT | Creates Teradata Analytic Functions. |
| DIPALL | Runs all DIP scripts that appear above DIPALL on the DIP menu screen. |
| DIPANSI | Initializes ANSI supported stored procedures. |
| DIPARR | Creates the TD_ARRAY data type and corresponding functions. |
| DIPBAR | Provides infrastructure to support Data Stream Architecture (DSA) Backup And Recovery (BAR). |
| DIPCAL | Creates TD_SYSFNLIB database, if it does not already exist, and enables Teradata Database embedded services system functions, calendar views, and calendar macros. |
| DIPCCS | 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 Teradata Vantage™ - Advanced SQL Engine International Character Set Support, B035-1125. |
| DIPCDC | Creates system-reserved replication groups and other infrastructure used for Teradata® Unity™ change data capture protocol for replication. This script is visible only when Teradata® Unity™ CDC is enabled in DBS Control. |
| DIPCRASH | Creates the database and views where crash dump information is stored. |
| DIPDATASET | Adds support for the DATASET data type and the Avro storage format. If a user-defined data type named DATASET already exists, this script is aborted, and the Teradata DATASET type is not created. The script may be re-run after the user-defined DATASET type is removed or renamed. |
| DIPDB | Creates all of the databases required by DIP scripts, and initializes the secondary indexes for DBC tables. |
| DIPDBCCMT | Initializes the comment string values for DBC tables, views, and macros. Consequently, HELP statement output displays information about expected values for table and view fields, and for macro parameters. |
| DIPDEM | 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. Successful creation of the stored procedures (SQL and external stored procedures), UDFs, and use of the created table functions requires a C compiler to be available on the Teradata system.
|
| DIPDSCSV | Enables the DATASET data type CSV storage format. |
| DIPERR | Loads error message files for storing the text of messages that Teradata Database components, software, and client connections generate. |
| DIPGEO | Initializes the geospatial features of the Teradata Database, creating the SYSSPATIAL spatial_ref_sys database. |
| DIPGLOP | 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 Teradata Vantage™ - SQL External Routine Programming , B035-1147 . DIPGLOP is available only with appropriate licensing. If you require GLOP support, contact your Teradata representative.
|
| DIPJDBC | Support functions for the JDBC API. |
| DIPJSON | Enables JSON functionality in Teradata Database. This script is only available after JSON has been enabled by setting a DBS control field.
|
| DIPMAPS | Creates initial system data distribution maps, in addition to procedures, tables, and views used to manage maps. |
| DIPMIG | Runs the following 5 scripts in preparation for complete system migrations: DIPERR, DIPDB, DIPVIEWS, DIPVIEWSV, and DIPBAR. |
| DIPOLH | Initializes the Online Help Syntax. |
| DIPOCES | Initiates the default cost estimate statistics. |
| DIPPATCH | Initializes standalone patch versions. Automatically executed by PUT for all maintenance and efix upgrades. |
| DIPPDCR | Creates a centralized repository for performance data, and infrastructure to support collection and reporting of performance data. |
| DIPPOST | Initializes objects that have dependencies on other functions and procedures that were previously created by DIP. |
| DIPPWRSTNS | Populates the DBC.PasswordRestrictions table with the list of words disallowed within a password. |
| DIPRCO | Finalizes the initialization of the DBC tables used for reconfiguration. |
| DIPRSS | Adds the ResUsage tables data columns. Allows logging of system performance statistics. |
| DIPRTBLOP | Creates ExecR table operator, which provides in-database analytics capability to users of R. R is an open-source programming language for statistical modeling and graphics. For more information on ExecR, see Teradata Vantage™ - SQL External Routine Programming , B035-1147 . |
| DIPRUM | Loads Resource Usage views and macros and enables report generation from data stored in the ResUsage system tables. 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.
|
| DIPSQLJ | Enables Java-based external stored procedures. Successful creation of the external stored procedures requires that there be a C compiler on the Teradata system.
|
| DIPSTATS | For more information, see Application Programming Reference. This script should not be run independently. It is run automatically as part of the DIPALL script.
|
| DIPSYSFE | Initializes the macros, procedures, and views that reside within the SystemFE database. |
| DIPSYSFNC | Enables Teradata Database system functions and Embedded Services Functions. |
| DIPSYSUIF | 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 Teradata Vantage™ - SQL Operators and User-Defined Functions, B035-1210. |
| DIPSZVIEWS | Creates legacy system views infrastructure for Secure Zones feature. This script must be run at the time Secure Zones is enabled, and is usually run by Teradata Support personnel. This script is not visible in the DIP menu unless the Secure Zones feature is enabled. Contact your Teradata representative to enable this feature.
|
| DIPSZVIEWSV | Creates Unicode system views infrastructure for Secure Zones feature. This script must be run at the time Secure Zones is enabled, and is usually run by Teradata Support personnel. This script is not visible in the DIP menu unless the Secure Zones feature is enabled. Contact your Teradata representative to enable this feature.
|
| DIPTDWM | Creates or upgrades the database infrastructure for workload management and alerting. 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.
|
| DIPUDT | Initializes the infrastructure for creating UDT objects and Period Data Type objects. |
| DIPVIEWS | Creates the non-Unicode compliant views and macros for access to DBC objects. |
| DIPVIEWSV | Creates the Unicode compliant views and macros for access to DBC objects, and populates all the comments for DBC system tables. |
| DIPXML | 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 dip n.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.