Table of Contents

Search

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

Dynamic Dictionary for Oracle Sources

Dynamic Dictionary for Oracle Sources

PowerExchange Express CDC for Oracle supports a dynamic dictionary based on a snapshot of the Oracle catalog to accommodate DDL changes to source tables and table partitions for restart processing. With the dynamic dictionary, Express CDC can update dictionary information in memory for the source tables of CDC interest when DDL changes are committed. The changes, along with the SCN and sequence number, are persisted to an external stage table or file system that records all changes of interest.
Use a dynamic dictionary in environments where DDL changes to source tables are likely to occur. If you use a static dictionary in this type of environment, data loss or corruption can occur after a CDC restart if tables were reorganized or renamed, tables or partitions were dropped, or table columns were added, dropped, or altered. By using a dynamic dictionary, you can avoid data loss and corruption after a restart.
To use a dynamic dictionary use, perform the following high-level implementation steps:
  1. Configure the PowerExchange Express CDC configuration file.
    You must define the DICTIONARY and STATESTORAGE statements. In the DICTIONARY statement, set the MODE parameter to DYNAMIC.
  2. Ensure that an initial snapshot of the Oracle catalog populates the state table or file that will store the dynamic dictionary information.
    The initial snapshot is automatically created when PowerExchange Express CDC first initializes after dynamic dictionary configuration .
  3. Warm start PowerExchange Express CDC or cold start the PowerExchange Logger. PowerExchange Express CDC loads the in-memory dictionary from the external state storage during initialization of the warm start or cold start.
    After initialization, when the latest commit SCN has caught up to the dictionary base SCN, all new DDL operations on tables of CDC interest are recorded in the state storage when they are committed
For more information about the dynamic dictionary, see the "Express CDC for Oracle" chapter in the
PowerExchange CDC Guide for Linux, UNIX, and Windows
.

0 COMMENTS

We’d like to hear from you!