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
  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. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

ORACLEID Statement

ORACLEID Statement

The ORACLEID statement specifies the Oracle source instance, database, and connection information for CDC.
Linux, UNIX, and Windows
Oracle CDC sources
CAPI_CONNECTION - ORCL and CAPI_CONNECTION - ORAD
Yes, for PowerExchange Oracle CDC with LogMiner and PowerExchange Express CDC for Oracle
ORACLEID=(
collection_id
,
oracle_db
[,
source_connect_string
]   [,
capture_connect_string
] [,
fifth_positional_parameter
] [,USEDBNAME] )
collection_id
Required. User-defined identifier for this ORACLEID statement. This value must match the ORACOLL parameter value in the ORCL CAPI_CONNECTION or ORAD CAPI_CONNECTION statement, the collection ID in the registration group defined for the source tables, and the DBID value in the PowerExchange Logger pwxccl configuration file.
Maximum length is eight characters.
oracle_db
Required. Name of the Oracle database that contains the source tables that are registered for change data capture. If you use PowerExchange Express CDC for Oracle to capture change data from a pluggable database (PDB) in an Oracle multitenant environment, this value is the name of the database that contains the PDB.
source_connect_string
Optional. Oracle connection string, defined in TNS, that is used to connect to the Oracle database that contains the source tables. This connection string must be defined in the Oracle Client tnsnames.ora file on the system with the source database.
For PowerExchange Oracle CDC with LogMiner and PowerExchange Express CDC for Oracle, the source connection string is used only for PowerExchange Navigator access to the Oracle source database. Enter this parameter in the dbmover configuration file on the machine from which the PowerExchange Listener retrieves data for PowerExchange Navigator requests. If you plan to run a database row test on extraction maps for the source tables, also specify the
capture_connect_string
parameter.
The source connection string is not used to transfer change data.
If this value is null and the Oracle source is
not
a PDB in a multitenant environment, the value of the ORACLE_SID environment variable is used by default. If you use PowerExchange Express CDC for Oracle to capture change data from a PDBs, you must enter a value in this parameter.
capture_connect_string
Optional. Oracle connection string, defined in TNS, that the PowerExchange Logger uses to connect to the Oracle database with the source tables for PowerExchange Oracle CDC with LogMiner or PowerExchange Express CDC with LogMiner. This connection string must be specified in the Oracle Client tnsnames.ora file that is used for connection to the Oracle source database. If you use PowerExchange Express CDC to capture change data from a PDB in an Oracle multitenant environment, specify the name of the PDB service entry in the tnsnames.ora file.
If this value is null and the Oracle source is
not
a PDB in a multitenant environment, the value of the ORACLE_SID environment variable is used by default.
If this value is null and the Oracle source is a PDB, PowerExchange cannot capture change data for the source. If you use PowerExchange Express CDC for Oracle to capture change data from PDBs, you must enter a value in this parameter.
Also, for PowerExchange Oracle CDC with LogMiner or Express CDC for LogMiner, if you have multiple Oracle databases and capture changes from a database other than the default database, you must specify both the
source_connect_string
and
capture_connect_string
parameters.
If possible, bypass the use of SQL*Net to improve PowerExchange Logger performance, even if the PowerExchange Logger is running on the same machine as the Oracle source database. Set the following environment variables, whenever possible, to enable connection to the appropriate Oracle database without using the
capture_connect_string
parameter and SQL*Net:
  • ORACLE_HOME
  • ORACLE_SID
  • PATH
  • On Linux or UNIX, one of the following:
    • LD_LIBRARY_PATH
    • LIBPATH
    • SHLIB_PATH
fifth_positional_parameter
Not used. Add a comma as a placeholder if you specify the USEDBNAME positional parameter, for example:
ORACLEID=(
collection_id
,
oracle_db
,
src_connect_string
,
capture_connect_string
,,USEDBNAME)
USEDBNAME
Optional. Specify this parameter only under all of the following conditions:
  • You upgrade to PowerExchange 9.1.0 or later from an earlier release.
  • You use Oracle 11
    g
    or later.
  • You run the following SQL query on the V$DATABASE view and the query returns different values for the NAME and DB_UNIQUE_DATABASE fields, including values that vary in case only such as ORAABC1 and oraabc1:
    select name, db_unique_name from v$database;
In this situation, the USEDBNAME parameter can prevent potential restart errors that are caused by the difference in the NAME and DB_UNIQUE_DATABASE values.
Alternatively, you can specify the DB_UNIQUE_NAME value in the second positional parameter,
oracle_db
.
  • PowerExchange requires an ORACLEID statement for each Oracle database for which you want to capture and extract change data. You can define a maximum of 20 ORACLEID statements in a single dbmover configuration file.
  • Define the ORACLEID statement in the dbmover configuration file on the system where the PowerExchange Logger runs, or if you plan to perform Oracle CDC without the PowerExchange Logger, on the system where your PowerExchange extractions run.