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

Catalog of MySQL Source Table Definitions

Catalog of MySQL Source Table Definitions

PowerExchange now requires a catalog in a MySQL database to store MySQL source table definitions. When PowerExchange detects a DDL change of CDC interest to a source table, PowerExchange updates the source table definition in the catalog. The catalog of updated source table definitions helps PowerExchange avoid errors when reading change data for a DDL-updated table.
PowerExchange updates the source table definitions in the catalog only for DDL change events that affect CDC. Typically, DDL changes of CDC interest are those that require you to re-create or modify the capture registrations and extraction maps for the source tables, for example, column add, drop, or rename operations and table drop or rename operations.
To prepare for catalog use, perform the following tasks:
  1. Create the catalog tables, PWXCatTables and PWXCatUpdates, on a Linux or Windows system. The tables can be in the MySQL source database or in another local or remote MySQL database. Use the PWXCATMY utility.
    A single catalog can record MySQL source table definitions for multiple PowerExchange registration-group instances.
  2. Verify that the catalog tables have the correct format. Use the PWXCATMY utility.
  3. Check that an active capture registration exists for each source table.
  4. Take a snapshot of the source table definitions and record the snapshot information in the catalog. The snapshot provides the baseline table definitions that will be updated by subsequent DDL changes. Use the PWXCATMY utility.
  5. In the DBMOVER configuration file, edit the MySQL CAPI_CONNECTION statement to specify the schema of the catalog tables in the CATSCHEMA parameter. Optionally, you can also specify catalog connection parameters. These parameters will be used during change capture processing.
With the PWXCATMY utility, you can perform all of the following catalog-related operations:
  • Create the catalog tables.
  • Show the DDL statements for creating the catalog tables.
  • Create a snapshot of the source table definitions and write that information to the catalog.
  • Verify that the catalog tables have the correct format.
  • Remove, or
    unregister
    , source table definitions from the catalog.
  • List the source table names for which table definitions exist in the catalog.
  • Dump the source table definitions that are recorded in the catalog.
  • Drop the catalog tables.
For more information about the catalog, see the
PowerExchange CDC Guide for Linux, UNIX, and Windows
. For more information about the PWXCATMY utility, see the
PowerExchange Utilities Guide
.

0 COMMENTS

We’d like to hear from you!