IBM Redbook：SAP BW on DB2 V8最佳实践与性能调优

需积分: 0 195 浏览量更新于2024-08-02 收藏 4.04MB PDF 举报

"Best Practices for SAP BW on DB2 UDB for z/OS V8" 是一本由IBM红皮书出版的指南，主要关注在IBM DB2 Universal Database (UDB) for z/OS V8平台上运行SAP Business Information Warehouse (BW)的最佳实践。书中详细介绍了如何充分利用DB2 V8为SAP BW带来的优势，并提供了性能优化和调优的建议。本书旨在帮助读者理解在大型主机系统z/OS上部署SAP BW的优势，包括提高效率、增强可扩展性和稳定性。作者团队由多位来自IBM的专家组成，他们深入研究了SAP BW与DB2 UDB V8的集成，以确保提供的信息准确且实用。主要内容涵盖以下几个关键知识点： 1. **SAP BW与DB2 UDB V8的兼容性**：本书适用于SAP NetWeaver 04 SR1，其中包含SAP BW 3.5版本和BI内容的3.53版本，以及DB2 UDB for OS/390和z/OS的8.1版本。这表明了DB2数据库与SAP BW软件的紧密集成，能够支持复杂的数据仓库操作。 2. **最佳实践**：书中详细列举了在z/OS环境中实施SAP BW的最佳实践，这些实践可能涉及数据加载策略、性能监控、查询优化、数据存储和备份恢复等方面，以确保系统的高效运行。 3. **性能和调优**：为了最大化系统性能，书中提供了关于数据库配置、索引设计、SQL查询优化等方面的建议。此外，还包括了针对特定工作负载的调优技巧，帮助用户应对大数据量和高并发的挑战。 4. **故障排查**：书中还包含了一部分关于故障诊断和解决的章节，指导读者在遇到问题时如何快速定位并修复，以减少系统中断的时间，保障业务连续性。 5. **安全性和可用性**：考虑到SAP BW通常处理敏感数据，书中的内容可能还会涉及DB2 UDB for z/OS的安全配置，如访问控制、审计和灾难恢复计划，以确保数据的安全和系统的高可用性。 6. **法规遵从性**：对于美国政府用户，书中可能会提及GSA ADP Schedule合同下的使用、复制和披露限制，以满足法规遵从性要求。本书不仅对SAP BW管理员和DB2数据库管理员具有极高价值，而且对IT项目经理、系统架构师和任何参与SAP BW在大型主机平台部署的人都是一份宝贵的参考资料。通过深入阅读和应用书中的建议，读者可以提升SAP BW在z/OS环境下的性能，降低运维成本，同时提高业务决策的效率和准确性。

2 Best Practices for SAP Business Information Warehouse on DB2 for z/OS V8

1.1 Product overview

The business warehouse solution from IBM and SAP can help your company collect, analyze,

and distribute critical data. mySAP Business Intelligence provides a full suite of end-user

reporting and analysis tools, including the following:

Advanced analytics Statistical and mathematical functions with a full range of

multidimensional analysis

Mobile business intelligence Accessible to a full range of wireless and mobile devices,

providing anytime, anywhere access

Business content Report templates and metrics, tailored for different user roles

in different vertical industries

This end-to-end implementation can give your business the ability to:

򐂰 Add commentaries to reports and key figures, essentially automating approval processes

򐂰 Visually represent data analysis in a wide variety of formats including grids, graphs, charts

and maps, through a unique toolset that allows for custom reporting environments

򐂰 Analyze data from both internal and external sources, and link traditional business

environments and e-business operations through data warehousing

򐂰 Combine, view, and deliver structured information (such as database reports), and

unstructured information (including e-mail), as well as internal and external data through

your existing enterprise portal

Many IBM Redbooks™ have been published about SAP systems on IBM zSeries; see

“Related publications” on page 259. The following subjects have been covered:

򐂰 Reliability, availability, and serviceability of SAP systems on IBM zSeries

򐂰 Security and integrity

򐂰 Scalability

򐂰 Continuing compatibility

򐂰 Changing workload

These are beneficial subjects for business intelligence (BI) systems because SAP BW

queries involve the batch processing of terabytes of data. The IBM mainframe solution is very

strong in this area.

Furthermore, the SAP BW application is different from other SAP modules, especially

regarding the use of a database. Thus it is important to look into the performance of SAP BW

