SAP on DB2 Universal Database for OS/390 and z/OS : Multiple Components in One Database (MCOD)

Front cover -- Contents -- Figures -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Become a published author -- Comments welcome -- Chapter 1. MCOD in a DB2 UDB for OS/390 and z/OS environment -- 1.1 Introduction -- 1.1.1 Motivation -- 1.1.2 Benefits -- 1.1.3 Drawbacks -- 1.1.4 Availability -- 1.2 Technical realization -- 1.2.1 General implementation -- 1.2.2 DB2-specific modifications -- 1.2.3 Independence of components -- 1.2.4 Implementation -- 1.3 Setup options -- 1.3.1 Basic setup considerations -- 1.3.2 Non-data sharing DB2 -- 1.3.3 Data sharing DB2 -- Chapter 2. Planning for an MCOD landscape -- 2.1 Planning for MCOD -- 2.1.1 Keep things as separate as possible -- 2.1.2 Size of the DB2 subsystem -- 2.1.3 Number of SAP systems in the MCOD landscape -- 2.1.4 Bufferpool tuning -- 2.1.5 Recovery of the DB2 subsystem -- 2.1.6 Resources for daily tasks -- 2.1.7 License key -- 2.1.8 Checklist -- 2.2 Install directly -- 2.3 Merging two systems -- 2.3.1 Three methods of merging -- 2.3.2 Additional tasks -- 2.3.3 Checklist for merging -- 2.4 Our system configuration -- Chapter 3. MCOD installation and merge using SAP tools -- 3.1 Introduction -- 3.1.1 SAP Basis Releases 4.6C and 4.6D -- 3.1.2 SAP Basis Releases 6.10 and later -- 3.2 Installing a new component -- 3.2.1 SAP Basis Releases 4.6C and 4.6D -- 3.2.2 SAP Basis Releases 6.10 and later -- 3.3 Merging components into an MCOD landscape -- 3.3.1 SAP Basis Releases 4.6C and 4.6D -- 3.3.2 SAP Basis Release 6.10 and later -- 3.4 Steps after installation or merge -- 3.5 Minimizing migration down time -- 3.5.1 Incremental migration -- 3.5.2 Merging without moving the data -- Chapter 4. Merging SAP components without moving data -- 4.1 Considerations for using this procedure -- 4.1.1 Reasons for choosing the merge in place procedure -- 4.1.2 Limitations.