1. Oracle GoldenGate Microservices Documentation
  2. Install and Patch
  3. Choose an Operating System for Installing Oracle GoldenGate for Db2 z/OS Remote Capture and Delivery

Choose an Operating System for Installing Oracle GoldenGate for Db2 z/OS Remote Capture and Delivery

Oracle GoldenGate for Db2 z/OS operates remotely on zLinux, AIX or Intel Linux systems. To capture data, a component must be installed on the Db2 z/OS system before installing Oracle GoldenGate. This component contains the Db2 instance to allow Oracle GoldenGate to read the Db2 log data.

To install Oracle GoldenGate on a remote zLinux, AIX or Linux system, choose from the following options to connect to Db2 z/OS:

  • Db2 Connect v10.5 or greater

  • IBM Data Server Driver for ODBC and CLI v10.5 or greater

  • IBM Data Server Client v10.5 or greater

  • IBM Data Server Runtime Client v10.5 or greater

Consider the following:

  • Extract uses Open Database Connectivity (ODBC) to connect to the Db2 subsystem on the z/OS system. If one of the other drivers is not already installed, the IBM Data Server Driver for ODBC and CLI is the most lightweight driver and is recommended for most configurations, although the other drivers are suitable also.

  • To capture Db2 log data, the log reader component must be installed in a Library (PDSE) on the z/OS system. Load Libraries (PDS) are not supported. The library must be authorized program facility (APF) helps your installation protect the system. APF-authorized programs can access system facility (APF) authorized. The log read component is called through SQL from the remote system and since it is APF authorized, an authorized Workload Manager (WLM) environment must also be used to run these programs since the default Db2 supplied WLM environment is not able to run authorized workload.

  • No special requirements beyond what capture already has for Oracle GoldenGate delivery. Because this Oracle GoldenGate release is a fully-remote distribution, the former Oracle GoldenGate Db2 Remote product is no longer shipped separately. However, Windows is not supported in Oracle GoldenGate for Db2 z/OS in this release. If you still require delivery to z/OS from Windows, then Oracle GoldenGate Db2 Remote 12.2 is still available.

  • UNIX System Services (USS) is no longer required (as in prior releases) except for a few installation procedures.

  • Windows only: To apply data to a Db2 target from Windows, Oracle GoldenGate Db2 Remote v12.2 must be used. Capture is not supported in this scenario.

  • Install Oracle GoldenGate Db2 Remote on a remote system for remote delivery to the Db2 target system. In this configuration, Replicat connects to the target Db2 database by using the ODBC API that is supplied in DB2Connect. This configuration requires Db2 z/OS to be installed on the remote system.

    Note:

    All of the Oracle GoldenGate functionality that is supported for Db2 z/OS is supported by DB2Connect. In addition, ASCII character data is converted to EBCDIC automatically by DB2Connect.

  • Although it is possible to install Oracle GoldenGate on zLinux, AIX, and Intel based Linux, the best performance is seen with a system that has the lowest network latency to the z/OS system that you use. Although it is possible to run over a wide area network, the performance suffers due to the increased network latency. Oracle recommends using a zLinux partition on the same physical hardware as the z/OS system that is running Db2 using Hipersockets or a VLAN between the partitions. Otherwise, systems connected with OSA adapters in the same machine room, would be the next best choice. Alternatively, the fastest Ethernet connection between the systems that is available would be acceptable.

Using the Remote Delivery to the Db2 z/OS using DB2Connect

  1. For the intermediary system, select any platform that Oracle GoldenGate supports for the Db2 for LUW database. This is the system on which Oracle GoldenGate is installed.

  2. Install and run Db2 z/OS on the selected remote system so that the Replicat process can use the supplied DB2Connect driver.

  3. Catalog the Db2 target node in the Db2 z/OS database on the remote system by using the following Db2 command:

    catalog tcpip node db2_node_name remote DNS_name server DB2_port-number

  4. Add the target Db2 database to the Db2 z/OS catalog on the intermediary system by using the following Db2 command:

    catalog db database_name as database_alias at node db_node_name

See the IBM Db2 z/OS documentation for more information about these commands.