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

Mapping Validation

Mapping Validation

When you create a replication configuration, the Data Replication Console validates table, view, and column mappings.
By default, the Data Replication Console does not allow you to map a source table to a target in the following circumstances:
  • The source table type is not supported.
  • The source table contains one or more columns that have unsupported datatypes.
Also, if you add virtual columns with an SQL or Tcl expression to a source, the Data Replication Console does not allow you to map the virtual columns to target columns that have incompatible datatypes.
You can use the
compatibility_checking_level
parameter in the
DataReplication_installation
/uiconf/default.cfg file to change the default mapping validation behavior. Options are:
  • 0
    . Disable mapping validation.
  • 1
    . Validate only column mappings, including virtual column mappings.
  • 2
    . Validate only table mappings.
  • 3
    . Validate table and column mappings. Map tables and views even if they include columns with unsupported datatypes. Map only the columns that have supported datatypes.
  • 4
    . Validate table and column mappings. Do not map tables and views that include columns with unsupported datatypes. Also, do not map virtual source columns to target columns that have incompatible datatypes.
Default value: 4
If the default.cfg file does not exist, use a text editor to create this file in the uiconf directory and then add the
compatibility_checking_level
parameter in the file. For more information, see Default.cfg File.

0 COMMENTS

We’d like to hear from you!