Skip to main content

GC 2-Way and 3-Way Buffer Cache in Oracle RAC

GC 2-Way and 3-Way Buffer Cache in Oracle RAC

Oracle RAC uses a shared cache architecture where each instance has its own buffer cache. To maintain consistency, Oracle uses the Global Cache Service (GCS) to coordinate access across nodes using mechanisms known as GC 2-Way and GC 3-Way buffer transfers.

🔁 What is Global Cache in RAC?

Global Cache ensures block consistency across instances in a RAC cluster. Instead of fetching from disk, Oracle RAC uses Cache Fusion to transfer blocks over the interconnect between nodes, reducing I/O and improving performance.

⚡ GC 2-Way Buffer Transfer

A GC 2-Way transfer happens when the block is shipped directly from the current holder to the requesting instance in just two messages.

  • 🔁 Request: Instance A → Instance B
  • 📦 Response: Instance B → Instance A

This is fast and efficient because it avoids additional overhead.

📘 Example

Instance A runs a DML and needs a block held by Instance B in exclusive mode. B sends it directly to A, completing the transfer in two messages.

⚠️ GC 3-Way Buffer Transfer

A GC 3-Way transfer involves three messages. This happens when the GCS must coordinate the block transfer, such as during ownership conflict or heavy workload.

  • 🔍 Request: Instance A → GCS
  • 🔄 GCS → Block Holder (Instance B)
  • 📦 Block: B → A (or via GCS)

This is slower due to more messaging and resource coordination.

📘 Example

Instance A requests a block. The GCS finds Instance B has it but is busy or the block needs role conversion. The block is transferred after GCS coordination, resulting in a 3-message round trip.

🆚 GC 2-Way vs GC 3-Way Summary

🔍 Feature GC 2-Way GC 3-Way
🔁 Messages 2 3+
⚙️ Transfer Type Direct from holder Indirect via GCS
⚡ Performance Faster Slower
📦 Block Path Instance B → A Via GCS or redirected

📊 Monitoring GC Transfers

Use this SQL to inspect GC performance:

SELECT name, value FROM v$sysstat WHERE name LIKE 'gc%';

Focus on metrics like:

  • gc current block 2-way
  • gc current block 3-way
  • gc cr block receive time

🔧 Tuning Tips

  • 🎯 Use service affinity to minimize cross-instance block requests
  • 📶 Ensure low latency interconnect (Infiniband/10G+)
  • 🔥 Avoid "hot blocks" shared by multiple instances

Understanding GC internals is crucial for every Oracle RAC DBA to ensure cluster performance and stability. 🚀

Comments

Popular posts from this blog

🚀 Automating Oracle Database Patching with Ansible: A Complete Guide

Oracle database patching has long been the bane of DBAs everywhere. It's a critical task that requires precision, expertise, and often results in extended maintenance windows. What if I told you that you could automate this entire process, reducing both risk and downtime while ensuring consistency across your Oracle estate? 💡 In this comprehensive guide, I'll walk you through a production-ready Ansible playbook that completely automates Oracle patch application using OPatch. Whether you're managing a single Oracle instance or hundreds of databases across your enterprise, this solution will transform your patch management strategy! 🎯 🔥 The Challenge: Why Oracle Patching is Complex Before diving into the solution, let's understand why Oracle patching is so challenging: 🔗 Multiple dependencies : OPatch versions, Oracle Home configurations, running processes ⚠️ Risk of corruption : Incorrect patch application can render databases unusable ⏰ Downtime requirements : Da...

🚀 DB BOT: Real-Time Oracle & GoldenGate Monitoring in Slack

In today's fast-paced DevOps environment, quick access to database metrics is essential. This blog will walk you through creating a Slack bot that provides real-time monitoring of Oracle databases and Golden Gate replication. With simple slash commands, your team can check tablespace usage, Flash Recovery Area status, and Golden Gate replication health directly in Slack. Project Overview Our "DB Bot" offers these key capabilities: Monitor tablespace usage across multiple Oracle databases Check Flash Recovery Area (FRA) status on multiple databases View GoldenGate process status across different servers List GoldenGate credential stores Monitor replication lag in GoldenGate Prerequisites Node.js v14+ Python 3.6+ Oracle client libraries (instantclient_21_19) Access to Oracle databases and GoldenGate servers A Slack workspace with permissions to add apps   Project Structure oracle-slack-bot...

Oracle Golden Gate Bi-directional Replication Implementation Guide

Oracle GoldenGate (OGG) is a comprehensive software package for real-time data integration and replication in heterogeneous IT environments. Bi-directional replication enables organizations to maintain synchronized data across multiple data centers, providing high availability, disaster recovery, and load distribution capabilities. This detailed guide provides step-by-step instructions for implementing Oracle GoldenGate bi-directional replication between two Oracle databases. Architecture Overview In this setup, we'll configure: TestDC1 : Primary data center with TestDB1 TestDC2 : Secondary data center with TestDB2 Bi-directional sync : Changes flow in both directions with conflict resolution Step 1: Software Installation ⚠️ SERVER EXECUTION: Perform these steps on BOTH TestDC1 and TestDC2 servers Step 1.1: Download and Prepare Software First, create the necessary directory structure and prepare for installation: # Create directory for the software mkdir /data01/ogg_setup cd /d...