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

Customizing Names of Calculated Metadata Columns

Customizing Names of Calculated Metadata Columns

If you use Audit Apply or Merge Apply mode, you can customize the names of metadata, before-image, and after-image fields that are included in audit log tables, Kafka messages, and the output files that are produced on
Cloudera,
Flat File,
and
Hortonworks
 targets.
The revised settings will be used in the DDL for generating or regenerating the audit log table, Kafka messages, or output files on the target.
  1. Click the
    Runtime Settings
     tab >
    Calculated Columns
     view.
    The following image shows this view:
    Calculated Columns view on the Runtime Settings tab
  2. Enter values in any of the fields, as needed.
    The following table describes the fields on the
    Calculated Columns
     view:
    Field
    Description
    Default Value
    Operation time and date on source
    The name of the metadata column that contains the date and time of an operation.
    OP_TIME
    Operation code on source
    The name of the metadata column that contains the operation type code.
    OP_CODE
    SCN of commit point
    The name of the metadata column that contains the SCN of the operation commit.
    OP_CMT_SCN
    Low SCN of commit point
    For Microsoft SQL Server sources, the name of the audit log table metadata column that contains the first part of LSN of the operation commit.
    No default
    Transaction commit time
    The name of the metadata column that contains the commit time of the operation.
    OP_CMT_TIME
    Transaction ID
    The name of the metadata column that contains the transaction ID.
    OP_XID
    Sequence number of an operation in a transaction
    The name of the metadata column that contains the sequence number of an operation in a transaction.
    OP_NUM_IN_TX
    User ID
    For DB2, Microsoft SQL Server, and Oracle sources, the name of the audit log table metadata column that contains the user ID of the database user who performed a DML operation, as recorded in the transaction log record for the operation.
    If you leave the field blank, the Data Replication Console does not include this column when generating audit log tables.
    No default
    User name
    For DB2, Microsoft SQL Server, and Oracle sources, the name of the audit log table metadata column that contains the name of the database user who performed a DML operation, as recorded in the transaction log record for the operation.
    If you leave the field blank, the Data Replication Console does not include this column when generating audit log tables.
    No default
    Before image column name ending
    The column name suffix for columns that contain the before-image values for Update and Delete operations. For Merge Apply, the column name suffix for audit log table columns that contain values from after-image primary key columns for Insert operations.
    For Kafka targets, this field is ignored. To change the suffix of the field in Kafka messages that contain the before-image data, use the apply.avro.avro_before_image_suffix runtime parameter.
    _OLD
    After image column name ending
    The column name suffix for columns that contain the after-image values for Insert and Update operations.
    • Either the before- or after-image suffix can be empty but not both. If both the before- and after-image suffixes are empty, the Applier cannot identify the before- and after-image columns in the audit log table.
    • For Kafka targets, this field is ignored. Kafka messages use the source column names as the names of the columns that contain the after image data.
    _NEW
    Log table suffix for merge apply
    A suffix for audit log table names.
    • For Merge Apply, the Applier uses this suffix to determine the audit log table that corresponds to each mapped target table.
    • For Audit Apply, the Data Replication Console uses this suffix to map the source tables to audit log tables based on wildcard expressions or exact name matching.
    • If the audit log table names with the default suffix of _LOG exceed the maximum table name length that your target database allows, enter a shorter suffix such as _L.
    • This field is ignored for configurations that do not use Merge Apply.
    _LOG
    Log table schema for merge apply
    When Merge Apply is used, a target schema for audit log tables.
    • For Netezza targets, leave the default value. You cannot override the schema for audit log tables because a Netezza user can own only one schema.
    • This field is ignored for configurations that do not use Merge Apply.
    No default
    Recursive level for row key changes
    When Merge Apply is used, the name of the audit log table metadata column that contains the first value for a key mutation trace.
    This field is ignored for configurations that do not use Merge Apply.
    OP_KEY_LEVEL
    Root ID for recursive key changes
    When Merge Apply is used, the name of the audit log table metadata column that contains the second value for a key mutation trace.
    This field is ignored for configurations that do not use Merge Apply.
    OP_ROOT_KEY_ROWID
  3. Save the configuration.
0 COMMENTS
We’d like to hear from you!