Table of Contents

Search

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

PowerExchange Express CDC for Oracle Configuration File

PowerExchange Express CDC for Oracle Configuration File

PowerExchange 10.5.5 includes the following new or changed parameters in the PowerExchange Express CDC for Oracle configuration file, pwxorad.cfg.
In the
ASMSTAGING
statement, you can enter the following optional parameters:
BFILEDIR=
directory
New.
If you are using BFILE reads of redo log data from staging files and want to run multiple PowerExchange Logger instances against the same database, you can specify a directory object name to use for dynamically created directory objects. This name overrides the default directory name of PWXSTAGINGDIR. For the directory to be created dynamically, you must have the CREATE ANY DIRECTORY privilege.
On RAC systems, if you granted permissions for the directory object to be created dynamically, when the directory object is created, the member number is appended to the directory name to avoid contention between the reader threads. Therefore, you can create multiple directory objects. For example, in a three-node RAC system, three directory objects are created: ARCHIVELOG_DIR1, ARCHIVELOG_DIR2, and ARCHIVELOG_DIR3.
LOCALDIR="/localmountpoint/directory|BFILE"
Changed
. If you want to use BFILE reads of redo log information stored in ASM staging files on the server, specify "BFILE" . By default, the Express CDC reader uses the PWXSTAGINGDIR directory object to locate the staging files. To override the PWXSTAGINGDIR directory object for BFILE reads, specify the BFILEDIR parameter.
In the
READER
statement, you can enter the following optional parameter:
ASM_CONNECTION_THREADS =
number_of_threads
New.
Enter the number of threads that a PowerExchange Express CDC reader can use to establish multiple connections to Oracle ASM to read data in parallel. This parallelism helps improve the read rate. In an Oracle ASM RAC environment, the reader for each RAC node can use the specified number of connection threads. Default is 3.
In the
OPTIONS
statement, you can enter the following optional parameters:
LOB_MAX_SIZE=
kilobytes
New.
The maximum size, in kilobytes, of LOB data that can be captured for a column selected for change capture. Default is 8192.
SUPPORT_LOB_OPERATIONS ={
Y
|N}
New.
Controls whether LOB data stored in a row (inline) is captured for columns that are selected for change capture. Default is Y.
SUPPORT_LOB_OUT_OF_ROW={Y|
N
}
New.
Controls whether LOB data that is stored either in a row (inline) or outside of a row (out-of-line) is captured for columns selected for change capture. Default is N. This parameter is ignored when SUPPORT_LOB_OPERATIONS=N.
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!