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 Group Definition File

A PowerExchange Logger group definition file contains one or more GROUP statements. Each GROUP statement contains REG or SCHEMA parameters that directly or indirectly identify a group of capture registrations and tables for which you want to create separate sets of PowerExchange Logger log files.

For the PowerExchange Logger to use the group definition file, you must specify the path and file name of the file in the GROUPDEFS parameter of the pwxccl.cfg file.

If you specify the GROUPDEFS parameter, the PowerExchange Logger ignores the EXT_CAPT_MASK parameter in the pwxccl.cfg file when creating log files.

The following table describes the statements and parameters in the group definition file:

Statement	Positional Parameter	Description	Data Type and Length
GROUP	group_name	A unique user-defined name for the group. This parameter is required.	VARCHAR(255)
GROUP	external_capture_mask	A unique path and file-name prefix for the PowerExchange Logger log files that are created for tables in the group. This parameter is required. This path and prefix is used for the group instead of the path and prefix that are specified in the EXT_CAPT_MASK parameter of the pwxccl.cfg file.	VARCHAR(255)
REG	registration_name	Optional. Registration name that is specified in the Name field of a capture registration. This lowercase name can be the full registration name or the first part of the name followed by an asterisk () wildcard. This parameter is optional. If omitted, the PowerExchange Logger assumes REG=.	VARCHAR(8)
SCHEMA	schema_name	Optional. Name of the override schema. You can optionally use this parameter for Db2 for i (i5/OS) sources and for Db2 LUW, MySQL, and Oracle sources on Linux, UNIX, or Windows. This parameter is not supported for SQL Server sources on Windows. If you use the offloading feature to have the PowerExchange Logger process data from z/OS sources, this parameter is also not supported for the z/OS sources.	VARCHAR(255)

Use the following rules and guidelines when you create a PowerExchange Logger group definition file:

Each group_name
must be unique within the group definition file.

Each external_capture_mask
must be unique on the system.

SCHEMA statements are optional for Db2 for i (i5/OS) sources and for Db2 LUW, MySQL, and Oracle sources on Linux, UNIX, or Windows. SCHEMA statements are not supported for SQL Server sources on Windows or any data source on z/OS.

If you use a SCHEMA statement, you must define a capture registration in the group. You can specify multiple SCHEMA statements under a GROUP if you want the tables with those schemas to be included in the group.

REG statements apply to the preceding SCHEMA statement. If a SCHEMA statement is not present, the REG statements apply to the preceding GROUP statement.

If the file contains a SCHEMA or REG statement without a preceding GROUP statement, the PowerExchange Logger issues a syntax error.

Do not include the same schema.table value in more than one group. If a table is included in multiple groups, only the first group that includes the table logs changes for it.

If you do not define at least one REG statement for a GROUP, the PowerExchange Logger includes all of the active capture registrations that are defined for the specified DBID instance and for which the

Condense

option is set to

Part

If a registration belongs to multiple groups, the PowerExchange Logger logs changes for that registration only under the first group in the group definition file that includes the registration.

Using PowerExchange Logger Group Definitions

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal