Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Replication 9.7.0
  • All Products

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

User Guide

User Guide

Back Next

Saving Replication Configurations to the Main Server Manager

Saving Replication Configurations to the Main Server Manager

After configuring a data replication in the Data Replication Console, save the configuration to the Server Manager.
  1. Click
    File
    Save
     on the menu bar, or click the
    Save
     icon button on the main toolbar.
  2. For Oracle sources, if all of the tables in the new configuration have a primary key definition or unique index, the Data Replication Console, by default, displays a prompt that asks if you want to run supplemental logging. Click
    Yes
     to enable supplemental logging for the source tables in the configuration.
    If you do not have sufficient privileges to manage database supplemental logging in Data Replication, the Console displays a warning message. In this case, save the configuration and follow the instructions in Managing Oracle Supplemental Log Groups to configure supplemental log groups and then save the generated SQL statements to a script file, which you can give to a database administrator.
    If you click
    Yes
     and a table includes a unique index that has only nullable columns, the Console enables supplemental logging for the unique index columns so that the Applier can build a WHERE clause to replicate Updates and Deletes. However, the Applier might then apply Update or Delete operations to an incorrect row if a table contains multiple rows with the same value in a unique index column. To prevent this problem, verify that the table does not contain multiple rows in which all index columns contain null values.
  3. For DB2 and Oracle sources, if any source table in the new configuration does not have a primary key or unique index definition, the Data Replication Console prompts you to select an option for replicating these tables.
    The following image shows this prompt:
    The prompt appears only if the
    Ask
     option under
    Supplemental Logging Settings
     is selected on the
    Runtime Settings
     tab >
    General
     view. The
    Ask
     option is selected by default.
    Options are:
    • View these tables
      . Displays only the affected mapped tables on the
      Map Tables
       tab. A prompt notifies you that enabling supplemental logging was canceled. Click
      OK
      . You can then assign a primary key or unique index definition to these tables in the source database, or save the configuration again to select a different option from the prompt.
    • Disable replication of UPDATE and DELETE operations for these tables
      . Allows you to replicate the configuration without assigning a primary key or unique index for the affected tables. This option minimizes the potential for replication errors, but Data Replication will not apply any Update or Delete operations from the source tables to the target.
    • Create a virtual index for all table columns
      . Allows Data Replication to create a virtual index and (for Oracle sources) supplemental log groups for all table columns. Informatica recommends this option.
      Data Replication uses the following naming pattern to create supplemental log groups for Oracle sources: 
      IDR_<
      object_ID_of_source_table
      >_<
      sequence_number
      >
      The incremental sequence number begins with 1 and is used to differentiate between the multiple supplemental log groups that are generated for a single table with more than 33 columns.
      After you save the configuration, you can edit which table columns are included in supplemental log groups on the
      Map Tables
       tab in the
      Manage Oracle Supplemental Log Groups
       dialog box.
    • Ignore
      . Saves the configuration without changes. Informatica does not recommend selecting this option because Update and Delete operations might be replicated incorrectly for the tables that do not have a primary key or unique index definition.
  4. For DB2 sources, the Data Replication Console displays a prompt that asks if you want to manage the DB2 DATA CAPTURE settings for the mapped source tables. Click
    Yes
     to manage these settings for the tables in the configuration. After you save the configuration, you can edit the DATA CAPTURE settings in the
    Manage DB2 DATA CAPTURE Settings
     dialog box, which is accessed from the
    Map Tables
     tab.
  5. For targets that use a recovery table, the Data Replication Console displays the
    Enter Recovery Table Name and Schema
     dialog box. Accept the default schema and table name for the recovery table that will be on the primary target or enter another schema or table name. For some targets, you might need to specify a database or owner name. Then click
    Yes
    .
    The Data Replication Console sets the apply.recovery_enabled parameter to 1 and the apply.recovery_table parameter to the recovery table name on the
    Runtime Settings
     tab >
    Advanced Settings
     view. When you start the Applier later, it transparently creates the recovery table on the target. For the Applier to create the recovery table, it must run under a user ID that has the privileges required to create a table on the target.
    If you click
    No
    , the recovery table is not created and the apply.recovery_enabled parameter is set to 0. If you want to use a recovery table later, you can create it in one of the following ways:
    • Manually create the table by using scripts. For more information, see DDL Statements for Manually Creating Recovery Tables. Then set the apply.recovery_enabled parameter to 1 and set the apply.recovery_table parameter to the schema and table name of the table that you created, before saving the configuration again.
    • Edit the configuration to set the apply.recovery_enabled runtime parameter to 1. Then save the configuration again. The
      Enter Recovery Table Name and Schema
       dialog box appears. Specify the schema and table name of the recovery table and click
      Yes
      . The Data Replication Console sets the apply.recovery_table parameter to the recovery table name. When you start the Applier later, it will create the recovery table.
The Server Manager saves the configuration on the Main server system.
0 COMMENTS
We’d like to hear from you!