Table of Contents

Search

  1. Preface
  2. Summary of PowerExchange New Features and Changes
  3. PowerExchange Installation and Upgrade
  4. PowerExchange Agent
  5. PowerExchange Client for PowerCenter
  6. PowerExchange Condense
  7. PowerExchange Listener
  8. PowerExchange Logger for Linux, UNIX, and Windows
  9. PowerExchange Navigator
  10. PowerExchange Monitoring and Tuning
  11. PowerExchange Utilities
  12. PowerExchange for Adabas
  13. PowerExchange for CA Datacom
  14. PowerExchange for DB2 for i
  15. PowerExchange for DB2 for Linux, UNIX, and Windows
  16. PowerExchange for DB2 for z/OS
  17. PowerExchange for CA IDMS
  18. PowerExchange for IMS
  19. PowerExchange for Microsoft SQL Server
  20. PowerExchange for MySQL
  21. PowerExchange for Oracle
  22. PowerExchange for PostgreSQL
  23. PowerExchange for VSAM and Flat Files
  24. PowerExchange ODBC

PowerExchange Express CDC for Oracle Configuration File

PowerExchange Express CDC for Oracle Configuration File

PowerExchange 10.4.0 introduces new parameters for the OPTIONS and READER statements in the PowerExchange Express CDC for Oracle configuration file, pwxorad.cfg.
OPTIONS statement
The following new, optional parameter is now available:
SPILL_FILE_PREFIX
New
. A file name prefix that consists of a temporary file path for the spill files. If you want to specify the directory where the spill files reside, specify the fully qualified path to the directory.
Linux or UNIX example:
SPILL_FILE_PREFIX=”/tmp/spillfiles/”
Windows example:
SPILL_FILE_PREFIX=”C:\tmp\spillfiles\xxx”
Default path is the TMP or TMPDIR environment variable value. If TMP or TMPDIR is not defined, the configuration uses the current directory.
READER statement
ARCHIVEDEST
New
. Specifies a list of numbers from 1 to 10, separated by commas. Each number represents the
n
value in an Oracle LOG_ARCHIVE_DEST_
n
initialization parameter. If you create more than one copy of each archive log, this parameter indicates the primary and secondary log destinations from which PowerExchange Express CDC reads archived logs. You can specify up to 10 destinations. The order in which you specify the destinations in the list determines the order in which PowerExchange Express CDC searches for archive logs. PowerExchange Express CDC tries to process the first two valid logs it finds in the specified destinations. If PowerExchange cannot read the first two logs, the process terminates.
PowerExchange Express CDC uses the secondary destination when the primary destination becomes unavailable or when the logs at the primary destination are unreadable, for example, because they have been corrupted or deleted.
For example, the Oracle source database uses the Oracle parameters LOG_ARCHIVE_DEST_1, LOG_ARCHIVE_DEST_2, and LOG_ARCHIVE_DEST_3 to create copies of archived logs. If you want PowerExchange Express CDC to use LOG_ARCHIVE_DEST_2 as the primary destination and ARCHIVE_DEST_3 as the secondary destination, set ARCHIVEDEST=(2,3).
Specifying one value for the ARCHIVEDEST parameter limits the resilience of the Express CDC log reader because the log reader then processes logs from only one archive log destination.
If you do not specify ARCHIVEDEST, PowerExchange Express CDC queries v$archived_log for valid logs, favoring file system logs over ASM logs for performance reasons. Specifying ARCHIVEDEST provides more control over this process. For example, if the database writes archive logs to ASM and the file system, and you do not have access to the file system logs, you can use ARCHIVEDEST to specify the ASM location only.
This parameter replaces the ARCHIVEDEST1 and ARCHIVEDEST2 parameters. ARCHIVEDEST1 and ARCHIVEDEST2 are deprecated.
For more information, see the "Express CDC for Oracle" chapter in the
PowerExchange CDC Guide for Linux, UNIX, and Windows
.

0 COMMENTS

We’d like to hear from you!