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
  • 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

Managing Open Transactions

Managing Open Transactions

In the Data Replication Console, you can view a list of open transactions for tables in the source database if you are an idradmin user or the owner of the selected configuration. You can commit or roll back corresponding transactions in the intermediate files to persist changes in the target database, if necessary.
  1. On the
    Server Manager
     tab >
    Configs
     view, select a configuration for which to view open transactions.
  2. To view the list of transactions that were open in the source database at the time of the last Extractor checkpoint, perform one of the following actions:
    • Click the
      Show Transactions
       icon button on the Replication Configurations toolbar.
    • Right-click the configuration row and click
      Show Transactions
      .
    The
    Open Transactions for Configuration <configuration_name>
     dialog box appears.
    The example Transactions of configuration 'Ora2OraSL' window displays a list of open transactions.
    The list of open transactions appears at the top. The transactions for unmapped tables that do not have a
    Begin Transaction Timestamp
     value appear first, and then the other transactions are sorted in chronological order from earliest to most recent
    Begin Transaction Timestamp
     value. You can filter the list by entering an XID in the text box in the top left corner. When you select a transaction in the list, the properties box beneath the list displays additional properties for the selected transaction.
    For DB2 sources, the list might include transactions that DB2 processes such as DB2HMON and DB2ACD open for maintenance tasks. These transactions are not related to data replication.
    The following table describes the properties that are displayed for each open transaction in the transactions list and in the properties box:
    Property
    Description
    Mark for Commit or Rollback
    Indicates if you marked the transaction for commit or rollback processing on the target.
    Transaction Name
    The name of the open transaction.
    XID
    The transaction ID of the open transaction.
    For Oracle sources, the
    Open Transactions for Configuration <configuration_name>
     dialog box might list multiple open transactions with the same XID value if Oracle reuses transaction IDs. When listing these transactions, the Data Replication Console first lists the transactions for unmapped tables that do not have a
    Begin Transaction Timestamp
     and then lists the other transactions in chronological order, beginning with the transaction that has the earliest
    Begin Transaction Timestamp
    .
    Begin Transaction LSN or Begin Transaction SCN (for Oracle sources)
    The SCN or LSN value for the BEGIN TRANSACTION operation.
    Loopback Transaction
    Indicates whether the Extractor skips the transaction based on the transaction name. The Extractor skips transactions if their names are specified in the
    SKIP_TX
     command line parameter. If the
    SKIP_DEFAULT_TX
     parameter is set to Y, the Extractor also skips transactions that have the default name of DbSyncTransaction. Valid values are:
    • true
      . The Extractor skips the transaction.
    • false
      . The Extractor does not skip the transaction.
    Records in Transaction
    The number of records in the transaction that are available in intermediate files.
    Database ID or Redo Thread ID (for Oracle sources)
    For Oracle sources, the unique identifier of a redo thread. For other sources, the unique identifier of a database.
    DDL Transaction or System Table Transaction (for Oracle sources)
    Indicates whether the transaction affects database system tables. A transaction that affects database system tables usually includes DDL operations. The database system tables that Data Replication monitors are specified in the following parameters in the
    DataReplication_installation
    /uiconf/default.cfg file:
    • db2_fixed_source_tables_names
    • mssql_fixed_source_tables_names
    • oracle_fixed_source_tables_names
    Valid values are:
    • 0
      . The transaction does not affect system tables.
    • 1
      . The transaction affects system tables.
    If the default.cfg file does not exist, you can create the file in the uiconf directory and then add parameters in the file. For more information, see Default.cfg File.
    Begin Transaction Timestamp
    The date and time of the first redo record for the mapped table. This value displays only if the transaction includes changes to a mapped table in the configuration. If the transaction includes changes to an unmapped source table, the
    Begin Transaction Timestamp
     property does not contain a value.
    Database Transaction Status
    The status of the transaction that is reported by the source database. If the source database does not contain information about the transaction, Data Replication sets the transaction status to NOT ACTIVE.
    Undo Block Address (UBA)
    For Oracle sources, specifies the Undo Block Address.
    Session ID
    For Oracle sources, specifies the identifier of the session that is associated with the open transaction.
    Session Serial Number
    For Oracle sources, specifies the serial number of the session that is associated with the open transaction.
    Internal LSN or Internal SCN (for Oracle sources)
    The SCN or LSN value for the BEGIN TRANSACTION operation in the database format.
    Internal XID
    The transaction ID in the database format.
    Transaction size
    The amount of data, in bytes, in the transaction records in the intermediate files.
    Database User Name
    The name of the database user who opened the transaction.
    System User
    The name of the system user who opened the transaction.
    Host
    The IP address or host name of the system with the database client that opened the transaction.
    Application ID
    For DB2 sources, the ID of the database client that opened the transaction.
    To get the latest information for the list of open transactions, click the
    Refresh
     icon button.
  3. If a transaction is causing a problem that you need to circumvent, you can commit or rollback the transaction in one of the following ways:
    • To mark an open transaction for commit processing on the target, select the transaction and click the
      Commit
       icon button. The Extractor adds a commit record for the selected transaction at the end of the next Extractor microcycle. The Applier commits this transaction on the target during the next apply cycle.
    • To mark an open transaction for rollback processing on the target, select the transaction and click the
      Rollback
       icon button. The Extractor adds a rollback record for the selected transaction at the end of the next Extractor microcycle. The Applier rolls back this transaction on the target during the next apply cycle.
    Committing or rolling back an open transaction in the Data Replication Console might result in data inconsistencies. For DB2 for Linux, UNIX, and Windows sources, change records that occur after the commit or rollback point in the source transaction are extracted and applied as part of the same transaction. However, for Oracle
    and Microsoft SQL Server
     sources, change records that occur after the commit or rollback point in the source transaction are not extracted and applied.
0 COMMENTS
We’d like to hear from you!