1. Oracle GoldenGate Classic Documentation
  2. Administer
  3. Performing Administrative Operations
  4. Changing Database Attributes
  5. Adding Tables to the Oracle GoldenGate Configuration

Adding Tables to the Oracle GoldenGate Configuration

This procedure assumes that the Oracle GoldenGate DDL support feature is not in use, or is not supported for, your database.

Note:

For Oracle and MySQL databases, you can enable the DDL support feature of Oracle GoldenGate to automatically capture and apply the DDL that adds new tables, instead of using this procedure. See the appropriate instructions for your database in this documentation.

Review these steps before starting. The process varies slightly, depending on whether or not the new tables satisfy wildcards in the TABLE parameter, and whether or not names or data definitions must be mapped on the target.

Prerequisites for Adding Tables to the Oracle GoldenGate Configuration

  • This procedure assumes that the source and target tables are either empty or contain identical (already synchronized) data.

  • You may be using the DBLOGIN and ADD TRANDATA commands. Before starting this procedure, see Reference for Oracle GoldenGate for the proper usage of these commands for your database.

To Add a Table to the Oracle GoldenGate Configuration

  1. Stop user access to the new tables.
  2. (If new tables do not satisfy a wildcard) If you are adding numerous tables that do not satisfy a wildcard, make a copy of the Extract and Replicat parameter files, and then add the new tables with TABLE and MAP statements. If you do not want to work with a copy, then edit the original parameter files after you are prompted to stop each process.
  3. (If new tables satisfy wildcards) In the Extract and Replicat parameter files, make certain the WILDCARDRESOLVEparameter is not being used, unless it is set to the default of DYNAMIC.
  4. (If new tables do not satisfy a wildcard) If the new tables do not satisfy a wildcard definition, stop Extract.
    STOP EXTRACT group
  5. Add the new tables to the source and target databases.
  6. If required for the source database, issue the ADD TRANDATA command in GGSCI for the new tables. Before using ADD TRANDATA, issue the DBLOGIN command.
  7. Depending on whether the source and target definitins are identical or different, use either ASSUMETARGETDEFS or SOURCEDEFS in the Replicat parameter file. If SOURCEDEFS is needed, you can specify the template with the DEF option of the MAP parameter.
  8. To register the new source definitions or new MAP statements, stop and then start Replicat.
    STOP REPLICAT group
START REPLICAT group
  9. Start Extract, if applicable.
    START EXTRACT group
  10. Permit user access to the new tables.