PowerExchange Express CDC for Oracle is more efficient and faster than PowerExchange Oracle CDC with LogMiner in many Oracle environments.
You cannot use both PowerExchange Express CDC for Oracle and PowerExchange Oracle CDC with LogMiner in the same PowerExchange instance with the same dbmover.cfg and pwxccl.cfg configuration files.
PowerExchange Express CDC requires the Oracle database to run in ARCHIVELOG mode with minimal global supplemental logging enabled. PowerExchange Express CDC can capture change data from most types of source environments, including those that use Oracle RAC and Automatic Storage Management (ASM), Oracle Data Guard logical or physical standby databases, Oracle Exadata database machines, or an Oracle multitenant pluggable database.
PowerExchange Express CDC runs on 64-bit operating systems only.
PowerExchange Express CDC does not use Oracle LogMiner to read the redo logs. It has its own log reader to get change data directly from the redo logs for real-time extraction processing. This architecture avoids the performance degradation that can occur on Oracle systems because of initialization of LogMiner sessions.
Also, PowerExchange Express CDC for Oracle does not use the PowerExchange UOW Cleanser. PowerExchange Express CDC capture components handle UOW Cleanser functions transparently for CDC sessions that run in real-time extraction mode. The capture components produce a change stream in which inserts, updates, and deletes are organized by transaction, and the transactions are arranged in their original commit order.
With PowerExchange Express CDC for Oracle, use of the PowerExchange Logger for Linux, UNIX, and Windows is optional but strongly recommended. The PowerExchange Logger writes successful units of work (UOWs) in chronological order by end time to PowerExchange Logger log files. CDC sessions can then extract the change data from the PowerExchange Logger log files in either continuous extraction mode or batch extraction mode. Benefits of using the PowerExchange Logger include fewer database accesses, faster CDC restart, and no need for prolonged retention of the Oracle redo files for CDC.
To configure PowerExchange Express CDC for Oracle, you must add some Oracle-specific statements to the dbmover configuration file. Also, define the separate PowerExchange Express CDC configuration file, which has the default file name of pwxorad. Other configuration tasks are similar to those for Oracle CDC with LogMiner. You create capture registrations, configure PowerCenter CDC sessions, and configure restart processing in the same manner as for Oracle CDC with LogMiner. The restart token format for PowerExchange Express CDC for Oracle sources is different from that for any other data source type, including Oracle CDC with LogMiner sources.
For tables that do not have row movement enabled, you can use the PowerExchange-generated DTL__CAPXROWID column in extraction maps and the OPTIONS ROWID=Y statement in the PowerExchange Express CDC for Oracle configuration file to include Oracle physical rowid values in change records. This feature is useful for processing rows in unkeyed tables during CDC extraction sessions.
If you currently use Oracle CDC with LogMiner and need better CDC performance, consider migrating to PowerExchange Express CDC for Oracle.