Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.
Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Ingestion and Replication H2L
  • All Products

Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. Ingesting Db2 for i Change Data into Snowflake with Cloud Mass Ingestion Databases

Ingesting Db2 for i Change Data into Snowflake with Cloud Mass Ingestion Databases

Ingesting Db2 for i Change Data into Snowflake with Cloud Mass Ingestion Databases

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

  • Verify that you use a Db2 for i version that
    Mass Ingestion Databases
     supports. See the KB article FAQ: What are the supported sources and targets for IICS Cloud Mass Ingestion service?.
  • For incremental load jobs and combined initial and incremental load jobs, grant the appropriate level of authority for accessing the Db2 journal and file objects that
    Mass Ingestion Databases
     uses to the user ID that runs
    database ingestion
     jobs. The following table lists these objects and their Db2 authority requirements:
    Object
    Authority
    Journal
    *USE *OBJEXIST
    Journal Library
    *USE
    Journal Receiver
    *USE
    Journal Receiver Library
    *USE
    File
    *USE
    File Library
    *USE
  • 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.
  • By default,
    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 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.
  • To use SSL data encryption for Db2 for i sources, when you configure the Db2 for i connection properties, select
    JTOpen
     in the
    JDBC Driver
     field and select
    SSL
     in the
    Encryption Method
     field.
    Also, add the required certificates to the Informatica Cloud Secure Agent JRE cacerts keystore in one of the following locations:
    For Linux: 
    Secure Agent Directory
    \jdk\jre\lib\security\cacerts
    For Windows: 
    Secure Agent Directory
    \apps\jdk
    LatestVersion
    \jre
    After you add the certificates, restart the Secure Agent to ensure the changes are reflected in the agent services app-truststore.jks files for the latest instances.
    For more information about adding certificates to the keystore, see HOW TO: Import certificates into Informatica Cloud Secure Agent JRE.

Usage considerations

  • Because
    Mass Ingestion Databases
     expects each source table row to be unique, Informatica recommends that each source table have a primary key.
    Mass Ingestion Databases
     does not honor unique indexes in place of a primary key. If no primary key is specified,
    Mass Ingestion Databases
     treats all columns as if they are part of the primary key.
  • 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.
  • Schema drift options are available for Db2 for i sources in database ingestion incremental load and combined initial and incremental load jobs.
    If you set the Add Column option to Replicate and then add a column with a default value to a Db2 for i source table,
    Mass Ingestion Databases
     adds the default value to the newly added table rows to the target. However, existing rows on the target are not updated to reflect the default values. To get the default value populated to the existing target rows, perform another initial load to re-materialize the target.
  • 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.
0 COMMENTS
We’d like to hear from you!