with DB2 V8 on zSeries, as this redbook does.

1.2 The audience for this redbook

The goals of this redbook are to give an integrated view of key SAP BW and DB2 for z/OS

performance indicators, and to offer a process for using them together.

The audience for this document includes both zSeries DB2 DBAs and SAP BW Basis

Administrators responsible for administering SAP BW on zSeries DB2 production systems,

and SAP BW functional architects responsible for designing the BW system’s InfoCubes,

Aggregates, and ODS objects.

Note: A key message is the importance of early cooperation between the functional

designers and the technical implementation.

Chapter 1. Introduction 3

The SAP BW solution is not the only DB2 V8 solution within a company. Most companies

have different legacy systems running on zSeries. For the IBM mainframe infrastructure, a

support organization exists within the company. Most groups tend to work independently from

each other.

With SAP BW on zSeries, as with other SAP solutions on the IBM mainframe, you must

communicate with all groups that are responsible for the operation of the SAP solution.

Ideally there should be a person in your organization who bridges the gap between the

different support groups. The user acceptance and performance of your SAP solution will

benefit.

The focus of this redbook is on performance problems: how to avoid them, how to

troubleshoot performance problems that cannot be avoided, and how to solve the problems

once identified. Most performance problems can be avoided if foresight is used and design

decisions take certain issues into consideration.

This book can also be used for decisions concerning SAP on zSeries, as discussed in 11.12,

“Flexible implementation with zSeries” on page 215. Key areas we cover are load

performance, query performance, performance during administration processing, and storage

reduction.

In general, database administrators (DBAs) are not responsible for some of the processes

discussed in this book, for example analyzing and defining SAP aggregates (which are

summary tables optimized for specific queries). It is important, however, for DBAs to be

aware of these activities, since aggregate analysis and definitions should generally be done

before solving a problem, when the root problem is a lack of aggregates. Missing or

improperly defined aggregates can cause increased CPU usage, excessive I/O activity, and

increased DB2 memory usage.

Evaluation of query performance for SAP BW requires both SAP information (such as query

performance indicators RSDDSTAT, or aggregate valuation and definition in RSA1) and also

DB2 indicators (such as cached statement statistics, or using DB2 EXPLAIN PLAN to analyze

the access path used by DB2).

Likewise, an SAP BW administrator may not be familiar with the technical issues of DB

structure, SQL evaluation, and DB2 parallelism capabilities. But if, after evaluating the data

model and aggregates, there are still performance problems, the SAP BW administrator can

work with the DB2 DBA to evaluate the DB2-related changes to address performance

problems. Not all problems can be solved with aggregates, and the BW administrator may

need to turn over some problems to the DB2 DBA.

1.3 Why run SAP BW on IBM zSeries

The “z” in zSeries signifies zero downtime. zSeries hardware is designed to meet the world’s

most critical computing needs. Reliability characteristics such as dynamic CPU sparing,

logical partitioning, error detection and correction, and hardware cryptography are built into

the architecture.

If the nonspecialist IBM system offers 99.99% availability, the result is only 53 minutes of

unplanned downtime per year. If the sysplex gives 99.999% availability, there is only 5

minutes per year of unplanned downtime.

1.3.1 Value provided by z/Series, z/OS, and DB2

In this section we give an overview of the value provided by z/Series, z/OS, and DB2.

4 Best Practices for SAP Business Information Warehouse on DB2 for z/OS V8

One-stop shopping

IBM provides a one-stop shop for all three components—hardware, operating system, and

database.

7 x 24 application availability

򐂰 99.999% database reliability offers resilience to unplanned outages. Such database

availability requires:

– A robust operating system; z/OS has more than one million lines of recovery code, and

has been evolving since 1966.

– Reliable hardware with internal redundancy and error correction logic; z/990 has a

mean time to failure (MTF) greater than 30 years.

– That a processor continues to operate after the loss of an engine.

– That there is no single point of failure (SPOF); this support is provided by Parallel

Sysplex® with DB2 Data Sharing.

– Coupling Facilities, which fully support structure duplexing and automated takeover.

– Reliable DBMS; DB2 has been evolving for more than 20 years and has been

stress-tested by more than 8,000 of the largest companies in the world.

– Dynamic CPU sparing; at a minimum, one of the z/Series processing units is

designated as a spare. If a running CPU chip fails and the instruction retry is

unsuccessful, the spare processing unit begins executing at precisely the instruction

