2 options
SAP on DB2 for z/OS and OS/390 : high availability and performance monitoring with data sharing / [Viviane Anavi-Chaput ... et al.].
- Format:
- Book
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Database management.
- IBM Database 2.
- OS/390.
- z/OS.
- Physical Description:
- xiv, 244 p. : ill.
- Edition:
- 1st ed.
- Place of Publication:
- Poughkeepsie, NY : IBM, International Technical Support Organization, c2003.
- Language Note:
- English
- Contents:
- Front cover
- Contents
- Notices
- Trademarks
- Preface
- The team that wrote this redbook
- Become a published author
- Comments welcome
- Part 1 Architecture and design choices affecting availability and performance
- Chapter 1. Introduction to SAP high availability and performance architecture
- 1.1 Why Parallel Sysplex and data sharing for SAP?
- 1.1.1 Continuous availability
- 1.1.2 Processor scalability
- 1.2 Parallel Sysplex architecture
- 1.3 DB2 data sharing architecture
- 1.4 SAP Sysplex failover architecture
- Chapter 2. Architecture options and trade-offs
- 2.1 DB2 data sharing design options for SAP
- 2.1.1 Option 0 - Single member with passive (inactive) standby member
- 2.1.2 Option 1: Two active members without passive standby members
- 2.1.3 Option 2: Two active members, each with a passive standby member in the same LPAR
- 2.1.4 Option 3: Two active members, with a passive standby member in an independent LPAR
- 2.1.5 How many data sharing groups?
- 2.1.6 How many data sharing members?
- 2.2 Failover design
- 2.3 ICLI design
- 2.3.1 How many ICLI servers?
- 2.3.2 Transition from ICLI to DRDA
- Chapter 3. Workload splitting and logon load balancing
- 3.1 Workload splitting
- 3.2 Logon load balancing
- 3.2.1 Core R/3
- 3.2.2 BW, CRM, APO
- 3.3 SAP scheduling and dispatching
- 3.3.1 Update (VB) Dispatching
- 3.3.2 Batch classes
- 3.3.3 RFC groups
- Chapter 4. MCOD with data sharing
- 4.1 Basic principles of MCOD
- 4.2 Performance versus high availability
- 4.3 Design choices with data sharing
- Chapter 5. Coupling facility design considerations
- 5.1 Coupling facility structure duplexing
- 5.2 CF sizing
- 5.2.1 MIPS
- 5.2.2 DB2 structures
- Part 2 High availability considerations
- Chapter 6. Single point of failure avoidance
- 6.1 SPOF candidates
- 6.1.1 Database server.
- 6.1.2 Application server
- 6.1.3 Disk subsystem
- 6.2 Design principles to avoid SPOF
- Chapter 7. SAP Sysplex failover
- 7.1 SAP Sysplex failover triggers
- 7.2 Important failover scenarios and system impact
- 7.3 Planned outage avoidance example
- Chapter 8. Automation architectures for availability in data sharing
- 8.1 What is automation?
- 8.2 Starting and stopping DB2 and SAP
- 8.3 Remote application server failover and failback
- 8.4 Local application server failover and failback
- 8.5 High availability enqueue failover and failback
- 8.6 Nondisruptive system-level copy
- 8.6.1 Nondisruptive system-level copy job flow
- 8.7 Automation for monitoring
- 8.7.1 Archive log process
- 8.7.2 Resource unavailable
- 8.7.3 Long-running units of recovery
- 8.7.4 SAP health check
- Chapter 9. Backup and recovery architecture in data sharing
- 9.1 Data sharing backup-recovery considerations
- 9.1.1 Data sharing recovery environment
- 9.1.2 Tablespace recovery
- 9.1.3 Recovering pages on the logical page list
- 9.1.4 Data sharing impact on SAP recovery procedures
- 9.1.5 Object-based backup: online and offline
- 9.1.6 Volume-based backup: online
- 9.1.7 Establishing a group-level point of consistency
- 9.1.8 Recovery to the current state
- 9.1.9 Recovery to a previous point in time
- 9.1.10 New utilities in DB2 V8 for online backup and point-in-time recovery
- 9.2 Data sharing considerations for disaster recovery
- 9.2.1 Configuring the recovery site
- 9.2.2 Remote site recovery using archive logs
- 9.2.3 Using a tracker site for disaster recovery
- 9.2.4 GDPS infrastructure for disaster recovery
- 9.3 Homogeneous system copy in data sharing
- 9.3.1 Planning for homogeneous system copy in data sharing
- 9.3.2 Designing homogeneous system copy in data sharing
- Part 3 Performance considerations.
- Chapter 10. Sysplex performance
- 10.1 What to measure: defining a baseline
- 10.2 CF performance monitoring and tuning
- 10.2.1 CF processor monitoring
- 10.2.2 CF storage utilization
- 10.2.3 CF link performance
- 10.2.4 CF signalling path length monitoring
- 10.3 WLM policies
- 10.4 RMF Monitor III - Work Delay Monitor
- 10.5 RMF Postprocessor reports
- 10.6 RMF Spreadsheet Reporter
- Chapter 11. Data sharing performance
- 11.1 What to measure: defining a baseline
- 11.2 Local buffer pool performance
- 11.3 Group buffer pool performance
- 11.3.1 Caching pages in the GBP
- 11.3.2 Calculating GBP hit ratios
- 11.3.3 Castout efficiency
- 11.4 Dynamic statement cache
- 11.5 Lock performance
- 11.5.1 DB2 locking mechanisms
- 11.5.2 Global locking
- 11.6 DB2PM statistics batch report
- 11.7 Tablespace partitioning
- 11.7.1 Partitioning to improve tablespace management
- 11.7.2 Partitioning to avoid I/O contention
- 11.7.3 Improving I/O performance for nonpartitioning indexes
- 11.7.4 Partitioning to distribute workload around the members
- 11.8 SAP update table partitioning
- 11.8.1 Analyzing the effectiveness of update table partitioning
- 11.9 Configuring for query parallelism
- 11.10 Managing DBM1 virtual storage
- 11.10.1 Managing SAP work processes
- 11.10.2 Monitoring work process utilization
- 11.10.3 Managing the DSC size
- 11.10.4 Managing open data sets
- 11.10.5 Monitoring storage
- 11.10.6 SAP-related enhancements in DB2 Version 7
- 11.10.7 SAP-related enhancements in DB2 V8
- 11.11 Configuring DB2 sort pool and workfiles
- 11.12 Backup policies: avoiding disruptive backups
- Chapter 12. SAP performance
- 12.1 Performance problem analysis route map
- 12.2 Route map for server-wide and system-wide performance analysis
- 12.3 Route map for process-specific performance analysis.
- 12.4 ST04 and DB2 performance monitoring tools
- 12.4.1 Installation checks
- 12.4.2 Dynamic Statement Cache analysis
- 12.4.3 DB2 subsystem activity
- 12.5 STAT and STAD statistics records
- 12.6 ST05 SQL trace
- 12.7 ST10 statistics analysis
- Appendix A. Checking SAP data sharing setup
- Check ICLI setup
- Check for buffer pool tuning
- VB update tables setup
- Check that logon load balancing has been implemented
- Check batch scheduling groups
- Check that VB dispatching has been implemented
- DBM1 virtual storage
- Sysplex failover setup
- Appendix B. Systems managed duplexing
- Activating a policy including system duplexing
- ICF failure
- Related publications
- IBM Redbooks
- Other IBM publications
- SAP publications
- Online resources
- How to get IBM Redbooks
- Index
- Back cover.
- Notes:
- "SG24-6950-00."
- "December 2003."
- Includes bibliographical references (p. 237-239) and index.
- OCLC:
- 80246009
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.