Sap On Db2 Universal Database For Os 390 And Z Os

SAP on DB2 for z/OS and OS/390: High Availability and Performance Monitoring with Data Sharing

This IBM Redbooks publication addresses the challenges posed by monitoring high availability, scalability, and performance in an SAP sysplex data sharing environment. It introduces the motivations for utilizing a design based on DB2 data sharing. It includes the principal SAP-DB2 data sharing architecture options and trade-offs used in the industry today and issues that play a role in both high availability and scalability, such as failover design, database connectivity design, workload splitting and load balancing, MCOD, and coupling facility design. The book discusses single point of failure, important failover scenarios and outage avoidance, automation of high availability constructs, and backup and recovery considerations in data sharing environments. Performance issues are detailed in the order you would approach them at planning and implementation time. First, it discusses tuning the sysplex, which is the base for a well-performing DB2 data sharing system, then tuning the DB2 data sharing system, which is the base for a well-performing SAP system, and finally, tuning the SAP system. The book focuses on initial planning for performance and monitoring it afterward, and explains the key points to look for to health-check your system and maintain high performance.

SAP on DB2 Universal Database for OS/390 and Z/OS

SAP on DB2 Universal Database for OS/390 and Z/OS

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.