RAC Basic
Shared Storage
Public IP
private IP
Virtual IP
* Cache Fusionis disk less cache coherence mechanism that provides copies of data blocks directly from one instance’s memory cache to another instance. All block transfers happen through the private interconnects between the rac nodes. * In a Single Node database, an instance looking for data block first checks in Local cache, if block is not in local cache then goes to disk to pull block from disk to cache and return block to client. * In RAC Database there is remote cache so instances should look not only in local cache but on remote cache. If cache is available in local cache then it should return data block from local cache; if data block is not in local cache, instead of going to disk it should first go to remote cache (remote instance) to check if block is available in local cache (via interconnect) This is because accessing a data block from a remote cache is faster than accessing it from disk.
All datafiles
control files
SPFIles
redo log files
OCR and Voting DISK
Services
Cache fusion Model is dependent on three services
* Global Resource Directory (GRD)
* Global Cache Service (GCS)
* Global En-queue Service (GES)
GRD (Global Resource Directory) resides in the SGA of every node.
* It contains information about the current status of all shared resources like blocks and locks.
* It’s maintained by GES (Global Enqueue Services) and GCS (Global Cache Services).
* GCS is the main controlling process that implements Cache Fusion.
* GCS tracks the location and the status (mode and role) of the data blocks.
* GCS also tracks the access privileges of various instances.
* It is also responsible for block transfers between the instances.
* Upon a request from an instance, GCS organises the block shipping and appropriate lock mode conversions.
* The Global Cache Service is implemented by various background processes such as the Global Cache Service Processes (LMSn) and Global Enqueue Service Daemon (LMD).
* The Global Enqueue Service (GES) manages or tracks the status of all the Oracle enqueuing mechanisms. This involves all non Cache fusion intra-instance operations.
* GES performs concurrency control on dictionary cache locks, library cache locks, and the transactions. GES does this operation for resources that are accessed by more than one instance.
CRS manages the availability of the RAC database by monitoring the status of the Oracle database instances and listeners running on each node in the cluster.
It also manages the startup and shutdown of these instances and listeners, and can initiate automatic failover of instances in the event of a node failure.
It's a clusterware component responsible for managing cluster membership and inter-node communication, helping ensure high availability and coordination between nodes in the cluster.
It also monitors the health of each node in the cluster and handles node failures by reconfiguring the cluster and redistributing workload as needed.
Post a Comment