Why Do I Use the SCAN IP Address to Connect to an Oracle RAC Cluster?
If the source Oracle database is an RAC cluster, you are advised to use SCAN IP+SERVICE_NAMES to create a task because SCAN IP has stronger fault tolerance, better load balancing capability, and faster synchronization.
- If the SCAN IP address is used, ensure that the SCAN IP address can communicate with all virtual IP addresses of the source database. Otherwise, the connection test cannot be passed.
- If SCAN IP is not used, the virtual IP address of a node can be used. If other nodes are abnormal, the synchronization process is not affected.
For details about the SCAN IP address, see the documents on the Oracle official website.
Real-Time Synchronization FAQs
- Can DRS Sync Tables of Different Schemas to the Same Schema?
- Can Online DDL Tools Be Used for Real-time Synchronization?
- Does DRS Support Bidirectional Real-time Synchronization?
- Why Do I Use the SCAN IP Address to Connect to an Oracle RAC Cluster?
- How Do I Check Supplemental Logging of the Source Oracle Database?
- Which Specifications Should I Select for My DRS Task to Synchronize Data to GaussDB(DWS)?
- Suggestions on Synchronizing Data to GaussDB(DWS)
- Character Set Compatibility Between Oracle and GaussDB
- Garbled Characters or Synchronization Failure Due to Incompatible Character Sets
- How Do I Specify the Start Point for DRS Incremental Synchronization?
- What Are Syntax Differences Between MySQL or MariaDB Versions?
- Configuring Remote Connection to a GaussDB Database
- Connection and Port Description for Incremental Synchronization from GaussDB
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore