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.8.0 HotFix 1
  • 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

Specifying the Database Logs from Which to Extract Data

To extract change data from DB2 for Linux, UNIX, and Windows archive logs
, Microsoft SQL Server backup logs,
MySQL binary logs,
 or Oracle archived redo logs and backup sets, you must specify the location of the log files. The log files can be on the local system or a remote system.
Data Replication searches for the last-used paths and directories for the Microsoft SQL Server backup log files
, MySQL binary log files,
 or Oracle archived redo logs and displays these locations on the
Extract Range
 tab, if found. For DB2 sources, you must add the directory that contains the DB2 archive log files.
Optionally, you can filter the logs for DB2,
Microsoft SQL Server,
and Oracle sources. Also, for
Microsoft SQL Server
and Oracle sources, you can configure extraction processing for database online logs.
  1. Click the
    Extract Range
     tab.
  2. To disable change data capture from online logs, clear one of the following options, depending on your source database type:
    • For Microsoft SQL Server sources, clear
      Read from online transaction logs
      .
    • For Oracle sources, clear
      Read from online logs
      .
    By default, Data Replication captures change data from online logs for these source types.
  3. To add the directory for DB2 archive logs
    , Microsoft SQL Server backup logs,
    MySQL binary logs,
     or Oracle archived redo logs and backup sets:
    1. Click
      Add Directory
      .
    2. In the
      Add Directory
       dialog box, select one of the following options to indicate the location of the log files:
      • File system
        . Use the location of the log files that you specify on the file system of the computer where the source Server Manager runs or on a network mapped share, such as NFS or Samba.
        This option is the only available option for MySQL sources.
      • Oracle ASM
        . For Oracle sources, use the location of the archived log files in ASM.
      • Default Archive Logs
        . For DB2,
        Microsoft SQL Server,
        and Oracle sources, search for archived logs in the database-specific location. Oracle archived redo logs can be in RMAN backup sets.
      The selected option determines what is displayed in the directory tree.
    3. Specify the directory that Data Replication scans for the log files in one of the following ways:
      • In the
        User-defined path
         field, type the directory path and press Enter.
      • In the directory tree, select the directory that contains the log files.
    4. For DB2, Oracle, and Microsoft SQL Server sources, select
      Scan subfolders
       to recursively search for log files in the subfolders of the specified directory.
    5. In the
      Filter files
       field
      or
      Base Bin Log File Name
       field
      , enter a mask for the names of the log files in the selected directory to be read.
      For MySQL sources, enter a mask for the base names of the binary log files.
      You can use the following wildcard characters:
      • An asterisk (*) to match all characters
      • A question mark (?) to match any single character
      • Square brackets ([ ]) to match only one out of several characters
      For example, to read all files with the .bak extension, enter *.bak.
      The
      Filter files
      or
      Base Bin Log File Name
       field cannot be empty. The default is the asterisk (*) wildcard character.
    6. Click
      OK
      .
      The directory path, filter mask, and scan subfolders setting are displayed on the
      Extract Range
       tab.
      The following image shows an example of a user-defined path to Oracle archive log files:
      User-defined path example on the Extract Range tab
      To edit the log path or filter, right-click the path and click
      Edit
      . To remove the log path and filter, right-click the path and click
      Remove
      , or select the path and click the
      Remove Selected
       button.
    7. Repeat steps a through f to specify additional log-file locations.
  4. For Oracle sources, if you specified multiple archive destinations, drag and drop the destinations in order of priority for Oracle Extractor processing. The first destination in the list has the highest priority, and the last destination has lowest priority.
    The Extractor starts reading redo logs or RMAN backup sets from the destination with the highest priority. If the Extractor cannot read a redo log at that destination, it switches to the destination with the next lower priority.
  5. Under
    Transaction log format
    , specify the DB2 or Oracle platform type and characteristics, which affect log file allocation:
    • In the
      Platform with logs
       list, select the platform type of the system that contains the source transaction logs. If you do not select a platform type, the
      Use default
       value remains selected, which causes the Extractor to use the platform on which the source database runs.
    • Select
      Little endian system
       for a little-endian system. Clear this box for a big-endian system.
    • In the
      System block size (bytes)
       field, accept the default value that is displayed for the selected platform type or enter another value.
    • In the
      Disk align size (bytes)
       field, accept the default that is displayed for the selected platform type or enter another value.
    Usually, the default values are acceptable.
0 COMMENTS
We’d like to hear from you!