Book description
The Multiple Components in One Database (MCOD) feature of SAP
enables a reduction in the number of DB2 systems that need to be
installed and maintained. This significantly simplifies overall
database administration and is considered one of the major DB2
competitive advantages.
This IBM Redbooks publication will help systems administrators,
database administrators, managers, and operation staff to plan,
implement, and administer an SAP MCOD landscape with DB2 Universal
Database (UDB) for OS/390 and z/OS as the database management
system.
We describe how to merge existing systems into a single DB2
subsystem. Two different methods are developed, each of them
addressing different needs. For small-to-medium SAP systems where
high availability is not a requirement, we explain how to use SAP
tools. For large systems, where the down time needed by SAP
standard procedures is not acceptable, we document a technique to
merge SAP components without moving the data.
We also provide a cloning procedure using the Control Center. We
show how to clone one component out of an MCOD landscape. We
address the backup and recovery implications in an MCOD
environment, to help database administrators plan accordingly. We
also describe how to set up and use the Computer Center Management
System (CCMS) in an MCOD landscape.
Please note that the additional material referenced in the text is not available from IBM.
Table of contents
- Figures
- Notices
- Preface
- Chapter 1: MCOD in a DB2 UDB for OS/390 and z/OS environment
- Chapter 2: Planning for an MCOD landscape
- Chapter 3: MCOD installation and merge using SAP tools
-
Chapter 4: Merging SAP components without moving data
- Considerations for using this procedure
- Planning considerations
- Merge in place scenario
-
Preparation steps
- Source: Create full backup of source system
- Target: Create full backup of catalog and directory of target
- Source: Redefine empty tablespaces as DEFINE NO in source
- Source: Reorganize tablespaces
- Source and Target: Create and populate metadata tables
- Source and Target: Define source objects in target system
- Target: Update metadata tables
- Target: Stop newly created databases
- Target: Prepare RUNSTATS JCL
-
Migration steps
- Source: Stop all update activity on source system
- Source: Perform full backup of source DB2 subsystem
- Source: Start source databases for UT access
- Source: Execute REPAIR on page set header pages
- Source: Stop source DB2 subsystem
- Target: Delete target data sets and rename source data sets
- Target: Start target databases in target system
- Target: Execute REPAIR LEVELID on tablespaces and indexes
- Cold start target system (optional)
- Target: Execute RUNSTATS
- Target: Perform IMAGE COPY
- Configure SAP application server
- Post-migration steps
-
Chapter 5: Cloning one component out of an MCOD landscape
- MCOD cloning: Just another homogeneous system copy
- Cloning scenario
-
Using the Control Center cloning wizard
- System requirements
- Skill requirements
- Prepare to create a cloning session
- Running the Control Center cloning wizard (1/4)
- Running the Control Center cloning wizard (2/4)
- Running the Control Center cloning wizard (3/4)
- Running the Control Center cloning wizard (4/4)
- Prepare for submitting the generated JCL
- XMAP member and MCOD cloning
- When do you have to regenerate JCL
- Running the generated JCL
- Additional considerations (1/2)
- Additional considerations (2/2)
- Chapter 6: PPT recovery of one system in an MCOD landscape
-
Chapter 7: Computer Center Management System (CCMS) and MCOD
- Setup of CCMS in an MCOD landscape
-
MCOD enhancements
- Tables and indexes monitor (transaction DB02)
- Central DBA planning calendar (transaction DB13C)
- DBA planning calendar (transaction DB13): Backup
- Backup monitor (transaction DB12)
- CCMS monitor set (transaction RZ20)
- Database performance analysis (transaction ST04) (1/2)
- Database performance analysis (transaction ST04) (2/2)
- Appendix A: Database layout
- Appendix B: Merge in place: Working with metadata tables
- Appendix C: Merge in place: Defining source objects in target system
-
Appendix D: Merge in place: Migrating the data
- Running the migration procedures
- Extracting information from the metadata tables
- Issuing DB2 START and STOP DATABASE commands
- Executing REPAIR on page set header pages
- Deleting created target data sets and renaming source data sets
- Executing REPAIR LEVELID on tablespaces and indexes
- Generating DDL for views
- Generating DDL for altering object sizes
- Appendix E: Additional material
- Abbreviations and acronyms
- Related publications
- Index (1/2)
- Index (2/2)
- Back cover
Product information
- Title: SAP on DB2 Universal Database for OS/390 and z/OS: Multiple Components in One Database (MCOD)
- Author(s):
- Release date: February 2003
- Publisher(s): IBM Redbooks
- ISBN: None
You might also like
book
Migrating Siebel Database from DB2/Oracle for NT to DB2 for OS/390
This IBM Redbooks publication will help you to migrate the Siebel 2000 V6.2.1 database from: DB2 …
book
Advanced Functions and Administration on DB2 Universal Database for iSeries
Dive into the details of DB2 Universal Database for iSeries advanced functions and database administration. This …
book
IBM Db2: Investigating Automatic Storage Table Spaces and Data Skew
The scope of this IBM® Redpaper™ publication is to provide a high-level overview of automatic storage …
book
Application Development for IBM CICS Web Services
This IBM® Redbooks® publication focuses on developing Web service applications in IBM CICS®. It takes the …