The PowerExchange Logger for Linux, UNIX, and Windows captures change data from DB2 database logs, Oracle redo logs, or a SQL Server distribution database and writes that data to PowerExchange Logger log files.
Use of the PowerExchange Logger is optional. To use the PowerExchange Logger, run one PowerExchange Logger process for each database type and instance. The PowerExchange Logger writes all successful UOWs in chronological order based on end time to its log files. This practice maintains transactional integrity. You can extract the change data from the PowerExchange Logger log files in either batch or continuous mode.
Benefits of the PowerExchange Logger include:
Source database overhead is reduced because PowerExchange makes fewer accesses to the source log files or database to read change data. For Oracle, this overhead reduction can be significant. The PowerExchange Logger can use only one Oracle LogMiner session to read change data for all extractions that process an Oracle instance.
You do not need to retain the source RDBMS log files longer than normal for CDC.
PowerExchange does not need to reposition its point in the DB2 or Oracle logs from which to resume reading data. This feature can significantly reduce restart times.
Informatica strongly recommends that you use the PowerExchange Logger rather than real-time extraction mode for both PowerExchange Oracle CDC with LogMiner sources and PowerExchange Express CDC for Oracle sources. For Oracle CDC with LogMiner, this configuration enables PowerExchange to use one Oracle LogMiner session for all extractions that process an Oracle instance.