CDC Guide for i5/OS

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

Back Next

Testing an Extraction Map

In the PowerExchange Navigator, perform a database row test to verify that PowerExchange can retrieve change data from a registered source based on an extraction map.

A database row test enables you to:

Preview change data that PowerExchange captured for the registered data source.

Preview change data that either PowerExchange Condense on i5/OS or z/OS or the PowerExchange Logger for Linux, UNIX, and Windows captured for registered source.

Verify that the extraction map properly maps the captured change data.

In the PowerExchange Navigator, open the extraction group and the extraction map.

Select the extraction map and click

File

Database Row Test

In the

Database Row Test

dialog box, enter information in the following fields:

DB Type: An option that indicates the extraction mode:

CAPXRT
. Real-time extraction mode or continuous extraction mode.

CAPX
. Batch extraction mode.
Location: Node name for the location of the system on which the captured change data resides. This name must be defined in a NODE statement in the dbmover.cfg configuration file on the Windows machine from which you run the database row test.
UserID and Password: Optional. A user ID and password that provides access to the source data.
Fetch: To preview data, select
Data
.
Application: An application name. For a row test, an application name is not required. However, you must enter at least one character in this field. PowerExchange does not retain this value.
SQL Statement: A SQL SELECT statement that PowerExchange generates for the fields in the extraction map. You can edit this statement, if necessary.
In the statement, a table is identified as follows:

Schema.RegName_TableName

Where:

Schema is a schema name for the extraction map.
RegName is the name of the capture registration that corresponds to the extraction map.
TableName is the table name of the data source.

If you enter

CAPX

in the

DB Type

field, you can extract change data only after PowerExchange Condense or the PowerExchange Logger for Linux, UNIX, and Windows closes at least one condense file or log file. Otherwise, PowerExchange does not display change data and writes message PWX-04520 to the PowerExchange message log. PowerExchange also writes this message if no change data for the source has been captured, condensed, or logged.

Click

Advanced

Complete the fields in the

CAPX Advanced Parameters

dialog box or

CAPXRT Advanced Parameters

dialog box.

If you use continuous extraction mode, enter the CAPX CAPI_CONNECTION name in the

CAPI Connection Name

field.

If you offload change data to PowerExchange Logger for Linux, UNIX, and Windows log files on a system that is remote from the source, enter the location of the extraction maps in the

Location

field.

Click

The database row test returns each change from the extraction start point, by column. The results include the PowerExchange-generated CDC columns, which provide information such as the change type, timestamp, and user ID.

Rename Saved Search

Table of Contents

CDC Guide for i5/OS

CDC Guide for i5/OS

Testing an Extraction Map

Testing an Extraction Map