Multiple Components in One Database - archive.sap.com · SAP AG2002, Title of Presentation, Speaker Name 2 Technical Setup The following slides show for all databases supported by

Multiple Componentsin One Database-Technical Implementation on Different Databases

Dr. Georg LeffersSAP AG

SAP AG 2002, Title of Presentation, Speaker Name 2

Technical Setup

The following slides show for all databases supported by SAP the

technical setup of an MCOD installation containing two systems.

The systems are named C11 and C12.

The part of the database that is used by system C11 is marked in

BLUE, parts of the system C12 are marked in RED, and commonly

used parts of the database are marked in YELLOW.

For more information about the actual supported mySAP.com

components and details about the possible combination of

components visit the quicklink MCOD on the SAP Service

Marketplace.

http://service.sap.com/mcodhttp://service.sap.com/mcodhttp://service.sap.com/mcodhttp://service.sap.com/mcod


DB2 UDB for z/OS and OS/390

DB2 - Database

C11/C12

/

Stogroup1 Stogroup<n> DB2 Catalog

DB2

SAPSYSTEMNAME 1 : C11 SAPSYSTEMNAME 2 : C12

DB – Schema: SAPC11 DB – Schema: SAPC12

C11 C12

C11STD C11BTD

Stogroup<n+1> Stogroup<m>

C12BTDC12STD


Implementation on DB2 UDB for z/OS and OS/390

Technical Implementation:

� One database will contain the data of all systems

� The first system works with the user SAPR3 (R/3 4.6) as databaseschema/ database user, each additional system creates its own database schema/database user SAP<SID>With the SAP Web Application Server 6.10 and higher, every system creates a schema/user SAP<SID>

� For each additional system an own set of Stogroups will be created (SAP will be substituted by <SID>)

� The VCAT identifier differs from system C11 to C12

� All systems will share the DB2 catalog as common resource

� The R/3 specific database administration tools can be configured to work on any system, if they access the database to monitor DB2

� Strong recommendation for using a data sharing system with one data sharing member handling one SAP component


DB2/iSeries

Operation System

Database


R3C11DATA

QSQJRN

R3C11JRN

R3C12DATA

QSQJRN

R3C12JRN


Implementation on DB2/iSeries


� All mySAP components use the single integrated database DB2 UDB

for iSeries

� There is no special implementation for the “Multiple Components in

One Database” solution

� Each SAP system on iSeries stores tables, indexes and views in a

separate library

� A library corresponds to a SQL schema

� Each SAP system has its own database journal

� Additional information is available with SAP note 443925


DB2/UDB Unix & Windows

db2 - Database

C11

/

sapdata1 sapdata2 sapdatat sapdata1

db2

sapdata<n>


DB – User: sapc11 DB – User: sapc12

C11 C12

sapdata2

PSAPDDIC SYSCATSPACE PSAPTEMP C12#DDIC


Implementation on DB2/UDB Unix & Windows



� The first system works with the user sapr3 as database schema/

database user, each additional system creates its own database

schema/database user sap<sid>

With the SAP Web Application Server 6.10 and higher, every system

creates a schema/user sap<sid>

� For each additional system an own set of tablespaces will be created

