Wiki Admin

Capture from Oracle RAC - DSS 6 | Data Source Solutions Documentation

Export as HTML Export as PDF Export as DOCX
Edit

Documentation: Capture from Oracle RAC - DSS 6 | Data Source Solutions Documentation

Capture from Oracle RAC

Data Source Solutions DSS supports capturing changes from Oracle Real Application Clusters (RAC). Capture from Oracle RAC is supported using the Direct Redo Access, or BFILE. Capture using LogMiner capture method is not supported.

Requirements

  • The DSS Agent Listener must be installed and configured on all RAC nodes using the same Port, User/Login, and Password across the cluster.

  • The agent property Agent_Server_Public_Certificate must be the same across all RAC nodes. To achieve this, before creating an Oracle RAC location, you must copy the DSS Agent configuration files (dssagent.user and dssagent.conf available in DSS_CONFIG/etc directory) from the primary RAC node to the rest of the nodes.

  • If the Agent_Server_Public_Certificate across all RAC nodes is not the same, you may encounter the F_JG2194: Remote certificate does not match required certificate error.

    • The dssagent.user file is available only if you have created agent users.
  • The directories DSS_HOME and DSS_CONFIG should exist on both the DSS Hub and DSS Agent machines and do not need to be shared. If DSS_TMP is defined, it should not be shared.
  • The DSS channel only needs one location for the entire RAC cluster. At runtime, a single capture job connects to one node and reads changes from the shared redo archives accessible to all nodes.
  • If you have a firewall configured between the hub and the RAC system, ensure to allow inbound communication from the hub to the Oracle TNS listener port on the SCAN address, and to the DSS Agent Listener on the VIP addresses of all RAC nodes.
  • If the Capture Checkpoint Tuning option is enabled, you must store the checkpoint files on the hub server. This is required because the directory on the remote location where the capture job would otherwise write checkpoints may not be shared accross the nodes inside the RAC cluster. Consequently, it may not be available if the capture job restarts. For more information, see Tuning Capture Checkpoints section.

How DSS Hub Connects to RAC

When capturing from Oracle RAC, the DSS hub connects using its own protocol to an DSS Agent Listener running on the RAC node.

The hub connects to a RAC node in the following sequence:

  1. The hub connects to the Oracle RAC SCAN address on the Oracle TNS listener port (typically 1521).
  2. The SCAN resolves the connection to a specific RAC node.
  3. The hub then connects to that node’s Virtual IP (VIP) address on the DSS Agent Listener port.

DSS UI Configuration

In DSS UI, the connection parameters for the Oracle RAC must be supplied while creating an Oracle location with Oracle RAC in Step 2. Select Agent Connection.