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. Appendix A: Troubleshooting
  19. Appendix B: Data Replication Files and Subdirectories
  20. Appendix C: Data Replication Runtime Parameters
  21. Appendix D: Command Line Parameters for Data Replication Components
  22. Appendix E: Updating Configurations in the Replication Configuration CLI
  23. Appendix F: DDL Statements for Manually Creating Recovery Tables
  24. Appendix G: Sample Scripts for Enabling or Disabling SQL Server Change Data Capture
  25. Appendix H: Glossary

Performing a Clean Operation on a Configuration

Performing a Clean Operation on a Configuration

You can remove replication processing information for all replication tasks that are associated with a replication configuration and optionally back up the existing configuration before starting clean processing.
  1. On the
    Server Manager
    tab >
    Configs
    view, select the configuration that you want to clean.
  2. Right-click the configuration row and click
    Clean
    , or click the
    Clean
    icon button on the Replication Configurations toolbar.
    The Data Replication Console prompts you to confirm the operation.
  3. If you do not want to back up the existing configuration prior to cleaning it, clear the
    Back up the configuration before clean processing
    option.
    Informatica recommends that you always back up the configuration to be cleaned. If a problem then occurs, the configuration information is retained in the backup for diagnostic use.
  4. Click
    Yes
    .
  5. For configurations that have a DB2 for Linux, UNIX, and Windows source, reset the db2.initial_lsn runtime parameter.
    The Extractor requires this step to correctly process the Extractor Start Point value.

0 COMMENTS

We’d like to hear from you!