1. Using Oracle GoldenGate Classic Architecture for Non-Oracle Databases
  2. Using Oracle GoldenGate for DB2 for i

Part II Using Oracle GoldenGate for DB2 for i

Oracle GoldenGate for DB2 for i supports capture and delivery of initial load and transactional data for supported DB2 for i database versions.

Oracle GoldenGate for DB for i supports the mapping, filtering, and transformation of source data, unless noted otherwise in this document, along with replicating data derived from other source databases supported by Oracle GoldenGate, into DB2 for i databases.

This part describes tasks for configuring and running Oracle GoldenGate for DB2 for i.

Topics:

  • Understanding What's Supported for DB2 for i
    This chapter contains information on database and table features supported by Oracle GoldenGate for DB2 for i.
  • Preparing the System for Oracle GoldenGate
    This chapter contains guidelines for preparing the DB2 for i system to support Oracle GoldenGate.
  • Configuring Oracle GoldenGate for DB2 for i
    This chapter contains instructions for configuring Oracle GoldenGate to capture source DB2 for i data and apply it to a supported target database.
  • Instantiating and Starting Oracle GoldenGate Replication
    This chapter contains instructions for configuring an initial load of target data, adding the required processes to instantiate replication, and perform the instantiation. The expected outcome of these steps is that source-target data is made consistent (known as the initial synchronization), and that Oracle GoldenGate captures and delivers ongoing transactional changes so that consistency is maintained going forward.
  • Using Remote Journal
    This chapter contains instructions for remote journal preparation and adding a remote journal. Remote Journal support in the IBM DB2 for i operating system provides the ability for a system to replicate, in its entirety, a sequence of journal entries from one DB2 for i system to another. Once setup, this replication is handled automatically and transparently by the operating system. The entries that are replicated are placed in a journal on the target system that is available to be read by an application in the same way as on the source system.