Table of Contents

Search

  1. Preface
  2. Data Replication Overview
  3. Understanding Data Replication
  4. Sources - Preparation and Replication Considerations
  5. Targets - Preparation and Replication Considerations
  6. Starting the Server Manager
  7. Getting Started with the Data Replication Console
  8. Defining and Managing Server Manager Main Servers and Subservers
  9. Creating and Managing User Accounts
  10. Creating and Managing Connections
  11. Creating Replication Configurations
  12. Materializing Targets with InitialSync
  13. Scheduling and Running Replication Tasks
  14. Implementing Advanced Replication Topologies
  15. Monitoring Data Replication
  16. Managing Replication Configurations
  17. Handling Replication Environment Changes and Failures
  18. Troubleshooting
  19. Data Replication Files and Subdirectories
  20. Data Replication Runtime Parameters
  21. Command Line Parameters for Data Replication Components
  22. Updating Configurations in the Replication Configuration CLI
  23. DDL Statements for Manually Creating Recovery Tables
  24. Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Glossary

Managing Oracle Supplemental Log Groups

Managing Oracle Supplemental Log Groups

For Oracle sources, you can use the Data Replication Console to add or remove the mapped source table columns that are in supplemental log groups. If you did not enable the Console to generate supplemental log groups when you saved the configuration, you can also add a supplemental log group.
To manage supplemental log groups in the Data Replication Console, the configuration must be open in Edit mode. To only view supplemental log groups, without making changes, the configuration can be open in Read mode.
  1. On the
    Map Tables
    tab, click the
    Manage Database Supplemental Logging
    icon button above the source table
    Filter
    list.
    The
    Manage Oracle Supplemental Log Groups
    dialog box appears.
  2. In the
    Schema
    list, select the source schema name for the mapped tables for which you want to view or edit supplemental log group columns.
    The
    Schema
    list displays only the schemas for which one or more source tables are mapped. By default, the source schema that is currently selected on the
    Map Tables
    tab is displayed, if it has at least one mapped table.
    A list of the mapped source tables that use the specified schema appears in the left list box. The following image shows the list of mapped source tables for the DATAREP_USER schema:
    The Supplemental Logging Management dialog box
    To display all source tables and schemas, including unmapped tables and schemas, select
    Show all objects
    . To display only the source tables that do not have a supplemental log group, select
    Show only the tables that do not have a supplemental log group (SLG)
    . To filter the list of source tables, enter the first few letters of a table name in the
    Table Filter
    field. For case-sensitive filtering, enclose the filter value in double quotation marks.
    If the source schema contains thousands of tables or the Data Replication Console runs in a local area network that is remote to the database server network, selecting
    Show all objects
    might significantly increase metadata caching time.
  3. In the left list box, select the source table for which to view or manage the columns in the supplemental log group.
    The
    Columns
    list box on the right displays the table columns and indicates which columns are in the supplemental log group. The
    Indexed
    column indicates whether a column is part of an index or primary key. To display only the columns that are
    not
    in the supplemental log group, select
    Show only the columns that are not in the supplemental log group (SLG)
    .
    Virtual columns in source tables do not appear in the
    Columns
    list box. You cannot add virtual columns to a supplemental log group.
  4. To add all of the columns in the selected source table to the supplemental log group, select
    All Columns
    check box for the table in the left list box. To remove all of the columns in the selected source table from the supplemental log group, clear the
    All Columns
    check box.
    If you want to select or clear the columns individually in the
    Columns
    list box on the right, clear the
    All Columns
    check box for the table.
    If a table has an existing supplemental log group that includes columns that are part of an index or primary key, clearing the
    All Columns
    check box deselects those columns. Informatica recommends that you always include columns that are part of an index or primary key in a supplemental log group to replicate change data accurately.
    After you edit the
    All Columns
    check box, a pencil icon appears next to it.
  5. In the
    Columns
    list box on the right, use the
    In IDR SLG
    check box to edit the columns that are in the supplemental log group:
    • To remove a column, clear the
      In IDR SLG
      check box.
    • To add a column, select the
      In IDR SLG
      check box.
    The
    In IDR SLG
    check box is unavailable for columns that have the following attributes:
    • Columns that contain Oracle datatypes that Data Replication does not support. You cannot add these columns to a supplemental log group.
    • Columns that contain the following Oracle datatypes: BLOB, CLOB, LONG, LONG RAW, NCLOB, and RAW. You cannot add these columns to a supplemental log group.
    To select all eligible columns in all of the source tables, click
    Select All
    . To clear all columns in all of the source tables, click
    Clear All
    . To revert to the supplemental log group settings that appeared when you first opened the
    Manage Oracle Supplemental Log Groups
    dialog box, click
    Reset
    . To refresh the supplemental logging settings to get the latest changes from the source database or the Server Manager CLI, click
    Refresh
    .
    If a supplemental log group exists, Data Replication generates a pair of SQL statements for each table for which you change the columns. Data Replication uses the following syntax for the supplemental log group SQL statements:
    ALTER TABLE
    "schema_name"
    .
    "table_name"
    ADD SUPPLEMENTAL LOG GROUP IDR_<
    object_ID_of_the_source_table
    >_<
    sequence_number
    > (
    "column_name"
    ,
    "column_name"
    ) ALWAYS
    ALTER TABLE
    "schema_name"
    .
    "table_name"
    DROP SUPPLEMENTAL LOG GROUP IDR_<
    object_ID_of_the_source_table
    >_<
    sequence_number
    >
    The ADD statement creates a new supplemental log group with the columns that you selected, and the DROP statement removes the previous supplemental log group if one exists.
    If a supplemental log group does not yet exist for a mapped source table, Data Replication generates only the ADD statement.
    If you edit the columns in the supplemental log group of a source table that is mapped in other configurations, make sure that you include all of the mapped columns from all of the configurations in the supplemental log group. Otherwise, errors might occur during replication processing. Include all table columns if you are not sure which columns to include.
  6. To save the SQL statements to a script file, perform the following substeps:
    1. Click
      Save
      .
      The
      Save
      dialog box appears.
    2. Enter a file name and path and click
      Save
      .
      A message confirms that the script file was saved successfully.
    3. Click
      OK
      .
    You can use the saved script file to run the SQL statements later. If you do not have the authority to run the SQL statements or manage supplemental log groups, give the script file to a database administrator who has the authority to run the statements.
  7. To run the SQL statements before exiting the dialog box, click
    Run
    .
  8. Click
    Close
    .
If you added any columns in unmapped source tables to a supplemental log group, map these tables on the
Map Tables
tab to include them in the replication configuration.

0 COMMENTS

We’d like to hear from you!