Creating a Netezza Physical Schema

10-4 Oracle® Fusion Middleware Connectivity and Knowledge Modules Guide for Oracle Data Integrator Create for this physical schema a logical schema using the standard procedure, as described in Creating a Logical Schema of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator and associate it in a given context.

10.4 Setting Up an Integration Project

Setting up a project using the Netezza database follows the standard procedure. See Creating an Integration Project of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. It is recommended to import the following knowledge modules into your project for getting started with Netezza: ■ CKM Netezza ■ IKM Netezza Control Append ■ IKM Netezza Incremental Update ■ IKM Netezza To File EXTERNAL TABLE ■ LKM File to Netezza EXTERNAL TABLE ■ LKM File to Netezza NZLOAD ■ RKM Netezza

10.5 Creating and Reverse-Engineering a Netezza Model

This section contains the following topics: ■ Create a Netezza Model ■ Reverse-engineer a Netezza Model

10.5.1 Create a Netezza Model

Create a Netezza Model using the standard procedure, as described in Creating a Model of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator.

10.5.2 Reverse-engineer a Netezza Model

Netezza supports both Standard reverse-engineering - which uses only the abilities of the JDBC driver - and Customized reverse-engineering. In most of the cases, consider using the standard JDBC reverse engineering for starting. Consider switching to customized reverse-engineering if you encounter problems with the standard JDBC reverse-engineering process due to some specificities of the Netezza JDBC driver. Note: When performing this configuration, the work and data databases names must match. Note also that the dollar sign is an invalid character for names in Netezza. Remove the dollar sign from work table and journalizing elements prefixes. Netezza 10-5 Standard Reverse-Engineering To perform a Standard Reverse-Engineering on Netezza use the usual procedure, as described in Reverse-engineering a Model of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. Customized Reverse-Engineering To perform a Customized Reverse-Engineering on Netezza with a RKM, use the usual procedure, as described in Reverse-engineering a Model of the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator. This section details only the fields specific to the Netezza technology: 1. In the Reverse tab of the Netezza Model, select the KM: RKM Netezza.project name. The reverse-engineering process returns tables, views, columns, Keys and Foreign Keys.

10.6 Setting up Data Quality

Oracle Data Integrator provides the CKM Netezza for checking data integrity against constraints defined on a Netezza table. See Set up Flow Control and Post-Integration Control in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for details.

10.7 Designing an Interface

You can use Netezza as a source, staging area, or a target of an integration interface. 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 Netezza data server.

10.7.1 Loading Data from and to Netezza

Netezza 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 Netezza and another type of data server is essential for the performance of an interface.

10.7.1.1 Loading Data from Netezza

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

10.7.1.2 Loading Data to Netezza

Oracle Data Integrator provides Knowledge Modules that implement optimized methods for loading data from a source or staging area into a Netezza database. These optimized Netezza KMs are listed in Table 10–2 . In addition to these KMs, you can also use the Generic SQL KMs or the KMs specific to the other technology involved.