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

Customizing the dbmover Configuration File for the PowerExchange Logger

To use the PowerExchange Logger, you must define the CAPT_PATH statement and certain source-specific statements in the dbmover configuration file.

Also, you can include some optional parameters to help make finding messages for the PowerExchange Logger easier or to send commands to a PowerExchange Logger process that is running in background mode.

Use the following key parameters:

CAPT_PATH: Required. Path to the local directory on a Linux, UNIX, and Windows system that contains the control files for CDC, including the CCT and CDCT files. The CCT file contains information about capture registrations. The CDCT file contains information about the PowerExchange Logger log files, such as file names and number of records.
CAPX CAPI_CONNECTION: Required for continuous extraction mode. If you want the CAPI to use continuous extraction mode for the extraction of change data from PowerExchange Logger log files, you must define a CAPX CAPI_CONNECTION statement.
LOGPATH: Optional. A unique path and directory for PowerExchange message log files on a Linux, UNIX, or Windows system. Use this parameter to create message log files in a directory that is separate from your current working directory so that you can find the message log files more easily.
SVCNODE: Optional. The TCP/IP port on which a command-handling service for a PowerExchange Logger process listens for commands that you issue with the pwxcmd program. You must define this parameter if you run the PowerExchange Logger process in background mode on a Linux or UNIX system. For more information about pwxcmd commands, see the
PowerExchange Command Reference
.
TRACING: Optional. Enables alternative logging. PowerExchange creates a set of alternative log files for each PowerExchange process in a separate directory. You can specify the directory location, the number of log files, and the log file size in MB. When a log file reaches the specified size, PowerExchange switches to the next log file and begins overwriting any data in that file. Alternative logging is faster and enables you to customize the amount of data logged for long-running jobs, such as a PowerExchange Logger process that runs in continuous mode. If you specify this statement, also specify the LOGPATH statement.