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.3
  • 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

Oracle Data Guard Physical Standby Databases or Far Sync Instances as Sources

Oracle Data Guard Physical Standby Databases or Far Sync Instances as Sources

PowerExchange Express CDC for Oracle can capture change data from Oracle Data Guard physical standby databases and far sync instances. PowerExchange monitors the standby and archived redo logs on the instance.
To use Oracle Data Guard far sync instances as sources, contact Informatica Global Customer Support.
Informatica recommends that you install and run PowerExchange on the machine with the physical standby database or far sync instance as reading log data across a network can be slower. A PowerExchange installation is not required on the primary database machine.
To configure change capture from a physical standby database or far sync instance, you must complete the following configuration tasks:
  • In the dbmover.cfg configuration file on the system where change capture runs, configure the following parameters in the ORACLEID statement:
    • The third positional parameter
      source_connect_string
       to point to the primary database in order to create registrations.
    • Do not specify the fourth positional parameter
      capture_connect_string
      . This information is provided by the DATABASE or STANDBY statement in the pwxorad.cfg file.
  • In the PowerExchange Navigator client, create a registration group for the instance and capture registrations for the Oracle source tables on the primary system from which the changes originate.
  • In the Express CDC pwxorad.cfg configuration file on the system where change capture runs, define the following statements:
    • A RAC statement if the primary database is a RAC database. This value is the number of active threads for the primary database.
    • A DATABASE statement that provides connection information to allow access to the Oracle catalog.
      If the source is a physical standby database open for read-only, provide the connection information for the standby instance.
      If the source is a far sync instance or a physical standby database in mount state, provide the connection information for the primary instance.
    • A STANDBY statement that provides connection information to the far sync instance or the physical standby database in mount state. The user that you specify for the STANDBY connection must have SYSDBA authority to access the fixed views and to monitor the progress of log transport from the primary in a database that is not open.
  • In the PowerExchange Logger pwxccl.cfg configuration file on the system where change capture runs, configure the DBID parameter to specify the Oracle collection ID that is defined in the registration group for the instance that contains registered source tables on the primary system.
In mount mode, use a password file for user authentication. To avoid granting permanent SYSDBA authority to the user on primary grant of SYSDBA to the user, copy the primary password file to the physical standby or far sync instance and then immediately revoke the authority after the copy operation. You must repeat this process whenever you refresh the password file.
0 COMMENTS
We’d like to hear from you!