Sei sulla pagina 1di 30
Implementing PowerExchange 8.6.1 Oracle LogMiner CDC in a Non-RAC Environment © 2010 Informatica Corporation

Implementing PowerExchange 8.6.1 Oracle LogMiner CDC in a Non-RAC Environment

© 2010 Informatica Corporation

Abstract This article describes how to implement PowerExchange 8.6.1 Oracle LogMiner change data capture (CDC)

Abstract

This article describes how to implement PowerExchange 8.6.1 Oracle LogMiner change data capture (CDC) in a non- RAC Oracle® environment on UNIX. It identifies the configuration steps that you perform in Oracle, PowerExchange, and PowerCenter to create a working CDC environment. It includes example configuration files, tips, and best practices.

Table of Contents

Overview

3

Implementation Scenario

3

Before You Begin

4

PowerExchange Installation

4

Information Required for CDC Configuration

5

Oracle CDC Restrictions and Requirements

7

Create Target Tables

7

Oracle Configuration Tasks

8

Step 1. Specify an Archive Log Destination

8

Step 2. Set the Oracle transaction_auditing Parameter

8

Step 3. Enable ARCHIVELOG Mode

8

Step 4. Stop and Restart the Oracle Database

8

Step 5. Grant the User Privileges Required for CDC

8

Step 6. Configure Oracle Minimal Global Supplemental Logging

9

Step 7. Create a Table Space Exclusively for Oracle LogMiner Use (Optional)

9

Step 8. Copy the Oracle Catalog to the Archived Logs

10

PowerExchange Configuration Tasks

10

Step 1. Customize the dbmover.cfg File on UNIX

11

Step 2. Customize the PowerExchange Logger pwxccl.cfg File

16

Step 3. Start the PowerExchange Listener

19

Step 4. Customize the dbmover.cfg Files on the Windows and PowerCenter Integration Service Machines

20

Step 5. Create Capture Registrations

20

Step 6. Add Change Indicator or Before Image Columns to Extraction Maps (Optional)

22

Step 7. Perform a Database Row Test of the Extraction Maps

23

Step 8. Materialize the Target Tables

23

Step 9. Start the PowerExchange Logger

23

Step 10. Allow Changes to Be Written to the Source Tables

24

PowerCenter Configuration Tasks

24

Step 1. Import Extraction Maps for Source Tables

24

Step 2. Import Target Table Definitions

25

Step 2. Import Target Table Definitions 25 Step 3. Create a Mapping 25 Step 4. Configure

Step 3. Create a Mapping

25

Step 4. Configure an Application Connection for the Oracle Sources

25

Step 5. Create a Workflow and Session

26

Step 6. Configure the Restart Token File

29

Step 7. Cold Start the CDC Workflow

29

Additional Information

29

Overview

This article summarizes the steps that are necessary to successfully implement PowerExchange 8.6.1 Oracle LogMiner CDC for multiple Oracle source tables in a non-RAC environment on UNIX. It includes example configuration files and best practices.

PowerExchange Oracle LogMiner CDC uses Oracle LogMiner to read change data from Oracle redo logs. To move the change data to target tables, PowerExchange uses the PowerExchange Client for PowerCenter (PWXPC) in conjunction with PowerCenter.

To implement Oracle CDC, you need to perform configuration tasks in Oracle, PowerExchange, and PowerCenter. Often, these tasks are performed by more than one person, for example, the Oracle DBA, target RDBMS DBA, system administrator, PowerExchange administrator, and PowerCenter developer.

This implementation uses the PowerExchange Logger for Linux, UNIX, and Windows, which is optional for Oracle LogMiner CDC. The PowerExchange Logger captures change data from Oracle redo logs and writes only the successful units of work (UOWs), in chronological order based on commit time, to PowerExchange Logger log files. The change data is extracted from the PowerExchange Logger log files in continuous extraction mode to provide near- real-time access to the data on the target machine. The benefits of using the PowerExchange Logger include fewer database accesses, faster CDC restart, and no need to prolong retention of Oracle redo files for change capture.

Note: Informatica strongly recommends that you use the PowerExchange Logger for Oracle LogMiner CDC. If you use real-time extraction mode without the PowerExchange Logger, PowerExchange starts a separate Oracle LogMiner session for each extraction session. Running multiple, concurrent LogMiner sessions can significantly degrade performance of the system where LogMiner runs.

Although this article focuses on UNIX, the information herein also applies to Oracle sources on Linux and Windows.

Implementation Scenario

Scenario: You need to keep a data warehouse synchronized with an Oracle production database in near real time.

This scenario makes the following assumptions about your CDC environment and requirements:

You are using PowerExchange CDC 8.6.1 or later with Oracle 10g or 11g.

You need to capture changes from about 50 Oracle source tables that are on a UNIX machine. The UNIX machine is remote from the PowerCenter Integration Service machine.

The PowerExchange Navigator and PowerCenter Client reside on the same Windows machine, which is remote from the PowerCenter Integration Service machine.

The Oracle source tables are not in an Oracle Real Application Cluster (RAC) environment.

You must move change data in near real time to multiple target tables on a remote machine.

You run the PowerExchange Logger for Linux, UNIX, and Windows on the Oracle source machine

You run the PowerExchange Logger for Linux, UNIX, and Windows on the Oracle source machine to capture change data continuously to PowerExchange Logger log files.

You extract change data from the PowerExchange Logger log files in continuous extraction mode. Continuous extraction mode provides near real time access to change data but is much less resource intensive than real-time extraction mode.

The Oracle source machine has sufficient memory and resources to handle CDC efficiently without offloading PowerExchange Logger processing.

You use PWXPC connections and PowerCenter workflows to extract the change data from the PowerExchange Logger log files and to write the data to multiple target tables.

Note: PWXPC is a native plug-in that is installed with PowerCenter on the Windows and PowerCenter Integration Service machines.

The following diagram shows the architecture for this scenario:

following diagram shows the architecture for this scenario: Before You Begin Before you configure Oracle CD

Before You Begin

Before you configure Oracle CDC, perform the following tasks:

1. Install PowerExchange software on the following machines:

UNIX machine that contains the Oracle source tables

Windows machine where the PowerCenter Client runs

PowerCenter Integration Service machine

2. Gather the information about your Oracle source and environment that is required for CDC configuration.

3. Review CDC limitations and restrictions.

4. Create the target tables.

PowerExchange Installation

PowerExchange installation on UNIX and Windows is all-inclusive. You do not install PowerExchange components separately.

On the UNIX machine with the Oracle source tables, extrac t files from the 32-bit

On the UNIX machine with the Oracle source tables, extract files from the 32-bit or 64-bit PowerExchange tar file for your UNIX operating system. Then run install.sh to perform the installation.

After installation completes, set the following environment variables:

Set the PWX_HOME environment variable to point to the PowerExchange installation directory.

Edit the PATH and LIBPATH environment variables to append the PowerExchange installation directory.

Verify that the LANG and LC_ALL environment variables are set to “C.” If these environment variables are not set to “C,” ask your UNIX administrator to change them.

On the Windows machine, run the PowerExchange 32-bit executable. You must install the Windows 32-bit executable to use the PowerExchange Navigator, even on a Windows 64-bit machine.

On the PowerCenter Integration Service machine, follow the PowerExchange installation instructions for the operating system type and bit-level. If the Integration Service runs on a 64-bit machine, use the PowerExchange 64-bit installation executable or tar file. If the Integration Service runs on a 32-bit machine, use the PowerExchange 32-bit executable or tar file.

For more information about UNIX and Windows installation procedures, see the PowerExchange Installation Guide.

Information Required for CDC Configuration

The following table identifies the information that you will need to enter for Oracle CDC configuration. The table includes example values. Example paths for PowerExchange items such as the CCT file, extraction maps, message logs, and PowerExchange Logger log files assume that you store these items in directories separate from the PowerExchange code, as recommended. For this scenario, assume that the PowerExchange code is installed at /pwx/test.

Note: In this table, “the UNIX machine” refers to the UNIX machine where the Oracle source tables reside.

Information

Where Specified

Example Value

Your Value

Oracle archive log destination

Oracle init.ora file or spfile SQL

/oracle_path/arch

 

Oracle user

SQL CREATE USER and GRANT statements for defining Oracle privileges for CDC

ORACAPT

 

Table space for Oracle LogMiner

DDL for creating the table space

LOGMNRTS

 

Datafile for the Oracle LogMiner table space

DDL for creating the table space

/oracle_path/datafilename.ora

 

User-defined name for the LISTENER statement, which is used to start or stop the PowerExchange Listener on the UNIX machine

The LISTENER statement in dbmover.cfg on the UNIX machine

pwxlst

 

Port number that the PowerExchange Listener uses on the UNIX machine

The LISTENER statement in dbmover.cfg on the UNIX machine

2480

 

Note: This port number is the default.

User-defined name for the NODE statement that is used to connect to the UNIX machine

A NODE statement in the dbmover.cfg files on the following machines:

ora_unix1

 

Windows machine with the PowerExchange Navigator and PowerCenter Client

PowerCenter Integration

Service machine

