CDC Guide for Linux, UNIX, and Windows

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

Back Next

Example of Remote Logging from a PowerExchange Express CDC for Oracle Source

In this example, you use a PowerExchange Logger for Linux, UNIX, and Windows instance on a UNIX system to capture change data from an Oracle instance on another UNIX system.

You want the PowerExchange Logger to capture change data from registered source tables in the Oracle ORAINST2 instance that runs on the PRODORA host and then log that data to its log files on a remote UNIX2 system. The system where the PowerExchange Logger runs is separate from the PowerCenter Integration Service system where you run CDC sessions. You must run a PowerExchange Listener on the source system and on the PowerExchange Logger system. You do not need to run a PowerExchange Listener on the PowerCenter Integration Service system.

The following image shows this shows the configuration:

First install PowerExchange on all three systems. Then perform the following steps to customize the PowerExchange Express CDC for Oracle, dbmover, and PowerExchange Logger configuration files and set the PWXPC connection attributes that PowerCenter CDC sessions require to extract change data from the PowerExchange Logger log files.

On the Oracle source system, perform the following configuration tasks:

Configure the PowerExchange Express CDC for Oracle configuration file. Use the sample pwxorad.cfg file that PowerExchange supplies in the directory that is specified in the PWX_HOME environment variable, or if that variable is not defined, in the PowerExchange bin directory. Include at least the following statements:

DICTIONARY
  MODE=STATIC
  SOURCE=ONLINE;
READER
  MODE=ACTIVE;

Ensure that the dbmover configuration file includes the following statements:

LISTENER=(unix1,TCPIP,2480)
ORACLE_CAPTURE_TYPE=D
CAPI_CONNECTION=(NAME=CAPIORA,TYPE=(ORAD,ORACOLL=COLINST2,PARMFILE=/Informatica/PowerExchangeVR/capture/pwxorad.cfg))
ORACLEID=(COLINST2,ORAINST2)

On the PowerExchange Logger system where the Logger log files reside, perform the following tasks:

Ensure that the dbmover configuration file includes the following statements:

LISTENER=(unix2,TCPIP,2480)
NODE=(unix1,TCPIP,PRODORA,2480)
...
LOGPATH=/pwx/logs/oracond
CAPT_XTRA=/pwx/capture/oracond/camaps
CAPT_PATH=/pwx/capture/oracond
/*
ORACLE_CAPTURE_TYPE=D
/* Source-specific CAPI Connection
CAPI_CONNECTION=(NAME=CAPIORA,TYPE=(ORAD,ORACOLL=COLINST2,PARMFILE=/Informatica/PowerExchangeVR/capture/pwxorad.cfg))
/*
/* CAPX CAPI Connection for continuous extraction
CAPI_CONNECTION=(NAME=CAPXORA,TYPE=(CAPX,DFLTINST=COLINST2,FILEWAIT=60,RSTRADV=600))

In the ORAD CAPI_CONNECTION statement, the PARMFILE parameter must point to the PowerExchange Express CDC for Oracle configuration file, pwxorad.cfg, that you created on the source system.

On the PowerExchange Logger system, customize the PowerExchange Logger configuration file, pwxccl.cfg. For this example, include the following statements:

DBID=COLINST2 
DB_TYPE=ORA
CONN_OVR=CAPIORA
CAPTURE_NODE=unix1
CAPTURE_NODE_UID=orauser
CAPTURE_NODE_EPWD=encrypted_password

The value of the DBID parameter must match the value of the first positional collection_id parameter, COLINST2, In the ORACLEID statement on the source system. The CAPTURE_NODE parameter points to the source system node where the PowerExchange Listener processes capture requests.

Start the PowerExchange Logger and the PowerExchange Listener on the PowerExchange Logger system. Verify that the PowerExchange Listener is also running on the source system.

On the PowerCenter Integration Service system, add the following NODE statements in the dbmover configuration file:

A NODE statement that points to the PowerExchange Listener on the source system

A NODE statement that points to the PowerExchange Logger system

The following example shows these NODE statements:

NODE=(unix1,TCPIP,PRODORA,2480)
NODE=(unix2,TCPIP,unix2,2480)

Create a PowerCenter mapping, session, and workflow.

Configure a PWX Oracle CDC Real Time application connection for CDC sessions that extract change data from the PowerExchange Logger log files.

For this example, set the following connection attributes:

For the

Location

attribute, enter unix2 to point to the node where the PowerExchange Logger log files reside. CDC sessions will read data from this location.

For the

Map Location

attribute, enter unix1 to point to the location of the extraction maps, which is the source system node.

For the

Map Location User

attribute, enter a valid Oracle user ID.

For the

Map Location Password

attribute, enter the password for the Oracle user ID.

For the

CAPI Connection Name

attribute, enter CAPXORA to indicate the CAPX CAPI_CONNECTION statement to use.

Cold start the CDC session.

The session begins extracting change data from the PowerExchange Logger log files.

Remote Logging of Data

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

0 COMMENTS

Back Next

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

CDC Guide for Linux, UNIX, and Windows

CDC Guide for Linux, UNIX, and Windows

Example of Remote Logging from a PowerExchange Express CDC for Oracle Source

Example of Remote Logging from a PowerExchange Express CDC for Oracle Source