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.4.0 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

Reference Manual

Reference Manual

Back Next

ORACLE_CAPTURE_TYPE Statement

ORACLE_CAPTURE_TYPE Statement

The ORACLE_CAPTURE_TYPE statement specifies that the CDC type to use for the PowerExchange installation. The only available type is PowerExchange Express CDC for Oracle.
The ORACLE_CAPTURE_TYPE value must be consistent with the ORAD type of CAPI_CONNECTION statement that is defined on the system that initiates the connection to the Oracle system for change capture.
Linux, UNIX, and Windows
Oracle
No 
ORACLE_CAPTURE_TYPE=D
  • D
    . PowerExchange uses Express CDC for Oracle and ORAD CAPI_CONNECTION statements.
No default value is available. The only valid value is D.
  • PowerExchange Express CDC for Oracle handles all character columns as variable length columns. This behavioral difference affects PowerExchange column-level processing and the view of the CDC extraction map that is imported into PowerCenter. All systems that are involved in Oracle change capture processing must be aware of the Oracle CDC type that is in use
    On the PowerExchange system where the ORAD CAPI_CONNECTION statements are defined, the CAPI_CONNECTION type implicitly defines the CDC type, and the ORACLE_CAPTURE_TYPE statement is optional. If other systems are involved in CDC processing, for example, because you run a separate PowerExchange Listener or use offload processing, you can define the ORACLE_CAPTURE_TYPE statement in the dbmover.cfg file on each system.
  • For the ORAD CAPI_CONNECTION statement, the ORACLE_CAPTURE_TYPE value must be D. Otherwise, PowerExchange issues an error message and ends abnormally.
0 COMMENTS
We’d like to hear from you!