CDC Guide for Linux, UNIX, and Windows

10.5
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

PowerExchange Logger for Linux, UNIX, and Windows

The PowerExchange Logger for Linux, UNIX, and Windows can capture change data from Db2 database logs, the Microsoft SQL Server distribution database, MySQL binary logs, Oracle redo logs, or the PostgreSQL table in which PowerExchange stores data from a PostgreSQL logical replication slot. The PowerExchange Logger then writes the captured 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.

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 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 PowerExchange Express CDC for Oracle sources.

Rename Saved Search

Table of Contents

CDC Guide for Linux, UNIX, and Windows

CDC Guide for Linux, UNIX, and Windows

PowerExchange Logger for Linux, UNIX, and Windows

PowerExchange Logger for Linux, UNIX, and Windows