2. Thomas Baus Senior Sales Consultant Oracle/SAP Global Technology Center Mail: thomas.baus@oracle.com Phone:+49 6227 8398-134

3. Oracle9i RAC for SAP Customers

4. Agenda  Driving Forces  Oracle9i RAC Architecture  Oracle9i RAC Scalability  Oracle9i RAC High Availability  Oracle9i RAC and SAP’s MCOD  Oracle9i RAC & Low Cost Technologies  Oracle9i RAC Release Strategy

5. Driving Forces

6.  Increased competition – Customers do not tolerate downtime – Management needs real-time information  System evolution – Growing amount of data – Changing workloads – Increasing complexity of IT landscapes – Increasing interaction between different systems

7. Driving Forces  Economic slowdown – Decreasing earnings – Need to improve margins – Less money available for investments

8. The Problem More IT investmentsLess IT investments Increased Competition System Evolution Economic Slowdown

9. The Solution  Get most out of existing resources – Opimize resource usage – Implement high availability solutions – Minimize administration costs  Protect existing, minimize new investments – Look for modularity and scalability of system components – Look for low cost technologies  Simplify IT landscape (“consolidation”)

10. The Solution  For several years, consolidation was the only strategy to reduce costs.  Modularity, scalability and low cost technologies require distribution.  This means, that we need a new concept of systems design: Consolidated and integrated systems should be distributed to cheap and standardized components.

11. Oracle9i RAC Architecture

12. Standard Oracle Architecture Instance Database

13. Shared Nothing Architecture Database Instance 1 Database Instance 2 Database Instance 3 Table A Table B Table C

14. Shared Disk Architecture Database Instance 1 Database Instance 2 Database Instance 3 Table ATable BTable C

15. RAC Architecure Database Instance 1 Database Instance 2 Database Instance 3 Table ATable BTable C Mirrored Disk Subsystem High Speed Interconnect Cache Fusion

16. Oracle9i RAC Scalability

17. 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)

18. 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

19. mySAP.com Scalability PresentationApplicationDatabase

20. mySAP.com Scalability PresentationApplicationDatabase

21. mySAP.com Scalability PresentationApplicationDatabase

22. mySAP.com/RAC Scalability PresentationApplicationDatabase

23. mySAP.com/RAC Scalability PresentationApplicationDatabase

24. mySAP.com/RAC Scalability PresentationApplicationDatabase

25. Parallel SD Benchmark  Oracle9i RAC running on HP (Compaq) Tru64  3-tier system  Finished: December 2001  Certified: June 2002 (2002029, 2002030, 2002031)  Goal: Prove scalability with max. CPU utilization

26. Parallel SD Benchmark Scalability: 1.8

27. Oracle9i RAC High Availability

28. Parallel Workload Study  Oracle9i RAC running on Windows 2000  2-tier systems  Finished April 2002  Not intended for certification  Goal: Prove scalability under conditions as close as possible to real world environments (CPU util. between 33% and 70%)

29. RAC Scalability 100 SAP SD Users + Oracle Instance 1 100 SAP SD Users + Oracle Instance 3 100 SAP SD Users + Oracle Instance 4 100 SAP SD Users + Oracle Instance 2

30. RAC Scalability + High Availability 133 SAP SD Users + Oracle Instance 1 134 SAP SD Users + Oracle Instance 3 100 SAP SD Users + Oracle Instance 4 133 SAP SD Users + Oracle Instance 2

31. Parallel Workload Study Users Throughput (Dsteps/Hour) Scaling 100 SD 35,364 Configuration 1 node 200 SD 70,320 1.99 2 nodes 300 SD 103,482 2.93 3 nodes 400 SD 133,840 3.78 4 nodes Phase 1: Scalability 400 SD 124,812 3 nodes Phase 2: High Availability

32. Parallel Workload Study

33. Oracle9i RAC & SAP’s MCOD

34. 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”)

35. Typical mySAP.com Landscape Oracle Instance 1 Oracle Instance 2 Oracle Instance 3 Oracle Instance 4 SAP R/3 Instance 1 SAP R/3 Instance 2 SAP CRM Instance 1 SAP BW Instance 1

36. mySAP.com and MCOD Oracle Instance 1 SAP R/3 Instance 1 SAP R/3 Instance 2 SAP CRM Instance 3 Oracle Instance 2 SAP BW Instance 4

