IBM DB2 Optimized for SAP
DB2 9.8 pureScale for SAP Applications
DB2 pureScale Feature for
Enterprise Server Edition
Unlimited Capacity
Buy only what you need, add
capacity as your needs grow
Application Transparency
Avoid the risk and cost of
application changes
Continuous Availability
Deliver uninterrupted access to
your data with consistent
SAP Applications on DB2 pureScale
End users
Can use SAP log-on groups to
direct similar work to same set of
servers
SAP application servers
Are connected to a DB2 member,
based on central configuration file
Automatic fail-over and fail-back in
case of a member failure
DB2 pureScale cluster
Central locking and cache
coherency (cluster caching facility)
Intra-cluster high-speed
communication, exploiting RDMA
technology
Built-in HA through DB2 built-in
cluster manager
Data resides in DB2 built-in cluster
file system
Shared Disks Member 1 Member 2
Application Servers Application Servers Application Servers
DB2 pureScale Availability Characteristics
Unplanned Outages: DB2 Members
Data availability
100%
time
Data in-flight on failed member
Member restart
Failure of a DB2 member
Connections from SAP application servers
automatically fail over to other members
Only data that was in-flight data at the failed
member is locked until member restart
completes. All other data and all other
members remain fully available
Automatic member restart
Attempt restart on member's home host
If restart is not possible on the member's
home host, DB2 will automatically perform
the restart on another host
DB2 will bring the member up at its home host
as soon as it becomes available again
Connections from SAP application servers
automatically fail back to the member at
transaction boundaries, invisible to the end
users
DB2 pureScale Availability Characteristics
Unplanned Outages: Cluster Caching Facility
Failure of primary cluster caching facility
Secondary cluster caching facility takes over
Very short period (typically seconds) where CF service
is suspended during switchover to secondary
Members continue running; if they request CF, those
requests will simply take a few more seconds to
complete
No errors are returned to the members
No loss of in-flight transactions
Failed cluster caching facility will automatically be
brought up as secondary once its home host becomes
available again
Failure of secondary cluster caching facility
Likely not perceived (very short hiccup)
No loss of in-flight transactions
DB2 pureScale Availability Characteristics
Planned Outages
Maintenance of a DB2 member
Transactions are transparently drained out from
the member
Connections from SAP application servers
switch over to other members at transaction
boundaries, invisible to the end users
Once DB2 member maintenance is completed,
the member is brought up again
Connections from SAP application servers
switch back to the member at transaction
boundaries, invisible to the end users
Maintenance of cluster caching facility
For maintenance of current primary:
Initiate role switch (secondary will take over)
Cluster caching facility is taken out of the cluster
and maintenance conducted
Cluster caching facility is integrated into the
cluster again
100%
time
Data availability
Data remains fully available
DB2 built-in High Availability
Traditional HA versus DB2 9.8 pureScale
Shared Disk HA
Active/passive solution
Requires no CPU cycles on standby
Medium-fast fail-over
Rolling OS, HW and DB2 fixpack update
DB2 High Availability Disaster Recovery (HADR)
Active/semi-active solution
Protection against disaster
Very fast failover
Rolling OS, HW and DB2 fixpack update
DB2 9.8 pureScale
Active/active: Database is distributed over several servers
Scaling across multiple servers
Continuous availability
DB2 pureScale Connectivity Setup Overview
Shared Disks Member 1
Application Server 1 Application Server 2
Member 2 db2dsdriver.cfg
Cluster Caching Facility
Centralized connectivity setup
Every SAP application server has a
primary (preferred) DB2 member and a
list of fail-over alternatives
Assured client affinity: All connections of
one SAP application server will equally
and automatically
fail-over in case of member
unavailability
Fail-back when the primary member
becomes available again
Connectivity is centrally configured at:
$(DIR_GLOBAL)/db6/db2dsdriver.cfg
Applies to AS ABAP and AS Java
Two types of connectivity setups
Simple, out-of-the-box configuration:
DB2 managed round-robin assignment
Roundrobin Connectivity Setup
Highlights
Simple out of the box configuration
No user interaction required
Configuration details
affinityFailbackInterval
Fail-back check interval in seconds
alternate_server_list
List of all DB2 members
client_affinity_roundrobin
List of SAP application servers for
round-robin assignment
Resulting connectivity setup
<configuration><DSN_Collection>
<dsn alias="CO1" name="CO1" host="db6m1.wdf.sap.corp" port="5912" /> </DSN_Collection>
<databases>
<database name="CO1" host="db6m1.wdf.sap.corp" port="5912"> <acr>
<parameter name="enableAcr" value="true"/>
<parameter name="enableSeamlessAcr" value="true"/> <parameter name="affinityFailbackInterval" value="5"/>
<alternate_server_list>
<server name="member_1" hostname="db6m1.wdf.sap.corp" port="5912" /> <server name="member_2" hostname="db6m2.wdf.sap.corp" port="5912" /> <server name="member_3" hostname="db6m3.wdf.sap.corp" port="5912" /> </alternate_server_list>
<client_affinity_roundrobin>
<client name="sap_as_1" hostname="db6as1.wdf.sap.corp" /> <client name="sap_as_2" hostname="db6as2.wdf.sap.corp" /> <client name="sap_as_3" hostname="db2as3.wdf.sap.corp" /> </client_affinity_roundrobin>
</acr> </database> </databases>
<parameters>
<parameter name="CommProtocol" value="TCPIP"/> </parameters>
</configuration>
Primary 1st fail-over 2nd fail-over
sap_as_1 member_1 member_2 member_3
sap_as_2 member_2 member_3 member_1
User-defined Connectivity Setup
Highlights
Allows individual and customized
setups
Targeted at experienced DBAs
Configuration details
affinityFailbackInterval
Fail-back check interval in seconds
alternate_server_list
List of DB2 members
affinity_list
Lists of member orders
client_affinity_defined
Assignments of SAP application
servers to an affinity_list
Resulting connectivity setup
<configuration><DSN_Collection>
<dsn alias="CO1" name="CO1" host="db6m1.wdf.sap.corp" port="5912" /> </DSN_Collection>
<databases>
<database name="CO1" host="db6m1.wdf.sap.corp" port="5912"> <acr>
<parameter name="enableAcr" value="true"/>
<parameter name="enableSeamlessAcr" value="true"/> <parameter name="affinityFailbackInterval" value="5"/>
<alternate_server_list>
<server name="member_1" hostname="db6m1.wdf.sap.corp" port="5912" /> <server name="member_2" hostname="db6m2.wdf.sap.corp" port="5912" /> </alternate_server_list>
<affinity_list>
<list name="as_group_1" serverorder="member_1,member_2" /> <list name="as_group_2" serverorder="member_2,member_1" /> </affinity_list>
<client_affinity_defined>
<client name="sap_as_1" hostname="db6as1.wdf.sap.corp" listname="as_group_1" />
<client name="sap_as_2" hostname="db6as2.wdf.sap.corp" listname="as_group_2" /> </client_affinity_defined> </acr> </database> </databases> <parameters>
<parameter name="CommProtocol" value="TCPIP"/> </parameters>
</configuration>
List Primary 1st fail-over
sap_as_1 as_group_1 member_1 member_2
Connectivity Setup: Display and Refresh
Connectivity Setup in DBA Cockpit
Overview about current SAP application
server – DB2 member connection status
Display of central configuration file
*
$(DIR_GLOBAL)/db6/db2dsdriver.cfg
SAP DBA Cockpit for DB2 pureScale
DB2 pureScale in DBA Cockpit
pureScale members are visible in
all existing DBA Cockpit screens
like DPF partitions
Apply SAP Note 1409540 to add
DB2 pureScale extensions to your
DBA Cockpit
DB2 pureScale Extensions
Cluster status
Cluster performance
Group bufferpool and local
bufferpool metrics
Package cache extensions
Cluster caching facility
Page contention analysis
pureScale Support in SAPINST
DB2 pureScale Topology Changes
Migration from ESE to pureScale
Add/drop DB2 members
Add/drop cluster caching facility
Creation and update of db2dsdriver.cfg
SAP Topology Changes
Installation of additional SAP instances
De-installation of SAP instances
Adopting DB2 9.8 pureScale:
Fresh SAP Installation
Create GPFS file systems for your SAP system
Install DB2 9.8 pureScale code
Create GPFS file systems using db2cluster command
Run SAP Installation based on DB2 9.7
Direct install using DB2 9.8 pureScale is currently not possible
Install the SAP system to the GPFS file systems using one
single storage path
SAPINST will install the SAP system using DB2 9.7
Upgrade from DB2 9.7 to 9.8 pureScale
Upgrade your DB2 9.7 ESE instance to 9.8 ESE
Use SAPINST to extend the 9.8 ESE instance to a
DB2 pureScale instance in your desired target topology
Adopting DB2 9.8 pureScale:
Upgrade of an existing SAP system
Create GPFS file systems
Install DB2 9.8 pureScale code
Create GPFS file systems using db2cluster command
Migrate to Automatic Storage on GPFS
Rebalance your table spaces online to automatic storage in
the new GPFS file systems
Exchange previous storage paths with new ones using
db2relocatedb
Upgrade from DB2 9.7 to 9.8 pureScale
Upgrade your DB2 9.7 ESE instance to 9.8 ESE
Use SAPINST to extend the 9.8 ESE instance to a
DB2 pureScale instance in your desired target topology
SAP Pilot Program for DB2 9.8 pureScale
SAP code level requirements
OLTP applications based on AS ABAP 7.0 and/or AS Java 7.0 and higher.
DBA Cockpit extensions according to
SAP Note 1409540
SAP kernel level according to
SAP Note 1414616
Your way to DB2 pureScale
DB2 pureScale is available through a pilot program.
See
http://www.sdn.sap.com/irj/sdn/db6
for more information:
Interested in becoming a DB2 9.8 pureScale pilot customer ?
Fill out the pilot questionnaire and register for the pilot program
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+,
POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP®product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.