1 / 23

Multiple Components in One Database (MCOD)

Learn about Multiple Components in One Database (MCOD), a new feature in mySAP.com installations allowing multiple components to run independently in a single database. This setup offers benefits such as flexibility, separate upgrades, and enhanced scalability. By consolidating SAP systems, administrative tasks are simplified, backup solutions are streamlined, and system landscape maintenance becomes more efficient.

sgarfield
Download Presentation

Multiple Components in One Database (MCOD)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multiple Components in One Database(MCOD) Consolidation of SAP systems with Multiple Components in One Database Dr. Georg LeffersSAP AG

  2. è è è è Agenda Introducing Multiple Components in One Database (MCOD) Simplifying the mySAP.com System Landscape using MCOD Availability & Outlook Technical Realization for the Oracle database

  3. è è è è Agenda Introducing Multiple Components in One Database (MCOD) Simplifying the mySAP.com System Landscape using MCOD Availability & Outlook Technical Realization for the Oracle database

  4. Multiple Components in One Database • Multiple Components in One Database (MCOD) is a new feature in the installation process for mySAP.com components • It provides the possibility to install several components independently in one single database SAP CRM SAP BW RDBMS SAP R/3 Enterprise SAP R/3 Enterprise

  5. Technical Realization • Each mySAP.com component connects the database with one single database user. This user is independent of the user logged on to the SAP system itself. The default database user was SAPR3 ( 4.6). • Databases support schema. Tables with the same name can exist independent in different schema with different contents. • Using a one to one relation between the database user and the database schema, each mySAP.com component uses its own schema by accessing the database with a unique dedicated database user. SAP R/3 SID = ER4 SAP CRM SID = CM1 T100 (SAPER4) T100 (SAPCM1) DB-User: SAPER4 DB-User: SAPCM1

  6. è è è è Agenda Introducing Multiple Components in One Database (MCOD) Simplifying the mySAP.com System Landscape using MCOD Availability & Outlook Technical Realization for the Oracle database

  7. SAP R/3 SAP BW RDBMS RDBMS RDBMS RDBMS RDBMS SAP CRM SAP SEM SAP EBP Highly Flexible IT Landscape Today Situation: N Systems, N Databases Benefits • Flexibility through components • Separate upgrades possible • Different operating systems and databases • Highest scalability achievable Administrative challenges • Maintaining different operating systems, databases • Complicated high availability solutions • Synchronized backup & restore

  8. SAP R/3 SAP BW SAP CRM SAP SEM RDBMS SAP EBP Installable on one physical server Simplification Of The System Landscape With MCOD Situation: N Systems, 1 Database Administrative opportunity • Multiple independent and different software solutions are located in one database • One logical and physical database instance • Point in time recovery of semantically related systems e.g. R/3 and CRM possible • Migration of existing systems is possible • All systems use the same OS/DB release

  9. business data SAP R/3 SAP CRM RDBMS X business data Independence Of Single Systems • (De)Installation of individual components • Upgrade of individual components • Data exchange on application level • Integrity of business data • No special coding for MCOD installations • No locking conflicts on database tables

  10. Installable on one physical server RDBMS RDBMS Separate OLTP And OLAP Systems Performance considerations • Some database systems require a different parameterization depending on the transactional behavior of the application. • For these database systems a separated installation of OLTP and OLAP systems is necessary. Database systems supporting a combined installation* • DB2 for IBM zSeries • DB2 for IBM iSeries • DB2/UDB for Window and Unix • Microsoft SQL Server • SAP DB OLTP OLAP SAP R/3 SAP BW SAP CRM SAP SEM SAP EBP * For details see the MCOD homepage

  11. multiple servers, one databases multiple servers, multiple databases one server, one database one server, multiple databases Various Deployment Options • Full range of scalability & flexibility • Decide how many different systems will reside in one physical database • Additive sizing approach

  12. Benefits detail: Estimated savings 10% of disk space Disk For example, tapes, tape drives, disk systems 30% of hardware backup costs Backup administration or high-availability concepts 40% of operating costs Reduced Maintenance & Operating Costs Only need to administer one database • Similar effort compared to maintain one component on one database

  13. Sizing & Administration • Sizing & Administration of an MCOD installation • The total sizing of an MCOD installation can be achieved by an additive sizing approach of the appropriate values of the single systemsExample: Combined installation of System1 and System2 using MCOD • Decide which systems to combine to achieve a maximum of savings in administration and system handling while keeping the flexibility of the complete installation

  14. System Recommendations • Combination of systems with semantically related data like R/3 and CRM. • Combination of systems of the same type e.g. combination of development systems or combination of production systems. • The combination of production and non production systems is not supported. Development System 1 ... Devevelopment System N Test System 1... Test System N Production System 1 ... Production System N

  15. è è è è Agenda Introducing Multiple Components in One Database (MCOD) Simplifying the mySAP.com System Landscape using MCOD Availability & Outlook Technical Realization for the Oracle database

  16. More Information What will be supported • MCOD is available on all OS/DB platforms supported by SAP • General Availability since 1st of July, 2002 • For the future all upcoming mySAP.com components are planned to be enabled for an MCOD installation • Information about the current available components is updated regularly and can be found at the service market place under the quicklink MCOD More information • http://service.sap.com/mcod

  17. Available mySAP.com Components

  18. Outlook Backup and recovery of single systems within an MCOD installation • Planned for SAP WebAS 6.30 introducing a backup and recovery on tablespace level in SAPDBA Transport of single systems • Implementation projects at customer side on the basis of transportable tablespaces Oracle RAC with MCOD • Improved scaling capabilities by distributing the single database nodes • Breakdown of the OLTP / OLAP division with an individual parameterization for the single database nodes • First tests planned for Q2/2003 in combination with blade servers

  19. è è è è Agenda Introducing Multiple Components in One Database (MCOD) Simplifying the mySAP.com System Landscape using MCOD Availability & Outlook Technical Realization for the Oracle database

  20. Oracle / SAPSYSTEMNAME 1 : C11 SAPSYSTEMNAME 2 : C12 oracle DB – User: sapc11 DB – User: sapc12 <DB_SID> sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata<n> PSAPC11 PSAPC1146D PSAPC11USR PSAPC12 PSAPROLL PSAPTEMP PSAPC1246D PSAPSYSTEM PSAPC12USR Oracle - Database <DB_SID>

  21. Implementation on Oracle • Technical Implementation • One database will contain the data of all systems • Each SAP system will create its own database schema/database user sap<SID> • Each SAP system will create its own set of tablespaces • The new tablespace layout is described in SAP note 490365

  22. Conclusion Main advantages are Full flexibility and independence of the installed components System spanning data consistency Simplified administration, backup and recovery Reduced maintenance and operating costs Additive sizing approach With “Multiple Components in One Database” SAP offers a powerful option to install several mySAP components in one physical database

  23. More Information Visit the MCOD homepage:http://service.sap.com/mcod Visit the SAP NetWeaver homepage:http://service.sap.com/netweaver

More Related