Professional Documents
Culture Documents
Oracle RAC On SAP Environment
Oracle RAC On SAP Environment
Oracle RAC On SAP Environment
Instanc Database
e
Shared Nothing Architecture
Database
Instance
1
Table A
Database
Instance
2
Table B
Database
Instance
3
Table C
Shared Disk Architecture
Database
Instance
1
Table A
Database
Instance Table B
2
Table C
Database
Instance
3
RAC Architecure
High Speed Interconnect
Database
Instance
1
Table A
Database
Instance Table B
2
Table C
Cache
Fusion
Oracle9i RAC
Scalability
RAC Scalability
In the past, clustered databases (OPS)
scaled well for specific types of applications:
– Data Warehouse
– Parallel-enabled OLTP
RAC with Cache Fusion delivers transparent
scalability to all types of applications
(including SAP applications)
RAC Scalability and SAP
In the past, the only way to scale the
database server was to replace a small
system by a larger system (“scale up”)
Oracle9i RAC provides an other option:
add more small systems (“scale out”)
Benefits:
– Protection of existing investments
– Less new investments
mySAP.com Scalability
10.000
8.000
6.000
4.000
2.000
0
1 node 2 nodes 4 nodes
Phase 1: Scalability
1 node 100 SD 35,364
2 nodes 200 SD 70,320 1.99
3 nodes 300 SD 103,482 2.93
4 nodes 400 SD 133,840 3.78
350%
300%
250%
200%
Total Throughput
150% Throughput/Node
100%
50%
0%
100 200 300 400 400
Users Users Users Users Users
1 Node 2 Nodes 3 Nodes 4 Nodes 3 Nodes
Oracle9i RAC
& SAP’s MCOD
MCOD
SAP requires more and more databases for
their different modules.
The SAP modules in a mySAP.com landscape
are not independent, e.g. SAP SD, SAP CRM
and BW interact and share data.
To guarantee the required consistency within
all these databases, SAP has developed
MCOD (“Multiple Components in One
Database”)
Typical mySAP.com Landscape
SAP R/3 Oracle
Instance Instance
1 1
SAP BW Oracle
Instance Instance
1 4
mySAP.com and MCOD
SAP R/3
Instance
1
SAP R/3
Instance
2
Oracle
SAP CRM Instance
Instance 1
3
SAP BW Oracle
Instance Instance
4 2
mySAP.com, MCOD & RAC
SAP R/3 Oracle
Instance Instance
1 1
SAP BW Oracle
Instance Instance
1 4
mySAP.com, MCOD & RAC
With Oracle 9i RAC, nodes can be optimally
customized for dedicated workloads
(e.g. CRM, HR, SD, Retail, etc.).
With Oracle 9i RAC, OLTP, BW and
batch-centric modules can be fine tuned
without affecting each other.
Only running all related SAP modules in
one database guarantees the consistency,
especially for backups.
Oracle9i RAC
& Low-Cost
Technologies
Blades
Up to 600 CPUs
per 19“ rack
Decreased space
requirements: up to 7 times less
space compared to classic servers
Decreased power requirements:
up to 5 times less power consumption
Decreased cooling requirements:
up to 5 times less cooling
Decreased price per CPU: up to 20 times less $/CPU
compared to a classic 32-way server
Blades: Expected Savings
Company60%
3 of data center space (19,000m2 vs. 48,000m2)
= € 7,000,000
business day.
CRM
~ 50% idle
Grid Computing
Grid to minimize unused resources.
Because different systems have different
resources requirements at different points in
time, free resources can be shared.
With Oracle Real Application Clusters (RAC),
additional database nodes can be added up
on demand.
Example: Remove a database node from the
CRM system and assign it to the Retail
system for POS uploads.
Grid Computing
idle idle
idle Retail
CRM
CRM
Retail
idle idle
idle CRM
Retail
Retail
CRM