SAP on Oracle:
Development Update February 2011
Dr. Christian GrafDevelopment ManagerDB Platforms Oracle & InformixOS Platforms SolarisSAP AG
© SAP 2010, Development Update SAP on Oracle, Page 2
Agenda
Oracle 11g Roadmap @ SAP
DBA Tools
Oracle 10g @SAP
New SAP/Oracle Patch Concept
© SAP 2010, Development Update SAP on Oracle, Page 3
Agenda
Oracle 11g Roadmap @ SAP
DBA Tools
Oracle 10g @SAP
New SAP/Oracle Patch Concept
© SAP 2010, Development Update SAP on Oracle, Page 4
SAP on Oracle 10g: Supported Releases
Patchset 10.2.0.4 is supported on ALL OS platforms
Additional necessary patches on top of 10.2.0.4 will be released monthly (at every10th of each month) through special SAP Patch Bundle
All 10.2.0.4 PSUs from PSU 4 on are available
Patchset 10.2.0.5 was released on Nov 10th for major OS platforms
Nov 10th SAP Patch Bundle includes first PSU of 10.2.0.5 (10.2.0.5.1)
Planned 2011: HPUX PA-RISC (March) , Linux & Windows Itanium
Oracle 10.2 adoption rate: ~ 90 % of SAP/Oracle customers are on 10g
© SAP 2010, Development Update SAP on Oracle, Page 5
Oracle Announcement 10g support
In May 2009 Oracle announced that Extended Support fees for Oracleversion 10.2 are waived for first year
No extra charged support for Oracle 10.2 until July 2011
Extended Support will be available for version 10.2.0.5 only until mid 2013Grace Period: 10.2.0.4 receives support until end of April 2011
For details see SAP Note 1339724
Specific Oracle 10.2 Extended Support note is in preparation
Conditions will be similar to Oracle 9.2 Extended Support(see SAP note 1110995)
© SAP 2010, Development Update SAP on Oracle, Page 6
Agenda
Oracle 11g Roadmap @ SAP
DBA Tools
Oracle 10g @SAP
New SAP/Oracle Patch Concept
© SAP 2010, Development Update SAP on Oracle, Page 7
This only affects Unix/Linux-platforms! Windows platforms are not affected.
Starting with Oracle patchset 10.2.0.4 Oracle provides socalled Patch SetUpdates (PSU)
A PSU is a collection of important fixes encountered by Oracle customers
Oracle releases a new PSU every three months
The PSUs will contain the Critical Patch Updates (CPU)(Oracle CPU concept will vanish)
PSUs must be applied on top of an already installed Patch Set
New Oracle Patch Concept:Patch Set Updates (PSUs)
© SAP 2010, Development Update SAP on Oracle, Page 8
Oracle database patches for Unix-platforms are now delivered in form of so-called SAP Bundle Patches (SBP)
– Initial Oracle versions: 10.2.0.4.4 & 11.2.0.1.1
A SBP consists of:– Current Patch Set Update (PSU)– SAP specific necessary Single- and Merge-Patches which are not contained in the PSU– Current SAP specific Optimizer-Merge-Patch– README.html: installation manual for SBP– bugs_fixed.html: list of patches contained in SBP
SBPs are cumulative. The next SBP will contain all previous patches and thenew patches in addition.Notation of SBPs:
SAP_<Oracle-version>_<YYYYMM>_<plattform>.zipExample: SAP_102044_201004_AIX.zip
For the installation you'll need MOPatch Version 2.1.1 or higherFor more details please see SAP note 1027012
New SAP/Oracle Patch Concept:SAP Patch Bundles & Patch Set Updates (PSUs)
© SAP 2010, Development Update SAP on Oracle, Page 9
Agenda
Oracle 11g Roadmap @ SAP
DBA Tools
Oracle 10g @SAP
New SAP/Oracle Patch Concept
SAP only certifies Oracle Database 11g Release 2
Only SAP products based on 6.40_EX2 kernel and later get certified with 11.211.2 support only for SAP products which are in SAP Extended Maintenance at least until the end of 2010
SAP 11.2 certification and Rollout happens in three OS waves (due to availability from Oracle)
SAP 11.2 certification happens in three stages:
Stage1: Runtime certificationAllows 11.2 database upgrade of existing SAP systems
Stage 2: SAP Upgrade and Enhancement Package Update certificationAllows SAP Upgrades and Enhancment Package Updates of Oracle 11.2 based SAP systems
Stage 3: Support for Oracle 11.2 based direct SAP installations (incl. Unicode Migration)Allows direct SAP system installations with Oracle 11.2
11g Rollout Schedule
11g11g
© SAP 2010, Development Update SAP on Oracle, Page 11
First wave was released on March 31st 2010Major UNIX platforms (AIX, HP-UX IA64, Solaris SPARC & x64) and Linux x64As of today ‚runtime certification‘ and upgrade certification (Stage 1 & 2)Stage 3: Released for NW 6.40, 7.00, 7.01 based products & PI, MI, Banking 7.10/11/20,
CE 7.20
Second wave was released on June 9th 2010.Covers Windows x86/x64 and HP-UX PA RISC.As of today ‚runtime certification‘ and upgrade certification (Stage 1 & 2)Stage 3: Released for NW 6.40, 7.00, 7.01 based products & PI, MI, Banking 7.10/11/20,
CE 7.20
Third wave will cover remaining OS platforms (planned for 2011)Windows IA64Linux on Power: Oracle has not yet decided about support Status ‚TBD‘Linux IA64: Desupported by Oracle. Last Oracle version will be 10.2.0.5
For current status please see SAP note 1398634
11g Rollout Schedule
11g11g
© SAP 2010, Development Update SAP on Oracle, Page 12
PSU 1 of 11.2.0.1 (11.2.0.1.1) released through June 10th SAP Patch Bundle
PSU 2 of 11.2.0.1 (11.2.0.1.2) released through September 10th SAP Patch Bundle
11.2.0.2 (first 11.2 patchset) was (pilot) released on November 10th via SAP Patch
Bundle
General Availability since mid January 2011
All OS platforms except Windows IA64
New SAP projects should start with 11.2.0.2 only
11.2 Patchset/PSU Schedule by SAP
11g11g
© SAP 2010, Development Update SAP on Oracle, Page 13
Advanced CompressionOLTP compressionSecurefile compressionRMAN Backup compressionData Guard Network compressionData Pump Export compressionLicense for ACO required
SAP ASFU license includes ACO
Index CompressionAlready supported by SAP (since version 10g)No additional license required
11g News for SAPOracle Feature Availability (with 11.2 SAP GA) – Space (I)
© SAP 2010 Development Update SAP on Oracle, Page 14
Dictionary-Only Add ColumnVery common operation within SAP BW application and SAP UpgradesFactor 10-20 performance improvement for SAP BW during add column processesSaves large amount of disk space
Deferred Segment CreationEmpty database objects will not consume any disk spaceVery important for SAP environments as 60-70% of all tables, lobs, indexes andpartitions in an SAP installation are empty
Saves disk spaceImproves query response times on space objects in Oracle Data DictionaryMakes database install part for SAP a lot faster
- Creation of empty tables, lobs, indexes and partitions are dramatically faster
11g News for SAPOracle Feature Availability (with 11.2 SAP GA) – Space (II)
© SAP 2010, Development Update SAP on Oracle, Page 15
Overview space savings with ACO on customer production databases
11g News for SAPOracle Feature Availability (with 11.2 SAP GA) – Space (III)
WithoutCompression
With compressionand other spaceoptimizations
FACTOR
Space Savings
Database (fully reorganized)
ECC 6.0
BI 7.0
CRM 7.0
4,782 GB
1,413 GB
950 GB
1,976 GB
543 GB
334 GB
2.4
2.6
2.8RMAN Backup (forcompressed database)
2,817 GB 667 GB 4.2
Export Data Pump 973 GB 156 GB 6.2
© SAP 2010, Development Update SAP on Oracle, Page 16
Performance Impact when using ACO on production database- Measured through Capture Replay Functionality of Real Application Testing Option
- 10.2.0.4 production workload was captured for more than 2 days
- No impact on production database during capture
Results:
- Factor 2.2 Space Savings
- 60% less physical reads
- 5% less physical writes
- 10% better database cache hit rate
- 30% higher redo rate
- No overhead in CPU consumption
11g News for SAPOracle Feature Availability (with 11.2 SAP GA) – Space (IV)
© SAP 2010, Development Update SAP on Oracle, Page 17
Implementation Guidelines for Compression Technologies in SAP Environments1. Start with Index Compression
- Improves R/3 Performance the most as all database access in R/3environments is index based, especially index range scans
- Up to 20% disk space reduction for complete database2. Implement OLTP Table Compression
- No real query performance benefit in R/3 environments- Provides very good disk space savings
3. Implement SecureFiles Compression- Very important for SAP Applications like CRM or XI who store large
(uncompressed) amount of data in LOBs.4. RMAN Backup Compression
- Additional disk space savings (even if database tables and indexes are alreadycompressed)
11g News for SAPOracle Feature Availability (with 11.2 SAP GA) – Space (V)
© SAP 2010, Development Update SAP on Oracle, Page 18
Securefiles
Significantly faster access times compared to LOBs in SAP environmentsIncreased transaction throughput on SAP cluster tables especially with RACPrerequisite for compression of SAP tables containing LOBs
11g News for SAPOracle Feature Availability (with 11.2 SAP GA) – Performance (I)
SAP VBDATA Throughput (Insert/Read/Delete)
0
0,5
1
1,5
2
2,5
1 2 4 8 16 32 64
row size in KB
Per
form
ance
Impr
ovem
ent F
acto
r
LONGs (9.2,10.2) LOBs (10.2,11.2) Securefiles 11.2
© SAP 2010, Development Update SAP on Oracle, Page 19
DirectNFS
Increases database throughput up to 50% in NAS environments with multiple NICsNAS Storage such as NetApp have become very popular in SAP environmentsdue to high flexibility, ease-of-use and NFS
– Very common in Linux environments. Ideal for Linux/RAC.– SAP and Oracle use NetApp for most development and operational systems
Up to 20% CPU savings on database server due to integrated NFS client in OraclekernelSuperior to any bonding solution – Faster and EasierBetter troughput than most SAN solutionsHighly available. Multiple network cards can be used between database server andNAS
11g News for SAPOracle Feature Availability (with 11.2 SAP GA) – Performance (II)
© SAP 2010, Development Update SAP on Oracle, Page 20
Database Vault 11.2 (separate license required)
EncryptionTablespace EncryptionSecurefile EncryptionRMAN Backup EncryptionExpdp EncryptionData Guard Secure Redo Transport
11g News for SAPOracle Feature Availability (with 11.2 SAP GA) – Security
All encryption functionality requires license for Advanced Security Option
ASO license is included in SAP ASFU license scope
© SAP 2010, Development Update SAP on Oracle, Page 21
Oracle RAC 11.2
New RAC 11.2 for SAP White Paper available on SDN
New SAPCTL Version 5.2 available to manage and control SAP critical resources throughOracle Clusterware
Old SAPCTL versions 4.x will not work with Oracle Clusterware 11.2
RAC 11.2 available on all UNIX and Linux platforms (for all SAP 6.40_EX2 kernels and up)
Supports the option to put OCR and voting disks on ASMNew RAC 11.2 installations onlyUpgrades from RAC 10.2 must still use shared filesystems for OCR and voting disks
Oracle Clusterware 11.2 now installed locally per nodeSame supported technology stacks defined in SAP Note 527843 stay in place
Cluster Filesystem or NAS NFSShared Oracle_HomesDatabase (data, control, redo, undo, archive, flashback)/sapmntOCR and voting disks (upgrades from RAC 10.2 or not using ASM)
Same versions for Clusterware and RDBMS softwareDifferent and improved network configuration required for Clusterware 11.2
© SAP 2010, Development Update SAP on Oracle, Page 22
ASM & ACFS is supported for Unix/Linux OS platforms with Oracleversion 11.2.0.2 ff since CW5/2011
Windows support planned during Q2/2011
ASM & ACFS support is provided for SAP releases that are supported withOracle version 11.2.0.2 or higher (SAP Kernel 6.40 or higher)
Oracle Grid release 11.2.0.2 or higher required
Single Instance and RAC support
ACFS required for RAC installations with ASM (not available on HPUX)
BR*Tools support is not yet completeMinimum BR*Tools 7.20 PL 12 required (see SAP note 1428529)
Backup/Restore support planned until end Q1/2011
‚brspace‘ support planned during Q2/2011
Direct SAP installation support with ASM is not yet available. An Oracle toolsbased migration of an existing system to ASM is required.
For more details (White Papers, etc.) please see SAP note 1550133
11g : Oracle ASM support for SAP
© SAP 2010, Development Update SAP on Oracle, Page 23
Oracle Exadata X2 / Database Machine support planned for mid 2011Linux x64 & SolarisFor Linux Oracle Linux (OL) mandatory for Exadata X2Oracle 11.2.0.2 ff required
11g PlansFeature/Product Availability planned for 2011
© SAP 2010, Development Update SAP on Oracle, Page 24
Agenda
Oracle 11g Roadmap @ SAP
DBA Tools
Oracle 10g @SAP
New SAP/Oracle Patch Concept
© SAP 2010, Development Update SAP on Oracle, Page 25
Partitioning Tools for SAP/Oracle non-BI systems
Motivation
Archiving of historical application data in SAP systems is a big challenge:
Archiving is a continuous process and generates significant system load
Archiving increases index and table fragmentation; reorganization of indexes and/ortables is a time- and resource-critical process
Range partitioning can be used to separate historical and current production data in order tominimize the above impacts
Problem: Application tables usually do not have a direct time dependent column in theprimary key
An alternative is to use an indirect time related column like document number, whichexists in large application tables and is usually part of the primary key
Defining suitable ranges based on document number is difficult
Transformation of an unpartitioned table into a partitioned one can be done online withOracle Table Redefinition package, but this is not a simple admin task
© SAP 2010 Development Update SAP on Oracle, Page 26
Full Integration of Range Partitioning into SAP OLTP products (e.g. ERP)
Partitioning Engine offers a predefined set of around 30 application tables to be partitionedbased on time based criteria
Existing non-partitioned tables will be converted through ABAP/SAP BR*Tools taskPartition Maintenance is fully automated through internal SAP SM37 job (no needfor DBA intervention)
PrerequisitesSAP systems based on 6.20 WebAS release and higher. Examples:
SAP ECC 5.0, ECC 6.0, Business Suite 7Requires minimum ABAP Basis Support Package (SP) level:
6.20 SP67, 6.40 SP25, 7.00 SP21, 7.01 SP 06, 7.10 SP 09, 7.11 SP04
BR*Tools 7.10 Patch 24 and higherOracle 10.2.0.4 and higher
General SAP support of Partitioning Engine started with availability of above mentionedSupport Packages
Entry point for interested customers: SAP Note 1333328
SAP Partitioning Engine (in a nutshell)
© SAP 2008, Development Update SAP on Oracle, Page 27
New Oracle 11g Features supported byBR*Tools 7.20 (1)
Online conversion to new SecureFile LobsImplemented as new action ‘lob2lob’ within BRSPACE reorganizationLob compression can be activated with the same actionCan be done only ‘online’ (by redefinition), not offline (by move/alter)
Support for the new table compression ‘FOR OLTP’The feature can be activated during table reorganization by BRSPACETable and Lob compression can be enabled at the same time
Support for the new features of Oracle 11g Data PumpComplete compression of the data in export dump filesComplete encryption of the data in export dump filesExport of individual tables from different schemas
Tablespace compression and encryptionAllows to set compression and encryption attributes at tablespace level
© SAP 2008, Development Update SAP on Oracle, Page 28
New Oracle 11g Features supported byBR*Tools 7.20 (2)
New features in the area of data encryption (TDE)Changing the Wallet password using ‘orapki’ utilityOpening the Oracle Wallet in the database mount statusPassword protection for closing the Oracle Wallet
Improvement in database reset/PIT recovery using flashbackIncreases the reliability of the determination of archivelog files needed
Cleaning up new Oracle 11g trace files in diagnostic directoriesBased on new Oracle 11g parameter ‘diagnostic_dest’Aware of new Oracle 11g trace file types, e.g. incident files
For more info see:SAP note 1430669 - BR*Tools support for Oracle 11gSAP note 1431296 - LOB conversion and table compression with BRSPACE 7.20SAP note 1428529 - Corrections in BR*Tools Version 7.20
© SAP 2010, Development Update SAP on Oracle, Page 29
SAP on Oracle live in SDN
SAP on Oracle forum:https://www.sdn.sap.com/irj/sdn/collaboration
-> Database & OS Platforms -> SAP on Oracle
SAP on Oracle content page:https://www.sdn.sap.com/irj/sdn/ora
-> SAP on Oracle
© SAP 2009, Development Update SAP on Oracle, Page 30
SDN Homepage: www.sdn.sap.com/irj/sdn/ora
© SAP 2011, Development Update SAP on Oracle, Page 31
SAP on Oracle: Twitter and FacebookTwitter: http://twitter.com/#!/SAPonOracle
Facebook: http://www.facebook.com/pages/SAP-on-Oracle/152816644759585
© SAP 2010, Development Update SAP on Oracle, Page 32
Thank you very much
for your attention!
Thank you!
© SAP 2010, Development Update SAP on Oracle, Page 33
Copyright 2010 SAP AGAll rights reserved
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 changedwithout prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned andassociated logos displayed 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. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains 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. 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, orother 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 ofmerchantability, 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 limitationshall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.Alle Rechte vorbehalten.