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
  • PowerExchange for CDC and Mainframe H2L
  • All Products

Table of Contents

Search

  1. Abstract
  2. Supported Versions
  3. Using Heartbeat Tables to Determine the Latency of Change Data Flow

Using Heartbeat Tables to Determine the Latency of Change Data Flow

Using Heartbeat Tables to Determine the Latency of Change Data Flow

Back Next

Analyzing Session Information in the Target Heartbeat Table

Analyzing Session Information in the Target Heartbeat Table

After you start a real-time CDC session that uses the heartbeat tables, the session writes a row of time stamp information to the PM_TGT_HEARTBEAT table each time the SRC_TSTAMP column in the PM_SRC_HEARTBEAT table is updated. You determine the frequency of the source updates.
If you configured multiple CDC sessions to include the heartbeat tables, the PM_TGT_HEARTBEAT table contains a session-specific row for each source update. You can query on a session name to find all rows for a particular session.
To monitor session performance or to troubleshoot suspected data latency issues, compare the time stamp values in a row for a session. Calculate the time difference between two different time stamps to determine the time delays during different processing phases. The following table describes what you can determine by comparing columns and calculating the difference between their time stamps:
Compare Columns
To Determine
SRC_TSTAMP and TGT_TSTAMP
The total time that the PowerCenter CDC session took to propagate an update end-to-end. Use this time interval as an indication of overall session performance for an update.
SRC_TSTAMP and CAPX_TSTAMP
The date and time when an update was written to the PM_SRC_HEARTBEAT table. These time stamps should be the same or nearly the same. If they are different, a PowerExchange change capture problem might exist.
CAPX_TSTAMP and MAP_TSTAMP
The time that the PowerCenter CDC session took to process an update to the PM_SRC_HEARTBEAT table. A large time interval might indicate a problem in either PowerExchange or the PowerCenter CDC session and workflow.
MAP_TSTAMP and TGT_TSTAMP
The time that the PowerCenter CDC session took to process and insert the change into the PM_TGT_HEARTBEAT table. A large time interval might indicate a delay in workflow processing.
0 COMMENTS
We’d like to hear from you!