in black and white
Main menu
Share a book About us Home
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

Teradata RDBMS Database Administration - NCR

NCR Teradata RDBMS Database Administration - NCR , 2004. - 616 p.
Download (direct link): teradatadatabaseadmin2004.pdf
Previous << 1 .. 185 186 187 188 189 190 < 191 > 192 193 194 195 196 197 .. 218 >> Next

ARC Using NetVault with Teradata Plugin Software

This utility has a GUI front-end to an ARC interface. For details on capabilities and configurations, see "Archiving with NetVault" on page 8-4 and nETVAULT Application Plugin Module User's Guide for Teradata by BakBone Software, Inc.

Teradata Parallel Data Pump (TPump)

The TPump utility allows real-time updates from transactional systems into the warehouse. TPump executes INSERT, UPDATE and DELETE statements, or a combination, to more than 60 tables at a time from the same source-feed.

TPump is an alternative to MultiLoad and is designed to replace BulkLoad.

The benefits of TPump include:

B - 2 Teradata RDBMS Database Administration

Appendix B: Import/Export Utilities

Import/Export Utilities

• Real-time inserts/updates to more than 60 tables simultaneously

• Low-volume batch maintenance

• Can provides continuous feed to the warehouse

• Runs in MVS, VM, UNIX, and Windows 2000 client environments

The data-handling functionality of TPump is enhanced by the TPump Support Environment. In addition to coordinating activities involved in TPump tasks, it provides facilities for managing file acquisition, conditional processing, and certain Data Manipulation Language (DML) and Data Definition Language (DDL) activities, on the Teradata RDBMS.

The TPump Support Environment enables an additional level of user control over TPump. For more information, see Teradata Parallel Data Pump Reference.

Restarts on TPump Jobs with Identity Column

TPump works on multi-statement requests. Each request has a specific number of statements depending on the PACK specification in the BEGIN LOAD command.

In ROBUST mode, each request is written into a restart log table. Since Teradata RDBMS guarantees either completion or rollback of all statements packed in a request, the restart log will always accurately reflect the completion status of a TPump import.

If a restart occurs, TPump will query the restart log table and re-execute requests that are not logged. This means it may be possible for a restart to generate duplicates if an insert request is repeated. Duplicates will not be detected if the target table is not defined with a UPI.

TPump will flag an error if it is run in simple mode and the target table has an identity column PI. This is because no restart log is used for restart recovery and duplicate rows could result if some requests are re-processed.

For more information on this utility, see Teradata Parallel Data Pump Reference.

Teradata Warehouse Builder

TeraBuilder is an object-oriented software system that executes multiple instances of data extraction, transformation, and load functions in a scalable, high-speed parallel-processing environment.

The main functional components of the TeraBuilder Infrastructure are the TeraBuilder processor, operator interface, and operators.

Components of the TeraBuilder Infrastructure

Each component is introduced in the following table. For more information, see

Teradata Warehouse Builder Reference.

B - 2

Teradata RDBMS Database Administration Appendix B: Import/Export Utilities

Import/Export Utilities

Component Description
Processor The TeraBuilder Processor parses, compiles, and executes the series of statements that you submit as a TeraBuilder job script. Functional components of the TeraBuilder Processor include: • An interface for submitting user requests • A compiler that validates the TeraBuilder job script statements and generates and optimizes an internal operating plan • An internal metadata manager • A data stream controller that uses parallel launch and interprocess communication facilities for routing data between operators • A checkpoint-restart manager that provides recovery functions for the entire TeraBuilder job
Operator Interface The TeraBuilder Operator Interface is a bidirectional call-level interface that provides the intercommunication between the TeraBuilder Processor and the TeraBuilder operators. All functional communication within the TeraBuilder Infrastructure is through the TeraBuilder Operator Interface— there is no direct communication between TeraBuilder operators, or between operators and the TeraBuilder Processor.
Operators Operators are the software components of the TeraBuilder Infrastructure that provide the actual data extract, transform, and load functions in support of various data stores.
Supported Record Formats
Record formats supported by these utilities may be any combination of the following:
Format Description
Teradata internal See the format outline below. This format is referred to as DATA in FastLoad utilities, and FASTLOAD in MultiLoad and FastExport utilities.
VAR Text Contains an undefined number of bytes with a defined field separator followed by and end-of-line character or sequence.
Unformatted Contains a stream of bytes with no control bytes. The layout of these records are defined by the applicable utility.
Previous << 1 .. 185 186 187 188 189 190 < 191 > 192 193 194 195 196 197 .. 218 >> Next