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.4.0 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Summary of PowerExchange New Features and Changes
  3. PowerExchange Installation and Upgrade
  4. PowerExchange Agent
  5. PowerExchange Client for PowerCenter
  6. PowerExchange Condense
  7. PowerExchange Listener
  8. PowerExchange Logger for Linux, UNIX, and Windows
  9. PowerExchange Navigator
  10. PowerExchange Monitoring and Tuning
  11. PowerExchange Utilities
  12. PowerExchange for Adabas
  13. PowerExchange for CA Datacom
  14. PowerExchange for DB2 for i
  15. PowerExchange for DB2 for Linux, UNIX, and Windows
  16. PowerExchange for DB2 for z/OS
  17. PowerExchange for CA IDMS
  18. PowerExchange for IMS
  19. PowerExchange for Microsoft SQL Server
  20. PowerExchange for MySQL
  21. PowerExchange for Oracle
  22. PowerExchange for PostgreSQL
  23. PowerExchange for VSAM and Flat Files
  24. PowerExchange ODBC

Release Guide

Release Guide

Back Next

Support for MySQL CDC Sources

Support for MySQL CDC Sources

PowerExchange 10.2 HotFix 1 adds support for change data capture from MySQL Enterprise Edition 5.7 source tables on Red Hat Linux or Windows operating systems.
PowerExchange uses the MySQL binary log reader, mysqlbinlog, to read change events for source tables from the MySQL binary log. PowerExchange and the mysqlbinlog utility must be installed on the same machine, which can be local to or remote from the database server. Use of the PowerExchange Logger for Linux, UNIX, and Windows is optional.
PowerExchange extracts change records from the change stream or Logger log files and makes the changes available to PowerCenter CDC sessions.
To capture change data for MySQL sources, you must specify the new MYSQL CAPI_CONNECTION statement in the DBMOVER configuration file. Also, create capture registrations and extraction maps for the MySQL source tables by using either the PowerExchange Navigator or DTLUCBRG utility. Both interfaces have been enhanced to support MySQL sources.
Also, verify that binary logging is enabled for the MySQL server with the following options: 
[mysqld]
server-id=
server_id

log-bin=
base_name

binlog-format=row
binlog-row-image=full
PowerExchange uses the server-id value of 369. Also, PowerExchange requires row-based binary logging with the row image type of full.
The binary log reader reads DML and DDL events. However, DDL events that create, drop, rename, truncate, or alter the mapped source tables usually cause PowerExchange capture processing to end except in the following cases:
  • If you set the ONTABLETRUNC parameter in the MYSQL CAPI_CONNECTION statement to WARN, capture processing can continue with a warning message when PowerExchange encounters a TRUNCATE TABLE event for a source table.
  • If a CREATE TABLE statement creates a table that was not previously registered and you use the PowerExchange Logger, capture processing can continue with a warning.
  • If an ALTER TABLE ADD COLUMN statement appends a column after all other columns, capture processing can continue.
PowerExchange supports all MySQL datatypes except spatial datatypes. The following additional restrictions apply:
  • PowerExchange limits the length of data in columns that have a mediumblob, longblob, mediumtext, longtext, enum, json, set, varbinary, or varchar datatype to 98,304 bytes.
  • PowerExchange converts binary json data to textual json data.
PowerExchange uses the DataDirect ODBC driver for MySQL, which is delivered in the PowerExchange installation, to retrieve source metadata from the MySQL database server.
For more information, see the
PowerExchange CDC Guide for Linux, UNIX, and Windows
, the
PowerExchange Navigator User Guide
, and
PowerExchange Utilities Guide
.
0 COMMENTS
We’d like to hear from you!