Supported Objects and Operations for Db2 for i

Oracle GoldenGate supports the following Db2 for i objects and operations.

  • Extraction and replication of DML operations .

  • Tables with the maximum row length supported by the database.

  • Tables that contain up to the maximum number of columns that is supported by the database, up to the maximum supported column size.

  • TRUNCATE operations are supported and are represented by DELETE FROM with no WHERE clause SQL statements and Clear Physical File Member (CLRPFM).

  • Base tables underlying Materialized Query Tables, but not the MQTs themselves. The target database automatically maintains the content of the MQT based on the changes that are applied to the base tables by Replicat.

  • Both Library (Native) names including members, and SQL names are allowed.

  • Partitioned tables

  • Supported options with SEND EXTRACT SHOWTRANS || SKIPTRANS || FORCETRANS command are:

    Supported options with SHOWTRANS: 

    SHOWTRANS [transaction_ID]  [COUNT n] 
[DURATION duration unit] [TABULAR] 
[FILE file_name] |
  • Options for SKIPTRANS and FORCETRANS:
    SKIPTRANS transaction_ID  [FORCE] 
FORCETRANS transaction_ID  [FORCE]

  • Limitations on Automatic Heartbeat Table support are as follows:

    • The ADD HEARTBEATTABLE command creates a new file called ogghbfreq in the Oracle GoldenGate installation directory. Do not delete this file because the pase heartbeat program reads the frequency values from it.

    • There is an extra executable in the Oracle GoldenGate build folder named ogghb.

    • An extra process named ogghb starts running on the IBM i system when the ADD HEARTBEATTABLE command runs until you disable the heartbeat with the DELETE HEARTBEATTABLE command. This process automatically restarts even if it is killed. To remove this process from the system, use the DELETE HEARTBEATTABLE command.

    • When using the ALTER HEARTBEATTABLE command to change the heartbeat frequency with the PURGE_FREQUENCY or RETENTION_TIME options, it might take some time for the new setting to take affect.

    • There is an initial delay of 30 seconds between ADD HEARTBEATTABLE and the first record is updated in the heartbeat seed table.

    • [THREAD n] and [DETAIL] is not supported.