Supported Objects and Operations for DB2 z/OS

This section lists the database objects and types of operations that Oracle GoldenGate supports.

  • Extraction and replication of DML operations on DB2 for z/OS tables that contain rows of up to 512KB in length. This size exceeds the maximum row size of DB2.

  • INSERT operations from the IBM LOAD utility are supported for change capture if the utility is run with LOG YES and SHRLEVEL CHANGE, and the source tables that are being loaded have DATA CAPTURE CHANGES enabled (required by Oracle GoldenGate) and are specified in the Oracle GoldenGate Extract configuration. Oracle GoldenGate also supports initial loads with the LOAD utility to instantiate target tables during initial synchronization.

  • Oracle GoldenGate supports the maximum number of columns per table, which is supported by the database.

  • Oracle GoldenGate supports the maximum column size that is supported by the database.

  • Extraction and replication of data that is stored using DB2 data compression (CREATE TABLESPACE COMPRESS YES).

  • Capture from temporal history tables is supported.

  • TRUNCATE TABLE is supported, but because this command issues row deletes to perform the truncate, they are shown in Oracle GoldenGate statistics as such, and not as a truncate operation. To replicate a TRUNCATE , the Replicat process uses a DELETE operation without a WHERE clause.

  • TRUNCATES are always captured from a DB2 for z/OS source, but can be ignored by Replicat if the IGNORETRUNCATES parameter is used in the Replicat parameter file.

  • UNICODE columns in EBCDIC tables are supported.

  • Supported options with SHOWTRANS
    SHOWTRANS [transaction_ID]  [COUNT n]
[DURATION duration unit] 
[FILE file_name] |

    transaction_ID and count cannot be specified together.

    transaction_ID and duration cannot be specified together.

  • Options supported with SKIPTRANS and FORCETRANS:
    SKIPTRANS transaction_ID  
[FORCE] FORCETRANS transaction_ID  [FORCE]