Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange CDC Introduction
  3. Part 2: PowerExchange CDC Components
  4. Part 3: PowerExchange CDC Data Sources
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for Linux, UNIX, and Windows

CDC Guide for Linux, UNIX, and Windows

Example of Remote Logging from an Oracle CDC with LogMiner Data Source

Example of Remote Logging from an Oracle CDC with LogMiner Data 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. The system where the PowerExchange Logger runs is separate from the PowerCenter Integration Service system where you run CDC sessions.
You need the PowerExchange Logger to capture change data from registered tables in the Oracle instance PRODORA on the source system and then log that data to its log files on the remote UNIX system. To do so, you must customize a PowerExchange Logger configuration file on the remote system and dbmover configuration files on both systems. Also, for the PowerCenter CDC sessions to extract change data from the PowerExchange Logger log files, you must add NODE statements for the source and PowerExchange Logger systems to the dbmover configuration file on the Integration Service system and configure some PWXPC connection attributes.
First install PowerExchange on all three systems. You must run a PowerExchange Listener on the source system and on the PowerExchange Logger system. A PowerExchange Listener is not required on the PowerCenter Integration Service system.
  1. On the Oracle source system, ensure that the dbmover configuration file includes the following statements:
    LISTENER=(unix1,TCPIP,2480) /* UOW Cleanser CAPI_CONNECTION=(NAME=UOWCORA,TYPE=(UOWC,CAPINAME=CAPIORA,RSTRADV=600)) /* Oracle Connection CAPI_CONNECTION=(NAME=CAPIORA,TYPE=(ORCL,catint=120,ORACOLL=PRODORA)) ORACLEID=(PRODORA,ORAINST2,ORAINST2,ORAINST2)
    The value of the first positional parameter,
    collection_id
    , in the ORACLEID statement must match the value of the DBID parameter in the PowerExchange Logger configuration file on the PowerCenter Integration Service system.
  2. On the PowerExchange Logger system with the log files, ensure that the dbmover configuration file includes the following statements:
    /* /* dbmover /* LISTENER=(unix2,TCPIP,2480) NODE=(unix1,TCPIP,prodora,2480) ... LOGPATH=/pwx/logs/oracond CAPT_XTRA=/pwx/capture/oracond/camaps CAPT_PATH=/pwx/capture/oracond /* /* Source-specific CAPI Connection CAPI_CONNECTION=(NAME=UOWCORA,TYPE=(UOWC,CAPINAME=CAPIORA,RSTRADV=600)) CAPI_CONNECTION=(NAME=CAPIORA,TYPE=(ORCL,CATINT=120,ORACOLL=PRODORA)) /* /* CAPX CAPI Connection for continuous extraction CAPI_CONNECTION=(NAME=CAPXORA,TYPE=(CAPX,DFLTINST=PRODORA,FILEWAIT=60,RSTRADV=600))
  3. On the PowerExchange Logger system with the log files, customize the PowerExchange Logger configuration file, pwxccl.cfg. For this example, include the following statements:
    /* /* pwxccl /* DBID=PRODORA DB_TYPE=ORA CONN_OVR=UOWCORA CAPTURE_NODE=unix1 CAPTURE_NODE_UID=orauser CAPTURE_NODE_EPWD=
    encrypted_password
    PROMPT=Y EXT_CAPT_MASK=/capture/condenseO COND_CDCT_RET_P=60 LOGGER_DELETES_EXPIRED_CDCT_RECORDS=Y COLL_END_LOG=0 NO_DATA_WAIT=0 NO_DATA_WAIT2=10 FILE_SWITCH_VAL=20 FILE_SWITCH_CRIT=M CAPT_IMAGE=BA
    The CAPTURE_NODE parameter points to the source system node where the PowerExchange Listener processes capture requests.
  4. Start the PowerExchange Listener and PowerExchange Logger on the remote system. Verify that the PowerExchange Listener is also running on the source system.
  5. On the PowerCenter Integration Service system, add the following NODE statements to 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.
    This example uses the following NODE statements in the dbmover file on the PowerCenter Integration Service system:
    NODE=(unix1,TCPIP,unix1,2480) NODE=(unix2,TCPIP,unix2,2480)
  6. Create a PowerCenter mapping, session, and workflow.
  7. 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.
  8. Cold start the CDC session.
    The session begins extracting change data from the PowerExchange Logger log files.

0 COMMENTS

We’d like to hear from you!