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 10.5.2
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: PowerExchange Client for PowerCenter (PWXPC)
  4. Part 3: PowerExchange ODBC
  5. Appendix A: PowerExchange Interfaces for PowerCenter Tips
  6. Appendix B: Datatypes and Code Pages
  7. Appendix C: PowerExchange Interfaces for PowerCenter Troubleshooting

PowerExchange Interfaces for PowerCenter

PowerExchange Interfaces for PowerCenter

Back Next

Default Restart Points

Default Restart Points

If you start a new CDC session and no restart token file exists, the PowerCenter Integration Service still runs the session. PWXPC passes null restart tokens for all of the sources to PowerExchange.
To indicate that the restart tokens are null, PWXPC issues message PWXPC_12060. PowerExchange then assigns the earliest possible restart point to each source.
Null restart tokens might produce unexpected results. Informatica recommends that you always specify valid restart tokens that indicate a point in the change stream where the source and target are in a consistent state.
The following table describes the default restart points that PowerExchange uses when it receives null restart tokens, by source and connection type:
Source Type
PWX CDC Change Connection
1
PWX Real Time Connection
2
All z/OS data sources
The oldest PowerExchange Condense condense file that is recorded in the CDCT file.
The PowerExchange Logger for
z/OS
 determines the best available restart point.
Usually, this point is the oldest restart point for which an archive log is available, or if no archive log is available, the oldest restart point for an active log.
DB2 for i5/OS
The oldest PowerExchange Condense condense file that is recorded in the CDCT file.
The oldest journal receiver that is still on the journal receiver chain.
DB2 for Linux, UNIX, and Windows
The oldest PowerExchange Logger for Linux, UNIX, and Windows log file that is recorded in the CDCT file.
The current log position at the time the PowerExchange capture catalog was created.
Microsoft SQL Server
The oldest PowerExchange Logger for Linux, UNIX, and Windows log file that is recorded in the CDCT file.
The oldest data that is available in the Publication database.
MySQL
The oldest PowerExchange Logger for Linux, UNIX, and Windows log file that is recorded in the CDCT file.
The oldest data available in the binary log. This position is the beginning of the binary log that has the log name that includes the lowest numeric suffix value. You can use the SHOW BINARY LOGS statement to identify this log.
Oracle
The oldest PowerExchange Logger for Linux, UNIX, and Windows log file that is recorded in the CDCT file - for PowerExchange Express CDC for Oracle.
The earliest available point in the change stream. More specifically, for PowerExchange Express CDC for Oracle, that point the beginning of the most recent archive log.
PostgreSQL
The oldest PowerExchange Logger for Linux, UNIX, and Windows log file that is recorded in the CDCT file.
The oldest data available from the replication store table.
Any data source type that is logged to a PowerExchange Logger for Linux, UNIX, and Windows
3
The oldest PowerExchange Logger for Linux, UNIX, and Windows log file that is recorded in the CDCT file.
The oldest PowerExchange Logger for Linux, UNIX, and Windows log file that is recorded in the CDCT file.
1. With a PWX CDC Change connection, you must use batch extraction mode.
2. With a PWX CDC Real Time connection, use real time extraction mode to extract data from the source change stream or use continuous extraction mode to extract data that is logged to a PowerExchange Logger for Linux, UNIX, and Windows instance.
3. Includes Linux, UNIX, and Windows data sources that are logged to a local or remote PowerExchange Logger for Linux, UNIX, and Windows instance. Also includes z/OS and i5/OS data sources that are logged to a remote PowerExchange Logger for Linux, UNIX, and Windows instance.
PowerExchange uses the default restart point only if all sources in a CDC session have null restart tokens. If some sources have non-null restart tokens, PWXPC assigns the oldest restart point of those restart tokens to sources for which no restart tokens are specified.
For example, a new CDC session contains the sources A, B, and C. The restart token file contains restart tokens for sources A and B. The restart point for source A is older than that for source B. Source C does not have existing or supplied restart tokens. Because some sources in the CDC session have explicit restart points, PWXPC does not assign null restart tokens to source C. Instead, PWXPC assigns the restart point for source A to source C because this restart point is the oldest one supplied.
0 COMMENTS
We’d like to hear from you!