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

DDL Replication

DDL Replication

Data Replication supports the replication of many types of DDL operations from DB2 for Linux, UNIX, and Windows, Microsoft SQL Server,
MySQL,
and Oracle sources to a target.
In the Data Replication Console, you can select the types of DDL operations to replicate on the
Map Tables
and
Map Columns
tabs. Also, from the
Map Tables
tab, you can customize apply settings to indicate the types of DDL changes to apply.
When the Data Replication Console retrieves metadata for the configuration from the source database, the Console gets the current SCN
, log coordinates,
or LSN and writes this value to the replication configuration. When you run the Extractor later, it skips DDL changes that have SCN
, log coordinate,
or LSN values that are lower than the SCN
, log coordinates,
or LSN in the configuration.
When replicating DDL operations between heterogeneous sources and targets, the source and target databases might support different sets of DDL operations. You can replicate only the source DDL operations that can be mapped to compatible target DDL operations.
The Applier might skip a DDL operation or end abnormally if you replicate a source DDL operation that cannot be represented in the SQL syntax for the target type.

0 COMMENTS

We’d like to hear from you!