where the other failed.

Activation of the spare is done completely by the hardware, enabling the system to be

restored to full capacity in less than one second. Because most hardware failures

requiring repair will not cause an outage at the time of failure or at the time of repair,

the zSeries achieves near-zero outage for unplanned hardware repairs.

򐂰 Minimial planned outages; this is also known as

continuous operations:

– Parallel Sysplex, coupled with DB2 Data Sharing and SAP Sysplex Failover, allows

rolling maintenance and upgrades of hardware, z/OS, and DB2 without an outage.

– DB2 Online Utilities eliminate database maintenance, which is the leading cause of

planned outages in a UNIX® or Windows® environment.

– All of this is further complemented by hot-pluggable features, including capacity upon

demand of zSeries and z/OS.

Capacity and scalability

򐂰 Vertical and horizontal

– Vertical growth is achieved through more or faster engines in a single symmetric

multiprocessor (SMP) - the traditional growth path for UNIX and Windows.

– Horizontal growth is achieved by clustering SIMPs with a single copy of the database

(also known as

parallel operation).

Parallel Sysplex provides horizontal growth: 1 - 32 engines x 32 CECs.

– DB2 Data Sharing is the only SAP-certified generally available (GA) clustered DBMS.

DB2 Data Sharing has been certified since 1997.

– DB2 Data Sharing has been in use in customer SAP environments since 1997.

– 64-bit real zSeries storage is in use by many SAP customers. z/OS sustains a higher

I/O rate than other platforms with 6 - 10 K I/Os/sec per I/O controller.

Chapter 1. Introduction 5

– DB2 V8 delivers 64-bit virtual storage, which allows more data in memory and the

easing of many system constraints related to addressability.

– Improved database-intensive performance

• Application servers running under z/OS provide data transfer using cross-memory

services. Linux® application servers on zSeries can use IBM unique hipersockets

for application server-to-database server communications.

– Sysplex with Coupling Facility.

– IO bandwidth, data in memory.

Large database manageability

򐂰 Multi-terabyte databases with hardware compression.

򐂰 Online backup and reorganizations.

򐂰 Storage technology (flash copy, snapshot).

򐂰 Self-tuning DASD—PAV, multiple allegiance.

򐂰 Leverage and protect investment.

򐂰 Multiple LPARs and priority schemes:

– DB2 hardware data compression is unique, and affects both performance and cost.

– UNIX and Windows solutions cannot afford the overhead of software compression.

– On the average, UNIX and Windows require 50% more disk than DB2 for z/OS.

– Customers typically have 4 to 10 copies of their production database, which quickly

grows into multi-terabyte size.

– z/OS and Linux application servers.

– MCOD - zSeries first - reduces complexity.

– Proven automation and end-to-end systems management.

– DR ready - GDPS® - cold, warm,

and hot.

– Non-disruptive CBU on/off.

– z/OS and DB2 skills and tools.

– Online backup and reorganizations (DB2 Online Reorg solutions are unique) eliminate

the major cause of planned outages.

– Storage technology (flash copy, snapshot)

• Integration of the disk controller database copy with the DBMS is unique with DB2

and ESS providing seamless, low overhead database backup.

– Self-tuning DASD - Parallel Access Volumes, multiple allegiance.

• Disk controller Parallel Access Volumes (PAV) with z/OS eliminates disk “hot spot”

tuning typical of a UNIX or Windows database server environment. PAV operates

across LPARS for multiple allegiance.

򐂰 Leverage and protect investment – some zSeries/DB2 capabilities that provide total cost

of ownership (TCO) and service level advantages:

– Multiple LPARs and priority schemes.

– z/OS and Linux application servers.

– MCOD - zSeries first - reduce complexity.

– Proven automation and end-to-end systems management.

剩余285页未读，继续阅读

crazybugcn

粉丝: 0

IBM Redbook：SAP BW on DB2 V8最佳实践与性能调优

How to get SAP Best Practices

Best Practices for DB2(DB2优化_english)

Best Practices Guide for SAP NetWeaver Portal

Best Practices with SAP S4HANA Embedded Analytics

Best Practices for Running VMware vSphere on iSCSI

Best Practices for Red Hat OpenShift on the VMware SDDC

Best practices for mission critical apps on Azure App Service

Best Practices for Performance

DB2 Best practices

Single sign-on best practices for Azure Active Directory

最新资源