Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.
Not Found
English

Page Not Found

The page or file you are looking for has been moved or no longer exists.

The following links might help you find the content you need:


You can also search the Documentation Portal or visit the home page.

English
  • Data Ingestion and Replication
  • All Products

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Back Next

Db2 for i sources

Db2 for i sources

To use Db2 for i sources in database ingestion tasks, first prepare the source database and review the usage considerations.

Source preparation

  • For incremental load jobs, journaling must be active on each database physical file that corresponds to a selected source table. Also, each journal must be configured with the IMAGES(*BOTH) option to store both before and after images of change data.
    If journaling is not active on a physical file for a source table, when you define a
    database ingestion
     task, you can generate a CDC script that activates it. The script issues the following command, which activates journaling and sets the IMAGES option to BOTH: 
    CALL QSYS2.QCMDEXC('STRJRNPF FILE(
    library
    /
    physical-file
    ) JRN(
    library
    /
    journal-name
    )
IMAGES(*BOTH)')
    If journaling is already active for a physical file for a source table, the CDC script output contains the following comment: 
    Table '
    table_name
    ' is skipped because journaling is already enabled.
  • Mass Ingestion Databases uses the DataDirect JDBC for IBM Db2 driver to connect to the Db2 for i database. Informatica recommends that the first user who creates and tests a Db2 for i Database Ingestion connection to the source database has DBA authority on the database. This authority is needed for the driver to create and upload the packages that it uses for Db2 access and to grant the EXECUTE privilege on the packages to PUBLIC. If a DBA user does not perform the first connection test, you must grant *USE authority on the CRTSQLPKG command for creating the packages and grant *CHANGE authority on the library in which the packages are created.

Usage considerations

  • When you define a database ingestion task, on the
    Source
     page, specify a journal name that is associated with the source tables that are enabled for journaling.
    Ensure that the case and spelling of the name in the
    Journal Name
     field and table selection rules match the journal and table name values in the Db2 source catalog.
  • Mass Ingestion Databases
     does not support the following Db2 for i data types:
    • BLOB
    • CLOB
    • DATALINK
    • DBCLOB
    • GRAPHIC
    • LONG VARGRAPHIC
    • VARGRAPHIC
    • XML
    Database ingestion
     jobs propagate nulls for columns that have these data types.
    For information about the default mappings of supported data types, see the Data Type Mappings Reference.
0 COMMENTS
We’d like to hear from you!