Loading Data to IBM DB2 for iSeries

11

14.8.2 Integrating Data in IBM DB2 for iSeries

Oracle Data Integrator provides Knowledge Modules that implement optimized data integration strategies for IBM DB2 for iSeries. These optimized IBM DB2 for iSeries KMs are listed in Table 14–6 . I In addition to these KMs, you can also use the Generic SQL KMs. The IKM choice in the Interface Flow tab determines the performances and possibilities for integrating. Using Slowly Changing Dimensions For using slowly changing dimensions, make sure to set the Slowly Changing Dimension value for each column of the target datastore. This value is used by the IKM DB2 400 Slowly Changing Dimension to identify the Surrogate Key, Natural Key, Overwrite or Insert Column, Current Record Flag and StartEnd Timestamps columns.

14.9 Specific Considerations with DB2 for iSeries

This section provides specific considerations when using Oracle Data Integrator in an iSeries environment.

14.9.1 Installing the Run-Time Agent on iSeries

The Oracle Data Integrator Standalone Agent can be installed on iSeries. See the Oracle Fusion Middleware Installation Guide for Oracle Data Integrator for more information.

14.9.2 Alternative Connectivity Methods for iSeries

It is preferable to use the built-in IBM DB2 Datadirect driver in most cases. This driver directly use the TCPIP network layer and require no other components installed on the client machine. Other methods exist to connect DB2 on iSeries.

14.9.2.1 Using Client Access

It is also possible to connect through ODBC with the IBM Client Access component installed on the machine. This method does not have very good performance and does not support the reverse engineering and some other features. It is therefore not recommended. Table 14–6 KMs for integrating data to IBM DB2 for iSeries KM Notes IKM DB2 400 Incremental Update Integrates data in an IBM DB2 for iSeries target table in incremental update mode. IKM DB2 400 Incremental Update CPYF Integrates data in an IBM DB2 for iSeries target table in incremental update mode. This IKM is similar to the IKM DB2 400 Incremental Update except that it uses the CPYF native OS400 command to write to the target table, instead of set-based SQL operations. IKM DB2 400 Slowly Changing Dimension Integrates data in an IBM DB2 for iSeries target table used as a Type II Slowly Changing Dimension in your Data Warehouse. 12 Product TitleBookTitle as a Variable

14.9.2.2 Using the IBM JT400 and Native Drivers

This driver appears as a jt400.zip file you must copy into your Oracle Data Integrator installation drivers directory. To connect DB2 for iSeries with a Java application installed on the iSeries machine, IBM recommends that you use the JT400 Native driver jt400native.jar instead of the JT400 driver jt400.jar. The Native driver provides optimized access to the DB2 system, but works only from the iSeries machine. To support seamlessly both drivers with one connection, Oracle Data Integrator has a built-in Driver Wrapper for AS400. This wrapper connects through the Native driver if possible, otherwise it uses the JT400 driver. It is recommended that you use this wrapper if running agents installed on AS400 systems. To configure a data server with the driver wrapper:

1. Change the driver and URL to your AS400 server with the following information:

■ Driver : com.sunopsis.jdbc.driver.wrapper.SnpsDriverWrapper ■ URL : jdbc:snps400:machine_ name[;param1=value1[;param2=value2...]]

2. Set the following java properties for the java machine the run-time agent deployed

on iSeries: ■ HOST_NAME: comma separated list of host names identifying the current machine. ■ HOST_IP: IP Address of the current machine. The value allow the wrapper to identify whether this data server is accessed on the iSeries machine or from a remote machine.

14.10 Troubleshooting

This section provides information on how to troubleshoot problems that you might encounter when using Oracle Knowledge Modules. It contains the following topics: ■ Troubleshooting Error messages ■ Common Problems and Solutions

14.10.1 Troubleshooting Error messages

Errors in Oracle Data Integrator appear often in the following way: java.sql.SQLException: The application server rejected the connection.Signon was canceled. at ... at ... ... the java.sql.SQLExceptioncode simply indicates that a query was made to the database through the JDBC driver, which has returned an error. This error is frequently a database or driver error, and must be interpreted in this direction. Only the part of text in bold must first be taken in account. It must be searched in the DB2 or iSeries documentation. If its contains sometimes an error code specific to your system, with which the error can be immediately identified.