Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.5
  • All Products

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

Back Next

Configuring PowerExchange for Express CDC

Configuring PowerExchange for Express CDC

You must complete several tasks to configure PowerExchange for Express CDC for Oracle and to start change capture.
The specific tasks depend on your configuration. The following task flow assumes that you use the PowerExchange Logger, as recommended.
Make sure that the system user ID under which the PowerExchange Express CDC for Oracle capture process runs has the authority to read the Oracle redo logs. Otherwise, the Express CDC log reader cannot directly read the log files, and the CDC session ends with error message PWX-36140.
  1. Configure the dbmover configuration file on the PowerExchange system that initiates the CAPI to capture change data from the Oracle source database.
    Include the following statements:
    • Required. CAPT_PATH and CAPT_XTRA statements.
    • Required. An ORAD CAPI_CONNECTION statement.
    • Required. An ORACLEID statement.
    • Recommended. An ORACLE_CAPTURE_TYPE statement.
    • Recommended. A CAPX CAPI_CONNECTION statement, if you use the PowerExchange Logger and continuous extraction mode.
    • Optional. An ORACLE_UNHANDLED_NUMASCHAR statement to treat NUMBER columns that have a precision greater than 28 or an undefined length as variable length strings and to treat FLOAT columns that have a precision greater than 15 as variable length strings. This behavior can prevent data loss. You must define this statement on the PowerExchange instance where the registration and extraction map information will be defined, before you create the registrations.
    If you run PowerExchange Express CDC and the PowerExchange Listener, consumer API (CAPI), and PowerExchange Logger on the Oracle system, as in Configuration 1, define the CAPX CAPI_CONNECTION and ORACLE_UNHANDLED_NUMASCHAR statements in this dbmover configuration file.
    If you capture change data from an Oracle Data Guard physical standby database, configure the ORACLEID and ORAD CAPI_CONNECTION in the DBMOVER configuration file on the standby system to point to the source instance on the primary system. If the primary system is a RAC environment, point to a single member in the RAC.
  2. Customize the PowerExchange Express CDC for Oracle configuration file, which has the default file name of pwxorad.cfg, on the change capture system.
    If you capture changes from RAC members, include the RAC statement.
    If you use ASM, include the ASM parameters in the READER statement.
    If the Oracle source database is in an Amazon RDS for Oracle environoment, specify RDS=Y in the DATABASE statement..
    To include rowid values in change records for tables that do not have Oracle row movement enabled, include the OPTIONS ROWID=Y statement. Provided that you use version 9.1.2 or later of the PowerExchange Navigator, PowerExchange can write rowid values to the generated DTL__CAPXROWID column in captured change records.
  3. Customize the PowerExchange Logger configuration file, which has the default file name of pwxccl.cfg, on the system where the PowerExchange Logger runs.
  4. Configure a dbmover configuration file on any other PowerExchange instance in the CDC environment that needs to read capture registrations or extraction maps from disk.
    If you use Configuration 2, include the following statements in the dbmover configuration file on the system with the separate PowerExchange Listener:
    • Required. An ORACLE_CAPTURE_TYPE statement.
    • Required. An ORACLEID statement.
    • Recommended. A CAPX CAPI_CONNECTION statement if you run the PowerExchange Logger on the change capture system and use continuous extraction mode.
    • Optional. An ORACLE_UNHANDLED_NUMASCHAR statement if you need PowerExchange to treat NUMBER columns that have a precision greater than 28 or an undefined length as variable length strings and to treat FLOAT columns that have a precision greater than 15 as variable length strings.
  5. In the PowerExchange Navigator, create a registration group and a capture registration for each Oracle source table.
    Make sure that you enter values in the following fields:
    • In the
      Type
       list, select
      ORACLE
      .
    • In the
      Collection ID
       box, enter a user-defined name for the Oracle instance. This value must match the collection ID in the ORACLEID statement in the dbmover.cfg file that is on the node specified in the
      Location
       field. If you use the PowerExchange Logger, this value also must match the DBID value in the PowerExchange Logger configuration file.
    • Set the
      Status
       option to
      Active
      .
    • In the
      Condense
       list, select
      Part
      . Informatica recommends this setting even if you do not use the PowerExchange Logger, because it allows you to implement the PowerExchange Logger later, if necessary, without changing the registration.
    • In the
      Supplement Log Group Name
       box, enter a name for the Oracle supplemental log group.
    If you want PowerExchange to run the DDL that it generates to create the supplemental log group at registration completion, select
    Execute DDL Now
    . However, Informatica recommends that you save the generated DDL to a file and give it to your Oracle DBA instead. The DBA can then use this DDL when migrating PowerExchange from a test or QA environment to the production environment.
    After you click
    Finish
    , PowerExchange generates corresponding extraction maps.
    For more information about registrations and extraction maps, see the
    PowerExchange Navigator User Guide
    .
  6. Perform a database row test on each extraction map.
    For more information, see the
    PowerExchange Navigator User Guide
    .
  7. Configure a restart point.
    For more information, see Creating Restart Tokens for Extractions.
  8. Materialize the target.
  9. Start the PowerExchange Logger.
Next, configure PowerCenter CDC sessions. You can use batch extraction mode, continuous extraction mode, or real-time extraction mode. For more information, see
PowerExchange Interfaces for PowerCenter
.
Back to Top
0 COMMENTS
Back Next
We’d like to hear from you!