37. mySAP.com, MCOD & RAC Oracle Instance 1 Oracle Instance 2 Oracle Instance 3 Oracle Instance 4 SAP R/3 Instance 1 SAP R/3 Instance 2 SAP CRM Instance 1 SAP BW Instance 1

38. 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.

39. Oracle9i RAC & Low-Cost Technologies

40. 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

41. Blades: Expected Savings Company 1 $500,000 to $1,000,000 per rack Company 2 60% per server, 90% of data center space (15m 2 vs. 156m 2 ) Company 3 60% of data center space (19,000m 2 vs. 48,000m 2 ) = € 7,000,000 Company 4 reduction from $54 to $31 per user

42. Blades & Oracle9i RAC  Blades have a high potential to cut cost  Oracle runs on blades  800 SD users with Oracle on a 2-way, Intel PIII, 800MHz, blade  With Oracle9i Real Application Clusters (RAC), blades can be clustered as instances of one database because of Oracle‘s shared disk architecture  Only Oracle 9i RAC can run on more than one blade with SAP

43. Grid Computing  Without Grid, systems have dedicated tasks.  Each system has to be sized for worst case peak load of his task.  Under normal conditions, systems run over hours with low load.  Potential CPU power is wasted, because unused.

44. Grid Computing Example 1: Retail  Within the normal business hours the system is under low load.  After business hours POS upload starts, new batch calculation starts, data collection and transfer to the BW systems starts. The system is now, but only a view hours, under the load it had to been sized for. Retail idle Retail idle ~ 50% idle

45. Grid Computing Example 2: CRM  Within the normal business hours, the system is under load it was sized for.  After business hours it runs with low load till the next business day. CRM idle ~ 50% idle

46. 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.

47. Grid Computing ~ 50% idle~ 25% idle Retail idle Retail idle CRM idle CRM idle Retail CRM idle CRM Retail

48. Centralized Storage  Storage Area Network (SAN) or Network- attached Storage (NAS)  Separates storage from the traditional server and puts it on special appliances  Provides a common storage pool that is highly scalable and flexible

49. Centralized Storage  Centralized storage matches the capabilities offered by blades and RAC: – Small computing units without local disk – Shared disk storage (RAC)  No Oracle Cluster File System required, if NAS is used

50. Linux  What is it? – Open-source operating system. – Supported by many hardware vendors. – Supported by many software vendors. – Increasing market share as server operating system.

51. Linux  Why can it save money? – Low-cost operating system. – Low-cost third-party software. – Homogeneous SW environment for heterogeneous HW (e.g. Linux on Blades or nearly any Intel based HW). – Low-cost training. Source: IDC White Paper “Maximizing the Business Value of Enterprise Database Applications on a Linux Platform” (2002)

52. Linux  Today Linux scales very well in SMP systems up to 4 CPU’s.  Linux on 8 CPU’s is still competitive, but between 4way and 8way systems the price per CPU increases significantly.  For SMP systems with more than 8 CPU’s, classic Unix systems are the best choice.  With Oracle Real Application Clusters (RAC), small 4 or 8way systems can be clustered to cross the today’s Linux limitations.  Commodity, inexpensive 4way Intel boxes, clustered with Oracle 9i RAC, help to reduce TCO.

53. Linux  Oracle has a strong commitment to support Linux.  Oracle 9i RAC for SAP certification on Linux has already been started by HP, Dell, Fujitsu-Siemens.  Oracle 9i RAC for SAP will be certified for RedHat and Suse.

54. Release Strategy

55.  SAP has – agreed to adopt, distribute and support Oracle9i RAC (May 2002) – certified a series of SD Parallel benchmarks using Oracle9i RAC on HP (Compaq) Tru64 Unix (May 2002).  RAC will be generally available for customers on HP (Compaq) Tru64 Unix within 6 months.

56. Release Strategy BenchmarkPilot Customer(s)AvailabilityTrue64 LinuxBenchmarkPilot Customer(s)Availability BenchmarkPilot Customer(s)AvailabilityAIX HP-UX Solaris BenchmarkPilot Customer(s)Avail BenchmarkPilot Customer(s)Avail BenchmarkPilot Customer(s)AvailWindows

57. A Q & Q U E S T I O N S A N S W E R S