Creating a DB2400 Physical Schema

5

14.5.1 Create an IBM DB2400 Model

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

14.5.2 Reverse-engineer an IBM DB2400 Model

IBM DB2 for iSeries supports both Standard reverse-engineering - which uses only the abilities of the JDBC driver - and Customized reverse-engineering, which uses a RKM to retrieve the metadata. In most of the cases, consider using the standard JDBC reverse engineering for starting. Consider switching to customized reverse-engineering for retrieving more metadata. IBM DB2 for iSeries customized reverse-engineering retrieves the physical files, database tables, database views, columns, foreign keys and primary and alternate keys. Standard Reverse-Engineering To perform a Standard Reverse-Engineering on IBM DB2 for iSeries 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 IBM DB2 for iSeries 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 IBM DB2400 technology: In the Reverse tab of the IBM DB2400 Model, select the KM: RKM DB2 400.project name.

14.6 Setting up Changed Data Capture

Oracle Data Integrator handles Changed Data Capture on iSeries with two methods: ■ Trigger-based CDC on the journalized tables. This method is set up with the JKM DB2400 Simple or JKM DB2400 Consistent. This CDC is not different from the CDC on other systems. See Section 14.6.1, Setting up Trigger-Based CDC for more information. ■ Log-based CDC by reading the native iSeries transaction journals. This method is set up with the JKM DB2400 Journal Simple and used by the LKM DB2400 Journal to SQL. This method does not support Consistent Set CDC and requires a platform-specific configuration. See Section 14.6.1, Setting up Trigger-Based CDC for more information.

14.6.1 Setting up Trigger-Based CDC

This method support Simple Journalizing and Consistent Set Journalizing. The IBM DB2 for iSeries JKMs use triggers to capture data changes on the source tables. Oracle Data Integrator provides the Knowledge Modules listed in Table 14–2 for journalizing IBM DB2 for iSeries tables using triggers.