Table of Contents


  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

CAPT_PATH Statement

CAPT_PATH Statement

The CAPT_PATH statement specifies the path to a directory on a Linux, UNIX, or Windows system that contains the control files for CDC.
Linux, UNIX, and Windows
Db2, Microsoft SQL Server, MySQL, Oracle, and PostgreSQL sources on Linux, UNIX, or Windows, and if you use remote logging, data sources on IBM i (i5/OS) or z/OS
Yes for CDC sources on Linux, UNIX, and Windows
For the
variable, enter the path to the local directory that contains the following control files for CDC:
  • CCT file, which contains capture registrations.
  • CDEP file, which contains application names for any PowerCenter extractions that use ODBC connections.
  • CDCT file, which contains information about PowerExchange Logger for Linux, UNIX, and Windows log files.
This directory can be one that you created specifically for these files or another directory.
Informatica recommends that you use a unique directory name to separate these CDC objects from the PowerExchange code. This practice makes migrating to a another PowerExchange version easier.
Default is the PowerExchange installation directory.
  • PowerExchange C-ISAM control files, such as the CCT, CDEP, and CDCT files, must be stored on local disk. Do not locate these files in SAN or NAS storage.
  • To provide a path to the directory that contains extraction maps, use the CAPT_XTRA statement.


We’d like to hear from you!