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

InitialSync Overview

InitialSync Overview

InitialSync is a Data Replication component that uses source tables to materialize targets. Run InitialSync prior to running the Extractor and Applier tasks.
On the system where InitialSync will run, you must install the connectivity software that Data Replication requires for the source database and target database.
InitialSync does not support Apache Kafka, Cloudera, Flat File, and Hortonworks targets. These target types do not require initial synchronization.
Alternatively, if you have a license for Informatica Fast Clone, you can use Fast Clone to perform a high-speed initial load of Oracle data to target systems. Fast Clone works with Oracle sources only. It loads data to most of the same targets that Data Replication supports and also has a data streaming capability for Amazon Redshift, Greenplum, Netezza, Teradata, and Vertica targets. For Greenplum, Netezza, and Teradata targets, DataStreamer is an optional component to load data faster. For Amazon Redshift targets, DataStreamer is a required component that is used transparently and always enabled.

0 COMMENTS

We’d like to hear from you!