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

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

Db2 for z/OS sources

Db2 for z/OS sources

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

Source preparation

  • Database ingestion 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. Mass Ingestion Databases 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 incremental load task, you must select the option
    Enable CDC for all columns
    in the
    CDC Script
    field.
    Mass Ingestion Databases
    generates a script for enabling CDC on the source tables. You can either execute the CDC script from the user interface if you have been granted the following privilege or ask a Db2 DBA who has SYSDBA authority to run the script:
    GRANT ALTER TABLE
    schema
    .
    table
    DATA CAPTURE CHANGES TO
    user
    <--for each source table COMMIT;
  • For incremental load operations, ensure that the following privileges and authorities are granted:
    If you do not have the authority required to issue these grants, ask a Db2 administrator who has SYSDBA authority or a higher authority level to issue them.
    Grant the following privileges to the user specified in the Db2 for zOS Database Ingestion connection properties:
    • To make the change data in the Db2 logs available to the stored procedure:
      GRANT ALTER TABLE
      schema
      .
      table
      DATA CAPTURE CHANGES TO
      user
      <--for each source table COMMIT;
    • To enable the user to obtain required information from the Db2 Instrumentation Facility Interface (IFI):
      GRANT MONITOR2 TO
      user
      ; COMMIT;
    • To grant authorities on the global temporary table to the user:
      GRANT READ ON !SCHEMA!.!STRPRC!_RS_TBL to
      user
      ; GRANT DELETE ON !SCHEMA!.!STRPRC!_RS_TBL to
      user
      ; GRANT EXECUTE !SCHEMA!.!STRPRC! to
      user
      ; COMMIT;
      Where !SCHEMA! and !STRPRC! are variables in the job JCL, which represent the stored procedure schema name and procedure name respectively.
      The first two privileges allow the user to read and delete the contents of the Global Temporary Table to which the stored procedure is writing the log data. The third privilege allows the user to run the stored procedure.
    Grant the following privileges to PUBLIC to enable the stored procedure to bind its Db2 plan:
    GRANT BIND, EXECUTE ON PLAN !STRPRC! TO PUBLIC; COMMIT;

Usage considerations

  • Mass Ingestion Databases
    does not support schema drift options for Db2 for z/OS sources in incremental load jobs.
  • Mass Ingestion Databases
    does not support the following Db2 for z/OS data types:
    • BLOB
    • CLOB
    • DBCLOB
    • 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!