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 Supports Oracle 12c Multitenant Pluggable Databases

PowerExchange Express CDC for Oracle Supports Oracle 12
c
Multitenant Pluggable Databases

Effective in PowerExchange 10.0, PowerExchange Express CDC for Oracle can capture change data from a pluggable database (PDB) in an Oracle 12
c
multitenant container database (CDB).
PowerExchange Express CDC can capture change data from only a single PDB at a time. If you want to capture change data for another PDB in the same CDB, you must configure a separate CDC environment.
To configure change data capture from a PDB, you must perform the following tasks:
  • Verify that the CDB is running in ARCHIVELOG mode.
  • Enable minimal global supplemental logging for either the PDB or CDB.
  • Add a PDB entry that includes the PDB service name to the tnsnames.ora file. For example:
    PDB1234= (DESCRIPTION= (ADDRESS=(PROTOCOL=TCP)(HOST=host1)(PORT=1521)) (CONNECT_DATA= (SERVER=DEDICATED) (SERVICE_NAME=pdb1234.informatica.com)))
  • If you log in to CDB$ROOT as a user with the DBA role, execute the following SQL statement to switch the session to the source PDB:
    ALTER SESSON SET CONTAINER=
    pdb_name
  • After you define an Oracle user for CDC, such as "ORACAPTL1," grant the following privileges to this user:
    GRANT CREATE SESSION TO “ORACAPTL1”; GRANT SELECT on “PUBLIC”.”V$PDBS” TO “ORACAPTL1”;
  • In the dbmover.cfg configuration file on the system where change capture occurs, configure the ORACLEID statement to point to the name of the database that contains the PDB and the name of the PDB service entry in the tnsnames.ora file. For example:
    ORACLEID=(PDB1234,ORADBNAME,
    tns_connection
    ,PDB1234)
    In this example statement:
    • The first positional parameter,
      collection_id
      , identifies the ORACLEID statement. In this case, it is also the PDB name. This parameter cannot be empty.
    • The second positional parameter,
      oracle_db
      , is the name of the Oracle database that contains the PDB. This parameter cannot be empty.
    • The third positional parameter,
      source_connect_string
      , is an Oracle connection string defined in the Oracle tnsnames.ora file for connection to the database. For PDBs, this parameter cannot be empty.
    • The fourth positional parameter,
      capture_connect_string
      , is the name of the PDB service entry in the Oracle tnsnames.ora file. For PDBs, this parameter cannot be empty.
If you move or clone the PDB for which PowerExchange Express CDC is capturing change data to another CDB, the PowerExchange Logger for Linux, UNIX, and Windows connection to the Oracle database is lost. You must cold start the PowerExchange Logger to prevent loss of change data.
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!