tasks, first prepare the source database and review the usage considerations.
Source preparation
Database ingestion and replication
incremental load jobs with a Db2 for z/OS source use a stored procedure to call the Db2 Instrumentation Facility Interface (IFI) to read change data from Db2 logs on the z/OS source system.
Database Ingestion and Replication
delivers the stored procedure libraries and JCL in the Db2 for zOS Database Ingestion connector package ZIP file. You must receive the stored procedure libraries into an APF-authorized library and then customize the JCL for your environment. The stored procedure runs in a Workload Manager (WLM) address space on the Db2 source system. For more information about z/OS system requirements, stored procedure setup, and required permissions, see
Installing and configuring the stored procedure for Db2 for z/OS CDC.
When you define a Db2 source in a
database ingestion and replication
incremental load task, you must select the option
Enable CDC for all columns
in the
CDC Script
field.
Database Ingestion and Replication
generates a script for enabling Db2 DATA CAPTURE CHANGES on the source tables and on certain Db2 catalog tables that are used for CDC. After this attribute is set for one job, all other jobs recognize that the attribute is enabled in Db2 for the catalog tables needed. You can either execute the CDC script from the user interface if you have sufficient privileges or ask a Db2 DBA who has SYSDBA authority to run the script.
Make sure the
Database Ingestion and Replication
user has the Db2 for z/OS privileges that are required for the
uses the Progress DataDirect JDBC IBM DB2 driver to connect to a Db2 for z/OS source. For a new implementation of
Database Ingestion and Replication
with Db2 for z/OS sources, the user who first runs an incremental job must have SYSADM or SYSDBA authority to establish JDBC connectivity.
If you perform both initial loads and incremental loads and want to use different users with different Db2 for z/OS privileges for these job types, perform the following steps:
Create separate Db2 for z/OS Database Ingestion connections for initial loads and incremental loads. In the connection properties, specify a user who has the Db2 privileges required for an initial load job or incremental load job that uses the connection.
To restrict access to connections to certain users, you can set explicit user permissions on a connection asset in
Administrator
. To use the connection for running a job, the user must have the Execute permission. This practice prevents a user who has a lower level of privileges from running a job that requires a higher level of permissions.
When you create a
database ingestion and replication
that uses the initial load or incremental load type, select the connection that specifies a user with the required Db2 privileges and asset permission.
Usage considerations
Because
Database Ingestion and Replication
expects each source table row to be unique, Informatica recommends that each source table have a primary key.
Database Ingestion and Replication
does not honor unique indexes in place of a primary key. If no primary key is specified,
Database Ingestion and Replication
treats all columns as if they are part of the primary key.
The default setting for z/OS is that schema drift is enabled when you run the ALTER statements for the catalog tables. Once schema drift is enabled for one job, it is enabled for all jobs. If jobs are running when the ALTER statements are running, the running jobs do not have schema drift enabled until they are subsequently stopped and resumed.
Database Ingestion and Replication
does not support schema drift for Db2 11 for z/OS sources.
Database Ingestion and Replication
does not support the following Db2 for z/OS data types:
BLOB
CLOB
DBCLOB
XML
Database ingestion and replication
jobs propagate nulls for columns that have these data types.