Information Where Specified Example Value Your Value Host name for the UNIX machine A NODE

Information

Where Specified

Example Value

Your Value

Host name for the UNIX machine

A

NODE statement in the

unix_host01

 

dbmover.cfg files on the following

machines:

Windows machine with the PowerExchange Navigator and PowerCenter Client

PowerCenter Integration

 

Service machine

Port number for PowerExchange use on the UNIX machine

A NODE statement in the

2480

 

dbmover.cfg files on the following

 

machines:

Windows machine with the PowerExchange Navigator and PowerCenter Client

Note: This port number is the default.

PowerCenter Integration

 

Service machine

Path to PowerExchange message log files on the UNIX machine

LOGPATH statement in dbmover.cfg on the UNIX machine

/pwx/logs

 

Subdirectory of the LOGPATH directory for alternative message log files for the PowerExchange Logger

PFX option of the TRACING statement in dbmover.cfg on the UNIX machine

altlogs

 

Path to the directory that stores the CCT and CDCT files on the UNIX machine. These files store information about capture registrations and PowerExchange Logger log files.

CAPT_PATH statement in dbmover.cfg on the UNIX machine

/pwx/capture

 

Path to the directory that stores extraction maps on the UNIX machine

CAPT_XTRA statement in dbmover.cfg on the UNIX machine

/pwx/capture/xtramaps

 

User-defined collection ID for an ORACLEID statement for the Oracle source instance. Maximum length is eight characters.

The following statements in dbmover.cfg on the UNIX

ORACOL01

 

machine:

First positional parameter in the ORACLEID statement

 

ORACOLL parameter in the ORCL CAPI_CONNECTION

DFLTINST parameter in the CAPX CAPI_CONNECTION

Also specified in:

Collection ID field when you create a registration group in the PowerExchange Navigator, or Instance field when you view registration group properties.

DBID parameter in pwxccl.cfg

Information Where Specified Example Value Your Value Oracle database name Second positional parameter in

Information

Where Specified

Example Value

Your Value

Oracle database name

Second positional parameter in an ORACLEID statement in the dbmover.cfg files on the UNIX and Windows machines

orcl01

 

A

database service name that

Third and fourth positional parameters in the ORACLEID

orcl01.world

 

PowerExchange uses to connect

to

the Oracle database

statement in the dbmover.cfg files on the UNIX machine and on the Windows machine. This value is the connect string in the Oracle Client tnsnames.ora file on the UNIX machine.

Oracle schema.table names for the source tables, and the columns from which to capture change data

Capture registrations that you define from the PowerExchange Navigator

   

Path and unique prefix to use for generating the PowerExchange Logger log files. To create the file names, the Logger appends the following:

EXT_CAPT_MASK in pwxccl.cfg file on the UNIX machine

pwx/pwxccl

 

.CND.CPyymmdd.Thhmmssnnn

Path and base name to use for generating the PowerExchange Logger checkpoint files

CHKPT_BASENAME in pwxccl.cfg on the UNIX machine

pwx/pwxccl.chkpt

 

Retention period, in days, for CDCT records and PowerExchange Logger log files

COND_CDCT_RET_P statement in pwxccl.cfg on the UNIX machine

30

 

Database user ID

CAPTURE_NODE_UID statement in pwxccl.cfg on the UNIX machine

oracapt

 

Database password or encrypted password

CAPTURE_NODE_PWD or CAPTURE_NODE_EPWD statement in pwxccl.cfg on the UNIX machine

oracapt

 

Oracle CDC Restrictions and Requirements

The following restrictions and requirements pertain to Oracle CDC:

PowerExchange cannot process copies of archived redo logs because Oracle LogMiner continuous mining reads archived redo logs only from the directory to which they were originally written.

The Oracle instance must be running in ARCHIVELOG mode.

Oracle global minimal supplemental logging must be enabled.

PowerExchange does not capture changes from columns that have certain datatypes such as LOB or LONG. For more information about datatype restrictions, see the PowerExchange CDC Guide for Linux, UNIX, and Windows.

Create Target Tables

In the target RDBMS, create the tables to which you want to apply Oracle change data.

For this scenario, assume that the target table columns have a one-to-one correspondence with the source table columns.

Oracle Configuration Tasks To configure Oracle for CDC, use the sample Oracle configuration script file,

Oracle Configuration Tasks

To configure Oracle for CDC, use the sample Oracle configuration script file, oracapt.sql, which is located in the PowerExchange installation directory. This script file contains sample SQL statements and comments to help you complete the required Oracle configuration steps.

Step 1. Specify an Archive Log Destination

Edit your init.ora file to specify the archive log destination and file-name format. For more information, see your Oracle database administrator’s guide.

Alternatively, if you use a server parameter file (spfile), issue the following SQL statements to indicate the archive log destination:

CONNECT SYS/sys_pwd AS SYSDBA; ALTER SYSTEM SET log_archive_dest_1 = 'location=/ oracle_path/arch' SCOPE=SPFILE;

Step 2. Set the Oracle transaction_auditing Parameter

If you use an Oracle version earlier than 10.1.0.1, verify that the transaction_auditing parameter is set to “True” in the init.ora file. This setting is required for Oracle CDC to work properly.

To set this parameter, issue the following SQL statement:

Alter SYSTEM SET transaction_auditing=TRUE SCOPE=SPFILE;

Step 3. Enable ARCHIVELOG Mode

For CDC, Oracle must be running in ARCHIVELOG mode.

To enable ARCHIVELOG mode, issue the following statements:

SHUTDOWN IMMEDIATE; STARTUP MOUNT; ALTER DATABASE ARCHIVELOG; ALTER DATABASE OPEN; SHUTDOWN IMMEDIATE; STARTUP;

Tip: Back up your database after both SHUTDOWN commands.

Step 4. Stop and Restart the Oracle Database

If you set the ARCHIVELOG mode or the “compatible” or “transaction_auditing” parameter, you must stop and restart the Oracle instance for your changes to take effect.

For more information, see the oracapt.sql file.

Step 5. Grant the User Privileges Required for CDC

To grant the user privileges required for Oracle CDC, use the SQL GRANT statements in the oracapt.sql file.

1. Log in to Oracle as a user who has the role of DBA or who has the authority to perform the tasks in Steps 6 through 9.

2. Optionally, issue the following SQL to create the user “ORACAPT” who can connect to the Oracle database to capture change data in real time:

CREATE USER "ORACAPT" PROFILE "DEFAULT" IDENTIFIED BY "oracapt" ACCOUNT UNLOCK;

GRANT "CONNECT" TO "ORACAPT"; 3. Issue the following GRANT statements to provide the mi nimum

GRANT "CONNECT" TO "ORACAPT";

3. Issue the following GRANT statements to provide the minimum privileges for running Oracle CDC to the user “ORACAPT” :

GRANT SELECT ON "PUBLIC"."V$INSTANCE" TO "ORACAPT"; GRANT SELECT ON "PUBLIC"."V$DATABASE" TO "ORACAPT"; GRANT SELECT ON "SYS"."DBA_LOG_GROUPS" TO "ORACAPT"; GRANT SELECT ON "SYS"."DBA_LOG_GROUP_COLUMNS" TO "ORACAPT"; GRANT SELECT ON "PUBLIC"."V$TRANSACTION" TO "ORACAPT"; GRANT SELECT ON "PUBLIC"."V$ARCHIVED_LOG" TO "ORACAPT"; GRANT SELECT ON "PUBLIC"."V$LOGMNR_CONTENTS" TO "ORACAPT"; GRANT SELECT ON "PUBLIC"."V$PARAMETER" TO "ORACAPT"; GRANT SELECT ON "PUBLIC"."V$NLS_PARAMETERS" TO "ORACAPT";

--

-- If you are using Oracle 10 g or later, include the following statement:

-- GRANT SELECT ANY TRANSACTION TO "ORACAPT";

--

GRANT EXECUTE ON "SYS"."DBMS_FLASHBACK" TO "ORACAPT";

GRANT EXECUTE ON "SYS"."DBMS_LOGMNR_D" TO "ORACAPT"; GRANT EXECUTE ON "SYS"."DBMS_LOGMNR" TO "ORACAPT";

Note: The GRANT LOCK ANY TABLE statement is not required because this scenario uses GENRLOCK=N for the ORCL CAPI_CONNECTION. With this setting, PowerExchange does not lock Oracle tables while creating restart points.

4. Issue the following GRANT statement if you plan to use the Oracle user ID that you specified in the CREATE USER statement to create capture registrations and to automatically run the DDL that PowerExchange generates for creating supplemental log groups at registration completion:

GRANT ALTER ANY TABLE TO "ORACAPT";

For a description of the minimum required Oracle system privileges and object privileges, see the CDC Guide for Linux, UNIX, and Windows.

Step 6. Configure Oracle Minimal Global Supplemental Logging

PowerExchange requires Oracle minimal global supplemental logging for Oracle LogMiner to properly handle chained rows.

To enable supplemental logging, log in to the Oracle database and issue the following SQL statement:

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; COMMIT;

