Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Appendix A: Datetime and Numeric Formatting
  24. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Data Export Process for Teradata Parallel Transporter

Data Export Process for Teradata Parallel Transporter

For Teradata sources, the archive or retirement job can use Teradata Parallel Transporter to export data from Teradata to the Data Vault.
When you run an archive or retirement job, the job checks if Teradata Parallel Transporter is enabled. If Teradata Parallel Transporter is enabled, the job may use a combination of utilities to export data. Teradata Parallel Transporter can only process data types that can be serialized into a string. This includes the following supported data types:
  • BYTEINT
  • SMALLINT
  • INTEGER
  • BIGINT
  • DECIMAL
  • NUMERIC
  • CHAR
  • VARCHAR
  • DATE
  • TIMESTAMP
  • TIMESTAMP WITH TIMEZONE
The job determines the utility to use based on the data types in the source table. The job uses Teradata Parallel Transporter to export data from tables that do not include binary or large object data types, such as BLOB and CLOB. The job uses Teradata JDBC FastExport to export data from tables that include binary or exotic data types.
When you run an archive or retirement job, the job uses a script template to create script files to submit query requests to Teradata Parallel Transporter. Teradata Parallel Transporter rewrites the query requests to optimize the query for maximum parallelism and maximum throughput. Then, Teradata Parallel Transporter writes the query results to BCP files.
Teradata Parallel Transporter saves the BCP files to the BCP file staging directory that is configured in the Data Vault target connection. The Data Vault Loader job moves the BCP files from the BCP file staging directory to the Data Vault.
Teradata Parallel Transporter is not supported in non-bulk mode.
Optionally, Teradata Parallel Transporter can compresses the BCP files. By default, Teradata Parallel Transporter does not compress the BCP files to optimize performance. You may need to compress the BCP files if you have a limited amount of BCP file staging space. You configure BCP compression in the Teradata source connection.
Informatica recommends that you upload Teradata drivers from the source itself so they can be used in the source connection.

0 COMMENTS

We’d like to hear from you!