(PSAP will be substituted by <SID>#)

� All systems will share the tablespaces SYSCATSPACE and

PSAPTEMP

� The R/3 specific database administration tools only works on the first

system (administrative definition of leading system)


/

C11DATA1 C11DATA2 C11LOG<m>

SQL Database C11


DB – User: C11 DB – User: C12

C11 Tables

C12 Tables

log log

C11DATA<n> C11LOG1… …

C12 Tables

C11 Tables

Catalog …

C12 Tables

C11 Tables

Roll, Temp, …

Microsoft SQL Server


Implementation on MS SQL Server



� In the past, all tables were owned by a single DB user dbo

� Now each SAP system will create its own database schema with

database user <SID> which owns all the tables and views


Informix

/SAPSYSTEMNAME 1 : C11 SAPSYSTEMNAME 2 : C12

DB – User: SAPR3 DB – User: SAPR3informix

TMPDBS<j>

LOGDBS /

PHYSDBS /

ROOTDBS *

C11

sapdata

physdev1 physdev<n>…

data1 … data<n>

PSAPBTABPSAPSYSTEM

C12

sapdata

physdev<1> physdev<n>…

data<1> … data<n>

PSAPC12

SYSTEM

PSAPC12

BTAB

Informix

Database

C11

Informix

Database

C12Informix

Database

Server

* Separated

physdev


Implementation on Informix


� One database server for all SAP systems

� Each SAP system will create its own database with own dbspaces

� No additional database/os users, each database will be owned by the

user sapr3


Oracle

/

oracle

<DB_SID>

sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata<n>

Oracle - Database

<DB_SID>



PSAPC11

PSAPC1246D

PSAPC1146D

PSAPSYSTEM

PSAPROLLPSAPC11USR

PSAPC12USR

PSAPTEMP PSAPC12


Implementation on Oracle



� 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


C12 Tables

Roll, Temp …

SAP DB

SAPSYSTEMNAME 1 : C11 SAPSYSTEMNAME 2 : C12/

SAPDB

<DB_SID>

sapdata


SAPDB - Database

<DB_SID>

saplog

diskd001 diskd002 diskd<n> diskl001 diskl<m>

C11 Tables

C12 Tables

Catalog …

log log

C11 Tables C11 Tables

C12 Tables

… …


Implementation on SAP DB


� One database instance will contain the data of all systems

� Each SAP system will create its own database schema with database

user sap<SID> all other resources within the database are shared

(catalog, devspaces,caches,...)

� Tables of the SAP systems and database system tables are spread

across all available data files without a definitive distribution.


Appendix

Installation:

� For mySAP components that are based on SAP Web Application

Server 6.20 and higher the MCOD installation option can directly be

chosen during the installation process.

� For mySAP components that are build on basis 4.6C and the SAP

Web Application Server 6.10, some modifications of the setup scripts

have to be done before starting the installation. These modifications

are described in detail for the different database/operation system

platforms in several SAP notes that can be accessed on the SAP

Service Marketplace.


� No part of this publication may be reproduced or transmitted in any form or for any purpose without the express

permission of SAP AG. The information contained herein may be changed without prior notice.

� Some software products marketed by SAP AG and its distributors contain proprietary software components of other

software vendors.

� Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of

Microsoft Corporation.

� IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®,

OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®,

Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

� ORACLE® is a registered trademark of ORACLE Corporation.

� UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

� Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and

other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

� HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology.

� JAVA® is a registered trademark of Sun Microsystems, Inc.

� JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented

and implemented by Netscape.

� MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

� SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other

countries all over the world. All other product and service names mentioned are trademarks of their respective

companies.

Copyright 2002 SAP AG. All Rights Reserved


� Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher

Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser

Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

� Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch

anderer Softwarehersteller enthalten.

� Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind eingetragene Marken der

Microsoft Corporation.

� IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®,

OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix

und Informix® Dynamic ServerTM sind Marken der IBM Corporation in den USA und/oder anderen Ländern.

� ORACLE® ist eine eingetragene Marke der ORACLE Corporation.

� UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group.

� Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® und

andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc.

� HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology.

� JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc.

� JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von

Netscape entwickelten und implementierten Technologie.

� MarketSet und Enterprise Buyer sind gemeinsame Marken von SAP AG und Commerce One.

� SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com und weitere im Text erwähnte SAP-Produkte und -Dienst-leistungen

sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen

Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen.

Copyright 2002 SAP AG. Alle Rechte vorbehalten

Documents

Multiple Components in One Database - archive.sap.com · SAP AG2002, Title of Presentation, Speaker Name 2 Technical Setup The following slides show for all databases supported by