Reverse-engineer a Teradata Model

11-6 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator 4. Set REVERSE_COLUMN_CHARACTER_SET to true if you want to reverse-engineer VARCHAR and CHAR for a Unicode database as CHARCHARACTER SET UNICODE or VARCHARCHARACTER SET UNICODE respectively, regardless of the use of CHARACTER SET UNICODE clause at table creation. The reverse-engineering process returns tables, views, columns, Keys primary indexes and secondary indexes and Foreign Keys. Descriptive information Column titles and short descriptions are also reverse-engineered Note that Unique Indexes are reversed as follows: ■ The unique primary index is considered as a primary key. ■ The primary index is considered as a non unique index. ■ The secondary unique primary index is considered as an alternate key ■ The secondary non unique primary index is considered as a non unique index. You can use this RKM to retrieve specific Teradata metadata that is not supported by the standard JDBC interface such as primary indexes.

11.6 Setting up Data Quality

Oracle Data Integrator provides the CKM Teradata for checking data integrity against constraints defined on a Teradata table. See Set up Flow Control and Post-Integration Control in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for details. Oracle Data Integrator provides the Knowledge Module listed in Table 11–2 to perform a check on Teradata.

11.7 Designing an Interface

You can use Teradata as a source, staging area or a target of an integration interface. It is also possible to create ETL-style integration interfaces based on the Teradata technology. The KM choice for an interface or a check determines the abilities and performance of this interface or check. The recommendations in this section help in the selection of the KM for different situations concerning a Teradata data server.

11.7.1 Loading Data from and to Teradata

Teradata can be used as a source, target or staging area of an interface. The LKM choice in the Interface Flow tab to load data between Teradata and another type of data server is essential for the performance of an interface. Table 11–2 Check Knowledge Modules for Teradata Database Recommended KM Notes CKM Teradata Checks data integrity against constraints defined on a Teradata table. Rejects invalid records in the error table created dynamically. Can be used for static controls as well as flow controls. This KM supports the following Teradata optimizations: ■ Primary Indexes ■ Statistics Teradata 11-7

11.7.1.1 Loading Data from Teradata

Use the Generic SQL KMs or the KMs specific to the other technology involved to load data from a Teradata database to a target or staging area database. For extracting data from a Teradata staging area to a file, use the IKM File to Teradata TTU. See Section 11.7.2, Integrating Data in Teradata for more information.

11.7.1.2 Loading Data to Teradata

Oracle Data Integrator provides Knowledge Modules that implement optimized methods for loading data from a source or staging area into a Teradata database. These optimized Teradata KMs are listed in Table 11–3 . In addition to these KMs, you can also use the Generic SQL KMs or the KMs specific to the other technology involved. Table 11–3 KMs for loading data to Teradata Source or Staging Area Technology KM Notes File LKM File to Teradata TTU Loads data from a File to a Teradata staging area database using the Teradata bulk utilities. Because this method uses the native Teradata utilities to load the file in the staging area, it is more efficient than the standard LKM File to SQL when dealing with large volumes of data. Consider using this LKM if your source is a large flat file and your staging area is a Teradata database. This KM support the following Teradata optimizations: ■ Statistics ■ Optimized Temporary Tables Management