Note: You must also define a supplemental log group for each Oracle source table. When you register an Oracle table in the PowerExchange Navigator, PowerExchange generates DDL for adding a supplemental log group for the table.

Step 7. Create a Table Space Exclusively for Oracle LogMiner Use (Optional)

Create a table space exclusively for Oracle LogMiner use to prevent the SYSTEM table space (for Oracle version 9i) or SYSAUX table space (for Oracle 10g or later) from becoming full during CDC.

This step is necessary only if you have not previously configured LogMiner for use with other Oracle features such as logical standby databases, Oracle Streams, or native Oracle change capture process.

1. To create the table space, issue the following DDL:

CREATE TABLESPACE "LOGMNRTS" NOLOGGING DATAFILE '/oracle_path/datafilename.ora' SIZE 50M REUSE AUTOEXTEND ON NEXT 10M MAXSIZE 100M EXTENT MANAGEMENT LOCAL;

Notes : Specify NOLOGGING if you use Oracle LogMiner only for PowerExchange CDC and an

Notes:

Specify NOLOGGING if you use Oracle LogMiner only for PowerExchange CDC and an occasional query. Change NOLOGGING to LOGGING if you use any of the following Oracle features: logical standby databases, Oracle Streams, or native Oracle change capture process.

For the DATAFILE value, specify a file name based on your local Oracle database file naming standards for the data files that comprise this table space.

2. Enter the following command:

EXECUTE SYS.DBMS_LOGMNR_D.SET_TABLESPACE('LOGMNRTS');

If this statement fails with the ORA_01353 message, see the comments in oracapt.sql for more information.

3. To recompile the SYS.DBMS_LOGMNR_D package, enter the following command:

ALTER PACKAGE SYS.DBMS_LOGMNR_D COMPILE BODY;

Step 8. Copy the Oracle Catalog to the Archived Logs

PowerExchange CDC requires a copy of the Oracle online catalog in the Oracle archived redo logs to determine the point from which to restart change data extractions.

To copy the catalog, issue the following command from a SQL*Plus session:

begin

SYS.DBMS_LOGMNR_D.BUILD(

options => sys.dbms_logmnr_d.store_in_redo_logs); end;

/

Tip: Periodically, PowerExchange requests Oracle to recopy the catalog. You can use the CATBEGIN, CATEND, and CATINT parameters in the ORCL CAPI_CONNECTION statement of dbmover.cfg to control how often Oracle copies the catalog and the time period within which the copy occurs.

PowerExchange Configuration Tasks

You must perform CDC configuration tasks on each machine where PowerExchange is installed.

This section guides you through performing the following tasks on the following machines:

On the UNIX machine that contains the Oracle source tables, customize the PowerExchange Listener configuration file, dbmover.cfg, and the PowerExchange Logger for Linux, UNIX, and Windows configuration file, pwxccl.cfg. Also, start the PowerExchange Listener and PowerExchange Logger.

On the Windows machine that contains the PowerExchange Navigator and PowerCenter Client, customize the dbmover.cfg file and create capture registrations.

On the PowerCenter Integration Service Machine, customize the dbmover.cfg file.

This section uses the following PowerExchange terminology:

A capture registration is a named definition of the source data for which you want PowerExchange to capture changes. A registration addresses a single table and specifies the columns for which to capture changes, the Condense option to use, and the registration status. When you define a capture registration, a corresponding extraction map is generated.

An extraction map is a definition of a change data extraction for a source table. PowerExchange generates an extraction map for each capture registration you define. You can edit the generated extraction maps to add or remove columns. You can also create additional extraction maps for a capture registration.

A registration group is a named set of capture registrations for capturing source data. The registration group definition includes the PowerExchange Listener location, the database type, and the user ID and password for accessing the source data. When you define a registration group, a corresponding extraction group is generated.

Step 1. Customize the dbmover.cfg File on UNIX On the UNIX machine that contains the

Step 1. Customize the dbmover.cfg File on UNIX

On the UNIX machine that contains the Oracle source tables, customize the dbmover.cfg configuration file.

Tip: A sample file for Linux and UNIX machines is located in your PowerExchange installation directory. Copy this file to another directory and customize the copy. This practice preserves your customized file if you upgrade PowerExchange.

The following sample dbmover.cfg file includes required and recommended statements for Oracle CDC.

/********************************************************************/ /* PowerExchange Configuration File /********************************************************************/

LISTENER=(pwxlst,TCPIP,2480)

NODE=(local,TCPIP,127.0.0.1,2480)

NODE=(pwxlst,TCPIP,127.0.0.1,2480)

NODE=(default,TCPIP,x,2480)

