Problems While Reading Journals

9 ■ The source table should be journaled and the iSeries journal should be readable by the user specified in the iSeries data server. ■ The source table should have one PK defined in Oracle Data Integrator. ■ The PK declared in Oracle Data Integrator should be in the 4096 first octets of the physical record of the data file. ■ The number of columns in the PK should not exceed 16. ■ The total number of characters of the PK column names added to the number of columns of the PK should not exceed 255. ■ Large object datatypes are not supported in the PK. Only the following SQL types are supported in the PK: SMALLINT, INTEGER, BIGINT, DECIMAL Packed, NUMERIC Zoned, FLOAT, REAL, DOUBLE, CHAR, VARCHAR, CHAR VARYING, DATE, TIME, TIMESTAMP and ROWID. ■ Several instances of CDCRTVJRN should not be started simultaneously on the same system. ■ Reinitializing the sequence number in the iSeries journal may have a critical impact on the program program hangs if the journal entries consumption date SNP_SUBSCRIBERS.JRN_CURFROMDATE is before the sequence initialization date. To work around this problem, you should manually set a later date in SNP_ SUBSCRIBERS.JRN_CURFROMDATE. Troubleshooting the CDCRTVJRN Program The journal reading process can be put in trace mode: ■ either by calling from your query tool the CDCRTVJRN stored procedure with the LogMsg parameter set to Y, ■ or by forcing the CREATE_SPOOL_FILE LKM option to 1 then restarting the interface. The reading process logs are stored in a spool file which can be reviewed using the WRKSPLF command. You can also review the raw contents of the iSeries journal using the DSPJRN command.

14.7 Setting up Data Quality

Oracle Data Integrator provides the generic CKM SQL for checking data integrity against constraints defined in DB2400. See Set up Flow Control and Post-Integration Control in the Oracle Fusion Middleware Developers Guide for Oracle Data Integrator for details. See Chapter 4, Generic SQL for more information.

14.8 Designing an Interface

You can use IBM DB2 for iSeries 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 an IBM DB2 for iSeries data server. 10 Product TitleBookTitle as a Variable

14.8.1 Loading Data from and to IBM DB2 for iSeries

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

14.8.1.1 Loading Data from IBM DB2 for iSeries

Oracle Data Integrator provides Knowledge Modules that implement optimized methods for loading data from IBM DB2 for iSeries to a target or staging area database. These optimized IBM DB2 for iSeries KMs are listed in Table 14–4 . In addition to these KMs, you can also use the Generic SQL KMs or the KMs specific to the other technology involved to load data from IBM DB2 for iSeries to a target or staging area database.

14.8.1.2 Loading Data to IBM DB2 for iSeries

Oracle Data Integrator provides Knowledge Modules that implement optimized methods for loading data from a source or staging area into an IBM DB2 for iSeries database. These optimized IBM DB2 for iSeries KMs are listed in Table 14–5 . In addition to these KMs, you can also use the Generic SQL KMs or the KMs specific to the other technology involved. Table 14–4 KMs for loading data from IBM DB2 for iSeries Source or Staging Area Technology KM Notes IBM DB2 for iSeries LKM DB2 400 to DB2 400 Loads data from an IBM DB2 for iSeries source database to an IBM DB2 for iSeries staging area database using CRTDDMF to create a DDM file on the target and transfer data from the source to this DDM file using CPYF. IBM DB2 for iSeries LKM DB2 400 Journal to SQL Loads data from an IBM DB2 for iSeries source to a ANSI SQL-92 compliant staging area database. This LKM can source from tables journalized with the JKM DB2 400 Simple Journal as it refreshes the CDC infrastructure from the journals. Table 14–5 KMs for loading data to IBM DB2 for iSeries Source or Staging Area Technology KM Notes IBM DB2 for iSeries LKM DB2 400 to DB2 400 Loads data from an IBM DB2 for iSeries source database to an IBM DB2 for iSeries staging area database using CRTDDMF to create a DDM file on the target and transfer data from the source to this DDM file using CPYF. SQL LKM SQL to DB2 400 CPYFRMIMPF Loads data from an ANSI SQL-92 compliant source database to an IBM DB2 for iSeries staging area database using a temporary file loaded into the DB2 staging area with CPYFRMIPF.