Professional Documents
Culture Documents
Oracle RAC: Overview of Real Application Clustering Features and Functionality
Oracle RAC: Overview of Real Application Clustering Features and Functionality
Overview
What is RAC? Cache Fusion Failover and Load-balancing Transparent Application Failover (TAF) Other RAC Features
Multiple instances of Oracle running on up to 8 nodes Multiple instances share a single physical database All instances can simultaneously execute transactions against the single database Caches are synchronized using Oracles Global Cache Management technology (Cache Fusion)
Oracle FailSafe on Windows OPS (Oracle Parallel Server) on multiple platforms OPS to RAC: 7.3 OPS 8i OPS 9i RAC 10g RAC
The clustering mechanism used to be more dependent on the Operating System. With 10g RAC, clustered database is built into Oracle
Full Cache Fusion Enhanced coordination of cache management and distributed lock manager (DLM) Lock simplification and automation Global Cache Service coordinates local buffer cache and remote block transfers Enhanced IPC Resource configuration simplification and automation Improved cluster aware tools Enhanced DBCA Oracle Enterprise Manager and Grid Control Integration Enhancements
Server
Server
Server
Server
Database
One set of data All nodes in the cluster see the same set of data All nodes have access Any node can update the data
Increased Manageability
Single Oracle Database Single management console Single system image for the database integrated with the cluster
Cluster-wide monitoring and diagnostics Oracle Enterprise Manager Integration (9i) Oracle DBConsole and Grid Control Integration (10g)
Shared
Disk access Resources that manage data All instances have common data & controls files Each node has its own dedicated:
Not Shared
System memory Operating system Database instance Application software Log files and Rollback segments
Load-balancing Failover
Node 1
Node 2
Node 3
Node 4
Database
Node 1
Client
Database
Node 2
Listeners choose least busy node when request comes in from client
Node 1
Client
Database
Node 2
Load-Balancing
Users
Node 1
Node 2
Node 3
Node 4
Database
Failover
If a node in the shared disk cluster fails, the system dynamically redistributes the workload among the surviving cluster nodes. RAC checks to detect node and network failures. A disk-based heartbeat mechanism uses the control file to monitor node membership and the cluster interconnect is regularly checked to determine correct operation. Reduced time to recovery with concurrent resource configuration and instance (cache) recovery Enhanced failover reliability in 10g with the use of Virtual IP addresses (VIPs)
Failover
Users
X
Server
Server
Server
Server
Database
Masks failures to end users; they dont need to log back into the system Applications and users are transparently reconnected to another node Applications and queries continue uninterrupted
Full Cache Fusion Enhanced coordination of cache management and distributed lock manager (DLM) Lock simplification and automation Global Cache Service coordinates local buffer cache and remote block transfers Enhanced IPC (InterProcess Communication) Resource configuration simplification and automation
No third-party clusterware software required Application workloads can be managed through named services Enterprise Manager manages RAC instances as a single image Fast recovery between the database and mid-tier applications Reduced message traffic, memory usage, and other resources
Performance Improvements
Is a major feature of RAC starting with 9i The underlying technology that enables RAC Protocol that allows instances to combine their data caches into a shared global cache Allows any node to get the most up-to-date data information from the cache of any other node in the cluster without having to access the disk drives again. Improved performance with 10g
Data from disk is read into memory on a node Data is updated on that node Data hasnt been written to disk yet.
Node A
Node B
ABC Data
Node A
Node B
ABC Data
ABC Data
Node B
ABC Data
Node B
ABC Data
Node B
Node B
XYZ Data
Node B
XYZ Data
ABC Data
Data is transferred immediately via the interconnect Shared cache minimizes slow I/O
Users
Server
Server
Server
Server
Database
to move the location of the resource masters for a database file to the instance where block operations are most frequently occurring. This optimizes Ability to move the ownership of a resource between instances of Real Application Clusters. Dynamic resource remastering is used to implement resource affinity for increased performance.
Review
What does cache fusion avoid that was mandatory in previous versions of Oracle Parallel Server? Which Oracle process is most important in managing user session failover? If the purpose of the interconnect is NOT to serve as a heartbeat, where is the heartbeat?
Summary
New Features Shared Everything Clustering Cache Fusion RAC Clustering failover & load-balancing