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

ORACLE_CAPTURE_TYPE Statement

ORACLE_CAPTURE_TYPE Statement

The ORACLE_CAPTURE_TYPE statement specifies which Oracle CDC solution is in use for a PowerExchange installation: PowerExchange Express CDC for Oracle or PowerExchange Oracle CDC with LogMiner.
The ORACLE_CAPTURE_TYPE value must be consistent with the type of Oracle CAPI_CONNECTION statement that is defined on the system that initiates the connection to the Oracle system for change capture.
To ensure consistent behavior, define the ORACLE_CAPTURE_TYPE statement on all systems that are involved in Oracle CDC processing, including the system where the CAPI_CONNECTION statements are defined.
Linux, UNIX, and Windows
Oracle
No
ORACLE_CAPTURE_TYPE={D|L}
  • D
    . PowerExchange uses Express CDC for Oracle and ORAD CAPI_CONNECTION statements.
  • L
    . PowerExchange uses Oracle CDC with LogMiner and ORCL CAPI_CONNECTION statements.
No default value is available.
  • PowerExchange Express CDC for Oracle handles all character columns as variable length columns, whereas PowerExchange Oracle CDC with LogMiner handles character columns as fixed length or variable length columns. This behavioral difference affects PowerExchange column-level processing and the view of the CDC extraction map that is imported into PowerCenter. As a result, 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 or ORCL CAPI_CONNECTION statements are defined, the CAPI_CONNECTION type implicitly defines the CDC type, and the ORACLE_CAPTURE_TYPE statement is optional. However, if other systems are involved in CDC processing, for example, because you run a separate PowerExchange Listener or use offload processing, you must define the ORACLE_CAPTURE_TYPE statement in the dbmover.cfg file on each system to explicitly define the CDC type.
  • You can use only one type of Oracle CAPI_CONNECTION in a dbmover.cfg file. The ORACLE_CAPTURE_TYPE value must be consistent with this CAPI_CONNECTION type. Otherwise, PowerExchange issues an error message and ends abnormally. The following settings are consistent:
    • If you use ORAD CAPI_CONNECTION statements, set ORACLE_CAPTURE_TYPE to D.
    • If you use ORCL CAPI_CONNECTION statements, set ORACLE_CAPTURE_TYPE to L.