Filip Slánička, DB2/SAP technical professional, Community of Practice, CEE
IBM DB2 optimized for SAP
© 2010 IBM Corporation
IBM & SAP partnership
© 2010 IBM Corporation
IBM DB2 optimized for SAP
IBM DB2 Optimized for SAP Initiative – Pillars
SAP runs IBM DB2 IBM DB2 is a widely used database platform at SAP IT
Partnership Joint SAP and IBM teams working on all aspects of the product
Product Integration One product, one maintenance strategy, one-stop service Technology Innovation Joint technology roadmap with agreed deliverables
Source: If applicable, describe source origin 3
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
IBM DB2 Optimized for SAP Initiative – Roadmap
2013 2012 2011 NW 7.0 EhP 1
NW 7.0 SR3
NW 7.0
Database Performance Warehouse Integrated Workload Management
Turn-key HA solution Turn-key compression Integrated MDC advisor Deferred Table Creation
Embedded database TCO: Reduced storage costs, self tuning Minimal admin
2007
Version 9.1
Version 8.2.2 4
DB2 9.8 pureScale Continuous availability Seamless OS and hardware maintenance OLTP scale out
2009 Version 9.7
2008
Even Deeper Deep Compression 40+% reduction in Indexes 40+% reduction in Temps Compressed LOBs
Near-0 Storage Admin
2006
2005
2010
Version 9.5
Sparse MDC tables for simple space reclaim Easy table space reclamation Ease the path to Automatic Storage
Integrated & automatic Extending Online Operations Change schema definitions online HA+DR Reorganization improvements Integrated Flash Copy Full 360° Monitoring Threaded Architecture DPF Scaling Improvements
Storage limits removed Selected Autonomic / TCO features Compression
Automatic storage admin 2. listopad 2010 Deployment optimized for SAP
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Partnership– Joint Development and Support
Toronto ISIS Development Support
Toronto DB2 Development
Toronto DB2 Service
SVL ISIS Development Support Beijing IBM-SAP Integration Center
SVL DB2 Development
SVL DB2 Service Walldorf Development Support
5
2. listopad 2010
Walldorf SAP Development
Böblingen IBM Porting Team
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Partnership : Aligned Maintenance Strategy
DB2 upgrades are never enforced DB2 can always be upgraded at current SAP level to benefit from the technology innovation roadmap 6
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Strategic Technology Alignment
VERSION RELEASE LATENCY
2.5 years
VERSION RELEASE LATENCY 4-8 weeks
7
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Database Patch Comparison for Current Versions Database DB2 8 DB2 9.1 DB2 9.5 DB2 9.7 Oracle 10.2g Oracle 11.2g Status: Prove:
# Patches
# Months
18 9 5 2 118 40
93 50 33 13 48 6
Less down time Less admi nistra tion
24th September 2010 SAP hint 101809, 1137346 SAP Marketplace Downloads Database Patches
SAP supports four DB2 versions SAP’s ‘7+2’ maintenance strategy fully supported by DB2 DB2 9.1, 9.5 und 9.7 - average 1 patch per 6 months Oracle 10gR2 - average 2 patches per 1 months Oracle 11gR2 - average 6 patches per 1 months Oracle 11gR2 patches for 6 months is more than the patches for all DB2 versions together
DB2 provides much more stable operating 8
2. listopad 2010
© 2010 IBM Corporation
Installation & set up
© 2010 IBM Corporation
IBM DB2 optimized for SAP
What DB2 Features are supported in SAPINST Here are a list of DB2 features that are automatically enabled by SAPINST – DB2 Silent Installation: installation of DB2 is embedded in in the installation. There is no need to pre-install DB2 prior to running sapinst.
– DB2 CLI Driver: DB2 CLI Driver, a.k.a thin client, is used to run SAP applications. There is no
Faster implementation
need to install DB2 Client software on each SAP application server.
– DB2 Automatic Storage Management: AutoStorage is supported by SAP and can be enabled from sapinst.
Lower time and risk
– DB2 Self-Tuning Memory Manager: STMM is supported by SAP and can be enabled from sapinst.
Smooth
– DB2 Automatic RUNSTATS: sapinst will enable DB2 automatic runstats feature by default
– DB2 Deep Compression – compressed all eligible tables
Automated
– HADR - fully integrated HA setup for clustering
Better Betterout-of-the-box out-of-the-boxuser userexperience experience
10
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Parameter Check Tool for SAP on IBM DB2 New option integrated within the SAP DBA Cockpit to check IBM DB2 configuration against current recommendations in SAP Notes: – Database manager configuration, – Database configuration and – Registry variables
Declaration of deviations “as intended“ to avoid further messages Easy to use interface to “correct“ deviations Support of systems running on many database partitions Planned to be supported for IBM DB2 9.1, 9.5, 9.7 and higher releases
11
2. listopad 2010
© 2010 IBM Corporation
Administration & monitoring
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Database Administration Workbench – DBACOCKPIT A comprehensive database administration interface to DB2 Performance Monitoring Tablespace Monitoring Backup & Recovery Configuration Database Job Scheduling Alert Monitor Diagnostics
13
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
SAP Performance Warehouse Integration of Database and Application Monitoring in one console Features: – Monitoring of historical performance relevant data – BI Analytics for performance data – Complete Set of predefined reports for IBM DB2 – Role model for other databases
14
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Enhanced IBM DB2 9.7 Database Monitoring Capabilities Optim Performance Manager
IBM DB2 Data Studio + DB2 Health Monitor http://www.ibm.com/developerworks/downloads/im/data/ http://www.ibm.com/developerworks/data/tutorials/dm-1012datastudiohealth/ Source: If applicable, describe source origin 15
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
DB6CONV – DB6CONV is a report to move one or more tables into a new tablespace or within the same tablespace; DB6CONV is started using transaction SE38. – DB6CONV is not part of a standard SAP delivery. It is available as a separate transport attached to OSS Note 362325 only. OSS Notes
362325: DB6: Table conversion using DB6CONV
(DB6CONV transport attached)
648432: DB6: New function modules for hash partitioning
1039544: DB6: Stored procedure for online table move
(stored procedure ONLINE_TABLE_MOVE attached)
© 2010 IBM Corporation © SAP 2009 / Page 16
Save your time, storage & money
© 2010 IBM Corporation
IBM DB2 optimized for SAP
IBM DB2 Storage Optimization – Overview SAP OEM license for IBM DB2 includes several storage optimization techniques: – Table Row Compression, – Index Compression, – Temporary Table Compression, – Backup Compression, – Deferred Table and Index Creation (by SAP), – LOB Inlining for enhanced Table Row Compression, – Value and Null Compression.
Source: If applicable, describe source origin 18
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
SAP DB2 migrations Non-DB2 DB2 Migrations (data compression only) – older DB2 version
Schaeffler (SAP BI, 8 TB 4,5 TB): Coca Cola (SAP ERP, 950 GB 575 GB): Kali+Salz (SAP ERP, 2500 GB 1375 GB): Thyssen-Krupp (SAP BI, 176 GB 92 GB): Schwartau (SAP ERP, 651 GB 377 GB): Tellabs (SAP ERP, 1061 GB 545 GB): Shoprite Checkers, South Africa ( SAP ERP 3.5 TB 1.4 TB )
44% 40% * 45% 48% * 42% 49% 64%
Oracle 10g DB2 migrations (data & index comp.) – current DB2 version
Audi Germany (SAP BW, 873 GB 408 GB): Audi Germany ( SAP FI/CO 1533 GB 409 GB ) Sikorsky US ( SAP R/3 5.1 TB 1.2 TB ) Ericsson Sweden ( ERP 1411 GB 569 GB ) Swiss Pharma Company ( BW 1991GB 824 GB ) Eli Lilly, US ( BW 6.0 TB 1.8 TB ) German Insurance Company ( ERP 542GB 189 GB ) Pepsico, US ( overall SAP storage reduction )
53% 73% 76% 60% 59% 70% 64% 55%
* Including unicode conversion 19
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
DB2 Data compression benefits Key resource utilization slashed
Before
•
Processor load up to 60%
•
Input/output traffic up to 70%
20%
•
Memory usage up to 40%
15%
•
10%
Compression is on external storage and in memory
CPU utilization for DB
Week Feb 1
Size reduced up to 85%
•
Time reduced up to 65%
Better batch performance •Up to 10x faster
Week Feb 8
Week Feb 15
Week Feb 22
2009
Better backup •
After
5% 0
Reduced size and time
Compression key
1200
Reads+writes per second
1000 800 600 400 200 0 Week Feb 1
Week Feb 8
Week Feb 15
Week Feb 22
2009
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Unicode overhead? DB2 compression to the rescue!
60+%
70+ %
575GB
950GB
60% 30%
50%
40%
70%
© 2010 IBM Corporation
Business Warehouse
© 2010 IBM Corporation
IBM DB2 optimized for SAP
SAP NetWeaver BW – IBM DB2 performance improvements DB2 "Database Partitioning Feature" (DPF) – Shared-nothing architecture with proven linear scale-out capability – Mature technology – almost all larger SAP BW customers on DB2 run with DPF – Fully supported since SAP BW 2.0 – Available with DB2 only
23
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
SAP NetWeaver BW – IBM DB2 performance improvements All records in this block are from region East and from year 97
Region
Region
Recor Recor d d Recor d
Multi Dimensional Clustering Page Page Page
24
East East North South 99 99 97 98
Year
Year
Prior to MDC
With MDC
2. listopad 2010
– Clusters tables based on multiple Columns. – More effective compared to Range Partitioning – Automatic Maintenance of Blocks – Improved Query, Roll-Out and Roll-In performance
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Block Elimination for Queries
YES ! NO !
YES !
YES !
YES !
NO !
Feb
Mar
Range Partitioning
A US
TV
TV
Stereo
Stereo
DVD
DVD
Jan
UK
a in h C
Jan
Feb
Mar
A US
UK
a in h C
MDC
SELECT revenue FROM table WHERE product=’DVD’ AND country=‘China’ 25
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
MDC Advisor Integration in SAP DBA Cockpit Fully integrated within SAP DBA Cockpit Features: – Automatic InfoProviders‘ workload collection – Provide MDC recommendations if appropriate – Take in account performance and space consumption in the recommendation
26
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
IBM DB2 Near-Line Storage for SAP NetWeaver BW – Concept SAP NW BW Near-Line Storage (NLS) Interface – Request based data transfer between BW Online Database and Near-Line Storage – Transparent access to NLS data with •BW Queries •Data Transfer Process (DTP)
IBM DB2 specific NLS implementation – Separate IBM DB2 database as NLS storage – NLS access via ABAP secondary connection – Defaults for IBM DB2 / NLS database: •Automatic Storage •Self Tuning Memory Management •Row Compression + Index compression (IBM DB2 9.7) •Multi Dimensional Clustering (MDC) •Database Partitioning Feature (optional)
SAP NetWeaver BW GUI
BW Query
SAP NetWeaver BW
BI OLAP
BIData OLAP BW Manager DBInterface Interface DB Layer Layer DBMS Relational DB DB Relational Interface Interface
General NLS General Near-Line StorageInterface Interface TREX NLS / DB2 LUW DB2 / Near-Line Interface Storage Interface ABAP secondary connection
BW Database Online Data
InfoCube 2009 2008 2007
DSO 2009 2008 2007 2006
Near-Line Storage DB2 Database InfoCube 2006 2005 2004 2003
DSO 2005 2004 2003
Source: If applicable, describe source origin 27
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
IBM DB2 Near-Line Storage for SAP BW – Integration Delivery with SAP NetWeaver BW with 7.01 SP6. Unicode Systems only Administration and monitoring of the NLS database (remote db) fully integrated into SAP DBA cockpit Set-up of NLS database integrated into SAP’s installation tool "One stop" support for BW and NLS database Based on proven IBM DB2 technology Included in SAP OEM license for IBM DB2 at no extra cost
Source: If applicable, describe source origin 28
* IBM DB2 license needed 2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Konec první části...
29
2. listopad 2010
© 2010 IBM Corporation
High Availability & Disaster Recovery
© 2010 IBM Corporation
IBM DB2 optimized for SAP
High Availability Database Cluster types 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 – Stealth OS and HW maintenance © 2010 IBM Corporation © SAP 2010 / Page 31
IBM DB2 optimized for SAP
Database Cluster (shared storage) – active / passive
© 2010 IBM Corporation © SAP 2010 / Page 32
IBM DB2 optimized for SAP
Database Cluster with HADR (2)
© 2010 IBM Corporation © SAP 2010 / Page 33
IBM DB2 optimized for SAP
Database Cluster with HADR (2) IBM DB2 HADR ( High Availability Disaster Recovery) Over long distances supported Faster Failover: only aborted transactions have to be rolled back Fast network between database servers recommended Synchronization: SYNC □ Write commited, when log writer on standby has written the log record to disk □ Impact: about 10% NEARSYNC □ Write commited, when Standby has acknowledged the retrieval of the log record □ Impact: about 6% ASYNC □ Write commited, when log redord was sent to standby □ Impact: about 4% No automatic failover cluster manager No DPF support © 2010 IBM Corporation © SAP 2010 / Page 34
IBM DB2 optimized for SAP
Database Cluster with HADR (1) IBM DB2 HADR (High Availability Disaster Recovery) – Replication for DB2 between database servers
VIP
Standby DB Server
Primary DB Server HADR
db2agent Log Buffer
Tabellen Indizes
HADR
Log Writer
Log Writer
Logs
Logs
Replay Master Shredder Redo Master Redo Workers
Tabellen Indizes © 2010 IBM Corporation
© SAP 2010 / Page 35
IBM DB2 optimized for SAP
Database Cluster pureScale – active / active
© 2010 IBM Corporation © SAP 2010 / Page 36
IBM DB2 optimized for SAP
DB2 pureScale Characteristics 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 performance
37
© 2010 IBM Corporation
IBM DB2 optimized for SAP
DB2 pureScale: Technology Overview Clients connect anywhere,… … see single database
Clients
– –
Single Database View
Clients connect into any member Automatic load balancing and client reroute may change underlying physical member to which client is connected
DB2 engine runs on several host computers –
Member
CS
Member
CS
Member
Member
CS
Integrated cluster services –
CS
– Cluster Interconnect CS
2nd CF
CS
Log
Log
Log
Shared Storage Access
Log
Co-operate with each other to provide coherent access to the database from any member
Primary CF
Failure detection, recovery automation, cluster file system In partnership with STG and Tivoli
Low latency, high speed interconnect –
Special optimizations provide significant advantages on RDMA-capable interconnects (eg. Infiniband)
Cluster Caching Facility (CF) – –
Efficient global locking and buffer management Synchronous duplexing to secondary ensures availability
Data sharing architecture Shared Database
– – – –
Stores data in a DB2 built-in cluster file system (GPFS) Shared access to database Members write to their own logs on shared disk Logs accessible from another host (used during recovery) © 2010 IBM Corporation
IBM DB2 optimized for SAP
Evaluation of DB2 pureScale with SAP Applications End users
•
Can use SAP log-on groups to direct similar work to same set of servers
SAP application servers
• Central Services
Application Servers
Application Servers
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
•
Cluster Services
Member 1
Cluster Caching Facility
Member 2
Member n
High speed interconnect
• •
Shared Disks
39
•
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
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Unplanned Outages of DB2 Members Failure of a DB2 member
X
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
• •
100%
Data in-flight on failed member
Member restart
Data availability
40
•
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
time
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Unplanned Outages of Cluster Caching Facility Failure of primary cluster caching facility
x
• •
Secondary cluster caching facility takes over
•
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
• • •
41
Very short period (typically seconds) where CF service is suspended during switchover to secondary
Likely not perceived (very short hiccup) No loss of in-flight transactions Failed cluster caching facility will automatically be brought up as secondary once its home host becomes available again
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Planned Outages Maintenance of a DB2 member • Transactions are transparently drained out from the •
X
•
X
•
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
•
100%
• Data remains fully available
• Data availability
42
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
time
© 2010 IBM Corporation
IBM DB2 optimized for SAP
DB2 pureScale Connectivity Setup Overview Centralized connectivity setup
• Every SAP application server has a • db2dsdriver.cfg Application Server 1
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
• •
Application Server 2
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
Cluster Caching Facility
Member 1
Member 2
• Applies to AS ABAP and AS Java Two types of connectivity setups
• Simple, out-of-the-box configuration: Shared Disks
43
•
DB2 managed round-robin assignment User-defined setup for advanced DBAs
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Round-robin Connectivity Setup
44
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 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
sap_as_3
member_3
member_1
member_2 © 2010 IBM Corporation
IBM DB2 optimized for SAP
DB2 PureScale SAPINST integration
45
© 2010 IBM Corporation
IBM DB2 optimized for SAP
DB2 pureScale in SAP DBA Cockpit pureScale in DBA Cockpit
• No changes required for existing •
screens pureScale members are visible in all existing DBA Cockpit screens like DPF partitions
DB2 pureScale
• Cluster status • Cluster performance • Group bufferpool and local • • • • 46
bufferpool metrics Package cache extensions Cluster caching facility Page contention analysis Client affinity display and reload
© 2010 IBM Corporation
IBM DB2 optimized for SAP
IBM DB2 for SAP Micro Outage feature •
•
•
IBM DB2 for SAP Micro Outage opens small maintenance window with limited impact on the SAP application SAP application and IBM DB2 remain online
Technical Implementation – Create empty db6_dbsl_quiesce_def_connections file in DIR_GLOBAL – Change of any DB6 profile parameters in SAP as trigger to start SAP Micro Outage – Check IBM DB2 active connections – Start maintenance activities if there is no active connection – Delete the db6_dbsl_quiesce_def_connections file Maintenance window duration specified by: rdisp/max_wprun_time
Source: If applicable, describe source origin 47
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Micro Outage feature (MOF) scenarios MOF (Note 1434153)
Graceful Maintenance Tool (GMT) SAP Note 1530812 Wrapper around MOF Checks system for errors and activates MOF + exit script
Graceful Cluster Switch Clean failover in HADR environment
© 2010 IBM Corporation © SAP 2010 / Page 48
IBM DB2 optimized for SAP
SAP Cluster Setup Tool Graceful Cluster Switch Graceful Cluster Switch – Automated, planned HADR database takeover with minimal system outage • significantly reduces the number of rolled back transactions • or even provides full transparent failover – Based on micro outage feature in the SAP DB2 for LUW DBSL Limitations – Long running database transactions: • Cluster switch has to be performed as fast as possible and in maximum processing time for dialog processes (profile paramter rdisp/max_wp_runtime, default: 300 seconds) • Short running transactions are blocked at transaction boundary • Long running transactions must be terminated (rolled back) to initialize the takeover – SAP NetWeaver ABAP servers only
© 2010 IBM Corporation © SAP 2010 / Page 49
IBM DB2 optimized for SAP
Graceful Cluster Switch / Micro Outage: 1. Check Prerequisites SAP NetWeaver ABAP
Application Servers
SAP kernel version 6.40 or higher
SAP DB2 for LUW DBSL: “DB6: patch collection 03/10“ (SAP Notes 1434153 and 1447436)
SAP remote enabled functions „DB6_GCS_ACTIVATE“ and „DB6_GCS_NOTIFY“ (SAP Note 1443426)
Application Servers
IBM DB2 for LUW HADR
Cluster Services
Primary
Standby
Check for long running transactions
Check HADR state is “Peer”
Check HADR log gap is not too high
Graceful Cluster Switch
Disks
db2sapcluster.sh v4.01 (SAP Note 960843)
Disks
Manual Micro Outage and Graceful Cluster Switch
Manual Micro Outage only
Graceful Cluster Switch only © 2010 IBM Corporation
© SAP 2010 / Page 50
IBM DB2 optimized for SAP
Graceful Cluster Switch / Micro Outage: 2. DBSL Micro Outage Close Connections SAP Applications
SAP applications with short running database transactions are frozen but not aborted
SAP DBSL for LUW Micro Outage Application Servers
Application Servers
Graceful Cluster Switch
HADR
Cluster Services
Primary
Disks
Close all database connections at transaction boundary
If still database connections are open after timeout
Standby
Overview is generated to decide if transactions should be terminated or graceful cluster switch should be aborted
Disks
Manual Micro Outage and Graceful Cluster Switch
Manual Micro Outage only
Graceful Cluster Switch only © 2010 IBM Corporation
© SAP 2010 / Page 51
IBM DB2 optimized for SAP
Graceful Cluster Switch / Micro Outage: 3. Database Maintenance Cluster Takeover
Application Servers
Application Servers
HADR
SAP Cluster Setup Tool
Cluster Services
Standby
Disks
Automated switch of DB2 HADR cluster roles
Primary
Disks
Manual Micro Outage and Graceful Cluster Switch
Manual Micro Outage only
Graceful Cluster Switch only © 2010 IBM Corporation
© SAP 2010 / Page 52
IBM DB2 optimized for SAP
Graceful Cluster Switch / Micro Outage: 4. Disable DBSL Micro Outage Disable SAP DBSL Micro Outage
Remove quiesce file: rm -f
/usr/sap//SYS/global/
db6_dbsl_quiesce_def_connections
Application Servers
SAP work processes scan each 60 seconds if file still exists. If control file is removed they re-establish the database connection and unfreeze the SAP applications.
Application Servers
HADR
Cluster Services
Standby
Disks
Primary
Disks
Manual Micro Outage and Graceful Cluster Switch
Manual Micro Outage only
Graceful Cluster Switch only © 2010 IBM Corporation
© SAP 2010 / Page 53
Summary
© 2010 IBM Corporation
IBM DB2 optimized for SAP
SAP on DB2 Key Technology Differentiators Selected SAP on DB2 differentiators: – DBACockpit – since R/3 4.6C – DB2_WORKLOAD=SAP – DB2 Compression – SAP on DB2 virtual tables – DB2 Integrated HA – DB2 Automatic Maintenance – DB2 Workload Management – Online Table Reorg – DB6CONV – DB2 Database Partitioning Feature – DB2 Multidimensional Clustering – DB2 in SAP‘s Database Performance Warehouse – SAP NetWeaver BW Nearline Storage on DB2 Not an exhaustive list - more information about SAP on DB2 in SDN.
55
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Important SAP customers migrate to DB2 Coca Cola, US PepsiCo, US Colgate, US Eli Lilly, US Fiat, Italy Barilla, Italy Ciba, Switzerland Pacific Corp, US SONY, Japan Carlsberg Breweries, Denmark Ericsson, Sweden Pilkington, Germany Faurecia, France LSI, US Stada, Germany Australian Wheat Board Netcare, South Africa
56
2. listopad 2010
Agrofert, Czech Rep Austrian Railways, Austria IDS Scheer Samsung, Korea Allianz, Germany Dansk Supermarket, Denmark Gieseke&Devrient, Germany Karstadt Itellium, Germany INA Schaeffler, Germany Modello, Mexico Austrian Railroad, Austria Mahle, Germany Telmex, Mexico Tellabs, US Orica, Australia Ducati, Italy Baywa, Germany Eurovia, France
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Chosen SAP DB2 customers in the Czech Republic Agrofert Holding, a.s. Veletrhy Brno, a.s. Vysoká škola báňská Mitas, a.s. Agrotec, a.s. HP Tronic Zlín, s.r.o. Česká zbrojovka, a.s. FAST ČR, a.s. VOKD, a.s. Styrotrade, a.s. Lias Vintířov GC System, a.s. Explosia, a.s. Svoboda Press, a.s. T.E.S. Elektronika, a.s. 57
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Development Skill Transfer E-Learning Expert Sessions on SAP with IBM DB2: http://www.sdn.sap.com/irj/sdn/db6?rid=/webcontent/uuid/400c5e34-c601-2c10-6cb4-9aff67ca31c3 Regular updates with newest topics from the Platform Development and Center of Excellence team, i.e.: – Monitoring and Administration with SAP on IBM DB2 - DB6CONV V5.00 – Performance Optimization with SAP on IBM DB2 - Key Performance Indicators – IBM DB2 Near-Line Storage Solution for SAP NetWeaver BW
Source: If applicable, describe source origin 58
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Additional Information News, Blogs, Backgrounds, Docs: https://www.sdn.sap.com/irj/sdn/db6 Discussion Forum: https://www.sdn.sap.com/irj/sdn/forum?forumID=187
Important SAP notes: http://goo.gl/XZT5E Remote Expert Sessions: http://goo.gl/mrrQn DB2 compression best practise: http://goo.gl/l88Of DB2 MDC best practise: http://goo.gl/LdzAE
IBM SAP DB2 Experts Wiki http://www.ibm.com/solutions/sap/us/detail/landing/J233701A22235G06.html IBM DB2 optimized for your SAP software: Customer reference stories, white papers, ... http://www.ibm.com/solutions/sap/us/detail/landing/J233701A22235G06.html Source: If applicable, describe source origin 59
2. listopad 2010
© 2010 IBM Corporation
IBM DB2 optimized for SAP
Hot Off the Press !! Get your copy now ..
60
2. listopad 2010
DOWNLOAD NOW !! http://bit.ly/DB2_SAP_PDF © 2010 IBM Corporation
IBM DB2 optimized for SAP
Koho kontaktovat?
Jiří Skoumal
[email protected]
61
2. listopad 2010
© 2010 IBM Corporation
[email protected]
Source: If applicable, describe source origin © 2010 IBM Corporation