Oracle RAC
Ahmed Saad
Oracle RAC
Real
Application
Clusters
Downtime
Oracle RAC
Unplanned Downtime
Software failures Hardware failures Human errors Disasters
Operating system CPU Operator error Fire
Database Memory User error Flood
Middleware Power supply DBA Earthquake
Application Bus System admin Power failure
Network Disk Sabotage Bombing
Tape
Controllers
Network
Power
Oracle RAC
Planned Downtime
Routine operations Periodic maintenance New deployments
Backups Storage maintenance HW upgrade
Performance mng Initialization parameters OS upgrades
Security mng Software patches DB upgrades
Batches Schema management MidW upgrades
Operating system App upgrades
Middleware Net upgrades
Network
Oracle RAC
What is Cluster ?
Group of servers acting as single system
Requires
-hardware
-software
Traditional use
-availability
-read-only Apps.
Oracle RAC
Oracle RAC
Server Availability Challenge
Server 1
Instance ‘A’
Server 1
Instance ‘A’
Database ‘A’
Oracle RAC
Clusters without RAC
Server 1 Server 2
Instance ‘A’
Database
Removes Server as SINGLE point of failure
Oracle RAC
Clusters without ‘Cloud’ Failover
Server 1 Server 2
Instance ‘A’
Database
Restart single instance on Server 2
Oracle RAC
Real Application Clusters
Server 1 Server 2
Instance ‘A’ Instance ‘B’
Database
SERVER failure - your database remains available
Oracle RAC
RAC vs. ‘Cold’ Failover?
Failover Operation RAC ‘Cold’
Reconfigure Group Membership 15 sec 0 sec
Reconfigure Distributed Locks 5 sec 0 sec
Failover Disk Volumes 0 sec Up to 20 min
Restart Oracle 0 sec Up to 5 min
Recover Oracle 20 sec 20 sec
Warm Buffer Cache 0 sec 10 + min
Total Failover Time < 60 sec > 35 min
Oracle RAC
Sharing Data and Memory
Data
A-Z
Works with ALL applications
Oracle RAC
Before Consolidation
Availability reliant on passive HW
No inherent scalability
Server HW dedicated to application
ERP DW Web CRM
Oracle RAC
Consolidation with RAC
Complete availability…unlimited scalability
Server HW shared between applications
ERP Web
DW CRM
Oracle RAC
Sources and the possibilities of servers
1-Load Balance
distribute the users to database servers equally.
2-Fail Over
In the case of giving a long quarry to a specific server and server panned
For any reason , don’t cancel the quarry but resume it on another server on
The RAC.
3-Parallel Processing
In the case of giving a complex query dividing it on more than one CPU.
Thank You