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 2
  • 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 General Runtime Settings

Specifying General Runtime Settings

You can set general runtime parameters on the
General
 view of the
Runtime Settings
 tab. These parameters enable important capabilities such as writing output to pipes, compressing data, and multi-threaded processing.
  1. Click the
    Runtime Settings
     tab >
    General
     view.
    The following image shows the
    General
     view when the source is Oracle:
    General view on the Runtime Settings tab
  2. Enter information in any of the fields, or accept the default values.
    The following table describes the fields in the
    General
     view:
    Field
    Description
    Default
    Create output as pipes instead of files
    For InitialSync operations and for change data replication in Merge Apply mode to Netezza targets, select this option to have Data Replication write output to pipes instead of files. Data Replication then loads data from the pipes directly into the targets.
    Clear this option to not write data to pipes.
    Selected
    Maximum size of each intermediate file (MB)
    The maximum amount of data, in megabytes, that you want a single intermediate .DAT file to contain. Options are:
    16
    ,
    32
    ,
    64
    ,
    128
    ,
    256
    ,
    512
    , and
    1024
     MB.
    Data Replication can create a new intermediate file only after the Extractor records a checkpoint. For more information, see Checkpoint Processing. If the Extractor captures a low volume of change data during a cycle, Data Replication might generate an intermediate file that is smaller than the specified maximum size. If the Extractor captures the maximum amount of data but a checkpoint is not triggered, Data Replication generates an intermediate file that is larger than the specified maximum size.
    For Oracle sources, if you set the
    extract.use_strict_intermediate_file_size
     runtime parameter to 1, the Extractor treats the specified maximum size as a hard limit. The Extractor estimates the size of the intermediate file when processing each change record. If the estimated file size exceeds the specified limit, the Extractor forces a checkpoint, writes the data, and closes the intermediate file.
    256
    InitialSync threads
    The number of threads for InitialSync parallel processing.
    4
    Applier threads
    The number of threads for Applier parallel processing.
    1
    Continuous replication latency
    The latency, in seconds, of Extractor change capture processing during continuous data replication. This value determines the duration of an Extractor microcycle. During a microcycle, the Extractor captures changes from database logs, creates an intermediate file, writes changes to the intermediate file, and then sleeps. When the latency period ends, the Extractor begins another microcycle.
    When setting the latency period, consider how it affects replication performance:
    • If the latency period is greater than the time it takes the Extractor to read changes from the database logs and write them to an intermediate file, the Extractor sleeps until the end of the latency period. To minimize inactive Extractor sleep periods, set the latency to a low value.
    • If the latency period is equal to or less than the time it takes the Extractor to read changes from the database logs and write them to an intermediate file, the Extractor continues processing and does not sleep. The Extractor begins a new microcycle as soon as it closes the intermediate file. However, if the latency is too low, the performance of the long-running Extractor task might be degraded because of high disk memory consumption and a high core load. In this case, try increasing the latency value in subsecond increments, such as 0.1.
    Default is 0.333 second, which is usually acceptable to process all changes in a microcycle. If necessary, you can adjust the latency in sub-second increments.
    After the Extractor creates the intermediate file, the Applier can start reading changes and applying them to the target. Therefore, the Applier might also run during a microcycle. For large transactions with many changes, the Applier waits until the Extractor writes all of the changes to the intermediate file, which might take several microcycles, and then begins apply processing.
    0.333
    Encryption Algorithm
    The encryption algorithm that Data Replication uses to encrypt the intermediate files. Options are:
    • NONE
      . Do not encrypt the intermediate files.
    • TRIPLE_DES
      . Use the Triple DES algorithm.
    • AES128
      . Use the AES algorithm with 128-bit key.
    • AES192
      . Use the AES algorithm with 192-bit key.
    • AES256
      . Use the AES algorithm with 256-bit key.
    NONE
    Oracle wallet
    Oracle sources only.
     If you have Oracle sources that use Oracle Transparent Data Encryption (TDE), click this button and browse to the Oracle TDE wallet. The wallet must be in PKCS #12 format.
    Not applicable
    Password
    Oracle sources only.
     If you specified the Oracle TDE wallet, enter the password for the wallet and click
    Open
    .
    No default
    Add Certificate
    Microsoft SQL Server sources only.
     If you have a SQL Server source database that uses Transparent Data Encryption (TDE), click this button and browse to the .pfx certificate file that you copied to the Data Replication installation directory where the Extractor runs.
    Not applicable
    Edit Certificate
    Microsoft SQL Server sources only.
     If you added a certificate for an encrypted Microsoft SQL Server database and want to change its path or password, click this button.
    Not applicable
    Delete Certificate
    Microsoft SQL Server sources only.
     If you want to delete a certificate that you specified for an encrypted Microsoft SQL Server database, select the certificate and then click this button.
    Not applicable
    Compress data on the fly
    Select this option to compress intermediate files during extraction processing to reduce the file size.
    Clear this option if CPU resources are restricted and you want to avoid the overhead of compression and decompression.
    Selected
    Data compression
    If you selected
    Compress data on the fly
    , select the compression method. The only available method is
    QuickLZ
    , which provides fast compression with a low compression ratio.
    QuickLZ
    Supplemental Logging Settings
    Enables database supplemental logging for source tables when you save the configuration. For Oracle sources, generates a supplemental log group for each source table. For DB2 sources, sets the DATA CAPTURE CHANGES option for each source table. For Microsoft SQL Server Sources, sets Change Data Capture for each source table. To control whether the Console automatically enables supplemental logging, select one of the following options:
    • Ask
      . Displays a confirmation prompt before the Data Replication Console enables supplemental logging for the source tables.
    • Yes
      . Enables supplemental logging for the source tables without first displaying a confirmation prompt.
    • No
      . Does not enable supplemental logging for the source tables. You must enable supplemental logging manually for your source tables.
    Ask
    Conflict Resolution > Logging path
    The path to the log file to which the Applier logs data conflicts that occur when applying change data to a target on which other change data activity is occurring. Click
    Browse
     to browse to the log file for the system where you run the Applier.
    No default
    Oracle Settings
    Oracle sources and targets only.
     Indicates whether to use database links (dblinks) when running InitialSync for an Oracle source and Oracle target. Options are:
    • Select Insert
      . Prevents Data Replication from using dblinks.
    • DBLink
      . Enables Data Replication to use dblinks.
    This option is a synonym for the
    initialsync.oracle.use_dblink
     parameter, which is set on the
    Runtime Settings
    Advanced Settings
     view.
    DBLink
    Disable secondary truncation checkpoint
    Microsoft SQL Server sources only.
     Select this option to disable secondary truncation checkpoint management by the Extractor.
    Select this option in the following cases:
    • You run the Extractor that reads transaction logs and SQL Server Change Data Capture (CDC) or native transactional replication against the same database. In this case, SQL Server must manage the secondary truncation checkpoint and produce backup logs.
    • You run two Extractors that read transaction logs against the same database. In this case, only one Extractor can manage the secondary truncation checkpoint.
    • You run the Extractor that reads transaction logs and a Microsoft SQL Server Backup task for which the
      Run the sp_repldone procedure
       option is selected.
    After you disable Extractor management of the secondary truncation checkpoint, ensure that the Extractor reads both the transaction and backup logs. Otherwise, incomplete data capture can occur.
    This option is a synonym for the
    extract.mssql.together_with_native_replication
     parameter on the
    Runtime Settings
    Advanced Settings
     view.
    Not selected
0 COMMENTS
We’d like to hear from you!