/*

APPBUFSIZE=128000

COLON=:

CONSOLE_TRACE=Y DECPOINT=. DEFAULTCHAR=*

DEFAULTDATE=19800101

MAXTASKS=5

MSGPREFIX=PWX

NEGSIGN=-

PIPE=|

POLLTIME=1000

TIMEOUTS=(60,3600,3600)

EXT_CP_SUPPT=Y LOGPATH=/pwx/logs

TRACING=/PFX=PWXLOG,RECLEN=255,FILENUM=3,APPEND=Y,FLUSH=99)

CAPT_PATH=/pwx/capture CAPT_XTRA=/pwx/capture/xtramaps /* /* An ORACLEID statement is required for each Oracle instance involved in CDC.

ORACLEID=(ORACOL01,orcl01,orcl01.world,orcl01.world)

/* /* CAPI connection statements:

/* /* A CAPX CAPI_CONNECTION is required for continuous extraction mode. CAPI_CONNECTION=(NAME=CAPX01,TYPE=( CAPX,DFLTINST=ORACOL01))

/*

/* Both UOWC and ORCL CAPI_CONNECTION statements are required for Oracle CDC. CAPI_CONNECTION=(NAME=CAPIORA1,TYPE=( ORCL,ARRAYSIZE=1000,BYPASSUF=Y,

CATBEGIN=00:01,CATEND=23:59,CATINT=1440,ORACOLL=ORACOL01,SELRETRY=0))

CAPI_CONNECTION=(NAME=CAPIUOW1,TYPE=( UOWC,CAPINAME=CAPIORA1,MEMCACHE=50000)) /*

CAPI_CONN_NAME=CAPIUOW1

/* /* To use pwxcmd to issue commands to PowerExchange Listener and Logger /* processes, include the following statements:

SVCNODE=(pwxlst,8500)

SVCNODE=(pwxccl_svc,8501)

CMDNODE=(pwxlst,LISTENER,unix_host01,8500)

CMDNODE=(pwxccl_svc,CONDENSE,unix_host01,8501)

/*

Key Parameter Descriptions

The following table describes key parameters for Oracle CDC using the PowerExchange Logger:

Parameter

Description

CAPI_CONN_NAME

Optional. Default CAPI_CONNECTION statement, across all source types.

Parameter Description CAPT_PATH Required. Specifies a path to the local directory where the CCT and

Parameter

Description

CAPT_PATH

Required. Specifies a path to the local directory where the CCT and CDCT files reside. This directory must exist on the UNIX machine. The CCT file contains capture registrations. The CDCT file contains information about PowerExchange Logger log files.

CAPT_XTRA

Required. Specifies a path to the local directory where extraction maps reside. This directory must exist on the UNIX machine.

CMDNODE

Optional. Specifies a service name and connection information for the PowerExchange Listener or PowerExchange Logger process to which you want to send pwxcmd commands from this machine.

Note: In this scenario, you run the PowerExchange Listener and PowerExchange Logger in background mode. To issue commands to background processes, you must use the pwxcmd program. However, you can also use pwxcmd to issue commands in foreground mode or from a script file. For more information, see the PowerExchange Command Reference.

For this scenario, define CMDNODE statements in the dbmover.cfg files on the UNIX and Windows machines so that you can issue pwxcmd commands from either machine.

Syntax is:

CMDNODE=( service_name , service_type , host_name , port_number )

Where:

service_name is a service name. This name can be any name you want to use. For consistency, you can match the service name in the corresponding SVCNODE statement in the dbmover.cfg file on this UNIX machine.

service_type is either “LISTENER” for the PowerExchange Listener or “CONDENSE” for the PowerExchange Logger.

host_name is the host name or IP address of the machine where the PowerExchange Listener or PowerExchange Logger runs. In this case, enter the host name or IP address of this UNIX machine.

port_number is the port number that is specified in the corresponding SVCNODE statement of the dbmover.cfg file on this UNIX machine. This port is the one on which the PowerExchange Listener or PowerExchange Logger listens for pwxcmd commands.

If you specify a CMDNODE statement, also specify a corresponding SVCNODE statement.

LOGPATH

Recommended. Specifies a unique path for PowerExchange message log files. Use this parameter to create message log files in a directory that is separate from your current working directory so that you can find PowerExchange messages more easily.

ORACLEID

Required. Specifies Oracle SID and connection information for the Oracle source database.

Syntax is:

ORACLEID=( collection_id , oracle_db , connect_string , capture_connect_string )

Where:

collection_id is a user-defined name for this ORACLEID statement. This value must match the ORACOLL value in the ORCL CAPI_CONNECTION statement, the collection ID that you specify in registration groups, and the DBID value in the PowerExchange Logger pwxccl.cfg file. Maximum length is eight characters.

oracle_db is an Oracle database name.

connect_string is a database service name that the PowerExchange Navigator uses to connect to the Oracle database. This value is the connect string in the Oracle Client tnsnames.ora file on the UNIX source machine, which is used to connect to the Oracle database.

capture_connect_string is a database service name that the PowerExchange Logger uses to connect to the Oracle database. This value is the connect string in the Oracle Client tnsnames.ora file on the UNIX source machine, which is used to connect to the Oracle

Parameter Description     database.   Tip : Informatica recommends that you set the following

Parameter

Description

 
 

database.

 

Tip: Informatica recommends that you set the following environment variables, whenever possible, to enable connection to the Oracle database without using the capture connect string and to bypass the use of Oracle SQL*Net:

o

ORACLE_HOME

o

ORACLE_SID

o

PATH

o

One of the following variables, depending on your UNIX platform type:

LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH

If you can bypass the use of SQL*Net when connecting to your Oracle database, you can improve PowerExchange Logger performance, even when running on the same machine as the Oracle database.

The capture string and capture connect string are required if you have multiple Oracle instances and you are capturing changes from an instance other than the default instance.

You can specify up to 20 ORACLEID statements in a dbmover.cfg.

CAPX CAPI_CONNECTION

Required for continuous extraction mode. Named set of parameters for continuous extraction of change data from PowerExchange Logger log files.

Syntax:

CAPI_CONNECTION=( NAME= name , [DLLTRACE= dll_trace_name ], [TRACE= trace_name ], TYPE=(CAPX, DFLTINST= collection_id , [FILEWAIT= seconds ] ))

Where:

NAME is a user-defined name for the CAPI_CONNECTION statement.

TYPE must be “CAPX” for continuous extraction mode with the PowerExchange Logger.

DFLTINST is the collection ID specified in the ORACLEID statement that is used by default when the Oracle instance is not specified for an extraction session. This value must also match the ORACOLL value in the ORCL CAPI_CONNECTION statement, the collection ID that you specify in registration groups, and the DBID value in the PowerExchange Logger pwxccl.cfg file. Maximum length is eight characters.

Other parameters are optional. For more information, see the PowerExchange Reference Manual.

ORCL CAPI_CONNECTION

Required. Named set of parameters that the CAPI uses to connect to the Oracle change stream and control extraction processing.

Syntax:

CAPI_CONNECTION=( NAME= name , [DLLTRACE= dll_trace_name ], [TRACE= trace_name ], TYPE=(ORCL, [ARRAYSIZE= nnnnnnnnnn ], [BYPASSUF=Y|N], [CATBEGIN= hh:mm ],

[CATEND=

hh:mm ],

[CATINT=

minutes ],

[COMMITINT= minutes ], [GENRLOCK=Y|N], [LOGDEST=dest],

Parameter   Description     [LGTHREAD= thread ], [ONLINECAT=Y|N], ORACOLL= collection_id ,

Parameter

 

Description

   

[LGTHREAD= thread ], [ONLINECAT=Y|N],

ORACOLL= collection_id , [SELRETRY= nnnnnnnnnn ], [SNGLINST=ora_instance]

)

)

Where:

NAME is a user-defined name for the CAPI_CONNECTION statement.

TYPE must be “ORCL” for Oracle CDC.

ARRAYSIZE is the size of the prefetch array that PowerExchange uses to read Oracle archived logs. Default is 100 rows. A value less than 100 can adversely affect Oracle capture performance.

BYPASSUF indicates whether PowerExchange ends abnormally or issues a warning message whenever it receives an unformatted log record from Oracle LogMiner. Default is N. Enter Y only if your Oracle instance contains Global Temporary tables.

CATBEGIN is the earliest 24-hour time of day, in hh:mm format, at which Oracle can attempt to write the Oracle catalog to the Oracle archive logs. Specify both CATBEGIN and CATEND with non-default values, or specify neither parameter. If you specify either CATBEGIN or CATEND, default of 00:00 is used.

CATEND is the latest 24-hour time of day, in hh:mm format, at which Oracle can attempt to write the Oracle catalog to the Oracle archive logs. Specify both CATEND and CATBEGIN with non-default values, or specify neither parameter. If you specify neither parameter, default of 24:00 is used. If you specify either CATBEGIN or CATEND, default of 00:00 is used.

CATINT is the interval, in minutes, between attempts to copy the Oracle catalog to the Oracle archive logs. Valid values are 1 through 1440. If the interval elapses outside of the CATBEGIN and CATEND timeframe, the catalog is copied during the next CATBEGIN and CATEND timeframe at the CATBEGIN time, if the PowerExchange Logger is running at that time.

ORACOLL is the collection identifier that is specified in the ORACLEID statement. This value must also match the DFLTINST value in the CAPX CAPI_CONNECTION statement, the collection ID that you specify in registration groups, and the DBID value in the PowerExchange Logger pwxccl.cfg file. Maximum length is eight characters

SELRETRY is the number of times that PowerExchange immediately loops back to the Oracle LogMiner call before implementing a graduated-scale wait loop. Valid values are 0 through 2147483647. Default is 1000. Informatica recommends a value of 0, which causes PowerExchange to not use non-blocking SQL. This setting improves CPU consumption but can prolong extraction session shutdown.

Tip: Include the CATBEGIN, CATEND, and CATINT parameters to control how often Oracle copies the Oracle catalog to the redo logs and the time period within which the copy occurs. If you do not have restrictions for this time period, do not specify CATBEGIN and CATEND.

For more information about optional parameters, see the PowerExchange Reference Manual.

SVCNODE

Optional. Specifies the port on which the command-handling service for a PowerExchange Listener or PowerExchange Logger process listens for pwxcmd commands. Define a SVCNODE statement for each PowerExchange Listener or PowerExchange Logger service to which you want to send pwxcmd commands.

Syntax is:

SVCNODE=( service_name , port_number )

Where:

service_name is:

Parameter Description       o For the PowerExchange Listener: The node name that is

Parameter

Description

 
   

o

For the PowerExchange Listener: The node name that is specified in the LISTENER statement.

o

For the PowerExchange Logger: The service name that is specified in the CONDENSENAME statement of the pwxccl.cfg file.

port_number is an available port number on which the PowerExchange Listener or PowerExchange Logger listens for pwxcmd commands. This port number must be different from the one specified in the LISTENER statement.

If you specify a SVCNODE statement, also specify a corresponding CMDNODE statement.

TRACING

Recommended. Enables PowerExchange to use alternative message log files for each PowerExchange process instead of the detail.log file for all PowerExchange processes. PowerExchange creates the alternative log files in a user-defined subdirectory of the LOGPATH directory. When an alternative log file becomes full, PowerExchange automatically switches to another log file. This parameter can help you find messages for a PowerExchange process more easily and prevent errors related to the message logs becoming full.

Syntax:

 

TRACING=(PFX= subdirectory ,[APPEND=Y|N],[BUFFERS= number ], [FILENUM= number_of_files ],[FLUSH= number_of_records ], [RECLEN= record_length ],[SIZE= log_size ],[VIEW=Y|N])

Where:

 

PFX is required and specifies the name of an existing subdirectory in which to store alternative log files.

APPEND indicates how PowerExchange writes messages to existing log files after a restart. Enter Y to have PowerExchange append new log records to the log file that was last used. Enter N to have PowerExchange overwrite the oldest log file. Default is Y.

FILENUM is the number of alternative log files. When a log file becomes full, PowerExchange switches to the oldest alternative log file and starts overwriting its contents. Valid values are 1 through 99. Default is 5.

FLUSH is the number of records that PowerExchange collects before flushing them to the log file on disk. PowerExchange periodically flushes log records to recover from out-of-space conditions. Low flush values can cause more I/O on the log file. Valid values are 1 through 99. Default is 99.

RECLEN is the record length that PowerExchange uses to write log records to the log file. PowerExchange writes the log record on multiple lines if the length of the message exceeds the record length. Valid values are 80 through 255 characters. Default is 80.

For more information about other optional parameters, see the PowerExchange Reference Manual.

UOWC CAPI_CONNECTION

Required. Named set of parameters for the UOW Cleanser. The UOW Cleanser reconstructs intermingled changes from multiple UOWs into complete and consecutive UOWs that are in chronological order by end time. This statement also points to the ORCL CAPI_CONNECTION.

Syntax:

 

CAPI_CONNECTION=( NAME=name, [DLLTRACE=trace_id], [TRACE=trace], TYPE=(UOWC, CAPINAME=capiname, [BLKSIZE= block_size ], [MEMCACHE= kilobytes ]

 

)

)

Where:

 
Parameter Description   • NAME is a user-defined name for the CAPI_CONNECTION statement. • TYPE

Parameter

Description

 

NAME is a user-defined name for the CAPI_CONNECTION statement.

TYPE must be “UOWC” for the UOW Cleanser.

CAPINAME matches the NAME value specified in the ORCL CAPI_CONNECTION statement.

MEMCACHE is the amount of memory cache, in kilobytes, that is allocated to the UOW Cleanser for reconstructing complete UOWs. Valid values are 1 through 519720. Default is 1024.

For more information about all dbmover.cfg parameters, see the PowerExchange Reference Manual.

Step 2. Customize the PowerExchange Logger pwxccl.cfg File

On the UNIX machine that contains the Oracle source tables, customize the pwxccl.cfg configuration file for the PowerExchange Logger.

Tip: PowerExchange provides an example pwxccl.cfg file in the PowerExchange installation directory. Copy this file to another directory and customize the copy. This practice preserves the customized file if you upgrade PowerExchange.

The following example is a customized pwxccl.cfg file:

DBID=ORACOLL1

DB_TYPE=ORA CAPT_IMAGE=BA CAPTURE_NODE_UID=oracapt CAPTURE_NODE_PWD=oracapt /* /*The following parameter is required to issue pwxcmd commands to the Logger:

CONDENSENAME=pwxccl_svc /* EXT_CAPT_MASK=pwx/capture/pwxccl CHKPT_BASENAME=pwx/capture/pwxccl.chkpt

CHKPT_NUM=3

COND_CDCT_RET_P=30

COLL_END_LOG=0

CONN_OVR=CAPIUOW1

FILE_FLUSH_VAL=10

FILE_SWITCH_MIN=(-1,0)

FILE_SWITCH_VAL=15

FILE_SWITCH_CRIT=M

NO_DATA_WAIT=1

NO_DATA_WAIT2=840

SIGNALLING=Y

/*SEQUENCE_TOKEN=0000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000

/*RESTART_TOKEN=00000000000000000000000000000000000000000000000000000000000000000

0000000000000000000000000000000000000000000

Key Parameter Descriptions

The following table describes key parameters for the PowerExchange Logger:

Parameter

Description

CAPT_IMAGE

Data image type that the PowerExchange Logger captures to its log files. Enter AI to capture after images only, or enter BA to capture both before and after images of the data.

Informatica recommends that you specify BA so that you have the flexibility to use either AI or BA for extraction and apply processing.

Parameter Description CAPTURE_NODE_EPWD or CAPTURE_NODE_PWD Optional. An encrypted password or clear text

Parameter

Description

CAPTURE_NODE_EPWD or CAPTURE_NODE_PWD

Optional. An encrypted password or clear text password that is associated with the user ID specified in the CAPTURE_NODE_UID parameter. This password, in conjunction with the CAPTURE_NODE_UID value, is used to control PowerExchange access to capture registrations and change data. Do not specify both CAPTURE_NODE_EPWD and CAPTURE_NODE_PWD.

CAPTURE_NODE_UID

Optional. User ID that is used to control access to capture registrations and change data. Enter a database user ID that permits access to Oracle redo logs and Oracle LogMiner.

CHKPT_BASENAME

Required. An existing directory path and a base file name for generated checkpoint files. Checkpoint files store information for properly resuming PowerExchange Logger processing after a warm start. The PowerExchange Logger writes information to the checkpoint files each time a log file switch or shutdown occurs. Maximum length is 256.

Example:

/capture/pwxlogger.chkpt

CHKPT_NUM

Recommended. Number of checkpoint files to use. Enter a value from 2 through 999999. Default is 3.

COLL_END_LOG

Required. PowerExchange Logger operational mode. Enter 0 for continuous mode. After each logging cycle, the PowerExchange Logger waits for the number of minutes specified in the NO_DATA_WAIT parameter before running another logging cycle.

COND_CDCT_RET_P

Recommended. Retention period, in days, for PowerExchange Logger log files and the CDCT records for the log files. Log files older than this period and their corresponding CDCT records are deleted automatically during PowerExchange Logger cleanup processing. Default is 60. Usually, a value from 7 to 30 is satisfactory.

Tip: Set this parameter to minimize the size of the CDCT file while preserving log files with the earliest change data that you might need to access. When you use continuous extraction mode, PowerExchange reads the CDCT file each time the interval specified in the FILEWAIT parameter of the CAPX CAPI_CONNECTION statement elapses. If a CDCT file becomes large, this read activity can increase I/O, system resource use, and latency of change data extraction.

CONDENSENAME

Optional. A name for the command-handling service for a PowerExchange Logger process to which you want to issue pwxcmd commands. Maximum length is 64 characters.

Syntax is:

CONDENSENAME= service_name

This service name must also be specified in a SVCNODE statement of the dbmover.cfg file on the machine where the PowerExchange Logger runs.

CONN_OVR

Recommended. Name of the override UOWC CAPI_CONNECTION statement to use for the PowerExchange Logger. If you do not specify CONN_OVR, the PowerExchange Logger uses the default CAPI_CONNECTION if one is specified in dbmover.cfg.

Note: In this scenario, the CONN_OVR statement is included for completeness but is not required because the default CAPI_CONNECTION is used.

DBID

Required. A source identifier, or instance name, that is defined in capture registrations. With DB_TYPE, it defines selection criteria for capture registrations in the CCT file. For Oracle, this value must match the first positional parameter in the ORACLEID statement in dbmover.cfg. This value should also match the ORACOLL value in the ORCL CAPI_CONNECTION statement and the collection ID in the registration group.

DB_TYPE

Required. Source RDBMS type. For Oracle, this value must be ORA.

Parameter Description EXT_CAPT_MASK Required. An existing directory path and a unique prefix to be used

Parameter

Description

EXT_CAPT_MASK

Required. An existing directory path and a unique prefix to be used for generating the PowerExchange Logger log files. PowerExchange considers any file that matches this path and prefix to be a PowerExchange Logger log file. Maximum length is 256 characters.

Example:

/capture/pwxlog

Warning: Do not use the same EXT_CAPT_MASK value for multiple PowerExchange Logger processes. Otherwise, a PowerExchange Logger process might corrupt log files that are used by another PowerExchange Logger process.

FILE_FLUSH_VAL

Recommended. File flush interval, in seconds, that the PowerExchange Logger waits before writing data to the current log file on disk. This parameter affects the latency of change data extractions that use continuous extraction mode. A file flush must occur before data can be read by extraction sessions. Enter a value from 0 through 86400. Default is -1, which causes the PowerExchange Logger process to not flush data to the current log file. Usually, the -1 value is used only when running extractions in batch extraction mode.

Warning: A value of 0 can degrade PowerExchange Logger and file system performance.

Enter a value this is appropriate for your CDC environment. Values that are too high can increase change extraction latency, and values that are too low can degrade PowerExchange Logger and system performance.

For this scenario, enter a value of 10.

FILE_SWITCH_CRIT

Optional. Units to use for the FILE_SWITCH_MIN and FILE_SWITCH_VAL parameter values. Enter M for minutes or R for records. Default is M. Use R for better control of file size.

FILE_SWITCH_MIN

Optional. File-switch criteria that the PowerExchange Logger uses when it encounters change data for a new source. You can use this parameter to reduce change data latency when running extractions in continuous extraction mode.

Syntax is:

FILE_SWITCH_MIN=( min_val , min_val_ign )

Where:

min_val is the minimum number of FILE_SWITCH_CRIT units that must elapse after the PowerExchange Logger encounters a change record for a source that has no entry in the CDCT file, before a file switch can be performed. Valid values are -1 (which causes PowerExchange to ignore this parameter) through 2147483647.

min_val_ign is the minimum number of FILE_SWITCH_CRIT units that must pass during a PowerExchange Logger cold start before the PowerExchange Logger uses the min_val value. Before the min_val_ign threshold is met, only FILE_SWITCH_VAL controls file switch activity. Valid values are 0 (which causes PowerExchange to use the min_val value) through 2147483647. This value is ignored if the PowerExchange Logger is warm started.

Default is (-1,0)

Warning: A value of (0,0) can result in a large number of file switches when the PowerExchange Logger is cold started and you have registered many source tables for PowerExchange Logger processing.

Parameter Description FILE_SWITCH_VAL Optional. Number of minutes or change records, as determined by

Parameter

Description

FILE_SWITCH_VAL

Optional. Number of minutes or change records, as determined by FILE_SWITCH_CRIT, that must elapse before PowerExchange performs a file switch. If the PowerExchange Logger log

files contain no data when this threshold is reached, the file switch does not occur. Default is

30.

This value affects the size of the log files. Specify a value that results in log files of the appropriate size for your environment.

Tip: When using continuous extraction mode, as in this scenario, set this parameter such that you have larger log files and a smaller CDCT file. When using batch extraction mode, set this parameter to a value that causes file switches to occur within a timeframe that meets your change propagation latency requirements.

NO_DATA_WAIT

Recommended. If you run the PowerExchange Logger in continuous mode, specify the number of minutes that the PowerExchange Logger must wait before starting the next logging cycle. Default is 60. For continuous extraction mode, enter the minimum value of 1 so that the next logging cycle starts shortly after the current one completes.

If the value of FILE_SWITCH_CRIT is M and the value of FILE_SWITCH_VAL is less than the value of NO_DATA_WAIT, the PowerExchange Logger uses the FILE_SWITCH_VAL value instead.

In this scenario, enter 1 to log changes on a near continuous basis.

NO_DATA_WAIT2

Recommended. Number of seconds that PowerExchange waits at the end-of-log for more change data before returning control to the PowerExchange Logger. If this wait period elapses and new change data has not been received, the PowerExchange Logger stops the current logging cycle. Default is 600.

If you set FILE_SWITCH_CRIT to M, for minutes, Informatica recommends that you enter a NO_DATA_WAIT2 value that is 60 seconds less than the FILE_SWITCH_VAL value. In this scenario, this value is 840 seconds.

RESTART_TOKEN and

Optional. Parameters that define a restart point for starting change data processing when a PowerExchange Logger is cold started.

SEQUENCE_TOKEN

If you enter 0s for both parameters, processing starts from the point in the redo logs where the last Oracle catalog write occurred.

If you enter token values other than 0, processing starts at the specific point defined by these token values.

If you do not specify these parameters, processing starts from the current end-of-log position.

Note: These parameters are ignored for a warm start.

For this scenario, leave these parameters commented out.

SIGNALLING

Indicates whether the PowerExchange Logger attempts to take automatic action in the event of certain errors. Default is N.

Enter Y to have the PowerExchange Logger automatically handle certain errors such as memory corruption. After the PowerExchange Logger handles an error, it attempts to shut down in a controlled manner.

For more information about dbmover.cfg parameters, see the PowerExchange Reference Manual.

Step 3. Start the PowerExchange Listener

On the UNIX machine that contains the Oracle source tables, start the PowerExchange Listener.

To start the PowerExchange Listener in background mode and run it continuously, enter the following command from the directory where dtllst resides:

nohup dtllst node_name [config=mydirectory/dbmover.cfg] [license=mydirectory/license.key] &

Where: node_name is the first positional parameter in the LIST ENER statement of your dbmover.cfg

Where:

node_name is the first positional parameter in the LISTENER statement of your dbmover.cfg on the UNIX machine.

config and license are options that are required only if you placed your dbmover.cfg and license.key files in a directory other than the PowerExchange installation directory, as recommended. In this case, mydirectory is the existing directory that contains your files.

For the scenario covered in this article, enter:

nohup dtllst pwxlst config= mydir/dbmover.cfg license= mydir/license.key &

For more information, see the PowerExchange Command Reference.

Step 4. Customize the dbmover.cfg Files on the Windows and PowerCenter Integration Service Machines

You must also customize the dbmover.cfg files on the Windows machine that hosts the PowerExchange Navigator and PowerCenter Client and on the PowerCenter Integration Service machine to add NODE statements that point to the UNIX machine that contains the Oracle source tables. PowerExchange uses these NODE statements to connect to the UNIX machine to read Oracle change data or metadata.

Note: You do not need to define a LISTENER statement in these dbmover.cfg files. The PowerExchange Listener runs only on the Oracle source machine to listen for SQL requests for data or metadata.

dbmover.cfg on the Windows Machine

On the Windows machine, add the following statements:

NODE=(ora_unix1,TCPIP,unix_host01,2480)

ORACLEID=(ORACOL01,orcl01,orcl01.world,orcl01.world)

CMDNODE=(pwxlst,LISTENER,unix_host01,8500)

CMDNODE=(pwxccl_svc,CONDENSE,unix_host01,8501)

The CMDNODE statements are optional. Include them to be able to issue pwxcmd commands from the Windows machine to the PowerExchange Listener and PowerExchange Logger processes that run on the UNIX machine.

For more information about issuing pwxcmd commands and the command syntax, see the PowerExchange Command Reference.

dbmover.cfg on the Integration Service Machine

On the PowerCenter Integration Serve machine, add the following statement:

NODE=(ora_unix1,TCPIP,unix_host01,2480)

Step 5. Create Capture Registrations

From the PowerExchange Navigator, create a registration group and then add a capture registration for each Oracle source table individually. PowerExchange automatically generates a corresponding extraction map when you complete

a registration.

A capture registration defines the columns for which to capture changes, the Condense setting required for the

PowerExchange Logger, and the registration status. An extraction map defines the columns that can be extracted for a

source table.

1. In the PowerExchange Navigator, click Add > Registration Group.

2. On the Add Registration Group page, enter the following information:

Field

Description

Example Value

Name

Enter a descriptive name for the registration group. Maximum length is 16 characters.

ORA01_PAYROLL

Field Description Example Value Location Enter the user-defined node name for the UNIX machine that

Field

Description

Example Value

Location

Enter the user-defined node name for the UNIX machine that contains the Oracle source tables, as specified in a NODE statement of the local dbmover.cfg on the Windows machine. The PowerExchange Navigator uses this information to connect to the UNIX machine.

ora_unix1

Type

Select ORACLE.

ORACLE

User ID

Enter a database user ID that has sufficient privileges to access the Oracle source tables for registration. This value should match the CAPTURE_NODE_UID value in pwxccl.cfg.

oracapt

Password

Enter the database password that is associated with the specified user ID. This value should match the CAPTURE_NODE_PWD or CAPTURE_NODE_EPWD value in pwxccl.cfg.

oracapt

Collection identifier

Enter the name that you specified for the first parameter in the ORACLEID statement of dbmover.cfg. This value should also match the ORACOLL value in the ORCL CAPI_CONNECTION statement and the DBID value in pwxccl.cfg.

ORACOL01

Add Registration

Select this option to have PowerExchange display the Add Capture Registration – Name and Table Filter page so that you can add capture registrations for Oracle source tables.

N/A

Tip: Alternatively, to add the registrations later, open the registration group and click Add > Capture Registration.

3. On the Add Capture Registration – Name and Table Filter page, enter the following information:

Required. In the Name field, enter a descriptive name for the registration in lowercase. This name can be up to eight alphanumeric characters in length and must begin with a letter.

Optional. In the Schema Name and Table Name fields, enter schema name and table name masks to filter the list of tables to register. Use the asterisk (*) anywhere in one of these masks to represent one or more characters.

When you click Next, the Add Capture Registration – Tables and Columns page appears and lists all tables that match your filter criteria.

4. In the Tables list, double-click a table that you want to register.

The table columns appear in the Columns list.

5. Select the columns for which to capture changes. Then click Next.

6. On the Add Capture Registration – Type page, enter the following information:

Field

Description

Type

Select Synchronous.

Status

Select Active to set the registration status to active when it is created.

Condense

Select Part to use the PowerExchange Logger.

Supplemental Log Group Name

Enter a supplemental log group name, or accept the default name, which has the format schema_tablename. A supplemental log group must be defined for each table for which you want PowerExchange to capture Oracle change data.

PowerExchange generates DDL for creating the supplemental log group for the table when you click Finish. You must save this DDL to a file. You can give the file to your Oracle DBA, or have PowerExchange run the DDL at registration completion.

Field Description Execute DDL now Select this option to have PowerExchange run the DDL for

Field

Description

Execute DDL now

Select this option to have PowerExchange run the DDL for creating the supplemental log group when you click Finish.

Do not select this option if you do not have the privileges that are required to create supplement log groups on the Oracle table. Instead, give the file with generated DDL to your Oracle DBA.

7. Click Finish.

The Save ALTER TABLE SQL file dialog box appears.

8. Enter the name of the file to which to save the DDL for creating the supplemental log group, and click Save.

PowerExchange saves the DDL file to the specified directory and writes the capture registration to the CCT file on the UNIX source machine. If you selected Execute DDL now, PowerExchange also runs the DDL. If a supplemental log group already exists for the table, an error occurs.

Tip: For change capture to occur, you must create a supplemental log group for every table that has an active capture registration with Condense set to Part in the registration group. Each supplemental log group must include all of the columns from which PowerExchange is to capture changes. If a supplemental log group with the same name already exists for a table, an error occurs.

For more information, see the PowerExchange Navigator User Guide.

Step 6. Add Change Indicator or Before Image Columns to Extraction Maps (Optional)

In the PowerExchange Navigator, you can edit the extraction maps to add PowerExchange-generated change indicator

(DTL_CI) and before image (DTL_BI) columns.

A DTL_CI column indicates if UPDATEs caused data in the column to change. Based on this information, you can

perform some processing, such as capture data only for the columns for which the indicator is Y. A DTL_BI column

stores the before image of data in a column that was updated. If you do not add DTL_BI columns, only the after image

is captured.

1. In the PowerExchange Navigator, open an extraction map for an Oracle source table.

2. Right-click in the Extraction Definition window, and select Amend Change Indicator/Before Image Extensions.

The Extract Definition - Amend Columns dialog box appears.

3. To add DTL_CI or DTL_BI columns, perform the following actions:

On the Change Indicators tab, select columns in the Available Columns list to which to add a DTL_CI column, and click Add.

On the Before Images tab, select the columns In the Available Columns list to which to add a DTL_BI column, and click Add.

4. Click OK.

The DTL

CI_column_name

and DTL_BI_column_name columns appear in the Extraction Definition window.

Tip: You can also remove columns from an extraction map. Open the extraction map and clear the column check boxes. Changes to the column data are still captured but not extracted.

For more information, see the PowerExchange Navigator User Guide.

Step 7. Perform a Database Row Test of the Extraction Maps In the PowerExchange Navigator,

Step 7. Perform a Database Row Test of the Extraction Maps

In the PowerExchange Navigator, you can perform a database row text on an extraction map to verify that PowerExchange can use it to access PowerExchange Logger log files and capture change data in near real time. This step is recommended.

1. In the PowerExchange Navigator, select an extraction map for an Oracle source table.

2. Click File > Database Row Test.

The Database Row Test dialog box appears.

3. In the DB_Type list, select CAPXRT.

4. In the Application field, enter any value. This value is required but serves no function for a row test.

5. In the Location, User ID, and Password fields, verify that the values match the values that you specified for the related registration group.

6. In the Fetch list, verity that Data is selected.

7. Verify that the SQL Statement box displays a SELECT statement for the correct extraction map.

8. Click Go.

When the row test completes, the Database Row Test window displays the change data retrieved from the PowerExchange Logger log files. If the window is blank, change data might not yet have been written to the log files. A blank window does not necessarily indicate an error.

Tip: After the PowerExchange Logger is running and has logged changes, you can perform a database row test to verify that change data is being logged to the PowerExchange Logger log files. Before running the row test, you must click Advanced and specify the CAPI_CONNECTION statement name, CAPX01, in the CAPI Connection Name field of the CAPXRT Advanced Parameters dialog box to use the continuous extraction connection.

For more information, see the PowerExchange Navigator User Guide.

Step 8. Materialize the Target Tables

You must initially populate the target tables with data from the Oracle source tables to provide a basis for applying changes. You should perform this task shortly before starting a CDC session in PowerCenter.

Before you materialize the targets, stop updates to the source tables.

To materialize the target tables, you can use PowerExchange or another tool. PowerExchange can efficiently move large amounts of data between different platforms in a single operation at a specific point in time. For more information, see the PowerExchange Bulk Data Movement Guide.

Note: Usually, bulk data movement and CDC use separate PowerCenter mappings.

Step 9. Start the PowerExchange Logger

On the UNIX machine with the Oracle source tables, cold start the PowerExchange Logger to begin capturing changes to PowerExchange Logger log files.

To cold start the PowerExchange Logger, enter the following command from the directory where pwxccl resides:

pwxccl

If you store the pwxccl.cfg file in a directory other than the PowerExchange installation directory, as recommended, you must include the “cs” option to point to the file:

pwxccl cs=directory\pwxccl.cfg

After the PowerExchange Logger has been cold started once, you can run it continuously in the background by entering the following command:

nohup pwxccl cs=directory\pwxccl.cfg 2>&1 < /dev/null &

For more information, see the PowerExchange Command Reference . Step 10. Allow Changes to Be

For more information, see the PowerExchange Command Reference.

Step 10. Allow Changes to Be Written to the Source Tables

Allow users to resume writing changes to the Oracle source tables.

The PowerExchange Logger captures the changes to its log files.

Note: When you start the CDC session in PowerCenter, it can begin extracting changes from the first PowerExchange Logger log file, provided that you use null restart tokens.

PowerCenter Configuration Tasks

In PowerCenter, you must import source and target definitions and define a mapping, connection, workflow, and session. PowerExchange works in conjunction with PWXPC and PowerCenter to apply the change data that is in the PowerExchange Logger log files to the target tables.

Tip: Informatica recommends that you use PWXPC instead of PowerExchange ODBC to integrate PowerExchange with PowerCenter. PWXPC provides additional functionality and better CDC restart and performance.

The following steps provide summary information related to CDC. For more information, see the PowerExchange Interfaces for PowerCenter, PowerCenter Designer Guide, and PowerCenter Workflow Basics Guide.

Step 1. Import Extraction Maps for Source Tables

To create an Oracle source table definition in PowerCenter, import the PowerExchange extraction map for the table.

Although PowerExchange can use the PowerExchange Listener to read table metadata directly from the Oracle database, Informatica recommends that you import the extraction map instead. The extraction map provides the additional DTL_ columns that PowerExchange generates, including the DTL_CAPXACTION column with the change type (INSERT, UPDATE, or DELETE). Also, the extraction map includes any DTL_CI and DTL_BI columns that you added for change indicators and before images.

1. Start PowerCenter Designer.

2. In the Source Analyzer, click Sources > Import from PowerExchange.

3. In the Import from PowerExchange dialog box, enter the following information:

Field

Description

Location

Enter the name that you specified as the first parameter in the LISTENER statement of the dbmover.cfg file on the UNIX machine where the Oracle source tables reside.

User Name

Enter the user name for the Oracle database.

Password

Enter the password associated with the user name.

Source Type

Select ORACLE.

CDC Datamaps

Select this check box in order to list extraction maps in the Select Datamaps box.

Schema

Optionally, enter a schema name mask to filter the extraction maps to be returned.

Permitted wildcards: Use an asterisk (*) to represent one or more characters anywhere in the name, and a question mark (?) for a single character.

Map name

Optionally, enter a map name mask to filter the extraction maps to be returned.

4. Click Connect.

The Select Datamaps box lists the extraction maps that match your criteria.

5. Select one or more extraction maps to import.

6.

Click OK.

6. Click OK . In the Repository Navigator, the Oracle sour ce table definitions appear under

In the Repository Navigator, the Oracle source table definitions appear under ORACLE_location.

Step 2. Import Target Table Definitions

In PowerCenter, import metadata for your target tables.

The method that you use depends on your target type. You might use PowerCenter or PowerExchange. For more information, see the PowerExchange Interfaces for PowerCenter and PowerCenter Designer Guide.

Step 3. Create a Mapping

Create a mapping that includes all of the Oracle source definitions and the target definitions.

In this scenario, you create a single mapping so that PowerExchange can use group source processing. With group source processing, PowerExchange, in conjunction with PWXPC, reads change data for all of the Oracle source tables from the PowerExchange Logger log files in a single pass to enhance throughput and reduce resource consumption. The source tables must be on the same Oracle instance.

Note: If you have a large number of source tables in a mapping, for example more than 75, memory might be insufficient to process all of the sources when the workflow runs. In this case, you might need to create multiple mappings.

To create a mapping, use the Mapping Designer. Add your source and target definitions and link them. For more information, see the PowerCenter Designer Guide.

Tip: Informatica recommends that you use the prefix “m_” for mapping names, for example, m_ora01_to_db2_cdc.

Step 4. Configure an Application Connection for the Oracle Sources

Configure a generic application connection for Oracle sources. For continuous extraction mode, you must use a “PWX Oracle CDC Real Time” connection type.

Note: In this step, you configure a generic connection object so that you can reuse it. You will customize connection attributes when you create a session.

1. In the Workflow Manager, click Connections > Application.

2. In the Select Type box, select PWX Oracle CDC Real Time.

3. Click New.

4. In the Connection Object Definition dialog box, set the following attributes:

Attribute

Value

Name

Enter a name for this connection object.

Code Page

Select the code page for the PowerCenter Integration Service to use to extract source data. In Unicode mode, you must select UTF-8 for Oracle CDC connections.

Location

Enter the node name for the UNIX machine where the PowerExchange Listener that stored the extraction maps for the Oracle source tables resides, as specified in a NODE statement of the dbmover.cfg on the Integration Service machine.

For this scenario, the value is “ora_unix1.”

User Name

Enter the Oracle user name.

For this scenario, the value is “oracapt.”

Password

Enter the password for the user name.

For this scenario, the value is “oracapt.”

Attribute Value Image Type Select AI , even though the CAPT_IMAGE parameter in the PowerExchange

Attribute

Value

Image Type

Select AI, even though the CAPT_IMAGE parameter in the PowerExchange Logger pwxccl.cfg file specifies BA.

In this scenario, both before images and after images are captured but only the after images are extracted and written to targets

Restart Token File Folder

Accept the default value of “$PMRootDir/Restart” as the restart token file directory. For this default only, PWXPC can automatically create the directory.

Number of Runs to Keep Restart Token File

Enter the maximum number of backup copies to keep of the restart token file. Default is 0. You should specify a value other than 0 or 1 option to retain more than a single pair of initialization and termination restart token files.

In this scenario, enter 5.

For more information about all attributes, see PowerExchange Interfaces for PowerCenter.

5. Click OK.

6. Click Close.

Step 5. Create a Workflow and Session

Create a workflow and session task to provide instructions to the PowerCenter Integration Service for extracting and applying change data. As part of defining the session, customize connection object attributes for the session. When you start the workflow, change data that has been captured to the PowerExchange Logger log files begins flowing to the targets.

1. Start the Workflow Manager.

2. In the Workflow Designer, create a workflow.

Tip: Informatica recommends that you use the prefix “wkf_” for workflow names, for example,

wkf_ora01_to_db2_cdc.

3. In the Task Developer, create a session task.

Tip: Informatica recommends that you use the prefix “s_” for session names, for example, s_ora01_to_db2_cdc.

4. Edit the session task to customize session attributes and options.

The following table describes the attributes and options in the Edit Tasks dialog box that are required or recommended for CDC:

Attribute or Option

Tab

Value

Commit Type

Properties

Select Source. This setting is required to be able to reset Commit On End Of File.

Commit On End Of File

Properties

Clear this check box. Otherwise, the Integration Service performs a commit when the session ends, after PWXPC has already committed restart tokens. This situation can cause duplicate data to occur after restart.

Recovery Strategy

Properties

Select Resume from last checkpoint. This setting is required for PWXPC and the Integration Service to properly resume extraction processing and target loads after a session stops.

Attribute or Option Tab Value DTM buffer size Properties Amount of memory allocated to the

Attribute or Option

Tab

Value

DTM buffer size

Properties

Amount of memory allocated to the session from the Data Transformation Manager (DTM) process for reading, writing, and transforming data. By default, the Integration Service determines the DTM buffer size at run time. The minimum is 12 MB. Often, the default amount is too low for CDC processing. Increase this value if necessary. The Integration Service interprets your value as bytes unless you append KB, MB, or GB.

Note: This value is related to the Default buffer block size on the Config Object tab. The minimum number of buffer blocks must be greater than the total number of sources and targets. The number of buffer blocks in a session = DTM buffer size / buffer block size. Default settings create enough buffer blocks for 83 sources and targets. If the session contains more than 83, you might need to increase DTM buffer size or decrease default buffer block size.

For more information, see the PowerCenter Workflow Basics Guide.

Stop on errors

Config Object

Enter 1 to ensure target data and restart token integrity is maintained.

Connections:

Mapping

Select the first Oracle source table in the left pane. Then, under Connections, select Application in the Type field. In the corresponding Value field, select the generic CDC Real Time connection object that you created.

For Oracle source tables other than the first table, select None in the Type field.

Type and Value

Note: In the next step, you customize connection attributes for the first source table and then apply the connection type and attributes to all of the other tables, which have a connection type of None.

5. On the Mapping tab, under Connections, click the pencil icon next to the Value field while the first Oracle source table is still selected in the left pane.

6. In the Connection Object Definition dialog box, customize the Oracle source connection attributes to be used for the session.

The following table describes the connection attributes that you should customize for a PowerExchange CDC session:

Attribute

Value

Application Name

Enter a unique application name. Maximum length is 20 characters.

Warning: If you use the same application name for different CDC sessions, data loss or damage to data integrity might occur.

Restart Token File Name

Enter a unique name for the restart token file.

UOW Count

Enter the number of units of work (UOWs) that PWXPC must process before it flushes the data buffer to commit the change data to the targets. Default is 1. A value of -1 disables this attribute.

Note: If you enter a large number, the RDBMS might hold many locks on tables until the UOW count is reached and commit processing is done.

For the commit to occur, the Minimum Rows Per commit threshold, if specified, must also be met.

You can also control commits that occur at UOW boundaries based on time by specifying the Real-time Flush Latency attribute. You can specify UOW Count or Real-time Flush Latency or both.

Attribute Value Idle Time Enter the number of seconds the PowerExchange Listener remains idle after

Attribute

Value

Idle Time

Enter the number of seconds the PowerExchange Listener remains idle after reaching the end of the change log, as indicated by the message PWX-09967, before returning an end-of- file (EOF). Default is -1, which causes an EOF to not be returned and the session to run continuously. A value of 0 causes an EOF to be returned at the end of log and the session to end successfully.

Real-time Flush Latency

Enter the number of milliseconds that must pass before PWXPC flushes the data buffer to commit the change data to the targets. When the real-time latency period expires, PWXPC continues to read the changes in the current UOW until the end of that UOW is reached. Then, PWXPC flushes the data buffer to commit the change data to the targets. Valid values are 0 to 86400. If you specify a value from 1 through 1999 or accept the default of 0, PWXPC uses 2000 milliseconds (or 2 seconds). A value of -1 disables this attribute.

For the commit to occur, the Minimum Rows Per commit threshold, if specified, must also be met.

You can also control commits that occur at UOW boundaries based on number of UOWs by specifying the UOW Count attribute. You can specify UOW Count or Real-time Flush Latency or both.

Maximum Rows Per commit

Enter the maximum number of change records that PWXPC must process before it can flush the data buffer to commit the change data to the targets. If necessary, PWXPC continues to process change records across UOW boundaries until the maximum rows value is met. PWXPC does not wait for a UOW boundary to commit the change data. Default is 0, which disables this attribute.

For the commit to occur, the Minimum Rows Per commit threshold, if specified, must also be met.

Tip: Usually, you set this attribute only if you have very large UOWs.

Minimum Rows Per commit

Enter the minimum number of change records that PowerExchange must read from the change stream before it can pass any commit record to PWXPC. Before reaching this minimum, PowerExchange passes only the change records, without any commit records, to PWXPC. Default is 0, which disables this attribute.

Tip: This attribute is useful if you have a large number of small UOWs and want a consistent flow of same-sized UOWs.

CAPI Connection Name Override

Enter the name of the CAPX CAPI_CONNECTION statement that you defined in the dbmover.cfg on the UNIX machine with the Oracle source tables.

In this scenario, the value is “CAPX01.”

For more information about Oracle connection attributes, see the PowerExchange Interfaces for PowerCenter guide.

Tip: When you are done and return to the Edit Tasks dialog box, right-click the Application field and select Apply Connection Attributes > To all Instances to apply the connection object attributes to the other Oracle source tables.

7. On the Mapping tab, select the first target table in the left pane and customize attributes.

The attributes that you set depend on your target type. You should at least set the following attributes:

For the Target load type attribute, select Normal.

For the Table Name Prefix attribute, enter the schema or owner name of the target table. Apply this attribute to all instances.

8. Link the Start and session tasks.

9. Save the workflow.

For more information about creating sessions and workflows, see the PowerCenter Workflow Basics Guide.

Step 6. Configure the Restart Token File The restart token file provides restart tokens for

Step 6. Configure the Restart Token File

The restart token file provides restart tokens for specifying the point in the change stream from which to start new CDC sessions. You can create a restart token file that sets specific restart tokens for each Oracle source table or that generates restart tokens that represent the current end of the change stream. Alternatively, you can let PWXPC create

a

restart token file that contains null restart tokens.

In

this scenario, let PWXPC create a restart token file that contains null restart tokens. With the null restart tokens,

change extraction processing will begin with the first PowerExchange Logger log file.

Important: Review the restart and recovery information in the PowerExchange Interfaces for PowerCenter guide. You must understand basic concepts about PowerExchange CDC restart and recovery to prevent change data loss and to preserve target data integrity.

During session initialization, PWXPC uses the name specified in the Restart Token File Name attribute to create an empty restart token file, if one does not exist. The restart token file name is one of the following values, in order of precedence: the Application Name value in the connection attributes, the workflow name, or the Restart Token File Name value in the connection attributes. By default, the workflow name is used. However, the workflow name might not result in a unique restart token file name. The restart token file name must be unique for each CDC session. Otherwise, session failures and potential data loss might occur. To ensure a unique name, verify that you entered an application name value in the source connection attributes.

PWXPC creates the restart token file in the directory that is specified in the Restart Token File Folder attribute of the source CDC connection attributes. If this attribute contains the default value of $PMRootDir/Restart, PWXPC also automatically creates this directory, if it does not exist.

During change data extraction processing, PWXPC updates restart tokens and stores the updated token values in the PM_REC_STATE table in the target database. You can use the restart token file to override the restart tokens in the PM_REC_STATE table, if necessary, for a warm start.

Step 7. Cold Start the CDC Workflow

Cold start the workflow to begin moving captured change data from the PowerExchange Logger log files to the target tables. When you perform a cold start, PWXPC reads the restart tokens from the restart token file only.

In Workflow Manager, right-click the workflow in the Respository Navigator and select Cold Start Workflow.

The CDC session starts. How long it runs depends on the Idle Time setting in the connection attributes. If you accepted the default value of -1, the session runs continuously until it is stopped or interrupted.

For more information about cold starts, warm starts, and recovery processing, see the PowerExchange Interfaces for PowerCenter publication.

Additional Information

For more information about PowerExchange CDC for Oracle, see the following resources:

PowerExchange CDC Guide for Linux, UNIX, and Windows: For configuration of the PowerExchange Logger and of CDC for Oracle and other data sources on Linux, UNIX, or Windows.

PowerExchange Interfaces for PowerCenter: For PWXPC information and PowerExchange CDC attributes and options in PowerCenter.

PowerExchange Reference Manual: For descriptions of all dbmover.cfg parameters, pwxcmd configuration, and PowerExchange security configuration.

How-To article: “Configuring PowerExchange 8.6.1 Oracle LogMiner CDC Parameters Based on Environment Type”

Key Knowledge Base (KB) articles:

- KB 108325: “Knowledge Link: Working with PowerExchange Oracle CDC sessions”

- KB 115883 : “FAQ: Where should PowerExchange CDC for Oracle components run?” You can

- KB 115883: “FAQ: Where should PowerExchange CDC for Oracle components run?”

You can access these publications and KB articles from my.informatica.com. New articles and KBs on Oracle CDC are added on a continuing basis. Search the Knowledge Base for additional articles and KBs periodically.

Author

Virginia Pfeifle Principal Technical Writer