Oracle 12c Database In-Memory, 12c Advanced Compression, 12c Active Data Guard, 12c Backup and Recovery, 12c ACFS Support, 12c Performance, 12c Manageability and Availability, 12c Core Data Services, 12c Flat Cubes, 12c HANFS Technology Update

T E C H N O L O G Y U P D A T E

®

No. 25 Oracle for SAP, July 2016 www.oracle.com/sap

2

D E A R S A P C U S T O M E R ,

Oracle provides the world’s most complete, open, and integrated technology stack including database, business software, operating systems, servers, and storage.

Oracle technologies make SAP applications run better.

The relationship of Oracle Corporation and SAP SE has been based on our long history, a rich heritage of joint developments and a bright future – for the benefit of mutual customers.

Oracle will support SAP Business Suite and SAP BW as long as SAP will be supporting them. As per SAP Note 1951491, with SAP NetWeaver 7.4 SP08, SAP is introducing innovation to take advantage of new technical capabilities of the Oracle Database platform

(i.e. Core Data Services) and Oracle Database In-Memory (SAP Note 2178980), and SAP BW optimized InfoCubes/Flat Cubes.

Both companies have had an ongoing commitment to our tens of thousands of joint customers for over 28 years.

Our longstanding reseller and support agreements provide enhanced access to Oracle Database technology and world class customer support. The Oracle product strategy provides flexibility and choice across the IT infrastructure. A growing majority of mid-size to the largest SAP enterprise customers, in every industry, entrust their application deployments to the Oracle

Database.

By choosing the Oracle Database and Database options, SAP customers significantly benefit through the ongoing innovations without disruption. By taking a closer look, at least eight differentiators have been identified which will explain in detail why the Oracle Database is the first choice for running SAP applications. They bring best performance and scalability, deployment flexibility, availability, reliability, disaster recovery, security, manageability, self management, support for very large databases, support for database consolidation and the integration of hardware and software. All SAP customers can enjoy the benefits of the features and functions of the Oracle Database to cost optimize their SAP deployments.

The following Oracle Database 12c options are SAP certified and available:

- Oracle Database In-Memory

- Information Lifecycle Management (ILM) /Automatic Data Optimization (ADO)

- Hybrid Columnar Compression (HCC) for Oracle Exadata and Oracle SuperCluster in conjunction with ILM

- Oracle Multitenant option

The Oracle Exadata Database Machine is engineered to consolidate all of your SAP and non-SAP Databases into a private

Database Cloud environment. It delivers the highest performance and most available platform for running the private

Oracle Database Cloud for all types of database workloads; including both Online Transaction Processing (e.g. SAP ECC 6.0), and Data Warehousing (e.g. SAP BW 7.0 and higher). The Exadata Database Machine is ready to tackle your largest and most important database workload – and often run them up to 10 times faster or more – deployed by a large number of

SAP customers today.

Oracle SuperCluster is the first general-purpose engineered system that combines the computing power of the new SPARC processor, the performance and scalability of Oracle Solaris 11, the optimized database performance of Oracle Exadata storage, and the optimized runtime for SAP kernel 6.40 and higher.

Oracle MiniCluster is an extremely simple and efficient engineered system designed to run enterprise databases and applications with uncompromising security.

Oracle redefines the economics of enterprise computing with a complete refresh and expansion of its SPARC M7,

T7 and S7 server portfolio providing customers the industry’s best value with leading price/performance.

Oracle provides a complete IT database and infrastructure stack to run SAP applications

3

Oracle Exalogic Elastic Cloud delivers virtually unlimited scalability, unbeatable performance, and previously unimagined management simplicity to SAP and non-SAP applications in combination with Oracle Exadata

Database Machine.

Oracle Private Cloud Appliance is an engineered system that radically simplifies the way customers install, deploy, and manage converged infrastructures, which can be used as virtualization platform for database and application.

The Oracle Database Appliance is a new way to take advantage of the world’s most popular Oracle Database, in a single, easy-to-deploy and -manage system. It’s a complete package of software, server, storage, HA and networking that’s engineered for simplicity; saving time and money by simplifying deployment, maintenance, and support of database workloads.

Oracle Linux 7 is the latest Linux version of Oracle for your SAP infrastructure computing needs. It is fast – delivers best performance for SAP – is up to date – brings the latest innovations to customers; is reliable – provides data integrity, better security, and improved application uptime; and is optimized for Oracle Databases underneath SAP.

Oracle VM Server for x86 is a free server virtualization solution that makes SAP and other enterprise applications easier to deploy, manage, and support.

The Oracle development teams on site at SAP SE in Walldorf, Germany continue to work together with SAP developers to ensure that SAP customers will always have access to the latest optimized Oracle technologies ensuring performance, reliability and innovation.

The Oracle for SAP Service & Support team offers Advanced Customer Services (ACS) that include health checks, workshops, database migrations, performance, tuning and ACS Oracle Solaris Services for SAP environments, including Assisted Services Engagements (Analysis/Enhancement and SAP Readiness Service for IT Infrastructure).

For more information or to see current and previous editions go to:

www.oracle.com/sap

We welcome your comments and questions. Please contact us at:

[email protected]

Sincerely,

Gerhard Kuppler

Vice President SAP Alliances

Oracle Corporation

Oracle Corporation: With more than 420,000 customers – including 100 of the Fortune 100 – and with deployments across a wide variety of industries in more than 145 countries, Oracle offers a comprehensive and fully integrated stack of cloud applications, platform services, and engineered systems, more than 25,000 partners worldwide, more than 130,000 employees, including 37,000 developers and engineers, 18,000 support personnel and 17,000 consulting experts.

4

C O N T E N T S

49

51

54

55

56

59

61

62

67

2-3

5

17

36

41

42

44

46

70

72

74

78

79

83

Editorial

Oracle Database 12c for SAP: Latest Database Technology and Support for Application Optimizations

Implementing a Data Management Infrastructure for SAP with Oracle Database Options and Packs

Why Oracle Database and Engineered Systems for SAP?

New ! 130,000 SAP SD Benchmark Users on Oracle SPARC M7-8 Server has been certified by SAP

New World Record ! SAP SD 130,000 Benchmark Users on Oracle SPARC M7-8 Server with Oracle 12c

Major Improvement in SAP CRM use with Oracle Database In-Memory at Bosch GmbH

Oracle Database In-Memory at Villeroy & Boch

SAP BI with Oracle Database In-Memory at DB Austria

Oracle Advanced Compression at Goodman Fielder, Australia

ElectraNet Gains Better Business Insight with Oracle Engineered Systems

Oracle Exadata Database Machine at Solvi Group, Brazil

Wumart Stores, China: Large SAP Cross Platform online System Migration with Oracle Golden Gate

Oracle SuperCluster at CELSA Group

Oracle Exadata at Lenta, Russia

Mission Critical Support Services for SAP Customers

Oracle SuperCluster M7 for SAP Customers

SAP Customers benefiting from Oracle Exadata Technology

High Availability for SAP Resources by SAPCTL

Engineered for innovation, efficiency and simplicity: Oracle engineered systems for SAP

What will the migration to S/4 HANA cost ?

Oracle DB and ES related Notes for SAP

Imprint

Oracle Database 12c for SAP: Latest Database Technology and Support for Application Optimizations

5

O R A C L E D A T A B A S E 1 2 c F O R S A P :

L A T E S T D A T A B A S E T E C H N O L O G Y A N D S U P P O R T F O R

A P P L I C A T I O N O P T I M I Z A T I O N S

Strategy and Roadmap

Integration Strategy

From the very beginning, the Oracle Database for SAP or SAP on Oracle Database strategy had been based on two pillars. The first pillar is the integration of Oracle

Database features with the SAP environment. The second pillar is the integration of SAP application features with the Oracle database.

The need to integrate Oracle Database features with the SAP

environment has always been visible. It was particularly obvious, whenever Oracle released new database features for which the SAP architecture was not prepared. An example that many customers still remember is the project to integrate Real Application Clusters (RAC) into an

SAP architecture based on the assumption that there can be many SAP Application Server instances, but only one

Database Server instance.

This is by no means a matter of the past. The current plan to make Oracle Multitenant available for SAP customers is a similar architectural revolution and requires no less effort than the RAC certification.

The need to integrate SAP application features with the

Oracle Database, on the other hand, has only rarely been recognized. The classic SAP applications (such as R/3 and

BW) have been developed on the Oracle Database. And when, later on, SAP started to support IBM DB2 and

Microsoft SQL Server as well, they put the least common denominator strategy in place, i.e. they used only those database features that were available in all supported databases. Not much stress, therefore, on the Oracle

Database.

This has changed with the advent of SAP’s own database

(HANA). SAP realized very soon that they had to drop the least common denominator strategy and to change their applications: As long as SAP applications treat

HANA as a database similar to all other databases, it is very difficult to convince customers that there is a benefit in implementing HANA. Therefore SAP has embarked on an application optimization project in order to allow

SAP applications to make use of special HANA features.

“Special HANA features”, however, does not mean

“HANA-only features”. There is nothing in HANA that cannot be done by the Oracle Database as well. Therefore the need to integrate SAP application features with the

Oracle Database has recently become more visible. It is recognized as the need to integrate SAP application optimizations designed with HANA in mind with the Oracle

Database or to support SAP application optimizations by the Oracle Database.

Today, both pillars supporting the SAP on Oracle Database strategy are clearly visible: Whenever Oracle releases a major new database feature, a development effort is needed to integrate it into the SAP architecture as well as the installation, administration and monitoring tools provided by SAP. Whenever SAP releases a new application optimization, a similar development effort is needed to integrate it with the Oracle Database technology.

Certification Roadmap

Standard maintenance for Oracle Database 11g (11.2.0.4) ended on January 31, 2015. The Extended Support phase, which is restricted to three years, has started as of February

2015. For Oracle Database version 11.2.0.4 Oracle offers

Extended Support until May 31, 2017 at no additional cost. (For more information see SAP Note 2098258.)

For the joint benefit of our customer base, Oracle and

SAP agreed to split the certification process into several phases. Segmenting the rollout in stages, allows for the

Oracle Database 12c to be made generally available as early as possible and ensures sufficient overlap with Oracle

Database 11g. Oracle and SAP have broken the “terminal release” custom (certification of release x.2 only; no certification of release x.1) valid for more than 10 years.

• Phase 1, called Base Certification, has already been completed in March 2015. Included are all features and options that have been previously available in

Oracle Database 11g plus several Oracle Database 12c features which are either completely transparent or require only minimal integration effort.

6

• Phase 2, completed in June 2015, is the first to offer a major new Oracle Database 12c option: Oracle Database In-Memory, a completely new option in Oracle

Database 12c.

• Phase 3, completed in December 2015, has added the new Information Lifecycle Management (ILM) features included in Oracle Database 12c Advanced Compression, as well as Hybrid Columnar Compression (HCC) with row-level locking on Oracle Exadata and Oracle Super-

Cluster.

• Phase 4, Oracle Multitenant completed the certification process for SAP customers. This option allows for the consolidation of many databases into a single container database. It is based on a completely new database architecture and therefore requires a considerable

Oracle/SAP integration effort.

5

Theoretically speaking, implementation of Oracle support for SAP application optimizations is an ongoing project that runs completely independent from the Oracle Database

12c certification process. However, in some cases certain

Oracle Database 12c features may be or are required.

• SAP Core Data Services, originally released with SAP

NetWeaver 7.40 (SP 05), is supported with Oracle

Database 11g and Oracle Database 12c. No particular features or options are required. (See SAP Note 1951491)

• Many data model optimizations will originally result in higher disk space requirements. In those cases the use of table compression is certainly not required, but recommended. And as a considerable percentage of the tables involved contain more than 255 columns,

Oracle Database 12c is the only version that allows customers to compress all relevant tables.

• Flat Cubes can only be used with Oracle Database 12c and Oracle Database In-Memory.

Base Certification Features

Advanced Compression

Customers running SAP applications on Oracle Database

11g can already choose from a variety of compression features: Index Key Compression and Compressed Index-

5

Organized Tables (IOTs) are standard database features.

OLTP Compression for structured data and SecureFiles

Compression for unstructured data are provided by Oracle

Database 11g Advanced Compression.

Oracle Database 12c for SAP: Latest Database Technology and Support for Application Optimizations

7

Oracle Database 12c Advanced Compression comes with many new features. Some of them are related to information lifecycle management support, which is available for SAP customers as of certification phase 2. However, there are several Advanced Compression Option features included in phase 1 that can be utilized today within SAP environments:

Advanced Index Compression

is a new form of index compression. Creating or rebuilding an index using Advanced

Index Compression reduces the size of unique and nonunique indexes, while still providing efficient access to the indexes. Benefits include:

• Advanced Index Compression works well on all supported indexes, including those indexes that are not good candidates with the existing Index Key Compression.

• Advanced Index Compression works at the block level to provide the best compression for each block.

This means that users don’t need knowledge of data characteristics – Advanced Index Compression automatically chooses the right compression per block.

Advanced Network Compression

can be used to compress the data to be transmitted at the sending side and then uncompress it at the receiving side to reduce the network traffic. Advanced Network Compression reduces the size of the data to be transmitted over a network connection.

Benefits include:

• Increased effective network throughput: Compression allows transmission of large data in less time. SQL query response becomes faster due to the reduced transmission time.

• Reduced bandwidth utilization: Compression saves bandwidth by reducing the data to be transmitted, allowing other applications to use the freed-up bandwidth. This also helps in reducing the cost of providing network bandwidth.

Advanced Network Compression can only be used if both the Database/Instant Client and the Database Server are upgraded to 12.1.0.2.

For more information about Oracle Database 12c Advanced Compression for SAP Systems see SAP Note

2138262.

Active Data Guard

Data Guard – the functionality needed to set up standby databases – is included in Oracle Database Enterprise

Edition. Active Data Guard is an extra option. In Oracle

Database 11g it offers additional features such as Automatic

Block Repair and Fast Incremental Backup. Active Data

Guard Far Sync, the main new feature with Oracle Database 12c, allows customers to combine high performance

(a characteristic of asynchronous data shipping) and zero data loss (a characteristic of synchronous data shipping) across large distance WANs.

For details see the article “Implementing a Data Management

Infrastructure for SAP with Oracle Database Options and

Packs” (“Data Guard and Active Data Guard” section) on page 25.

Backup and Recovery

Oracle Recovery Manager (RMAN)

provides a comprehensive foundation for efficiently backing up and recovering the

Oracle Database. It is designed to work intimately with the server, providing block-level corruption detection during backup and restore operations. RMAN optimizes performance and space consumption during backup through the use of file multiplexing and backup set compression.

RMAN also integrates with Oracle Secure Backup, as well as third party media management products, for tape backup.

Cross Platform Backup and Restore

enables you to transport data across platforms by using full and incremental backup sets.

The Oracle Database 12c allows you to transport data across platforms using either full or incremental backups, using image copies or backup. To perform cross-platform backups using backup sets, the destination database must be Oracle 12c or later. This newly added feature simplifies platform migration and minimizes read-only downtime on the source database.

While RMAN remains the most popular tool to perform

Oracle Database backups, another commonly used method for taking database backups is to create a storage snapshot of all files in the database. Mount the snapshot on a different server (other than the one that runs the production database) and copy the data to a tertiary storage such as tape, thus offloading the backup processing from the production server.

Storage Snapshot Optimization

enables you to use

8 third-party technologies to take a storage snapshot of your database without the need for putting the database in

BACKUP mode.

Snapshots taken this way are “crash-consistent”, provided the storage product adheres to specific guidelines outlined in Oracle documentation. Crash-consistent backups can be opened and used after undergoing a full crash recovery.

However, they cannot be reliably used for point-in-time

recovery, as the redo logs do not contain sufficient information to remove the data files’ inconsistencies.

Alternatively, snapshots taken in backup mode, i.e.

ALTER DATABASE [BEGIN|END] BACKUP

, remove the point-in-time recovery restriction. However, each database needs to be placed in this mode before the snapshot is taken, and taken out of this mode when the snapshot completes. This complexity is magnified when the procedure must be done for tens, hundreds, or thousands of databases. In addition, during this mode, whole block images are written to redo logs as they are changed, inducing additional I/O activity.

With Oracle Database 12c, the

RECOVER ... SNAPSHOT TIME command, storage snapshots taken without the database in backup mode can be recovered in one step, whether to the current time or a specific point-in-time after the snapshot was taken, without any additional procedures.

By supporting all types of recovery operations using these snapshots, this optimization effectively eliminates the need for backup mode and its associated complexity and overhead, freeing the DBA‘s time to focus on more critical production tasks.

ACFS Support

If you work with Exadata, you are probably aware that

ACFS has not been supported until now.

ACFS is now supported on Exadata

, if you are running Grid Infrastructure version 12.1.0.2 or later. In SAP environments this can be used for SAP shared file systems (

/sapmnt,

etc.).

However, it is not meant as an alternative for running databases on ASM. Oracle Databases have to stay on ASM using the Exadata Storage nodes. This is the only supported configuration.

High Availability Network File Storage (HANFS)

for Oracle

Grid Infrastructure provides uninterrupted service of

NFS V2/V3 exported paths by exposing NFS exports on

Highly Available Virtual IPs (HAVIP) and using Oracle

Clusterware agents to ensure that the HAVIPs and NFS exports are always online. If a cluster node fails, the

HAVIP and NFS exports are automatically migrated to a surviving node.

The HANFS feature enables highly available NFS servers to be configured using Oracle ACFS clusters. The HANFS cluster configurations may be built from your existing infrastructure or commodity servers and storage. This provides network services similar to ‘network filer’ at a fraction of the cost.

Performance

The UNION and UNION ALL operators in SQL statements connect two or more branches (e.g. subqueries):

<branch1> UNION <branch2>. Traditionally, in queries of this type, the branches execute one after another, meaning that only one branch is executed at a certain point in time, followed by the next branch, and so on in a serial manner. Oracle Database 12c introduces

Concurrent

Execution of Union and Union All Branches

, meaning that one set of parallel servers will be executing one branch, a second set of parallel servers will be executing a different branch, and so on, all at the same time.

The ability to parallelize these branches will lead to much faster statement execution. In particular, it will improve SAP BW performance.

Manageability and Availability

Database administrators can now perform a variety of additional reorganization operations online using BR*Tools:

Online Move Partition

: Starting with Oracle Database 12c, the

ALTER TABLE ... MOVE PARTITION operation functions as a non-blocking online DDL command, while DML operations continue to execute uninterrupted on the partition that is being moved. Additionally, global indexes are maintained when a partition is moved, so that a manual index rebuild is no longer required.

Oracle Database 12c for SAP: Latest Database Technology and Support for Application Optimizations

9

Move Datafile Online:

Prior to Oracle Database 12c, moving datafiles has always been an offline task. There were certain techniques you could employ to minimize that downtime, but you couldn‘t prevent it completely. Oracle

Database 12c includes an enhancement to the

ALTER

DATABASE

command to allow datafiles to be moved online.

Rebuild Index-Organized Tables:

Because index-organized tables are stored as B-tree indexes, you can encounter fragmentation as a consequence of inserts, updates and deletes.

However, you can use the

ALTER TABLE ... MOVE ONLINE statement to rebuild an index-organized table and reduce this fragmentation.

For more information see SAP Notes 1856270 and

2087004.

5

Microsoft Windows

Oracle Database 12c supports the use of an

Oracle Home

User

, which can be specified at installation time. The

Oracle Home User is introduced to host Oracle Services for greater security using a low privileged non-administrator account. Oracle Home User can be a Windows

Built-in Account or a standard Windows User Account

(not an Administrator account). This account is used for running Windows services for Oracle Home. For enhanced security, Oracle recommends using a standard Windows

User Account (instead of a Windows Built-in Account).

For more information see SAP Note 1915302.

Base Certification and Application Optimization

In Oracle Database 11g, structured table data compression

(OLTP compression) is not supported for tables with more than 255 columns. In Oracle Database 12c Advanced

Compression, the

255-columns limit is removed

, and the table compression without this limit is available for SAP customers since the base certification.

On the surface this seems to be a minor improvement, however tables having more than 255 columns are commonly found in almost all SAP systems.

A particularly interesting example is discussed in SAP

Notes 1835008 and 1892354: Several application

5 optimizations implemented by SAP can only be used, if some tables traditionally implemented as cluster tables are declustered. As the data in these cluster tables is normally stored in a compressed manner by SAP, customers find that the tables can grow considerably when they are converted to transparent tables. Unfortunately some of the declustered tables have more than 255 columns. The Oracle

Database 11g Advanced Compression could not help to reduce their size. With the Oracle Database 12c Advanced

Compression Option, it is now possible to compress and manage the data residing in these very wide tables.

10

Core Data Services

Many people believe that SAP’s decision to abandon the least common denominator strategy and to optimize their applications with HANA in mind are seen as a threat by Oracle. And it is certainly true that in the SAP world

HANA is a competitor of the Oracle Database. However, in many cases SAP’s new application optimizations are greeted with a sigh of relief by Oracle employees as well as by Oracle customers. Taking SAP Core Data Services

(CDS) as an example, it is easy to explain why.

The main question behind Core Data Services is: What is a database? What can it do? And what can it not do?

The traditional answer to this question claims that a database is nothing but a dumb data store. It is a container that can permanently store data, but that’s it. Whenever a customer wants to do something useful with the data, it must be transferred to the application server, because the intelligence sits in the application server.

Traditional SAP applications are based on this very concept. The disadvantages are obvious: If the sum of 1 million values needs to be calculated and if those values represent money in different currencies, 1 million individual values are transferred from the database server to the application server – only to be thrown away after the calculation has been done. The network traffic caused by this approach is responsible for the bad performance.

More than 25 years ago the developers of the Oracle

Database asked: Would not it be nice, if this sum could be calculated on the database server side? Would not this improve the performance dramatically? They came up with a different answer to the question what a database is: A database is not only a data store. Not only can it store data, it can also store and execute procedures working with those data – pieces of code that originally were part of the application running on the application server, but are now moved to the database server. So the application is split into two tiers, one of them running on the application server, the other one on the database server, and therefore the database server is an application tier.

But the Oracle developers did not only ask questions.

They did not only come up with a new concept. They also built a new database version that was able to store and execute database procedures (Oracle 7, released

1992). However, at that time the Oracle Database was the only database that could be used as an application tier. Stored procedures were not part of the least-common-denominator feature subset, and therefore SAP declined to use them.

When, 20 years later, SAP started to promote HANA, one of the first things they discovered was that their own applications were the worst enemies of the new in-memory database architecture. As long as an application believes that a database is essentially a dumb data store, that only itself can do calculations efficiently and that therefore individual values need to be transferred over the network,

Oracle Database 12c for SAP: Latest Database Technology and Support for Application Optimizations

11 it actively destroys all potential benefits of an in-memory database. At that time SAP realized that they had to abandon the least common denominator strategy and its counterpart, the dumb data store concept.

As a response to this insight, SAP developed the “Push down” strategy: push down code that requires data-intensive computations from the application layer to the database layer. They developed a completely new programming model that allows ABAP code to (implicitly or explicitly) call procedures stored in the database. And in order to prevent pure chaos, they defined a library of standard

5 procedures. This library is called Core Data Services (CDS).

And they agreed to make this library available for non-

HANA databases, too, if those databases support stored procedures.

The 20 years between the release of Oracle 7 and the release of SAP Core data Services explain the sighs of relief breathed by Oracle customers and employees: The performance gains achieved by SAP’s push-down strategy would have been possible 20 years earlier. But better late than never.

Oracle Database In-Memory

Oracle Database 12c comes with a Database In-Memory option, however it is not an in-memory database. Supporters of the in-memory database approach believe that a database should not be stored on disk, but (completely) in memory, and that all data should be stored in columnar format. It is easy to see that for several reasons (among them data persistency and data manipulation via OLTP applications) a pure in-memory database in this sense is not possible. Therefore components and features not compatible with the original concept have silently been added to in-memory databases such as HANA. Oracle has chosen the opposite strategy: Data can be populated into an In-Memory Column Store whenever this makes sense. In all other cases data are stored and handled as in the past. (For more information on the concepts of Oracle

Database In-Memory see the article “Implementing a

Data Management Infrastructure for SAP with Oracle

5

Database Options and Packs”, in particular the sections

“Oracle Database In-Memory”, page 22, and “Summary”, page 34.

Oracle Database In-Memory has been certified for SAP in

June 2015. Unlike similar options offered by competitors, the use of Oracle Database In-Memory is not limited to SAP Business Warehouse (SAP BW). It is supported for all SAP applications based on SAP NetWeaver, including typical OLTP applications. However, this does not mean that it is always a good idea to use Oracle Database In-Memory. This option is a solution for a specific problem – or for a certain set of problems. It cannot solve all problems. It cannot improve performance in all cases.

If used in an inappropriate manner, it can even – like a pure in-memory database – degrade system performance.

Therefore the SAP applications that can benefit from data being loaded into the column store must be selected carefully.

12

Applications must be selected, individual tables must be selected – the implementation of Oracle Database

In-Memory in SAP environments seems to be difficult.

However, beta customers and early adopters consistently mention as their very first experience that Oracle Database

In-Memory for SAP can be implemented quickly and easily. This seems to be counterintuitive, but it can be explained easily.

First, many customers are already aware of the queries and jobs that take too much time to complete, and they know which tables are involved. In those cases the task to select appropriate SAP applications and tables is trivial.

Second, for customers who do not want to implement

Oracle Database In-Memory in order to fix specific issues, but prefer a general approach, Oracle provides an In-Memory Advisor – a wizard that analyzes the workload of a particular system and recommends tables to be populated into the column store based on the amount of memory

5 that is available. (This means that the frequently asked question “How much memory do I need in order to use

Oracle Database In-Memory?” is completely meaningless.

It’s the other way round: You tell Oracle how much memory you have, and the advisor will let you know how that amount of memory can be used in the most efficient way.)

Third, once the relevant tables are determined, everything is easy and breathtakingly fast: By issuing an

ALTER TABLE XXX INMEMORY statement you declare that those table data should be available in the column store and from this point on everything else happens automatically in the background.

Finally, unlike the migration to an in-memory database such as HANA the implementation of Oracle Database

In-Memory does not require a revolution: no new hardware, no new operating systems, no new database. Customers can continue to use the existing infrastructure, and what administrators need to know about Oracle Database

In-Memory can be learned within a few hours.

Flat Cubes

When the certification of Oracle Database In-Memory for SAP was announced in June 2015, the announcement included a couple of restrictions. In particular, it was strongly recommended not to drop any standard indexes or aggregates.

In this case (as in all other cases described in this article) the Oracle/SAP development team, which is responsible for the integration of SAP and Oracle technologies, had

5 to follow SAP’s learning curve. The situation immediately after the certification of Oracle Database In-Memory for SAP (in this case: for SAP BW) simply mirrors the early stages of SAP’s project to provide SAP BW on

HANA. A certain disappointment with the restrictions mirrors SAP’s experience that the traditional SAP BW data model is not compatible with the new concept of an in-memory database. And Flat Cubes, which will be explained in this section, mirror the new data model that

SAP designed for HANA.

Oracle Database 12c for SAP: Latest Database Technology and Support for Application Optimizations

13

In many cases, data to be loaded into the Business Warehouse arrive as very wide records. E. g. company name, zip code, city, and street address are combined with carrier details, order number, order date, invoice number and dozens, if not hundreds of other data items in one single record. But in the early days of data warehousing, when databases were disk-based only and disk space was expensive, it was not acceptable to waste disk space for redundant data such as the company or the carrier details which occur 1000 times, if that particular company sends

1000 orders, and 100,000 times, if that particular carrier is engaged to fulfill 100,000 shipments. Therefore database architects came up with a design called star schema: subsets of data which belong together (all customer details, all carrier details) are moved to separate tables, which are called dimension tables. The remaining data plus IDs pointing to the relevant entries in the dimension tables is stored in the fact table.

Such a split was not enough in all cases. E. g. a certain combination of zip code, city name and street may occur several times in the CUSTOMERS as well as in the

CARRIERS table. If the same split operation is applied again, additional tables are created which, however, are not connected to the fact table, but to the dimension tables. This results in a more complex, but also (from a disk-space point of view) more efficient design, which is called snowflake schema. High-end data warehouses such as SAP BW add yet another level of detail tables, thus relying on the extended snowflake schema.

This complex architecture has been designed in order to optimize the data model for the requirements of traditional, disk-only relational databases. However the new databases with their focus on memory – and in this respect there is no difference between SAP HANA and Oracle

Database In-Memory – have very different requirements.

Therefore SAP designed a new data model for SAP BW on HANA and consequently called it HANA-Optimized

InfoCubes.

The simplest, but somewhat surprising description of

HANA-Optimized InfoCubes is this: If the process of optimizing the SAP BW data model for disk-oriented databases led from flat and therefore wide records to the extended star schema, the process of optimizing the data model for memory-oriented databases is simply the way

back from extended star to flat and wide.

Not all the way back, however. HANA-Optimized

InfoCubes combine the fact table (actually: the E and F fact tables) and the dimension tables (first level of details) in one single table, whereas the small level 2 and 3 tables

(characteristics, attributes and hierarchies) remain in place.

This change is sufficient to improve performance and manageability considerably.

Traditional “star” (= extended snowflake) schema

14

New flat cube design

This new data model removes the main disadvantages of the previous data model without sacrificing its benefits.

It is no longer necessary to split the incoming, wide records in order to distribute them over many tables – this speeds up data load. The traditional indexes are not needed anymore – this speeds up data load as well. It is no longer necessary to join the tables later on – this speeds up query processing. And the main disadvantage of the flat data model, which originally motivated the development of the extended snowflake schema, the disk and memory requirements of redundant data, is no longer an issue thanks to the compression features that are available today for data on disk as well as for data in memory.

5

If this new data model is made available for a non-HANA database, “HANA-Optimized InfoCubes” is obviously not an appropriate name. “SAP BW Flat InfoCubes for

Oracle” or simply “SAP BW Flat Cubes for Oracle” is exactly the same data model, called by a different name.

It requires Oracle Database 12c and Oracle Database

In-Memory, as Flat Cubes outside of the Column Store do not make any sense.

Flat Cubes for the Oracle Database is available since

February 2016 for pilot customers. The plan is to make it generally available by June 2016.

Deferred Compression and Information Lifecycle

Management

Some of the new features in Oracle Database 12c Advanced Compression have already been discussed in the “Base

Certification Features” and “Base Certification and Appli

5 cation Optimization” sections. However, two major new features are still missing, because they were not included in the base certification, but certified a few months later

(December 2015) for SAP environments: Heat Map and

Automatic Data Optimization (ADO). The basic concepts behind these two features are discussed in the article

Oracle Database 12c for SAP: Latest Database Technology and Support for Application Optimizations

15

“Implementing a Data Management Infrastructure for

SAP with Oracle Database Options and Packs” see in particular the section “Advanced Compression (Oracle

Database 12c)”, page 20. Here, therefore, we will briefly look at the SAP-specific implementation details.

Oracle Database 12c Advanced Compression allows customers to distinguish between current (“hot”) and historical (“cold”) data. Initially, however, it is not clear what exactly the words “hot” and “cold” mean. So this needs to be defined:

ALTER TABLE <table_name> ILM ADD POLICY

<action>

AFTER <n> DAYS OF NO MODIFICATION;

The third line of this SQL statement answers the question.

New data are considered “hot”. If it turns out that they have not been modified for a certain number of days (30,

60, 90 days), they are considered “cold” – assuming that the customer does not want to define intermediate levels such as “warm”. But if we look closer, we find that the only question that has been answered so far is: When do we call data “cold”? What we still do not know (and what the database system still does not know) is: If data have cooled down – then what? What should happen? This is to be defined in line 2:

ALTER TABLE <table_name> ILM ADD POLICY

ROW STORE COMPRESS ADVANCED ROW

AFTER 40 DAYS OF NO MODIFICATION;

In this example we assume that (in this particular table) hot data are not compressed at all, and we tell the system that (a) any data not modified for 40 days should be considered cold and that (b) cold data should be compressed using the table compression algorithm provided by Oracle

Database 12c Advanced Compression.

How do we, and how does the system know that data have not been modified for 40 days? It is the job of Heat

Map to provide this kind of information. Heat Map automatically tracks modification and query timestamps at the row and segment levels, providing detailed insight into how data is being accessed. Automatic Data Optimi-

zation (ADO), then, automatically moves and compresses data according to user-defined policies (such as that which we have used here as an example) based on the information collected by Heat Map.

So far the

ALTER TABLE

statement has been used to define the ILM policy. In SAP systems, however, where we have to deal with tens of thousands of tables, this approach would be very cumbersome. Therefore SWPM

(SAPinst) uses a different option provided by the Oracle

Database:

ALTER TABLESPACE TSX DEFAULT ILM ADD POLICY

ROW STORE COMPRESS ADVANCED ROW

AFTER 40 DAYS OF NO MODIFICATION;

In this example we do not define a special policy for an individual table, but a default policy on the tablespace level.

It is automatically applied to all tables created in this tablespace, unless a table comes with an individual policy.

Customers running Oracle Database 12

c

on an Oracle

Engineered System (Exadata, SuperCluster) can benefit from Hybrid Columnar Compression – a set of compression algorithms designed for purely historical data as an alternative to archiving. If Advanced Compression compresses data by a factor of 2 or 3, Hybrid Columnar Compression can easily achieve compression factors of 10 or 15.

In this situation, we would call data not modified for

40 days “warm”, and we would reserve the word “cold” for data not changed during a considerably longer period

(e.g. 6 or 12 months). We would keep the previous policy as compression tier 1 (for warm data) and add an additional policy as compression tier 2 (for cold data).

And we would separate unpartitioned and partitioned tables in different tablespaces, because Hybrid Columnar

Compression compresses complete partitions instead of individual blocks:

ALTER TABLESPACE TSY DEFAULT ILM ADD POLICY

ROW STORE COMPRESS ADVANCED ROW

AFTER 40 DAYS OF NO MODIFICATION;

ALTER TABLESPACE TSY DEFAULT ILM ADD POLICY

COLUMN STORE COMPRESS FOR QUERY LOW ROW LEVEL

LOCKING SEGMENT AFTER 6 MONTHS OF NO MODIFI-

CATION;

16

Oracle Database 12c for SAP: Latest Database Technology and Support for Application Optimizations

Oracle Multitenant

For information on Oracle Multitenant see the article

“Implementing a Data Management Infrastructure for

SAP with Oracle Database Options and Packs” (in particular the section “Oracle Multitenant”, page 26).

SAP Notes related to Oracle Database 12c

DB: Features: Overview

105047, Support for Oracle Functions in the SAP Environment

1914631, Central Technical Note for Oracle Database 12c Release 1 (12.1)

2133079, Oracle Database 12c: Integration in SAP Environment

DB: Option: Advanced Compression

2138262, Oracle Database 12c Advanced Compression for SAP Systems

2157904, Oracle 12c: Conversion of Compressed Tables

2166836, Oracle 12c: Problem during SAP Upgrade with Compressed Tables

2254836, BR*Tools Support for Oracle ADO/ILM

2254866, Using Oracle Database 12c Automatic Data Optimization

2255992, R3load and R3szchk: New Oracle Feature for Database ILM Policy

2258061, Enhancements for ADO/ILM for Table Conversions or System Copy

DB: Option: In Memory

2137032, DBA Cockpit: Monitor for In-Memory Feature

2178980, Using Oracle Database In-Memory with SAP NetWeaver based Products

2189163, Oracle Database In-Memory Advisor for SAP

DB: Option: Database Vault

2218115, Oracle Database Vault 12c

DB: Installation and Upgrade

1915299, Troubleshooting Software Installation for 12.1.0.2

1915301, Database Software 12.1.0.2 Installation on Unix

1915302, Database Software 12.1.0.2 Installation on Windows

1915315, Database Upgrade Scripts for 12.1.0.2

1915317, Migrating to Software Owner ‚oracle‘

1915323, OS User Concept for Oracle Database 12c Release 1

2064206, Database Upgrade to 12.1.0.2 with Grid Infrastructure

DB: Patches

1915313, Current Patch Set for Oracle Database 12c Release 1 (12.1)

1915316, Database: Patches for 12.1.0.2

2145572, Grid Infrastructure: Patches for 12.1.0.2

DB: Instance Configuration

1888485, Database Parameters 12.1.0.2

DB: Admin: BR*Tools

2087004, BR*Tools Support for Oracle Database 12c

Engineered Systems

2145628, Exadata/SuperCluster: Patches for 12.1.0.2

2290084, SAP Software and Oracle Database Appliance Version 12.1

Oracle Database Options and Packs for SAP Customers

17

I M P L E M E N T I N G A D A T A M A N A G E M E N T I N F R A S T R U C T U R E

F O R S A P W I T H O R A C L E D A T A B A S E O P T I O N S A N D P A C K S

Introduction

Database Editions

Oracle Database is available in five editions, each suitable for different development and deployment scenarios.

However, only Oracle Database Enterprise Edition is certified and supported in SAP environments, as SAP applications are very demanding and cannot be run efficiently without the enterprise computing features provided by Oracle Database Enterprise Edition.

Database Options and Managements

In addition, Oracle offers several database options, management packs, and other products that enhance the capabilities of Oracle Database for specific purposes.

They extend the power of Oracle Database Enterprise

Edition to meet customer- or application-specific requirements in the areas of efficient use of disk space, performance and scalability, high availability, security and compliance, data warehousing and big data, and manageability.

Options and Packs in SAP Environments

This article is about database options and management packs for SAP customers. There are some differences between a pure Oracle Database and an Oracle Database for SAP perspective:

• Even if an option is certified, the use of some of its features may not be permitted. As this is an overview article, not all details can be discussed. If in doubt, again, check SAP Note 105047.

• Due to peculiarities of the SAP data model or application design, an Oracle Database option or management pack may not be optional, but required. E.g. SAP Business

Warehouse (BW) on Oracle Database requires Oracle

Partitioning.

• From a pure Oracle perspective, an option or pack is licensed separately. However, an Oracle Database

Enterprise Edition license bought from SAP (ASFU) already includes some (but not all supported) options and packs without additional payment. For details see

SAP Note 740897.

Figure 1: Oracle Database Enterprise Edition, Database Options (certified and required, or certified and optional) and Enterprise Manager Packs (certified and required, or certified and optional).

18

The common denominator of all issues mentioned above is the fact that by default (and by definition) a table in the database is an unordered set of records with no guaranteed physical sequence whatsoever, whereas from a user, application, or DBA perspective this set of data may consist of certain subsets which should ideally be separated from other subsets. Oracle Partitioning allows users to implement such subsets by physically storing related data as closely together as possible.

Table and Index Partitioning

Structure and Infrastructure

As we said before, database options extend the power of

Oracle Database Enterprise Edition in the areas of efficient use of disk space, performance and scalability, high availability, security and compliance, data warehousing and big data, and manageability. In this article, however, we will focus on one single aspect: Database options help im-

plement structure. When the amount of data in one single database grows, when data coming from different sources or even multiple, previously independent databases are consolidated in one single data management infrastructure (as in Oracle Multitenant), the unstructured mass of data will become unmanageable at a certain point. Therefore consolidation requires differentiation. Or: Infrastruc-

ture requires structure.

Challenge:

In more and more situations today the distribution of the data on disk turns out to be a problem:

(a) Single queries or complex batch jobs accessing a certain subset of the table data need too much time to complete.

(b) Data load (SAP BW) is either slow, because it must update many indexes; or indexes are dropped and rebuilt, in order to reduce load time, but this slows down user queries.

(c) Data archiving results in heavily fragmented databases.

(d) Customer wants to implement information lifecycle management (see Oracle DB 12c section of this presentation).

Value Proposition:

Oracle Partitioning divides tables and indexes into smaller units (called partitions) and forces all data to be stored in the appropriate unit.

Partitions can be accessed and managed individually and independently from each other. Therefore:

(a) Ideally a query now finds all relevant data in one single partition and can ignore all other partitions

(„partition pruning“). This can reduce the runtime considerably.

(b) If the indexes defined on a partitioned table are partitioned as well, individual index partitions can be dropped and rebuilt while all other partitions remain untouched.

(c) The data archiving strategy can be based on the partition structure, and this can avoid disk space fragmentation.

(d) Partitioning is one of the basis technologies for information lifecycle management.

Certification/Support:

Oracle Partitioning is certified for all SAP NetWeaver applications.

Versions:

Oracle Database 11g, Oracle Database 12c

Implementation:

Partitioning (range partitioning) is configured and used by default in SAP BW on Oracle.

In SAP OLTP systems, it can either be implemented using the SAP Partitioning Engine (which covers the data archiving issue) or by Oracle ACS for SAP.

Oracle Database Options and Packs for SAP Customers

19

Figure 2 explains why storing related data as closely together as possible makes such a difference. It shows database blocks filled with records. The different colors represent criteria such as different months or different locations. And we assume that the applications accessing those data in most cases want to retrieve all records having the same color.

Figure 2: Table Partitioning – Physically store subsets of related data as closely together as possible

Under these circumstances, the situation shown on the left hand side is the worst that can be imagined: Each database block contains one record of each color. Or, to put it differently, all subsets of records having the same color are distributed over all blocks. This is the worst possible situation from an I/O perspective (a query looking for all records of a certain color needs to read 8 blocks), from a memory perspective (even if all users work with records of the same color, all 8 blocks need to be cached completely in database memory), therefore from a performance perspective

(too much I/O means unsatisfactory performance), from a database administration perspective (subsets of records having the same color cannot be managed independently), and from an ILM perspective (“hot” and “cold” data cannot be separated).

The situation shown on the right hand side, in contrast, is optimal (again: under the circumstances described above):

All records having the same color are now stored together in one and the same database block. This is optimal from an I/O perspective (a query looking for all records of a certain color needs to read only 1 block), from a memory perspective (if all users work with records of the same color, only 1 block needs to be cached in database memory), therefore from a performance perspective (significantly less

I/O means significantly better performance), from a database administration perspective (subsets of records having the same color can be managed independently), and from an

ILM perspective (“hot” and “cold” data can be separated).

Now, multiply the number of records and blocks shown on this slide. Then a partition is the subset of all blocks containing records of the same color.

Advanced Compression (Oracle Database 11g)

Challenge:

In more and more cases today the size and the expected future growth of the database becomes a problem. Aspects of this problem include: Storage cost, performance guarantees (SLAs), cloning and backup of database files within a reasonable time.

Value Proposition:

Oracle Advanced Compression uses a different format for storing table data. Together with other compression technologies, which come with Oracle Database Enterprise Edition (e.g. Index

Key Compression), it helps reduce the database size by 50% or more. This is the essential benefit in the sense that this is the effect Advanced Compression is designed for. And if the source database is smaller, the creation of backup and other copies needs less time.

As an additional benefit customers using Advanced

Compression may see a performance improvement.

Additional (as opposed to essential) here means: It may, but it is not guaranteed to happen.

Certification/Support:

Oracle Advanced Compression is certified for all SAP NetWeaver applications. Implementations are supported by SAP.

Implementation:

Oracle Advanced Compression can be implemented easily in SAP environments, as SAP provides the tool BRSPACE, which is aware of all

SAP-specific requirements. For details check SAP

Note 1431296.

20

On the left-hand side, figure 3 shows a typical Oracle

Database which forms an integral part of an SAP (in this case: SAP ERP) system. Approximately one third of the allocated disk space is used for indexes (red), and two thirds contain table data (blue). Table data in turn can be divided into structured data (organized in columns) and unstructured data (e.g. PDF or image files).

Oracle Database 11g can compress all three types of data:

• Index Key Compression is available for indexes. Index-

Organized Tables (IOTs) can be compressed as well. Both features are included in Oracle Database Enterprise

Edition, and do not require Advanced Compression.

• OLTP Compression, a major feature of Advanced Compression, can be used to compress structured table data. It is not restricted to OLTP systems, but can be implemented in SAP BW systems as well.

• SecureFiles Compression (an Advanced Compression feature, too) can be used to compress unstructured table data.

If all features are implemented and all appropriate database objects are compressed, customers have seen 55% disk space savings on average. (This assumes a completely reorganized database. If a fragmented database has not been reorganized, the effects of reorganization and compression are combined, in which case customers have seen up to 80% disk space savings).

Advanced Compression (Oracle Database 12c)

Challenge:

(a) Data compression in Oracle Database 11g has several limitations. In particular, tables having more than 255 columns cannot be compressed.

(b) Data load is slowed down, if target tables are compressed.

(c) No support for automated Information Lifecycle

Management.

Value Proposition:

Oracle Database 12c Advanced

Compression lifts the 255-columns limitation and allows more tables to be compressed. Completely new features (Heat Map, Automatic Data Optimization) enable customers to implement deferred data compression and sophisticated Information Lifecycle

Management (ILM) strategies.

The maximum disk space savings which can be achieved depend on the characteristics of the data and the data characteristics depend on the SAP applications used.

Usually SAP BW (BI) data can be compressed more efficiently than SAP ERP (ECC) data, and SAP CRM data permit even higher disk space savings.

Oracle Database 11g Advanced Compression offers more than OLTP and SecureFiles compression. Backup files created by RMAN and export files created by Data Pump can be compressed substantially, even if tables and indexes in the production database are already compressed.

Additionally, redo log data can be compressed as well before being shipped from the production to a standby database (see the Data Guard section in this article).

Figure 3: Oracle Database 11g Index Key Compression and Advanced Compression

(OLTP Compression, SecureFiles Compression)

Certification/Support:

Some new features included in

Oracle Database 12c Advanced Compression have already been certified in March 2015. Certification of the ILM features was end of Q4 2015.

Implementation:

Details will be provided at the time of certification.

Related Feature:

Oracle Database 12c Hybrid Columnar

Compression (which is not included in Advanced

Compression, but is a feature available on Oracle‘s

Engineered Systems) provides stronger compression algorithms particularly suited for “cold” (i.e. historical) data. Certification of HCC on Oracle Engineered

Systems has been done in December 2015.

Oracle Database Options and Packs for SAP Customers

21

Base Certification Features

In Oracle Database 11g, the index and table compression features have several limitations. That is why Oracle

Database 12c Advanced Compression offers a new, more efficient index compression algorithm (Advanced Index

Compression) and increases the maximum number of columns for tables to be compressed. For details see the article “Oracle Database 12c for SAP – Roadmap and

Base Certification Features.”

Heat Map and Automatic Data Optimization

In addition to those improvements, Oracle Database 12c

Advanced Compression comes with two completely new features. Heat Map automatically tracks modification and query timestamps at the row and segment levels, providing detailed insights into how data is being accessed. Auto-

matic Data Optimization (ADO) automatically moves and compresses data according to user-defined policies based on the information collected by Heat Map.

Deferred Compression

Based on the information provided in the Advanced

Compression (Oracle Database 11g) section, it might seem that compression simply reduces the disk space needed, and has nothing to do with database structure.

However, this is an illusion. Even in Oracle Database 11g, we need to distinguish between tables that benefit and tables that do not benefit from compression (if this were not the case, compression could be made the default), i.e. between tables that should and tables that should not be compressed.

Nevertheless, this is still a very basic and inflexible distinction. Take, e.g., an SAP BW table that is used for data load. On the one hand, such a table could be compressed, because for most of the time it is accessed in read-only mode. On the other hand, it should not be compressed, because this would slow down the load operations considerably. In Oracle Database 11g the recommendation is: Do not compress such a table.

Heat Map and Automatic Data Optimization allow you to introduce a new differentiating parameter: If a table or partition should be compressed, when would you like it to be compressed? In Oracle Database 11g compression happens immediately or not at all. In Oracle Database 12c you can specify that data should be loaded today and

(automatically) compressed tomorrow.

Information Lifecycle Management

Even more parameters can be introduced thanks to the new features in Oracle Database 12c Advanced Compression. One of them is location. When you have “hot”

(current) and “cold” (historical) data in your database, and you have two different types of storage, too, then you can ask the question: Where? Where would like which data to be stored?

Using Partitioning in addition to Advanced Compression, you can – or rather: you can have the system – move data from one tablespace (= storage tier) to another, when they

“cool down”, thus freeing up space on a more expensive storage tier for more important (“hot”) data. This is called

(automatic) storage tiering.

Hybrid Columnar Compression (HCC)

Finally, if you run Oracle Database 12c on Oracle Exadata or Oracle SuperCluster, you can introduce the question:

How? How, i.e. using which algorithm, do you want data to be compressed?

In addition to OLTP and SecureFiles Compression, this

Engineered Systems support Hybrid Columnar Compression. As the name implies, this technology utilizes a combination of both row and columnar methods for storing data. This hybrid approach achieves the compression benefits of columnar storage, while avoiding the performance shortfalls of a pure columnar format. The compression rations that can be achieved by using HCC are much higher than those seen with “normal” compression. Therefore HCC is particularly suited for “cold” data.

Due to the missing row-level locking feature, it had not been possible to certify Oracle Database 11g Hybrid

Columnar Compression for use in SAP environments.

In Oracle Database 12c, however, this feature is available on Oracle Exadata and Oracle SuperCluster. On these machines it is now possible to implement (automatic)

compression tiering. This means that, while “hot” data remain uncompressed, “warm” data may be compressed using the standard compression algorithms (Advanced

Compression) and “cold” data using Hybrid Columnar

Compression.

22

Figure 4: Oracle Database 12c Advanced Compression – Support for Information Lifecycle Management (ILM)

Oracle Database In-Memory

Challenge:

In more and more systems, meeting analytics performance requirements turns out to be a challenge. This is true for long-running queries in

BW. However, it can also happen in OLTP systems, e.g. if a very flexible implementation of operational planning/reporting allows users to create many, slightly different query variants.

Value Proposition:

Oracle Database 12c In-Memory allows administrators to dedicate a certain amount of database server memory to the Column Store – a

Memory: The New Dual-Format Architecture

Oracle Database has traditionally stored data in a row format. This format is ideal for online transaction (OLTP) systems, as it allows quick access to all columns in a record.

A column format database stores each of the attributes about a transaction or record in a separate column structure.

This format is ideal for analytics, as it allows for faster data retrieval when only a few columns are selected but the query accesses a large portion of the data set.

But what happens, when your system is characterized by a mixed workload? Up until now you have been forced to pick just one format and suffer the tradeoff of either sub-optimal OLTP or sub-optimal analytics performance.

The only way to optimize for both OLTP and analytics had been to copy data from OLTP systems to analytic systems using complex ETL processes that add a great deal of expense and latency.

memory structure that stores data in column format instead of in row format. Setup of the Column Store is fast and easy. Having available in column format can improve query performance substantially.

Certification/Support:

Versions:

Oracle Database In-Memory is certified for all SAP NetWeaver applications.

Oracle Database 12c

Implementation:

For an overview and pointers to more detailed documents see SAP Note 2178980.

Oracle Database 12c In-Memory optimizes both analytics and mixed workload OLTP, delivering outstanding performance for transactions while simultaneously supporting real-time analytics, business intelligence, and reports. This breakthrough capability is enabled by the dual-format

architecture of Oracle Database In-Memory. This architecture eliminates the tradeoff by representing tables simultaneously using traditional row format and a new in-memory column format. The Oracle SQL Optimizer automatically routes analytic queries to the column format and OLTP queries to the row format, transparently delivering best-of-both-worlds performance. Oracle Database

12c automatically maintains full transactional consistency between the row and the column formats, just as it maintains consistency between tables and indexes today.

Oracle Database Options and Packs for SAP Customers

23

Disk: Nothing Has Changed

The new column format is a pure in-memory format.

Tables are stored on disk using Oracle’s existing row-based

(or – on Engineered Systems – hybrid columnar) formats.

Since there is no persistent columnar storage format, there are no additional storage costs or storage synchronization issues. Nor is there a need to modify the database. Oracle

Database 12c In-Memory can be implemented without a database migration or a table reorganization.

As a result, the new Oracle Database 12c In-Memory feature is fully compatible with existing standard or optional database features such as table and index compression, table encryption, and table partitioning. It is also compatible with the scale-out architecture provided by Real Application

Clusters (RAC) and with all existing high availability technologies (such as Data Guard). These features work exactly the same way with and without Oracle Database

In-Memory.

Easy to Implement and Manage

In addition to being compatible at the database feature and application level, Oracle Database In-Memory is easy to implement and manage. Enabling Oracle Database

In-Memory is as easy as setting the size of the in-memory column store and identifying tables or partitions to bring into memory. Background processes populate data from storage into in-memory columns while the database remains fully active and accessible.

Fine-Grained Control

An easy start based on intelligent defaults for typical situations – this is what Oracle customers expect. In addition, however, Oracle customers expect mechanisms, which allow for fine-grained control and tuning. Oracle

Database 12c In-Memory provides such mechanisms.

Examples are:

• Tables can contain “cold” data, which are neither updated anymore nor accessed by queries. If those tables are very large, it would be a waste of memory to keep them completely in the in-memory column store.

Therefore administrators may want to restrict the population process to the data really needed by DSS queries. Table partitioning allows them to make this happen. If the table is partitioned in a useful way (e.g. by month), this internal structure can be used to define a horizontal subset of the table data to be kept in the in-memory column store.

• One or several table column(s) may contain data that are not relevant for DSS queries. Again the database administrator may wish to restrict the data to be kept in the in-memory column store, but in this case the goal is to define a vertical subset of the table data, i.e. to exclude one or more columns from the population process. And again it is possible to make this happen, because Oracle Database In-Memory allows administrators to specify different in-memory characteristics for different table columns.

• The Oracle Database has been optimized and tuned for decades to scale-up on SMP servers. Large SMP servers are well suited for in-memory workloads, too, because all memory is accessible to all processors over an extremely high speed Backplane. In addition to being able to scale up, however, Oracle Database In-Memory can also scale out to very high memory and CPU capacities by using all of the memory and processors in a cluster of servers

(RAC). In such environments, all objects populated into memory will by default be distributed across all in-memory column stores in the cluster. On Oracle

Engineered Systems, objects can also be duplicated.

This means that an object (or part of an object, e.g. a partition) populated into the in-memory column store will have a mirrored copy placed on one of the other nodes in the RAC cluster. Duplicating data provides in-memory fault tolerance as it ensures data is still accessible via the in-memory column store even if a node goes down or is taken down for maintenance.

Figure 5: Oracle Database 12c In-Memory – Dual memory format, single disk format

24

Real Application Clusters (RAC)

Challenge:

When the workload on a database server increases (due to new application versions, additional applications, or more users), the traditional solution is to replace the existing server with a bigger one

(scale-up). Big servers, however, are very expensive.

In order to guarantee high availability of the database server, traditionally a failover cluster is implemented.

Such a solution, however, has at least two disadvantages:

(a) A failover cluster relies on the concept that, at any given moment, only one database instance running on one machine can be active. The other machine

(most probably an expensive server, too) is always idle.

(b) When a problem on the primary machine is detected, an Oracle Database Server instance needs to be started on the secondary machine. In this particular situation, startup can take up to 30 minutes – which means: up to 30 minutes unplanned downtime.

Value Proposition:

Real Application Clusters (RAC) allows multiple instances to be up and running and to access the same database at the same time. As these instances can and in most cases do run on different machines, customers have the option to implement a scale-out approach: 4, 6, or 8 small servers can handle the same workload as one big server. However, they are much cheaper. And they can be added as needed.

In this architecture, all Oracle instances are up and running at the same time. Therefore no restart is required. If one of the RAC servers fails, the other instances can take over. A reconnect of the affected users is a matter of seconds, not of minutes.

To summarize all this in a few words: The value proposition of Oracle Real Application Clusters combines workload distribution, scalability, high availability, better manageability, and cost savings.

Certification/Support:

Oracle Real Application Clusters is certified for all SAP NetWeaver applications.

Versions:

Oracle Database 11g, Oracle Database 12c

Implementation:

Customers can use any general-purpose machine (Unix, Linux, or Windows) certified by SAP to build a RAC system. In addition, Oracle offers Engineered Systems (Exadata, SuperCluster), which make the implementation considerably easier.

Oracle Grid Infrastructure provides a set of base technologies that simplify implementation and help save money.

Figure 6 illustrates the RAC benefits which have been mentioned before:

Scalability: Using RAC, the scale-out approach, which is always supported on the SAP Application Server level, can be implemented on the database level, too. In this example, 5 SAP Application Server instances, running on

5 different machines, are connected to 4 Oracle Database

Server instances, running on 4 different machines.

Figure 6: Real Application Clusters (RAC) for scale-out and immediate (instance) failover

Oracle Database Options and Packs for SAP Customers

25

High Availability: If one of the Oracle instances goes down, the affected SAP instance(s) is/are automatically reconnected to one of the available Oracle instances.

After this operation users can continue their work. The failover occurs within seconds.

Oracle Grid Infrastructure provides the base technologies that are required to enable RAC. It can be divided into two main components:

• In order to let multiple Oracle instances access the database files at the same time, a cluster file system is needed. Therefore Oracle provides Oracle Automatic

Storage Management (ASM). Unlike other, third-party cluster file systems, it is optimized for Oracle Database files, and it comes for free.

Data Guard and Active Data Guard

• Oracle Clusterware is the cross-platform cluster software required to run the RAC option for Oracle Database.

It enables the nodes to communicate with each other, allowing them to form a cluster of nodes which behaves as a single logical server. Similar to Oracle ASM, which eliminates the need for a third-party cluster file system, Oracle Clusterware eliminates the need for third-party cluster management software.

Oracle Clusterware can provide high availability and resource management for SAP resources just as it does for

Oracle resources. Therefore Oracle/SAP Development has created an Oracle Clusterware tool, SAP Control (SAPCTL), to enable customers to easily manage SAP high availability resources.

Challenge:

RAC provides high availability by multiplying the number of Oracle instances. Such high availability, however, is restricted to the instance level. Even in a RAC-based system, the database remains a single point of failure. This means that DBA errors, data corruption, server or data center failures can make the whole system unavailable.

Value Proposition:

Data Guard removes this single point of failure. The technology allows customers to set up a standby (shadow) database as a copy of the primary (production) database and then keep the two databases synchronized. Please note that Data Guard is included in Oracle Database Enterprise Edition.

It is not an option.

However, Active Data Guard is an option. In Oracle

Database 11g it offers additional features such as Automatic Block Repair and Fast Incremental Backup.

Active Data Guard Far Sync, the main new feature with Oracle Database 12c, allows customers to combine high performance (a characteristic of asynchronous data shipping) and zero data loss (a characteristic of synchronous data shipping).

Certification/Support:

Oracle Data Guard is certified for all SAP NetWeaver applications. However, only physical standby databases are supported, logical standby databases are not.

Oracle Active Data Guard is certified for all SAP

NetWeaver applications. However, Real-Time Query is not possible in SAP environments, because even report generation is not a read-only operation.

Versions:

Oracle Database 11g, Oracle Database 12c

Implementation:

Standard Oracle setup procedures apply. In the white paper “Oracle Standby Database”

SAP describes BR*Tools support.

Data Guard can provide both zero data loss protection and near-immediate restoration of service should a production database become unrecoverable for any reason. This is accomplished using the combination of Data Guard synchronous redo transport and a replication-aware apply process at the standby database. The impact that any synchronous replication method can have on database performance, however, often makes it impractical to implement zero data loss protection when large distances separate the primary and replica database(s). Rather than impact database performance, many enterprises will compromise on data protection by implementing asynchronous replication and accept that an unrecoverable outage will result in varying degrees of data loss.

26

Active Data Guard Far Sync, a new capability with Oracle

Database 12c, eliminates the need to compromise by extending zero data loss protection to a replica database located at any distance from the primary database. Far

Sync provides zero data loss protection for a production database by maintaining a synchronized standby database located at any distance from the primary location, and can do so without performance impact and with minimal cost or complexity. A new type of Data Guard destination called a far sync instance receives changes synchronously from a primary database and forwards them asynchronously to a remote standby. Production can be quickly failed over, manually or automatically, to the remote standby database with zero data loss.

A far sync instance is a light-weight entity that manages only a control file and log files. It requires a fraction of the CPU, memory, and I/O of a standby database. It does not have user data files, nor does it run recovery. Its only purpose is to transparently offload a primary database of serving remote destinations. A far sync instance can save network bandwidth by performing transport compression using Oracle Advanced Compression.

Take for example an existing asynchronous Data Guard configuration with a primary in Boston and a standby in San Francisco. Upgrade to zero data loss simply by using Active Data Guard to deploy a far sync instance within synchronous replication distance of Boston (less than 150 miles). There is no disruption to the existing environment nor is there any requirement for proprietary storage, specialized networking, more database licenses, or complex management.

Figure 7: Active Data Guard Far Sync – High performance, zero data loss across large distance WAN

Oracle Multitenant

Challenge:

Many SAP landscapes consist of a few large and a considerable number of small or very small systems. However, the existence of many small

SAP systems based on as many independent database servers has several disadvantages:

• Many small systems (even virtualized ones) use

too many hardware resources (memory, CPU)

• Too much time is spent for the administration of

so many small database systems

Oracle Database 12c Multitenant introduces a new architecture that enables customers to easily consolidate multiple databases, without changing their applications.

This new architecture delivers all the benefits of managing many databases as one, yet retains the isolation and resource prioritization of separate databases.

Value Proposition:

Oracle Multitenant reduces resource consumption by separating “container” and “pluggable” databases. It simplifies administration by moving standard operations to the “container database” level.

Certification/Support:

Oracle Multitenant is available.

Version:

Oracle Database 12c

Implementation:

For more information please see http://scn.sap.com/community/oracle or www.oracle.com/sap

Consolidation Approaches

Large enterprises may use hundreds or thousands of databases. Often these databases run on different platforms on multiple physical servers. A database may use only a fraction of the server hardware capacity. This is an expensive approach which fails to maximize the usage of both the hardware and human resources.

Oracle Database Options and Packs for SAP Customers

27

A typical response to the management problem is to place

multiple databases on each server (either as direct installs or using virtual machines). The problem is that the multiple database instances do not share background processes, system and process memory, or Oracle metadata. Another response is to logically separate the data into schemas (schema consolidation). The problem is that these virtual entities are difficult to manage, secure, and transport.

Oracle Multitenant Architecture

Oracle Database 12c Multitenant is based on an approach called database consolidation. It delivers a new architecture that allows one single Container Database (CDB) to hold many Pluggable Databases (PDBs). See figure 8.

An existing database can simply be “plugged into” a CDB.

At any time, then, it can be unplugged and plugged into another CDB. Unplug/plug is even supported across

Oracle Database software versions.

From the point of view of the client application connecting to the database server via Oracle Net, the PDB is the database. A PDB is fully compatible with a non-CDB – a rule also known as the PDB/non-CDB compatibility guarantee.

Resource Utilization and Resource Management

The many PDBs in a single CDB share its memory and

background processes. This enables consolidation of many more databases compared to the old architecture, offering similar benefits to schema-based consolidation but with none of the major application changes required by that approach.

Horizontal partitioning of the Oracle data dictionary (a conceptual partitioning, not a physical table partitioning) removes the need to store and manage system-wide metadata in every single database. The “lower” half (implemented in the CDB) holds the system-wide metadata – and nothing else, while the “upper” halves (implemented in the PDBs) hold application-specific metadata – and nothing else.

Creating pluggable databases, moving pluggable databases between containers, and cloning pluggable databases are done with new SQL commands and take just seconds. When the underlying file system supports thin provisioning, many terabytes can be cloned almost instantaneously.

Sharing of background processes, memory structures, system-wide metadata, and database files results in considerably decreased resource consumption. In addition, Oracle

Database 12c Resource Manager is extended with specific functionality to control the competition for resources between

PDBs within a CDB.

Manage Many Databases as One

By consolidating existing databases as pluggable databases, administrators can manage many databases as one.

Benefits include:

• The investment of time and effort to patch one CDB results in patching all of its many PDBs. To upgrade all PDBs hosted in a CDB, simply upgrade the CDB and all hosted PDBs are upgraded “in-place”.

• Instead of executing separate database backups, administrators only require to back up their database at the

CDB level. In other words, all PDBs consolidated into a container will be backed up as one, and administrators retain the flexibility to perform recovery operations at individual PDB level, if required.

• Administrators maintaining standby systems in another data center (using Data Guard or Active Data Guard) will only need to set up a standby configuration at the

CDB level, to replicate all PDBs consolidated in that container.

Figure 8: Oracle Multitenant – New architecture for consolidating databases and simplifying operations

28

Oracle Advanced Security

Challenge:

In order to read or update data in an Oracle

Database that is the data store of an SAP application, the obvious and only choice for legitimate users is this particular application. Attackers, however, who want to bypass SAP‘s user management and access control, could use either a network sniffing tool to capture data in transit or some kind of file editor to read data at rest, i.e. in a database file copy.

Value Proposition:

Oracle Advanced Security is a bundle of features that allow administrators to encrypt data and make it harder for attackers to understand what they see. Oracle Network Encryption can be used to protect data in transit, while Oracle Transparent

Data Encryption and Backup Set Encryption protect data in the production database files as well as their backup copies.

Certification/Support:

Oracle Advanced Security is certified for all SAP NetWeaver applications.

Implementations are supported by SAP.

Versions:

Oracle Database 11g, Oracle Database 12c

Implementation:

Advanced Security features are activated either via the Oracle Net configuration or using SAP‘s BR*Tools. Details can be found in SAP

Notes 973450, 974876, and 1324684.

Protecting Data in Transit: Oracle Network Encryption

In SAP environments, users do not directly connect to the

Oracle Database server. They connect to an SAP application server instance, and the SAP application server instance in turn connects to the Oracle Database server. So, in this case, the application server instance is the Oracle client, and Oracle’s network encryption encrypts all data traveling between application server and database server.

Oracle’s network encryption requires Oracle software, which is not installed on end-user devices. Therefore other technologies or products must be used to protect the communication between SAP users and SAP application servers.

However, people do not only attempt to read data in transit, they can also try to intercept and modify them.

Therefore, in addition to network encryption, Oracle also supports crypto-checksumming to ensure data integrity.

Both encryption and crypto-check- summing are completely transparent to the application, and in both areas the system administrator can chose between several algorithms.

1

1 Please note: As of June 2013, network encryption and crypto-checksumming are no longer part of Oracle Advanced Security. They are included without additional cost in all licensed editions of all supported releases of the Oracle database.

Protecting Data at Rest: Oracle Transparent Data Encryption

Oracle Transparent Data Encryption (TDE) is applied to data in the files which make up the production database (as opposed to backup files, which will be discussed in the next paragraph). As the name indicates, TDE is transparent to the application; no application changes are required. Starting with SAP NetWeaver version 7.20, you can use BRSPACE to set the encryption attribute on a tablespace level. BRSPACE can also be used to manage the wallet, which stores the encryption keys.

Transparent Data Encryption comes in two flavors. The first one (available since Oracle Database 10g) is called

Column Encryption, because you select just a few of the many SAP tables, or even individual columns of these tables that contain sensitive data and encrypt them. Everything else remains unencrypted. The second one (available since

Oracle Database 11g) is called Tablespace Encryption. It allows you to encrypt complete tablespaces, which may contain hundreds, thousands, or tens of thousands of tables.

Protecting Data at Rest: Oracle Backup Encryption

If you decide to use column encryption in your database backups then it is generally much easier to steal backups of the database files than can the production database itself.

Therefore, the third set of features in Oracle Advanced

Security is related to backup encryption.

Oracle Database Options and Packs for SAP Customers

29

If you simply backup your database files, only those columns that are encrypted in the production database files are encrypted in the backup copies. However, combining

Oracle Recovery Manager (Oracle RMAN) and Oracle

Advanced Security, whole backup sets (that is, all data) can be encrypted.

Figure 9: Oracle Advanced Security – Encrypt data in transit or at rest

Database Vault

Challenge:

Data encryption does not help, if attackers do not use third-party tools, but Oracle tools to bypass the SAP applications. This is particularly dangerous in the case of privileged database users

(database administrators). And it is particularly relevant, if database administration is outsourced or data are stored in the cloud.

Value Proposition:

Oracle Database Vault replaces the traditional database privilege management strategy with a new, more flexible and more powerful one.

It goes far beyond traditional user–privilege or user– role correlations. Oracle Database Vault allows companies to implement and enforce concepts such as the segregation of duties or the four eyes principle.

Certification/Support:

Oracle Database Vault is certified for all SAP NetWeaver applications. Implementations are supported by SAP.

Versions:

Oracle Database 11g, Oracle Database 12c

Implementation:

Database Vault is managed using the

Oracle Database Vault Administrator (DVA).

Privileged database users – like database administrators

– can use DBA tools and directly connect to the database, thus bypassing SAP’s security checks (see figure 10).

Against this kind of threat, encryption does not help. If someone is able to connect successfully using a sufficiently privileged account, and if he or she then sends a query, the Oracle Database will generously deliver the result set to this user. If the requested data is encrypted, Oracle will decrypt it. From an Oracle Database perspective the request sent by this user seems to be a perfectly valid request.

This can happen, because traditionally, if you were explicitly granted a sufficient number of system privileges, you implicitly received object privileges for all tables as well. For decades people found this acceptable. Recently, however, companies began to ask: Is it really necessary and is it really desirable that a database administrator, who is supposed to manage the database structure, is by default able to read (and even change) all data in the database?

Oracle Database Vault

A solution to this problem requires a new privilege management strategy in the database. This strategy should continue to provide system privileges and object privileges, but it should get rid of implicitly granted object privileges.

This is exactly what Oracle Database Vault does. It replaces the traditional, somewhat clumsy privilege management strategy with a new, more flexible one. It eliminates all implicit grants and instead provides a means to explicitly define access rights as well as the circumstances under which they are effective. This goes far beyond traditional user – privilege or user – role correlations.

30

Oracle Database Vault allows companies to implement and enforce concepts such as the segregation of duties or the four eyes principle.

Oracle Database Vault for SAP

Oracle Database Vault, as sold by Oracle, is just a tool box.

It is true that it comes with predefined realms and roles, but those are realms for system tables and very general

(if fundamental) roles. These predefined components allow

Oracle Database Vault to be functional and allow you to use it, but they do not protect your application-specific data. That is because Oracle does not know anything about your applications and your data. Oracle can only give you a toolbox, and it is up to you to determine your security requirements and translate these requirements into an access control policy.

But there is an important difference. As long as customers use home grown applications, it is simply not plausible for Oracle to do more. However, if thousands or tens of thousands of companies use a certain standard application and the security requirements of all these companies are

(at least to a certain point) identical, because they are results of the application design, then it makes much more sense for Oracle to analyze the requirements and implement a basic security policy.

Oracle has actually done this, saving customers the time that is needed to implement the boring basics of an application-specific security policy, and protecting these companies from forgetting to implement some of the basics. As of today, Oracle provides a whole family of predefined application-specific Oracle Database Vault policies, and Oracle Database Vault for SAP is a member of this family.

Figure 10: Oracle Database Vault – Privileged user access control and analysis

Real Application Testing (RAT)

Challenge:

Database software patches or upgrades, modified database server configurations, and the implementation of new database features/options can improve performance, availability and security of the database server and the whole system. In particular if the implementation must take into account customer- or application-specific characteristics, administrators will want to know in advance how the new feature or configuration works in the production system.

Value Proposition:

The main problem with many test systems is that the workload applied to them is smaller than or different from the workload of the production system, and that a new feature or configuration works well in the test system, but not in the production system. Therefore Oracle Real Application Testing allows customers to capture production database workload and replay it on a test system. Combining these two steps, allows for the true effects of the changes to be understood using a real-life workload before they are implemented in production systems.

Certification/Support:

Oracle Real Application Testing is certified for all SAP NetWeaver applications.

Implementations are supported by SAP.

Versions:

Oracle Database 11g, Oracle Database 12c

Implementation:

As this is a database-only feature, no SAP tool support is required. For details see SAP

Note 1426980.

Oracle Database Options and Packs for SAP Customers

31

Oracle Real Application Testing enables you to perform real-world testing. By capturing production database workloads and assessing the impact of system changes before production deployment, it minimizes the risk of instabilities associated with changes. Oracle Real Application Testing comprises two components: Database

Replay and SQL Performance Analyzer.

Database Replay

Load testing today is generally done using tools that allow testing teams to generate synthetic workloads based on what they expect users to do on a system. These workloads can then be replayed by application virtual users, which simulate the end users by submitting requests to the application. Although widely used, this approach has a number of shortcomings when it comes to testing database level changes:

• Creating the synthetic workload can take a considerable time and requires programming expertise.

• User behavior is not well understood, so many possible workflows are often missed in the synthetic tests.

• Production scale database concurrency is near impossible to simulate with these tools.

• A full application stack is required for testing as these tools simulate end users.

The Database Replay feature included in Oracle Real Application Testing provides DBAs and system administrators with the ability to faithfully, accurately and realistically rerun actual production workloads, including online user and batch workloads, in test environments. By capturing the full database workload from production systems, including all concurrency, dependencies and timing,

Database Replay enables you to realistically test system changes by essentially recreating production workloads on the test system, something that a set of scripts can never duplicate. With Database Replay, DBAs and system administrators can test:

• Database upgrades, patches, parameter, schema changes, etc.

• Configuration changes such as conversion from a single instance to RAC, ASM, etc.

• Storage, network, interconnect changes.

• Operating system, hardware migrations, patches, upgrades, parameter changes.

SQL Performance Analyzer

Database Replay delivers half of what Oracle calls Real

Application Testing; the other half is provided by another tool, SQL Performance Analyzer. The main difference between these two tools is the scope involved: Whereas

Database Replay applies to the capture and replay of all activities in a database, SQL Performance Analyzer allows you to capture specific SQL statements and replay them.

The latter offers a significant advantage for SQL tuning, because you can tweak the SQL statement issued by an application and assess its impact.

SQL Performance Analyzer (SPA) can predict and prevent

SQL execution performance problems caused by environment changes. It provides a granular view of the impact of environment changes on SQL execution plans and statistics by running the SQL statements serially before and after the changes.

Figure 11: Real Application Testing (RAT) – Capture and replay real database workload

32

Enterprise Manager Packs

Challenge:

Monitoring and managing a complete IT infrastructure often can be challenging. Administrators may end up with a considerable number of management tools designed for this or that particular purpose.

Value Proposition:

Oracle, being a vendor of the whole

IT stack from hardware via databases to applications, realized that there is a need for an integrated enterprise management tool. However, in order to avoid unnecessary complexity, Oracle Enterprise Manager

Grid/Cloud Control is divided into a base product and several packs dedicated to special features. With or without packs – Oracle Enterprise Manager always provides a complete view of the IT landscape.

Certification/Support:

Generally speaking, SAP on

Oracle customers have a choice. On the one hand there is the BR*Tools family of management tools provided by SAP. These tools include SAP-specific knowledge and are therefore easy to use. On the other hand there are the powerful Oracle Enterprise Manager and its packs. However, in some cases Oracle

Enterprise Manager or one of its packs are required

– either because there is no BR*Tools support for an

Oracle Database feature (example: Database Vault) or because SAP and Oracle functionality are integrated so completely that the former is not possible without the latter (example: SAP DBA Cockpit and Enterprise

Manager Diagnostics Pack).

Versions:

Oracle Database 11g, Oracle Database 12c

Implementation:

For general information about using

Oracle Enterprise Manager in SAP environments see

SAP Notes 355770 and 1028068. Special use cases are discussed in additional notes and white papers.

SAP DBA Cockpit and Enterprise Manager Diagnostics Pack

The Oracle Diagnostic Pack provides automatic performance diagnostic and advanced system monitoring functionality. The Diagnostic Pack includes the following features:

• Automatic Workload Repository (AWR): AWR is a built-in repository within every Oracle Database that contains operational statistics about that particular database and other configuration and usage information.

At regular intervals, the Oracle Database takes a snapshot of all its performance statistics and workload information and stores it in AWR. AWR forms the foundation for most of the self-management functionality of Oracle

Database. It is the source of information that gives the

Oracle Database a historical perspective on how it is being used and enables it to make decisions, which are accurate and specifically tailored for the system‘s environment. Most of the self-managing features of the Oracle

Database rely heavily on the information captured in

AWR. The data in AWR is also useful for diagnosing all types of performance issues ranging from persistent or comparative performance diagnosis.

• Automatic Database Diagnostic Monitor (ADDM):

ADDM builds upon the data captured in AWR. ADDM makes it possible for the Oracle Database to diagnose its own performance and determine how any identified problems could be resolved. ADDM runs automatically after each AWR statistics capture and makes the performance diagnostic data available immediately.

ADDM examines data captured in AWR and performs analysis to determine the major issues on a proactive basis, recommends solutions and quantifies expected benefits.

• Active Session History (ASH): All active database sessions are automatically sampled once every second and stored in the ASH. The data is captured in a rolling buffer in database memory. The ASH data shows where the database is currently spending its time and highlights any performance bottlenecks. As ASH captures the session state with many performance attributes, the in-memory ASH data can be very effectively used to understand the database workload profile and pro-actively diagnose any transient performance issue, such as a CPU spike or an I/O storm, that occurs for a very short duration.

Oracle Database Options and Packs for SAP Customers

33

Oracle Diagnostics Pack diagnostics and analysis features such as ADDR, ASH, and AWR are tightly integrated with SAP‘s DBA Cockpit. Therefore DBA Cockpit has a mandatory requirement for Oracle Diagnostics Pack.

Database Lifecycle Management Pack

The Provisioning and Patch Automation Pack automates the deployment of software, applications, and patches.

It makes critical data center operations easy, efficient and scalable, resulting in lower operational risk and cost of ownership. The ability to provision the entire software stack that includes the operating system, middleware and database, supplemented by comprehensive reporting tools, make the Provisioning and Patch Automation Pack an extremely significant entity in overall system management space.

The Provisioning and Patch Automation Pack includes an end-to-end patching solution that works seamlessly across a wide range of products and customer environments.

The patching application automates the deployment of

Oracle patches for the database and the underlying operating system. The application takes care of pre- and post

-patching steps such as shutdown and startup of services, and dictionary changes, if required. It also leverages the flexible Deployment Procedure framework, that lets users add custom steps for specific actions within the patching process.

The Provisioning and Patch Automation Pack also comes with out-of-box Deployment Procedures to provision the Oracle Database (both single instance database and

RAC), Oracle Clusterware and Oracle Automatic Storage

Management from “gold images” following the best practices for maximum availability. The gold images are tested and approved software images and can be patched to any level before deployment.

For SAP environments, the MOPatch utility is integrated with the deployment procedures of Oracle Enterprise

Manager to automate the orchestration of patching for

Oracle Databases. See white paper “Patching of Oracle

Databases in SAP Environments using Oracle Enterprise

Manager”.

Figure 12: Oracle Enterprise Manager Diagnostics Pack and SAP DBA Cockpit

34

Summary

In a certain sense, the Oracle Database has always been a data management infrastructure, and therefore there has always been a need to provide support for two opposite goals: consolidation, and separation or differentiation.

Oracle has always been a multi-user, multi-schema, and possibly multi-application database. Therefore – apart from the very basic split of the available data into different tables – there was a need to separate application-specific schemas. For performance reasons, there was a need to separate the files used for user/application data from those used for redo log or undo information. Being a complete data management system, the Oracle Database has nevertheless always provided adapters, gateways, and other means that allow interactive users and batch jobs to join data stored in the Oracle Database with data coming from other, external data sources.

However, as a result of the growing amount of data, increasing workload, and shrinking maintenance windows that many customers experience, Oracle needed to provide additional, more sophisticated solutions. This has happened in Oracle Database 10g, in Oracle Database 11g, and again in Oracle Database 12c.

Defining Subsets of Data

Released for the first time several versions and many years ago, Table and Index Partitioning is still a good example of data differentiation and a powerful technology. Therefore it has been discussed at the very beginning of this article.

It is used to define subsets of table data which can be accessed and managed independently.

Subsets and Access Patterns

When determining a specific partitioning strategy it is important to not only look at the data but to consider the access patterns as well. Partitioning a table by month may turn out to be useless or even negatively impact performance, if most queries access the data by location.

However, distinguishing subsets of data by access pattern in new, previously impossible ways is the main goal of many Oracle Database 12c features and options.

Heat Map, a feature included in Advanced Compression, automatically tracks modification and query timestamps, thus providing detailed insights into how data is being accessed. Automatic Data Optimization automatically moves and compresses data according to user-defined policies based on the information collected by Heat Map.

This means that storage and compression tiering can be implemented, i.e. the selection of different storage media and different compression algorithms for different subsets of data which are defined by different access characteristics.

Oracle Database In-Memory allows administrators to distinguish between different types of transactions as well as different data representations in memory and to avoid the trade-off which results from the requirement to pick one single data format for all types of transactions and applications. Based on the new In-Memory option, Oracle

Database 12c can provide data used by OLTP transactions in row format, and at the same time data used by analytics in column format.

Workload Distribution

Other options focus on workload distribution. A prominent example is Real Application Clusters (RAC), which allows customers to split the system workload and let many servers, running at least as many Oracle instances, handle the workload. It is up to the customer to decide whether all instances should handle the same type (or mixture) of workload(s) or different instances should be responsible for different types of workload (e.g. interactive transactions vs. batch jobs).

Oracle Database Options and Packs for SAP Customers

35

Figure 13: Oracle’s multi-tiered data management infrastructure

In addition to enabling workload distribution, RAC increases the system availability. This is even more true for

Data Guard. Nevertheless, Data Guard does not require the standby database to be idle. It can be used for operation such as backup or – under certain conditions – reporting.

In other words: Data Guard helps implement workload distribution as well.

Data Access Policies

In a somewhat different sense, Oracle‘s security options are related to access patterns as well. In particular Database

Vault lets security administrators define and enforce access policies which prevent privileged users from reading or manipulating data they are not supposed to access. Phrases such as “segregation of duties” make it very clear that even here we are talking about the balance between separation and combination.

Database Administration

Oracle Database 12c Multitenant moves the data management infrastructure principle to a completely new level:

We do not simply talk about an infrastructure for many tables or many users. We talk about an infrastructure for many databases. And here consolidation clearly requires separation.

To put it simply, Multitenant is about the distinction between those administration tasks that should be executed for every single database individually (because there are differences) and those that can be executed once for all or at least for a certain group of databases (because there are no differences). E.g. to apply a certain patch to 25 database systems means to repeat the very same process

25 times. Therefore Oracle Multitenant moves this operation to the Container Database layer, where it can be done once for all Pluggable Databases. On the other hand, a point-in-time recovery is an operation to be performed on the PDB level, as it should not affect other PDBs.

In addition, the Provisioning and Patch Automation Pack allows administrators to automate those operations which are similar in all cases. Examples are the deployment of

Oracle patches or the provisioning of new systems based on “gold images”.

Monitoring and Testing

Will your systems benefit from these features? How can you be sure? And how should the features be implemented in order to have a positive impact on your systems? Real

Application Testing will help you to answer these and similar questions.

36

From best Performance over best Availability to best Support for DB Consolidation – a lot of good Reasons/Differentiators using Oracle Database for SAP applications

W H Y O R A C L E D A T A B A S E A N D E N G I N E E R E D S Y S T E M S F O R S A P ?

From SMEs to the largest companies around the world, tens of thousands of customers benefit from using the

Oracle Database for SAP. There are many good reasons for this. Have a closer look at the outstanding differentiators which make Oracle Database for SAP the primary choice for the majority of SAP customers.

For more than 28 years Oracle and SAP have collaborated to optimize the Oracle Database for SAP customers.

Renewing commitments and agreements underline the long-established relationship and partnership. Above all:

SAP customers benefit from Oracle innovation. Oracle innovation provides flexible solutions which allow you to meet your business needs and requirements. On the other side SAP customers value the great sustainability and protecting investments using Oracle Database for SAP applications.

As we look in more detail, it will be clear why Oracle

Database for SAP is the leading and best RDBMS running

SAP applications. In this context, let‘s have a closer look at the key differentiators between the Oracle Database for

SAP as compared against other databases which can be used in combination with SAP applications. There are not less than 8 differentiators, regarding Oracle Database for SAP

11g, 12c and Oracle Exadata Machine respectively Oracle

Engineered Systems (with important features/options):

Oracle Database for SAP Differentiators

1.) Best Performance & Scalability

Oracle has world record SAP SD and BI-D (BI-Data Mart) benchmark results, with exceptional scaling and performance across SMP and Cluster environments on Unix and Linux.

Oracle Real Application Clusters (RAC) provide a flexible way to achieve near linear scalability of SAP applications.

With RAC, customers have a choice to either scale up or scale out the database server layer. Since all RAC nodes are active, it helps SAP customers to meet the demands of production workload requirements. Widely adopted by customers, Oracle RAC is the only generally available clustered database solution certified for all SAP products.

RAC makes SAP resources highly available based on Oracle

Clusterware and avoids the need for 3rd party software.

Oracle Automatic Storage Management (ASM) is a volume manager and a file system for Oracle Database files that supports single-instance Oracle Database and Oracle Real

Application Clusters (Oracle RAC) configurations. ASM is Oracle‘s recommended storage management solution that provides an alternative to conventional volume managers, file systems, and raw devices.

The Oracle Database In-Memory Option accelerates

Analytics, Data Warehousing, Reporting and OLTP performance. The In-Memory Option to Oracle Database

12c is 100 percent compatible with existing applications and leverages all existing Oracle Database functionality.

Every Application that runs on Oracle Database 12c can automatically and transparently take advantage of Oracle

Database In-Memory Option. Existing applications will retain full functionality while experiencing effortless speedups. New applications can be developed that were previously impractical due to performance limitations.

SAP BW Flat Cubes with Oracle Database In-Memory: The data modeling technique Flat Cubes (also called “HANA-

Optimized InfoCubes” by SAP), allows customers to

Why Oracle Database and Engineered Systems for SAP?

37 simplify the SAP BW data model. Benefits for SAP on

Oracle customers: Cost savings through higher performance and optimized integration of SAP BW with Oracle Database 12c, no indexes and aggregates required, faster query response times and faster data loads.

With Oracle Exadata Database Machine customers can scale up/out incrementally and on demand. Start with the appropriate Exadata size – eights, quarter, half, or full rack.

Exadata is upgraded to the next larger size before you need additional speed or capacity. No need for a forklift upgrade, simply scale up/out the existing system.

Exadata includes a unique technology to offload data intensive SQL operations into the Oracle Exadata Storage

Servers and only the rows and columns that are directly relevant to a query are sent to the database servers.

As a result, it provides outstanding performance for transaction processing and data warehousing. SAP transactions requesting data will likely be serviced from flash memory for ultra-fast retrieval. Reporting and Batch users will not interfere with SAP transactional users. SAP BW/BI data warehouses will return queries to users orders of magnitude faster.

2.) Best Deployment Flexibility

Widest range of supported platforms; Unix – Linux –

Windows – “Oracle is Oracle is Oracle”. The same code base across all operating systems means, Oracle has the same features, tools and functionality on all hardware platforms and operating systems, so customers can choose the most cost effective platform for their implementations.

Should customers require a change in operating systems,

Oracle offers fast and efficient Oracle-to-Oracle (O2O) migration services. Many customers cannot afford the downtime associated with an offline migration. For these situations, Oracle offers it’s Triple-O service. The service is a near zero downtime online Oracle to Oracle migration.

The outage requirements are then cut from hours to minutes independent of the database size.

A new option for Oracle Database 12c, Oracle Multitenant helps customers reduce IT costs by simplifying consolidation, provisioning, upgrades, and more. It is supported by a new architecture that allows a Multitenant container database to hold many pluggable databases. An existing database can be simply adopted, with no change, as a pluggable database. No changes are needed in the other tiers of the application.

Traditionally, Oracle has provided Oracle Database Server software to be installed on systems made up of third-party hardware and a third-party operating system. This approach is still possible. However, in addition Oracle provides

“Engineered Systems”, where Oracle manufactures the machine, the operating system and the database. All the embedded components to run an Oracle Database are pre-configured, pre-tuned and pre-tested by Oracle experts, eliminating weeks or months of effort typically required to deploy a high performance system.

3.) Best Availability and Reliability

Real Application Clusters (RAC) for SAP removes the database server as a single point of failure. The database remains online as long as one or more database instance is still up and running. Oracle Data Guard complements

Oracle RAC, providing a disaster recovery solution that requires no SAP downtime in case of failure. Data Guard is often used in combination with Flashback (technology to rewind database changes without any restore to dramatically minimize downtime). Online Patching allows customers to install single or bundle patches completely online, without requiring the database instance to be shut down.

SAP customers are able to use Oracle Cloud File System

(ACFS), which is part of Oracle Database 12c Release 1

(12.1.0.2) (and can be used as well on X2, X3, X4 and

X5) to complement Oracle Automatic Storage Management

(ASM) in order to store non-Database files on ACFS which will be even available on Exadata X5 to store SAP related files like/sapmnt and/usr/sap/trans and skip using external

NFS file systems.

Oracle Database 12c Business Benefits for SAP Customers (1)

38

Oracle Exadata Database Machine for SAP customers is a highly engineered and pre-validated configuration.

It provides built in High Availability, ‘out of the box’.

With Exadata’s redundant architecture, all single points of failure are eliminated. Familiar features such as mirroring, fault isolation, and protection against drive and cell failure have been incorporated into Exadata to ensure continual availability and protection of data.

Exadata is prebuilt, reducing time and costs for deployment, installation, and configuration (HW, OS, DB,

RAC, Clusterware etc.).

4.) Best Support for Very Large Databases

The Oracle Database is well known for providing the most efficient use of disk space. This is extremely important to SAP customers as the size of their databases continue to grow dramatically.

Compression of B Tree indexes, which make up to one third of disk space allocated to databases in SAP environments, reduces I/O and improves overall performance by allowing more index information to be stored in the same amount of memory (cache).

Table compression, implemented in Oracle’s Advanced

Compression, uses a unique algorithm that eliminates duplicate values within a database block, even across multiple columns. This approach combines disk space reduction, performance benefits and ease of management.

Oracle Database 12c Advanced Index Compression uses an unique algorithm to optimize space for index entries at a block level resulting in less amount of disk space needed, faster access to data and higher throughput of the

SAP system.

Out-of-line LOBS (SecureFiles) Compression, Client-

Server Network Compression, Data Guard Compression,

Expdp Compression and RMAN Backup Compression are further enhancements to the compression features SAP customers can benefit from.

The complete unload and load of data during a Unicode migration (required by all new SAP releases) was optimized by Oracle to achieve the fastest SAP Unicode Migrations, with up to 1 terabyte/hour data transfer rates and it is fully integrated with SAP products. Even the largest multi terabyte databases have been migrated in one weekend.

SAP customers using Oracle Databases also take advantage of a rich collection of table partitioning types to reduce

I/O and improve performance. Oracle Database 11g

Release 2 enriches this list with sub-partitioning and interval partitioning meant to enhance design flexibility and application performance.

In Oracle Database 12c, several new features have been added to the Advanced Compression Option (ACO) which enhance the storage management capabilities of Oracle

Database. Heat Map automatically tracks modification and query timestamps, providing detailed insights into how data is being accessed.

Hybrid Columnar Compression – available on Oracle Engineered Systems (Exadata platform) – enables the highest levels of data compression and provides enterprises with tremendous cost-savings and performance improvements due to reduced I/O. Average storage savings can range from

10x to 15x depending on which Hybrid Columnar Compression level is implemented.

Many environments are reaching the end of their useful life and are costly to maintain. Exadata and Exalogic provide a simple and easy way to manage an environment – a viable option for a private cloud.

SAP Business Warehouse:

- Huge and complex infocubes, queries or transactions

with large database time

- Large daily extracts with a limited time window

- Large extracts can flood the network

Oracle Database 12c Business Benefits for SAP Customers (2)

Why Oracle Database and Engineered Systems for SAP?

39

5.) Best Database Security

Compliance and security are more important now than ever before.

Oracle’s Advanced Security Transparent Data Encryption (TDE) makes encryption of sensitive data simple by transparently encrypting data when it is written to disk. Oracle Database provides; Tablespace Encryption

(encrypts all data within one tablespace), RMAN Backup encryption, Data Guard Secure Network, Expdp, and

SecureFile Encryption.

With Oracle Database Vault, protective realms around SAP application database objects can be established to prevent privileged database users from accessing sensitive data and to enforce separation of duties among privileged database users.

Oracle Database Vault helps customers meet regulatory compliance requirements by enforcing separation of duties.

Database Vault 12c privilege analysis with minimizing number of granted roles.

All Oracle Security features are available for all database configurations (single instance, RAC) and all Hardware/

OS platforms – including the Exadata Database Machine.

Exadata for SAP satisfies even the most stringent security and high-availability requirements. It is a complete, pre-built, balanced and secure cloud-based machine for mission critical databases with all available high security features of Oracle, like Database Vault.

6.) Best Manageability and Self-Management

Oracle Enterprise Manager Grid Control (EM), SAP DBA

Cockpit, and SAP BR Tools rely on Oracle Automatic

Workload Repository (AWR) that automatically stores workload and performance statistics so administrators and support engineers can analyze and quickly resolve performance issues, whether the root cause happened hours or days before.

Real Application Testing (RAT) to evaluate and implement changes in the customer data center infrastructure e.g. operating system, hardware migrations, patches and upgrade changes. Database Replay (part of RAT) enables customers to realistically test system changes essentially recreating production workloads on the test system.

A very exciting functionality for SAP customers in

Oracle 12c is Information Lifecycle Management (ILM) and Automatic Data Optimization (ADO). These features combined along with the Heat Map can be utilized to build a robust ILM strategy. This strategy incorporates automatic tiering and compression of your data to meet the policies you define.

Bundle Patches are created and certified in conjunction with SAP and bundled for simplicity. Applying the

Exadata Bundle Patches and the SAP Database Bundle

Patches is all that is required. BR TOOLS have been expanded to support ASM and Exadata.

Exadata for SAP:

– Makes complex integration work and manual tuning

(database, storage, network, and server) superfluous

– Optimally supports implementations, migrations, and consolidations for quick, inexpensive project runtimes

– Enables users to implement a highly efficient centralized data pool featuring a multitude of system databases

7.) Best Support for DB Consolidation

Oracle supported traditional DB consolidation methods like virtual machines or schema consolidation for a long time. And SAP customers benefitting from saving costs and effective infrastructure optimization.

Oracle Engineered Systems like Exadata Database Machine gave customers new opportunities for DB consolidation and infrastructure cost savings with reduced complexity.

More-and-more SAP customers are using Exadata for this stated purpose: the consolidation of their numerous “SAP databases”.

SAP can be included in enterprise-wide database consolidation plans on Oracle Exadata Database Machine. Consolidate all databases on a modernized database platform and lower overall database costs due to consolidation; there are great advantages of the opportunity to consolidate multiple dispersed Oracle Databases into one Exadata environment. Administrators can focus on managing

Exadata, not on maintaining own unique configurations.

40

Why Oracle Database and Engineered Systems for SAP?

Oracle Database12c Multitenant gives DB consolidation projects above the said before massive additional advantages.

The Multitenant Option provides higher productivity and resource/cost savings for customers who realize DB consolidation projects by significant simplification. Oracle

Multitenant introduces a new architecture that enables customers to easily consolidate multiple databases, without changing their applications, but allowing the management as one grouped resource with minimized memory resources.

SAP customers can manage many databases as one (patching, backup, etc.). More efficient utilization of system resources/resource management can be realizing in an easy and very efficient way.

8.) Best Integration of Hardware and Software

For years Oracle Database Server Software checks the ability of relevant hardware components. E.g. for using flash, encryption etc. With Oracle 12c In-Memory scans use super-fast “Single Instruction Multiple Data Values”

(SIMD) vector instructions, if supported by CPU. So, the get together or the integration of hardware and software will be reached by using Oracle 12c a new step of quality and effectiveness.

Exadata is an Oracle Engineered System and is prebuilt, reducing time and costs for deployment, installation, and configuration (HW, OS, DB, RAC, Clusterware etc.).

Exadata for SAP customers consolidates platforms, databases, provides best integration of hardware and software in the first place and reduces power and cooling of your

SAP environment.

Oracle Database 12c certification:

Phase 1, called Base Certification, has already been completed in March 2015. Included are all features and options that have been previously available in Oracle

Database 11g plus several Oracle Database 12c features which are either completely transparent or require only minimal integration effort.

Phase 2, completed in June 2015 is the first to offer a major new Oracle Database 12c option: Oracle Database

In-Memory, a completely new option in Oracle Database 12c.

Phase 3, completed in December 2015, has added the new

Information Lifecycle Management (ILM) features included in Oracle Database 12c Advanced Compression, as well as Hybrid Columnar Compression (HCC) with row-level locking on Oracle Exadata and Oracle SuperCluster.

Phase 4, Oracle Multitenant completed the certification process for SAP customers. This option allows for the consolidation of many databases into a single container database. It is based on a completely new database architecture and therefore requires a considerable Oracle/SAP integration effort.

Oracle Database for SAP Differentiators

CERTIFICATION SAP

®

Standard Application Benchmarks

41

N E W ! 1 3 0 , 0 0 0 S A P S D B E N C H M A R K U S E R S O N O R A C L E S P A R C M 7 - 8

S E R V E R H A S B E E N C E R T I F I E D B Y S A P

For More Information

SAP standard application benchmarks:

http://www.sap.com/benchmark

Trademark Notice

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries.

See

http://www.sap.com/corporate-en/legal/copyright/index.epx

for additional trademark information and notices.

Oracle and Java are trademarks or registered trademarks of Oracle Corporation, its subsidiaries, and related companies in the US and elsewhere.

All SPARC trademarks are used under license, and are trademarks of SPARC International, Inc. in the USA and elsewhere. The SPARC64 trademark is a trademark of SPARC International, Inc. in the US and elsewhere, and is used under license.

UNIX is a registered trademark of the Open Group in the US and elsewhere.

SPEC (The Standard Performance Evaluation Corporation), SPECint and SPECfp are registered trademarks of Standard Performance Evaluation Corporation (SPEC) in the US and other countries.　

Details and the latest information of this benchmark can be found at

www.spec.org

.

All other product names and company names mentioned herein are the trademarks or registered trademarks of their respective firms.

42

N E W W O R L D R E C O R D !

S A P S D 1 3 0 , 0 0 0 B E N C H M A R K U S E R S O N

c

Oracle‘s SPARC Servers have produced amazing results setting a new 8-processor systems world record for the

SAP SD two-tier benchmark. These results attest to the power of the SPARC architecture and the unique scalability of Oracle Solaris and the Oracle 12c Database.

Customers running SAP on Oracle servers can leverage such performance to consolidate workloads and dramatically reduce data center costs.

The SAP SD Standard Application Benchmark is an ERP business test that is indicative of full business workloads of complete order processing and invoice processing, and demonstrates the ability to run both the application and database software on a single system. It represents the critical tasks performed in real-world ERP business environments and it‘s the benchmark most widely used by SAP customers.

System /CPU CPUs

Cores

Threads

OS Database Users

Release

SPARC M7-8 /

SPARC M7

@ 4.133GHz

8 /

256 /

2048

Oracle Solaris 11

Oracle Database 12c

EHP5 for SAP

ERP 6.0

SAPS Certification

#

130,000 713,480 2016020

IBM Power

Enterprise

System E870 /

POWER8

@ 4.19 GHz

8 /

80 /

640

AIX 7.1

DB2 10.5

EHP5 for SAP

ERP 6.0

79,750 436,100 20144034

Fujitsu PRIME-

QUEST 2800E3

Intel Xeon E7-

8890 v4

@ 2.20 GHz,

HPE Integrity

Superdome X /

Intel Xeon E7-

8890 v3

@ 2.5 GHz

8 /

192 /

384

16 /

288 /

576

Windows Server 2012

R2 Standard Edition /

SQL Server 2012

EHP5 for SAP

ERP 6.0

74,000 404,200 2016023

Windows

Server 2012

R2 DC Edition

SQL Server 2014

EHP5 for SAP

ERP 6.0

100,000 545,780 2016002

New World Record ! SAP SD 130,000 Benchmark Users

43

The SPARC M7-8 server (8 cpus/256 cores/2048 threads) running SAP Enhancement Package 5 for SAP ERP 6.0 is 63% faster than the eight-cpu IBM Power Enterprise

System E870 (8 cpus/80 cores/640 threads) and 30% faster than the HPE Integrity Superdome X which even contains twice as many cpus (16 cpus/288 cores/576 threads).

The Oracle database logfiles resided on an Oracle FS1-2 storage system which wrote 800 MB/sec with a service time of 1 millisecond in average during the high load phase of the benchmark. To achieve these results, the

Oracle FS1-2 storage system was solely configured with

HDDs, no SSD were needed.

Link to benchmark certification

130,000 SAP SD Benchmark Users on Oracle‘s SPARC M7-8

Server Certified by SAP (PDF) http://www.oracle.com/us/solutions/sap/nl25benchmark-sparc-m7-3021033.pdf

Oracle and Java are registered trademarks of Oracle and/ or its affiliates. SAP and all SAP logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. Other names may be trademarks of their respective owners.

Results as of May 30th, 2016. Source: SAP,

www.sap.

com/benchmark

.

The following two-tier SAP Sales and Distribution (SD) application benchmarks have been certified with SAP enhancement package 5 for SAP ERP 6.0:

• SPARC M7-8, 8 cpus / 256 cores / 2048 threads,

SPARC M7, 4.133 GHz, 130000 SD Users, 713480

SAPS, Solaris 11, Oracle 12c, SAP Certification

Number: 2016020

• HPE Integrity Superdome X, 16 cpus / 288 cores /

576 threads, Intel Xeon Processor E7-8890 v3, 2.5

GHz, 100000 SD Users, 545780 SAPS, Windows

Server 2012 R2 Datacenter Edition, SQL Server 2014,

Certification Number: 2016002

• IBM Power Enterprise System E870, 8 cpus / 80 cores / 640 threads, POWER8, 4.19 GHz, 79750 SD

Users, 436100 SAPS, AIX 7.1, DB2 10.5, Certification

Number: 2014034

• Fujitsu PRIMEQUEST 2800E3, 8 Processors / 192

Cores / 384 Threads, Intel Xeon Processor E7-8890 v4, 2.20 GHz, 74000 SD Users, 404200 SAPS,

Windows Server 2012 R2 Standard Edition, SQL

Server 2012 , Certification Number 2016023

44

Bosch GmbH accelerates business processes and reduces costs with Oracle Database In-Memory – no changes to existing

SAP application required

M A J O R I M P R O V E M E N T I N S A P C R M U S E W I T H O R A C L E D A T A B A S E

I N - M E M O R Y

The Bosch Group is a leading global supplier of technology and services. It employs roughly 375,000 associates worldwide (as of December 31, 2015). The company generated sales of 70.6 billion euros in 2015. Its operations are divided into four business sectors: Mobility Solutions,

Industrial Technology, Consumer Goods, and Energy and

Building Technology. The Bosch Group comprises Robert Bosch GmbH and its roughly 440 subsidiaries and regional companies in some 60 countries. Including sales and service partners, Bosch’s global manufacturing and sales network covers some 150 countries. The basis for the company’s future growth is its innovative strength. Bosch employs 55,800 associates in research and development at roughly 118 locations across the globe. The Bosch

Group’s strategic objective is to deliver innovations for a connected life. Bosch improves quality of life worldwide with products and services that are innovative and spark enthusiasm. In short, Bosch creates technology that is

“Invented for life.”

Bosch GmbH is known for being a market leader and an innovative company. They often uses the tagline “technology invented for life” which provides insight into their business objectives to improve the quality of life, and to deliver innovation for a “connected life”.

For well over a decade, Bosch has relied on Oracle as their preferred database vendor for use with SAP. The Oracle database is a core element and important cornerstone in the Bosch infrastructure. Oracle databases are operated autonomously in combination with the various SAP applications and ideally respond to the varied needs of this successful and diversified group.

The IT department consists of more than 1,500 IT specialists and process experts. It was only logical as an

Oracle/SAP customer to fully explore the features and options of the new Oracle Database 12c at an early stage.

In mid-2015, the primary focus was on the features and benefits of Oracle Database In-Memory.

“We wanted to find out exactly how Oracle Database

In-Memory could help us to implement optimizations in our use of SAP. This applied to both OLAP and OLTP applications. We quickly realized that we stood to benefit in many ways, especially in terms of SAP CRM usage,” explains a project manager and database expert from the

IT operations organization.

The Bosch IT team discussed solution scenarios and use cases both in-house and with Oracle. It became clear that

Oracle Database In-Memory offered significant advantages when used with SAP BW Analytics.

But even more important to Bosch was the fact that Oracle

Database In-Memory in Oracle 12c also enables planned, prioritized optimizations to be achieved in OLTP systems, and specifically with SAP CRM. This was in fact the most pressing problem. The Bosch IT team needed a suitable solution to eliminate sub-optimum performance when using SAP CRM / OLTP at reasonable cost. Oracle Database

In-Memory in Oracle 12c was the right way to go.

The challenge of secondary indexes

In this CRM use case it was mainly secondary indexes, as well as the extra custom-made indexes that had to be regularly created, that proved to be problematic. According to

Bosch: “As a result of the intensive and distinctive use of

SAP CRM functions by users, the IT team was obliged to continually create extra indexes for certain CRM objects and tables. This was the only way to use the system in line with our individual usage requirements. However, it wasn‘t possible to achieve 100% application coverage in this way, especially in terms of search options and search availabilities in CRM. This is because not all such search options can be supported by additional indexes. Some application functions simply resulted in a timeout.”

Approximately, 80 additional indexes were created and accumulated over time. This resulted in a considerable increased need for maintenance demands and performancerelated tuning as well as cost-intensive resource use. It was also necessary to set aside a large amount of storage capacity for these indexes, which were also large objects.

Major Improvement in SAP CRM use with Oracle Database In-Memory at Bosch GmbH

45

The SAP CRM system is used by around 3,500 users throughout the Bosch Group, The CRM system being discussed here is one of several CRM systems Bosch operates. The largest of which has a data volume of over 1TB.

Following a PoC and several tests, it became clear that

Oracle Database In-Memory is not only effective as a performance enhancer but it is equally as effective as a means of countering problematic secondary indexes. With Oracle

Database In-Memory, many of these indexes can be removed. This prompted Bosch to put Oracle 12c with

Oracle Database In-Memory to productive use in conjunction with the SAP CRM system. A detailed analysis was carried out to find out which tables were suitable for

In-Memory. The IT team identified them and the most important ones were able to be replaced. One major advantage is that the benefits of Oracle Database In-Memory technology can be gained without any changes to SAP applications, with the continued use of existing hardware

(virtualized and Unix-based servers), and without data migration. It is usually only necessary to provide In-Memory servers / RAM hardware resources (virtualized or non-virtualized) for tables that were to be involved with

In-Memory processing.

High satisfaction with Oracle Database In-Memory

„The improvements achieved in the SAP CRM system through Oracle Database In-Memory have turned out exactly as we planned. User satisfaction has risen considerably and IT-supported business processes are now running smoothly without delays and can be fully utilized as standard. The amount of IT administration has also been noticeably reduced thanks to the substantial reduction in index creation and maintenance, which in turn results in cost savings.

In the use case described, Oracle Database In-Memory eliminated the need for many secondary and custom-made indexes of large tables while accelerating OLAP use.

Inserts, Updates and Delete statements processed normally. No negative impact on the system performance was observed.

Additional tuning can be accomplished easily by increasing the cache for the In-Memory Store and assigning specific tables to occupy the space. The Oracle In-Memory Advisor, a component supplied with Oracle 12c, also makes it possible to identify tables suitable for use with In-Memory.

Problems / challenges

• Bosch was looking for ways to optimize its use of SAP

CRM. Specific tables having a large number of secondary indexes were causing particular difficulties.

These difficulties resulted in frequent user dissatisfaction, costly administration and maintenance, and the provision of additional IT resources (such as storage).

Solution

• With Oracle Database In-Memory, it is possible to replace additional custom-made indexes. Oracle

In-Memory in Oracle 12c is used for the tables that made these indexes necessary

Benefits

• Now users can make full and effective use of SAP CRM

• Reduced costs for system / database administration

• In-Memory is only activated for selected tables

• Saving in terms of storage resources for secondary indexes that are no longer needed

• Lower number of indexes means accelerated business

processes

• Faster SAP CRM response times and higher system

performance.

• Use of Oracle Database In-Memory without changes to

SAP applications

• Continued use of existing hardware; only In-Memory /

RAM must be provided

46

Renowned ceramics manufacturer Villeroy & Boch AG and hosting partner Rödl IT Operation GmbH test

Oracle Database In-Memory for SAP NetWeaver BW

H U G E P E R F O R M A N C E B O O S T C O N F I R M E D ,

M I N I M A L I M P L E M E N T A T I O N E F F O R T C O M E S A S S U R P R I S E

With an annual revenue of approximately

€ 800 million and over 7,300 employees, Villeroy & Boch AG is one of the world‘s leading manufacturers in the ceramics industry.

The family business, which was founded in 1748 and is headquartered in Mettlach/Germany, stands for innovation, tradition and exceptional style. As a renowned lifestyle brand, Villeroy & Boch offers products from the sectors

Bathroom, Wellness and Tableware, and is active in 125 countries.

Both business areas use an SAP ERP and an SAP BW system as well as other SAP solutions. Villeroy & Boch has been using Oracle‘s proven, reliable database to great advantage for around 20 years. Over the years the use and importance of BW/BI has steadily increased. The company has approximately 2,500 SAP users worldwide, including around 1,700 in the SAP BW environment.

Certified SAP hosting partner Rödl IT Operation GmbH

(with offices in Mettlach, Selb, and Frankfurt) operates and manages a range of systems including all SAP systems on behalf of Villeroy & Boch AG.

As Villeroy & Boch CIO and IT Director Thomas Ochs explains, „It was at an event organized by German-speaking

SAP user group DSAG in early 2015 that we learned about the new Oracle Database 12c for SAP and the Oracle Database In-Memory technology, mainly from the standpoint of potential performance improvements for our SAP

NetWeaver BW systems. Some time later our hosting partner Rödl IT Operation GmbH suggested performing a joint test of the Oracle 12c technology as part of a transparent proof of concept (PoC), and we agreed. The questions that interested us most were: What potential performance improvements could we achieve by using Oracle Database

In-Memory for SAP BW? And how much implementation work would be involved?”

Tests on an SAP BW sandbox

For the tests with Oracle Database In-Memory, fact tables

(E and F tables) from the largest COPA cube at Villeroy

& Boch AG were used, with around 94 million rows.

“Obviously, we wanted to perform the tests with real production data to produce results and an actual comparison of the outcome with and without In-Memory. With these kinds of tests it was mainly about read times for data and queries both with and without database aggregation. We also wanted to evaluate how this Oracle 12c technology works with identical hardware configurations and the addition of more memory,” says Harald Wolf, Senior

Consultant BI at Villeroy & Boch within the corporate IT team, who carried out the PoC in close collaboration with

Klaus Lehnen, head of the competence center for SAP-based technology at Rödl IT Operation GmbH.

Oracle Database In-Memory at Villeroy & Boch

47

Summary of test results: Oracle 12c In-Memory option at Villeroy & Boch

Customer  Results  :  Oracle  Database  In-­‐Memory    

 

Example  SAP  BW  COPA  PoC

 

20  

10  

0  

50  

40  

30  

80  

70  

60  

Query1  

Prod.  (no  In-­‐Memory)  

Query2  

PoC  (In-­‐Memory)  

Queries  

•  

SAP  COPA  Query  1  

–

 

RunCme  reducCon  factor:  33x  

•  

SAP  COPA  Query  2  

–   RunCme  reducCon  factor:  30x  

Copyright  ©  2014  Oracle  and/or  its  affiliates.  All  rights  reserved.    |   Public                          [email protected]    

Customer  Results  :  Oracle  Database  In-­‐Memory    

 

Example  SAP  BW  COPA  PoC

 

Timeout  

60  

50  

40  

30  

20  

10  

0  

100  

90  

80  

70  

Test1   Test2  

Prod.  (no  In-­‐Memory)  

Test3  

PoC  (In-­‐Memory)  

SAP  TransacNon  LISTCUBE  

•  

Test  1:  

–  

–

 

1  Mio  records  w/o  aggregaNon  

RunNme  reducNon  factor:  

150x  …  4.800x  

•

 

Test  2:  

–  

–

 

1  Mio  records  with  aggregaNon  

RunNme  reducNon  factor:  

4x  

•

 

Test  3:  

–  

–

 

94  Mio  records  with  aggregaNon  

Impossible  without  In-­‐Memory  

Copyright  ©  2014  Oracle  and/or  its  affiliates.  All  rights  reserved.    |   Public                          [email protected]    

For the PoC the partners constructed an SAP BW sandbox which was an exact copy of the productive SAP BW system, with a total of 64GB of In-Memory storage being earmarked for the database. The Oracle database for the

SAP BW system was then upgraded from 11g to 12c.

Lehnen explains, “The aim was to test Oracle Database

In-Memory on comparable standard hardware. For both the

BW sandbox with 128GB of RAM and the BW PROD system with 96GB of RAM we used an X86 RedHat

Linux-based system environment virtualized with VMware on two CPUs with a total of 16 cores.”

He goes on to explain how the Oracle 12c upgrade and the activation of Oracle Database In-Memory was completed in around five hours. The entire PoC was carried out in 1.5 days with very reasonable resource utilization.

After an initial brief test, only two database parameters were adjusted as a recommended tuning measure.

The LISTCUBE transaction was used for all the tests performed by the partners. The database response times were calculated with SQL traces using SAP transaction ST05

(performance analysis). All data was compressed beforehand utilizing Oracle Advanced Compression.

Exceeding expectations

In total, Villeroy & Boch and Rödl IT Operation GmbH carried out four different test scenarios on the SAP BW sandbox with Oracle Database In-Memory. Each was followed by an evaluation of the results from the SAP application.

In the first test, 1 million records were selected without database aggregation and processed with In-Memory, several times over. The database processing time was measured with preparation and transfer times being measured separately. For the PROD system, the data showed that the entire process took 24 seconds. The equivalent process in the SAP BW sandbox with Oracle

Database In-Memory yielded a significant reduction in processing time as it was reduced to 160 milliseconds and as little as 5 milliseconds in some cases.

The second test was similar to the first, but the 1 million records selected were aggregated in this case. Comparative measurements showed that the database time was reduced by 75% as the runtime went from 44 seconds to 11 seconds.

33 seconds fewer to process each request.

In a third test, the entire data volume of the loaded tables

(94 million records) was read from the memory and aggregated in just 22 seconds. A comparable test in the SAP

BW PROD system could not be completed due to a timeout.

48

Oracle Database In-Memory at Villeroy & Boch

Finally, Villeroy & Boch concentrated on the processing of existing COPA queries and preparing the results with web templates. Two heavily processed SQL candidates were chosen. The results for query test 1 showed the database time with Oracle Database In-Memory taking 1.5 seconds while that same statement takes 50 seconds in the SAP

BW PROD system. Query test 2 had similar results.

What took 72 seconds in the SAP BW PROD system only takes 2.5 seconds with Oracle In-Memory.

In the words of Harald Wolf, “With our tests based on

Oracle 12c and Oracle Database In-Memory, the PoC produced amazing results in terms of improved performance.

From a BI point of view I was also especially pleased with the fact that once SAP applications have been created, they can be used with Oracle Database In-Memory without any modifications. It‘s also easy to choose which SAP BW tables are processed with In-Memory and which are not.”

Low resource requirement, many benefits

Thomas Ochs sums up the result, “Obviously, we expected the Oracle Database In-Memory technology to deliver a certain performance boost. The final result was a marked improvement, which revealed how much potential the technology has to offer. The IT team at Villeroy & Boch was pleasantly surprised at how little implementation work was involved and how quickly the tests could be performed.”

Klaus Lehnen from Rödl IT Operation GmbH notes,

“The benefits that can be achieved with the use of Oracle

Database In-Memory for existing SAP customers with the Oracle database are very substantial, with moderate costs and only a modest amount of implementation work.

This is also due to the fact that existing hardware infrastructures can be used and no modifications are required on the application side.”

He sums up by saying, “Migration projects to Oracle 12c

– if you can call them that – with the use of Oracle Database In-Memory are very low-risk, as well as being easy to manage and easy to calculate. Furthermore, the whole process is based on Oracle, a long-established stability factor for databases in the SAP environment.” Rödl IT

Operation GmbH also provides hosting services to numerous SAP customers, most of whom rely on the tried-andtested combination of SAP and Oracle Database.

After the successful testing Villeroy & Boch AG is now adopting Oracle Database In-Memory for their SAP installations BW and CRM.

SAP BI Oracle Database In-Memory at DB Masters Austria

49

S A P B I W I T H O R A C L E D A T A B A S E I N - M E M O R Y A T D B M A S T E R S

In-Memory database technology has been around since the

1990’s. Numerous database vendors have come and gone and filled that niche for years. In 2011 SAP came up with the HANA In-Memory concept. The initial idea was to efficiently handle analytical queries through columnar stored data structures. Planned as a BWA replacement the technology matched well.

Later SAP expanded the concept to include OLTP. Technically, they chose to mix self-developed and acquired technologies such as P*Time, TREX Search Engine, MaxDB

(livecache), and Sybase ASE for this purpose. Customers wanting to exploit the In-Memory technology from HANA require special hardware to run the system and a migration/conversion from the technology they knew today to the HANA flavor of the day.

Nearly at the same time, Oracle fully integrated the In-

Memory technology into the Oracle 12c database.

The Oracle database In-Memory promises good performance of high analytical processing capabilities, near transparent implementation, and requires no special hardware or data migration. When done properly, customers will continue to use the performance, scalability, availability, and reliability available today with the added high performance analytical capability.

This paper explores the pre-certification testing and findings of one customer’s experience with the Oracle database

In-Memory. The Oracle Database In-Memory is certified for use with SAP of June 2015.

We at DB Masters in Austria are focused on solving customer business challenges by proper implementation of the Oracle Database and related technologies. We have experience with many large ERP systems and understand their special needs. However, our focus is Oracle centric

- independent of the applications running on it. We are in business since 2000 servicing customers across Europe.

Our customer list is long.

When Oracle 12.1.0.2 In-Memory has been initially released by Oracle one of our customers expressed interest in this technology. The company approved to a proof of concept to evaluate the performance impact for their SAP

BW application.

We took the “top” (longest running) SQL statement from their production SAP BI and captured measures from the following scenarios:

• The “current” query runtimes from the production environment as baseline – which is not entirely accurate as there are a lot of other activities in the database.

• 11gR2 with both the original buffer cache size and

256GB cache. – Statements were executed several times to warm up the cache so we were able to eliminate the I/O time from the execution. This allowed us to measure performance differences between Oracle

11gR2 and Oracle 12c results.

• 12cR1 with both the original buffer cache size and

256GB cache. – Statements were also executed several times to warm up the cache so we were able to eliminate the I/O time from the execution. This allowed us to measure to performance differences between Oracle

11gR2 and Oracle 12c results. The runtime difference between Oracle 11g and 12c were negligible. We can assume there are no performance differences for the test statements.

• Enable Oracle Database In-Memory and put all related objects into the In-Memory Column store. Several configuration settings were tried – like different In-Memory compression options – but at the end all results where done with FOR QUERY LOW compression.

50

SAP BI Oracle Database In-Memory at DB Masters Austria

Here are the results over all queries – keep in mind that this is an older SAP BI Version, not “optimized” for

Oracle Database In-Memory technology:

Type of test Result

Runtime on production system Always between 2500 and 2750 seconds

depending on the current system load

11g / 12c Test system original buffer cache About 1455 seconds

11g / 12c Test system 256GB buffer cache About 382 seconds

Using Oracle Database In-Memory with About 118 Seconds

QUERY LOW Compression

The numbers are not as impressive as when Larry announced the Oracle Database In-Memory, but depending on the baseline running up to 25 times faster does not look so bad.

There still remains the question often coming:

“Why do you not put the whole database into buffer cache?”

This would speed up the system by a factor of 7-8.

The answer is easy: most customers will not be willing to pay for servers having the required amount of memory.

If your SAP BI database is 5, 10 or more TB in size, you would still need up to 50% of the database size for buffer cache. Today, there are servers having up to 32TB and even more memory, but they are very expensive. Current

Intel based servers with 2 sockets are able to address up to

3TB memory – typically affordable servers are populated with up to 1.5TB memory.

The advantage of Oracle 12c Database In-Memory is that only table data must fit into the SGA. This typically ranges between 1/3 to 1/2 of the database size, depending on the type of system. The fact that In-Memory table data is stored and accessed in a compressed form means that the footprint will be reduced further. Our tests indicate that most SAP BI tables could be compressed to a factor between 2 to 4x’s of the original table size. In other words, the size of the In-Memory table will be 1/2 to 1/4 of the original table size.

A current Intel based server with 2 sockets and 1.5TB memory should be able to put a 10TB SAP BI database completely into the memory! Additionally, you can get rid of indexes only used to speed up lookups – especially bitmap indexes needed for query performance. Fewer indexes to maintain will speed up data loading processes in a dramatic way while reducing disk space and backup sizes.

Another advantage of Oracle Database In-Memory is the short amount of time it takes to implement it. Believe it or not, this customer POC was done within 5 hours – including creating a clone of the database on the test system and running all of our tests! You may compare this to any SAP Feature implementation project you like to.

Deactivating the Oracle Database In-Memory is also quite easy. One simple command line directive dynamically enables and disables the feature. This offers a quick and efficient fallback if any show stopping issues should arise.

Last but not least – how is this effecting HA/DR? With

Oracle database In-Memory, you may continue to still utilize all High Availability functionalities like Oracle

RAC, Oracle Data Guard, and failover solutions from

Oracle or other vendors. No changes. Recoverability remains also untouched. The feature is fully integrated with all of the Oracle HA and DR capabilities.

In summary, experience with this new Oracle feature was very positive. It lived up to our expectations with respect to the ease of implementation and the performance benefits. It is now a certified option and nearly transparent to implement. Customers now have a viable option to explore this technology at a reasonable cost with no business disruption.

About the Author:

Christian Pfundtner, CEO of DB Masters, is working with Oracle Databases since 1992 (Oracle 6). One of the first 4 OCMs in Europe. Our focus is on the Oracle

Database – but unlike many our competitors we take care of all related layers – from the disk (storage) up to the user. We offer all kinds of evaluations. Business and current database requirements, current licensing state, recommendations on best practices for implementing

Oracle to address your needs and to maximize your ROI, performance tuning and troubleshooting.

DB Masters GmbH

Stammersdorfer Str. 463

2201 Gerasdorf, Austria

www.dbmasters.at

Oracle Advanced Compression at Goodman Fielder

51

“The driver for implementing Oracle Advanced Compression was the growth in our SAP ECC6 database size.

By using Oracle Advanced Compression, we freed up a total of 20 TB over multiple SAP ECC6 instances. We targeted the top 20 tables by growth, and compression was done without outages. The process was completely transparent to our users. I was very satisfied with the ease of use, and the end result.”

– I A N L O F L E Y,

Technical Services Manager

O R A C L E A D V A N C E D C O M P R E S S I O N R E D U C E S B U S I N E S S -

C R I T I C A L S A P D A T A S T O R A G E R E Q U I R E M E N T S B Y 4 0 %

A T G O O D M A N F I E L D E R

Executive Summary

The massive growth in data volumes being experienced by enterprises introduces significant challenges. Companies must quickly adapt to the changing business landscape without impacting the bottom line. IT managers need to efficiently manage their existing infrastructure to control costs, yet continue to deliver extraordinary application performance.

The Oracle Advanced Compression option and Oracle

Database together provide a robust set of compression, performance and data storage optimization capabilities that enable IT managers to succeed in this complex environment.

Whether it is a cloud or an on-premises Oracle database deployment, Oracle Advanced Compression can deliver robust compression across different environments with no changes in applications. Benefits from Oracle Advanced

Compression include smaller database storage footprint, savings in backups and improved system performance.

This Case Study discusses how Goodman Fielder benefited by using Oracle Advanced Compression in their businesscritical SAP application environment, not only improving performance, but also reducing their existing storage requirements by more than 40%, thus allowing Goodman

Fielder to put off new storage acquisition costs.

Read more to learn how they accomplished this.

About Goodman Fielder

The company has an excellent portfolio of well known consumer brands in some of Australia‘s largest grocery categories, including Meadow Lea, Praise, White Wings,

Pampas, Mighty Soft, Helga‘s, Wonder White, Vogel‘s

(under license), Meadow Fresh and Irvines.

Goodman Fielder products cover every meal occasion, including breakfast, lunch, dinner and snacks. Goodman

Fielder also produce and market bread, milk, margarine, flour, dressings, condiments, dips, mayonnaise, frozen pastry, cake mix, pies, savories, desserts, sauces, vinegar and cooking oils.

Goodman Fielder is headquartered in Sydney and employs approximately 5,000 people in Australasia and the Pacific

Islands. The company manufactures their products in almost 50 plants in Australia, New Zealand, Papua New

Guinea, Fiji and New Caledonia.

Data Growth Challenges

Goodman Fielder’s SAP ECC application is a businesscritical application across the company’s sites throughout

Australia and New Zealand. This OLTP application is at the heart of Goodman Fielder’s daily business transactions and processing. Any system issues or performance degradation, of the SAP ECC application, would have serious consequences for the business in the manufacturing and delivery of their products to consumers.

52

Oracle Advanced Compression at Goodman Fielder

Goodman Fielder’s SAP ECC database has been growing at the rate of 350-400 GB / month. Within the last two years, the overall size of the database doubled and reached close to 10 TB. With this rate of data growth, the company needed to lower data storage costs without impacting database performance.

Started with a Proof of Concept

Goodman Fielder performed a POC (Proof-of-Concept) with Oracle Advanced Compression on SAP in their test environment. By compressing the larger tables, Goodman

Fielder freed up almost 50% of space in the test environment. The POC also helped the Goodman Fielder DBA team to have a good idea on the timings needed to compress each table.

After thorough testing with business users, that also included performance verifications, Goodman Fielder decided to implement Advanced Compression in their production environment. Goodman Fielder enabled compression one table at a time and completed the implementation over a period of three weeks without any downtime.

Compelling Performance

A key area that, along with compression savings, was of interest to Goodman Fielder during their evaluation of Advanced Compression was the system performance after compression of the data. During their testing and after implementation in their production environments, there was no performance degradation related to compression and in fact, Goodman Fielder saw performance improvements in various SAP transactions as shown in the table above.

“Oracle Advanced Compression exceeded our expectations.

It enabled us at Goodman

Fielder to reduce our database growth, reduce our data storage footprint by 40% and did so without performance impact.

A win all around for us!”

– TAPAN VADODARIA, Oracle DBA

Compelling Storage Savings

Advanced Compression reduced the size of Goodman

Fielder’s production database from 10 TB to 6 TB.

This compression immediately allowed the DBA team to have over 4 TB of free allocated space at the database level – space that can be reused for future transactions and storage. As Goodman Fielder copies their production environment to other auxiliary environments, the total disk space savings were boosted to a total of 20TB.

Goodman Fielder’s DBA team planned and targeted the compression of a total of 20 SAP tables consuming more than 50 GB of data. During the planning stage, Goodman Fielder’s DBA team used the Oracle Compression

Advisor which predicted an average compression ratio of 4.79x for the database tables involved, with the final results of the compression matching or exceeding the findings.

The DBA team also converted the database LOB objects to the modern and optimal SecureFiles architecture and then compressed it with SecureFiles LOB Compression

(LOW ratio), as recommended by the SAP BRSPACE tool. The result established significant space savings for the LOB objects with no performance impact.

Oracle Advanced Compression at Goodman Fielder

53

Goodman Fielder’s DBA team used the SAP BRSPACE tool for enabling compression, and one of the biggest and heavily used SAP tables, GLPCA, reduced in size from

700 GB to 144 GB.

The other benefit the DBA team discovered, after implementing OLTP Table Compression, was that the overall growth rate of the database dropped from 350 GB per month to less than 200 GB per month. Goodman Fielder had to invest heavily in regular purchases of additional disk space earlier and by freeing up existing storage, additional storage purchases were deferred, thus producing speedy savings.

Goodman Fielder’s DBA team enabled Advanced Compression in their production environment compression during business hours with no performance impact – all the tables were compressed without any downtime.

Conclusion

By using Oracle Advanced Compression, Enterprises can minimize their CapEx and OpEx costs without sacrificing application performance and downtime. Advanced

Compression can deliver savings on managing structured and unstructured data and can reduce database storage footprints by 2x to 4x across different environments with no changes required in the applications.

Environment

• IBM P7 w/ AIX 7.1

• SAP ECC 6.0

• Oracle Database Enterprise Edition

• Advanced Compression option

Key Takeaways

• SAP ECC OLTP database was growing at a rate

of 350-400 GB / month

• Cost of storage was increasing as a result of the

growth rate

• Compression was transparent to business users,

and was enabled without an outage

• POC in test environment surprised Goodman Fielder

regarding how much space saving was possible

• Implemented compression across Production,

Staging (UAT) and Test environments

Advanced Compression Features Used

• OLTP Table Compression

• SecureFiles LOB Compression

For more information, please reach out to your Oracle

Account Manager.

Best Practice:

Oracle’s free Compression Advisor to use a very useful tool for estimating compression ratios, information about advisor is available on OTN at: http://www.oracle.com/technetwork/ database/options/compression/downloads/index.html

Oracle Customer:

Goodman Fielder

Location:

Sydney, Australia

Industry:

Food Company

Employees:

5,000

54

ElectraNet – Oracle Press Release

ElectraNet Creates Financial Reports 16x Faster, Slashes Annual Maintenance Costs by US$330,000

E L E C T R A N E T G A I N S B E T T E R B U S I N E S S I N S I G H T W I T H

O R A C L E E N G I N E E R E D S Y S T E M S

ElectraNet, the primary transmission network service provider (TNSP) and system control center operator for

South Australia, has been able to gain more actionable insights into the electricity market and improve decision making as a result of its selection of Oracle Engineered

Systems.

By using Oracle Exadata Database Machine

to support its

SAP and other reporting applications, the organisation can now create financial reports in just 15 seconds, as opposed to taking up to four minutes. The new system also delivers significantly faster reports around daily electricity pricing and customer consumption, and gives instant availability to electricity market data, an activity which was previously taking minutes.

“The utility industry has always been data-driven. Our challenge wasn’t having enough data, it was how to pull quality information out it in a timely manner. Oracle

Exadata has been essential in helping us achieve this. The integration between the hardware and the software on the one platform really brings out performance benefits. As far as I‘m aware, no other system integrates the software so well with the hardware,” said Mark Jones, Database

Administrator, ElectraNet Pty. Ltd.

In addition to providing a high-performing and costeffective database platform to elevate business performance, the new infrastructure has also reduced the total cost of ownership (TCO). It has halved the annual IT maintenance costs - from US$660,000 to US$330,000 - and reduced licensing costs - as a result of consolidating 37 servers and 10 virtual machines onto two Oracle Exadata units; one for production and one for disaster recovery.

ElectraNet has also saved 15 hours per month on system maintenance tasks, such as database and server patching, by leveraging Oracle Platinum Services to help ensure faster problem resolution.

“Bringing the best possible service to our customers at the lowest possible cost is key for us. However, the challenge of managing the distribution and transmission infrastructure across vast rural areas can make that goal hard to achieve.

Being able to gain near real-time access to our business information has enabled us to identify opportunities to streamline our operations and make better decisions for both our immediate and future needs,” Jones continued.

Business resiliency has also improved. ElectraNet has gained the ability to complete data backups 3x faster - in just two hours instead of up to six - and by using a pre-configured, pre-tuned, pre-tested, engineered system, it has been able to help ensure high system availability.

“Utility companies today are focused on running agile operations and providing the best value for customers.

By choosing Oracle Exadata, ElectraNet has been able to get more value from its enterprise data, achieve faster decision-making, increase the efficiency and effectiveness of nearly all aspects of its business, and improve its competitiveness,” said Carlos Cienfuegos, head of Exadata and

Strategic Solutions, Oracle Australia and New Zealand.

The company engaged Gold level member of Oracle PartnerNetwork (OPN), Blue Crystal Solutions for initial set up and worked with Oracle Advanced Customer Support for

SAP database migration. In fact, by using Oracle Advanced

Customer Support Services’ best practices and expertise to help ensure rapid and smooth migration, data migration for SAP applications and other reporting applications to

Oracle Exadata was completed in less than one day.

“Using Oracle Advanced Customer Support Services for migration reduced our risk. As they are SAP certified, they have already seen most of the issues that we could have faced, so they know the work arounds and fixes for them. As a result, we had a lot less down time – estimated at nearly 75 percent less – than anticipated,” Jones concluded.

Contact Information:

Antoinette Georgopoulos

Oracle +61 2 9491 1698 [email protected]

Oracle Exadata Database Machine at Solvi Group Brazil

55

S O L V I G R O U P I N B R A Z I L C U T S E N V I R O N M E N T M A N A G E M E N T

C O S T S W I T H O R A C L E E X A D A T A

The Solvi Group consists of over 60 companies operating in the field of Environmental Engineering, with recognized competence operates in the following business areas: urban waste, industrial waste, Sanitation, Construction and Energy Recovery.

The Environmental Projects Company’s objective is to invest in other companies as a partner or shareholder, in

Brazil or abroad.

Learn how Oracle Exadata helps Solvi reduce Solvi’s added environment management costs and improve availability, performance, and storage. End users also benefit as SAP and other systems running on Exadata became more available and responsive. In the following you read the video interview of Henrique Fassi Lobao, IT Information

Manager at Solvi Solutions, Sao Paulo, Brazil.

Here at Solvi, we had a problem related to our database management. Our infrastructure wasn’t centralized. For each system, we used a different server, so our management efforts were substantial. Besides having many separate servers we had little availability. Each server supported a system and if one server was down, that system was also down. We also had issues in performance. After implementing Exadata, we solved several key challenges facing our organization. First being environment management.

We centralized all our databases on one Engineered system thus drastically reducing hours dedicated to its management.

We have a small staff for this purpose, so we’ve reduced overtime. Now our DBAs have free weekends. Time they didn’t have before. Now we work regular hours, within the 8-hour period, 5 days a week and have free weekends.

We also saw benefits from environment availability. This had been a serious issue for us.

If a server was down, that system was down too. Now with Exadata’s redundancy for customers, we can even conduct maintenance tasks, such as patching or updating, without compromising availability. I can do without a database host, without a storage machine, during maintenance and have the application system work perfectly.

The third improvement we saw was in performance.

We had issues with backups. Our window of time was relatively short, so backups would still be in progress at

8 am the next day. With Exadata, we can easily finish our backups well before business hours, and we’re also saving on backup storage, because now we work with compressed backups. Before we couldn’t, due to the high processing power required. Now we’re able to do this in a highly efficient way, with plenty of time for other tasks.

Exadata is not directly used by end-users. But end-users directly benefit from Exadata. SAP and other systems running on Exadata become highly available and responsive to their needs. It improves system usability, time response, and availability as a whole, stability that users can always rely on. Using Exadata at Solvi has helped us to reduce costs. We managed to reduce added costs related to environment management and system unavailability.

These are indirect costs, but they also have an influence on the end when users who must send electronic invoices, for example. They and the business are greatly affected when the system is down.

Our availability relied on a single server. If it was down, the system wasn’t available. This is just an example. Now thanks to our Oracle Exadata and Oracle Database, we no longer suffer from that.

After implementing Exadata, any unavailability is caused by the application system itself, and not by the database.

Our database is 100% responsive and alive. We also plan to look into other Oracle solutions, from which we could really benefit.

Exalogic, for applications and eventually specific products for other systems. We like SuperCluster for our SAP BW environment. We intend to look into offerings based on previous products and experience, we believe they’ll increase our productivity and success.

Source: http://medianetwork.oracle.com/video/player/

4120342309001

56

A L A R G E S A P C R O S S P L A T F O R M O N L I N E S Y S T E M M I G R A T I O N

W I T H O R A C L E G O L D E N G A T E

Introduction

Wumart Stores, Inc. is a large scale retail group focusing on departmental stores, supermarkets and convenience stores. They have over 700 stores spread mainly across

Beijing, Hangzhou, Tianjin, Zhejiang, Hebei, and

Shanghai, with total annual turnover exceeding RMB 40 billion.

• Wumart was experiencing rapid growth in their

business both in terms of revenue and number of retail

outlets, and the existing infrastructure was struggling

to cope with the business demands

Implementation Partner

Beijing Giantower Technology Co Ltd

is an Oracle Gold partner. They have a highly competent and experienced technical team with special expertise in Oracle Engineered Systems and

Oracle Database. They provide systems integration service and deployment of ERP applications on Oracle Engineered

Systems. They helped to deploy the first

Exadata Database Machine in China, and also did the first deployment of SAP on Exadata in China. Their range of services includes:

• Deployment and maintenance of

Oracle Engineered Systems

• SAP on Oracle Engineered Systems end-to-end solutions and services

• SAP Migration, Upgrade,

Optimization, and maintenance

• Oracle Database design, deployment, and maintenance

• The existing IT landscape was a traditional silos of

monolithic systems and they wanted to refresh it into

a modern private cloud-based infrastructure

• Wumart wanted to move to X86 architecture to reduce

hardware and operational costs, as well as to improve

the overall SAP system performance

Existing Systems Issues

• For the core SAP systems, the CPU and Memory utilization were consistently over 90%, and at 100% during peak periods, resulting in slow response time and bad customer experience

• The silos of systems could not be dynamically re-balanced for different workload patterns thus causing resources unable to be re-deployed easily to systems requiring them

• Costs of acquiring and maintaining existing infrastructure kept increasing quickly

• With fast business growth and shorter product lifecycle of the infrastructure, it was difficult to achieve investment protection on the infrastructure

• Existing infrastructure was large and complex, difficult to maintain, resulting in increasing IT operational costs

Challenges

• Migrate 8TB of SAP ECC database from UNIX to

Exadata with a downtime of less than 20 minutes

• There were almost 100 RFC interfaces surrounding the ECC system

• Lack of adequate hardware resources on the surrounding systems for testing

• Change of IP addresses, hostnames, and DNS during migration

• Short project schedule, extremely short testing period permitted

• Migrate 3 large productive systems within 3 months

• Large number of custom developed ABAP programs in each system

Oracle Online System Migration at Wumart Stores

57

Migration Go-live Plan (Synchronized in Paralell, Steped Go-live)

Major Migration Process

After detailed analysis of the existing systems environment and many discussions with both SAP and Oracle on the project specifics, we decided on the “Parallel Synchronized

Testing with Stepped Go-Live.” This took into account the customer’s specific request to ensure no impact to productive operations, guaranteed data integrity, and zero risk to business operations. Giantower developed a technical solution based on the special capability of Oracle Golden

Gate software. First they used RMAN to replicate a complete SAP database on an intermediate environment and then they used Oracle Transportable Tablespace (TTS) to complete the initial database migration including endian conversion on to the target Exadata machine. After that, they employed Oracle Golden Gate to synchronize the target database on the Exadata with the source system running on IBM P750. With this, they have created a comprehensive data integrity and data completeness testing mechanism and were able to do an online database migration cutover.

End Results and Benefits achieved

• After the migration, the four core productive databases were consolidated on to Oracle Exadata, the application instances were also virtualized in a pool of X86, thus completing a total conversion from the traditional IBM

POWER platform to a high reliability and high performance private cloud computing architecture.

58

Oracle Online-Line System Migration at Wumart Stores

Comparison of Performance Improvement before and after migration

• The comparison of the AWR report before and after the migration revealed that there were performance improvements of between 8 times to 15 times. The

Exadata machine that consolidated the 4 productive

Comparison of AWR before and after Migration

databases had an average CPU utilization of only 15%.

The performance of the ECC system had an average performance improvement of more than 6 times.

The project delivered a consolidation of systems, provided a highly resource optimized private cloud computing environment, resulted in a high performing and advanced architecture to enable the company to better handle the expected growth in business volume.

If you need more information, please contact below:

Website

: www.giantower.com

Contact Person

Frank Zhu

Email:

[email protected]

Phone: (86)18611920045

Oracle SuperCluster at CELSA GROUP

59

“Oracle SuperCluster gives us peace of mind by eliminating downtime in our business-critical logistics

planning and dispatching processes, and it enables our customers to optimize their supply chain, knowing

our products are delivered on time and reliably.”

– J E S U S M A Y O R D O M O , 　

CIO, CELSA GROUP

C E L S A G R O U P I M P R O V E S S A P E N T E R P R I S E A P P L I C A T I O N

P E R F O R M A N C E 3 X , S A V E S U S $ 6 5 6 , 0 0 0 I N L A B O R C O S T S ,

A N D D E P L O Y S I T S T R U C T U R E T O S U P P O R T C O N T I N U E D

G R O W T H

Serving industrial customers on five continents and with more than 50 companies operating under its umbrella,

CELSA GROUP is the largest steel producer in Spain and one of the largest in Europe. CELSA GROUP is highly diversified in the products the company manufactures – including forged, laminated, and processed steel.

Challenges

• Eliminate downtime in the company’s enterprise resource planning (ERP) systems, which lead to delayed deliveries of steel products and expose the company to late penalties and lost business

• Improve IT performance to boost resource planning and

financial reporting efficiency across CELSA GROUP’s

more than 50 entities

• Optimize backup processes to save time and money while meeting the company’s rigid requirements – that no data be lost in an emergency

Solutions

• Ensured reliable, on-time delivery of millions of tons of steel per year by eliminating downtime in the company’s SAP ERP systems with Oracle SuperCluster and

Oracle Exadata Database Machine, optimizing supply chains for CELSA GROUP and customers

• Saved more than US$656,000 annually in labor costs by optimizing financial reporting, consolidating data from more than 2,000 users dispersed across the group’s more than 50 entities

• Improved ERP systems speed 3x, enabling the company to optimize logistics processes and gaining the ability to support planned growth for the next four years without adding any additional IT resources

• Tripled backup speeds and queries to geographically separate data centers with Oracle Data Guard, optimizing IT resources and the time dedicated to managing backups

• Scaled up CELSA GROUP’s data storage capacity, meeting the company’s increasingly demanding requirements to analyze data to find trends and improve efficiency across steel manufacturing operations

• Contracted Oracle partner, BT, to deploy Oracle

SuperCluster, ensuring custom pre-implementation planning, same-day migration, and post-implementation support

60

Oracle SuperCluster at CELSA GROUP

Implementation Process

CELSA GROUP migrated seamlessly to Oracle SuperCluster in less than a day thanks to in-depth pre-implementation analyses and preparation by Oracle and Oracle partner

BT. In addition to migrating CELSA GROUP to Oracle

SuperCluster, BT hosts CELSA GROUP’s SAP system, providing CELSA GROUP with data centers and Oracle

SuperCluster infrastructure, while managing and operating the platform 24/7.

https://www.bt.es

Partner

BT analyzed CELSA GROUP’s IT requirements and business needs and provided analysis and tests to demonstrate that Oracle SuperCluster would best meet them. BT prepared the implementation, completed the migration in less than a day with minimal involvement from CELSA

GROUP, and remains involved post-implementation in training and support should any issues arise.

Why Oracle

“We considered a number of alternatives to improve the

IT infrastructure of our SAP ERP systems, but our tests demonstrated Oracle SuperCluster would best meet our requirements for robustness, effectiveness, price, and quality,” said Jesús Mayordomo, CIO, CELSA GROUP.

http://www.celsagroup.com

Oracle Customer:

CELSA GROUP

Location: Barcelona, Spain

Industry: Industrial Manufacturing

Employees:

7,000

Annual Revenue: $1 to$5 Billion

Oracle Products & Services:

• Oracle SuperCluster

• Oracle Exadata Database Machine

• Oracle Active Data Guard

Oracle Exadata at Lenta – Oracle Press Release

61

Lenta implements an IT infrastructure optimization project using Oracle Exadata

Saint Petersburg, Moscow. April 24, 2015

Lenta, (LSE, MOEX: LNTA), one of the biggest retail chains in Russia, optimized its IT infrastructure using the

Oracle Exadata Database Machine.

It’s use yielded a fourfold increase in data processing speed in the retailer‘s

ERP system.

Oracle Platinum Partner State Corporation KORUS

Consulting was the lead partner in the project supported by the software and hardware experts from FORS Distribution, an Oracle distributor in Russia.

Lenta‘s IT landscape consists of more than 20 corporate information systems, 300 data links connecting stores and distribution centers with the head office, as well as several server rooms integrated in the data center. The IT team supports more than 6,000 workstations located in various regions of the country.

Lenta‘s intense growth – opening new stores and distribution centers combined with numerous business processes changes – resulted in more users, more data and an increased load on the existing information systems. This was the catalyst

and driver for the retailer‘s major IT initiative to review the current IT landscape and find new high-tech solutions to improve data processing speed and generate strategic reports.

„Retail‘s growth and development into a mature, highlycompetitive industry in Russia led to a new understanding of business needs and expectations of new capabilities from information technology. State-of-the-art solutions are becoming an integral part of business. We realize that having effective information systems that work in real time with a heavy load is a serious advantage. That‘s exactly why the next stage in the development of our company‘s

IT landscape was to obtain software and hardware solutions that let us efficiently resolve issues related to both the scaling-up and performance of our IT systems,“ said

Vsevolod Kuzmich, CIO of Lenta.

In 2013, when the project began all business systems were running on modern enterprise-level RISC machines combined into clusters for efficient use of resources through load balancing. While the strategy for developing the

IT infrastructure was being prepared it was discovered that this sort of architecture has several limitations and is inferior to the new technology solutions that have emerged in the market.

Lenta‘s IT team studied reports from the leading global analytical agencies and selected a few possible solutions that had been tested on real data. In addition to the baseline selection criteria – guaranteed fault tolerance, the ability to work with large volumes of data, the availability of qualified system integration partners in Russia, partners with experience in deploying a significant number of similar systems – the system‘s scalability and performance were important parameters in the selection process.

In the final stage, two systems from different vendors were chosen. Testing them required creating identical production loads using real data on test benches. Performance was assessed based on the speed of building resource-intensive reports and the time required to perform the most complex transactions under different load conditions. There was also a comparison with the same metrics from the existing infrastructure. Depending on the technology, the cumulative effect observed in the pilot project was a four-fold increase in performance and a reduction in data storage, thanks to compression and

Oracle technical features.

62

After several rounds of testing it was determined that the optimal solution for Lenta‘s challenges is Oracle Exadata.

The choice was based on both technical criteria, such as fault tolerance, scalability, and performance, as well as the fact that the Oracle solution makes it possible to consolidate the business-critical systems using Oracle Database.

At present, the enterprise resource planning system

(SAP ERP) and several other business applications have been migrated to Oracle Exadata. Using Oracle Exadata productively for SAP applications demonstrated that the company‘s hopes for improved performance were fully realized. Oracle ensures that applications work 24x7 without interruption.

Quotes

“An important factor in the final choice of a solution was the stability of the ERP system running on it. For any retailer, ERP is the central nervous system with a huge amount of data being sent and processed. Our ERP system currently stores about 20 TB of data that three to four thousand employees work with everyday, so the system must be able to operate 24/7, 365 days a year,” said

Vsevolod Kuzmich. “Using it over the course of the year we can see that our hopes have been fully justified by

Oracle Exadata‘s reliability and, of course, we‘re still impressed by the system‘s speed of deployment – migrating the SAP ERP production system to Exadata only took three days.“

“I also want to mention that we found a way to optimize our TCO (total cost of ownership),” said Nikolay Vyatkin,

Deputy IT Director for Infrastructure and Services at

Lenta. “First, Oracle Exadata on high-capacity disks was chosen as the solution. Second, during operation we saw that disk space and memory were utilized faster than processing power, so we did not scale up the system linearly during expansion for 2015. Instead, we simply added memory and disk space, which is several times less expensive than the standard approach to scaling up. Such flexibility is a serious advantage of Oracle systems over the other solutions that we looked at.”

“The multi-fold increase in performance and the consolidation of IT resources are our optimized systems‘ most important advantages, which are so needed by clients today.

We are happy that Oracle Exadata is helping Lenta, a leader of the Russian retail business, grow rapidly and lower their IT cost of ownership by providing a substantial increase in performance not only for Oracle applications but also for solutions from other vendors. Importantly, they are running on Oracle Database, the world‘s leading

DBMS,” said Andrey Pivovarov, Head of the Advanced

Technologies for Pre-Project Consulting at Oracle CIS.

“More and more top companies in Russia are choosing our integrated systems to accelerate innovations in their businesses, and we will continue to support our customers with the most advanced solutions.”

Partners

KORUS Consulting Group

is a Russian systems integrator offering IT consulting services regarding the creation, optimization, and automation of business processes.

KORUS Consulting is an Oracle Platinum Partner.

KORUS Consulting’s dedicated business of IT outsourcing and systems integration provides a full range of services in creating, auditing, and maintaining IT infrastructure, and choosing and delivering IT equipment. One of the company’s key industry specializations is end-to-end automation of retail enterprises. KORUS Consulting’s customers include Metro Cash & Carry, Azbuka Vkusa,

Korablik, ZAO Tander (Magnit chain), Lenta, Monex

Trading, O’KEY, SPAR Retail, TsUM, Trading House

TsentrObuv, Tyumenskiy TsUM, and others.

Media contact: Yuliya Smirnova, tel.: +7 (921) 768 85

63+7 (812) 677 56 90, +7 (495) 647 50 46

FORS Distribution

(www.partner.fors.ru), an Oracle distributor in Russia and Mongolia, was founded in

2011 under the auspices of the center for working with partners of FORS, an acknowledged expert on Oracle technologies in the Russian market. The main elements of FORS Distribution’s business today are: distribution of Oracle software and hardware, technical consulting and training on Oracle technologies for partners, and services to test and migrate complex solutions as part of the multi-purpose and innovative FORS Solution Center.

The company’s resources include a team of sales experts, affiliate network managers and marketing managers, a logistics department, and a technical consulting department.

Oracle Exadata at Lenta – Oracle Press Release

63

About Lenta

Lenta is one of the largest retail chains in Russia and the country’s second largest hypermarket chain (in terms of

2014 sales). The Company was founded in 1993 in St.

Petersburg. Lenta operates 123 hypermarkets in 63 cities across Russia and 27 supermarkets in Moscow, with a total of approximately 793,804 sq.m of selling space.

The average Lenta hypermarket store has selling space of approximately 6,200 sq.m. The Company operates six owned hypermarket distribution centres.

The Company’s price-led hypermarket formats are differentiated in terms of their promotion and pricing strategies as well as their local product assortment. The

Company employed approximately 30,655 people as of

30 June 2015.

The Company’s management team combines a mix of local knowledge and international expertise coupled with extensive operational experience in Russia. Lenta’s largest shareholders include TPG Capital and the European Bank for Reconstruction and Development, both of which are committed to maintaining high standards of corporate governance. Lenta is listed on the London Stock Exchange and on the Moscow Exchange and trades under the ticker: ‘LNTA’.

About Oracle

Oracle creates hardware and software optimized to work both in the cloud and in corporate data centers.

For more detailed information about Oracle (NYSE:

ORCL) please see www.oracle.com.

Trademarks

Oracle is a registered trademark of Oracle Corporation and/or its subsidiaries. Other names are trademarks of their respective owners.

For more information, contact Anna Komyagina,

Senior Marketing Manager at FORS Distribution:

Phone: +7 495 913-3-913,

E-mail: [email protected]

64

M I S S I O N - C R I T I C A L S U P P O R T S E R V I C E S F O R S A P C U S T O M E R S

For organizations using SAP for critical operations, seamless data availability, optimal performance, and reduced IT risk are essential for business success. Oracle

ACS services deliver mission-critical support services to help you maintain and maximize the performance of your

Oracle systems. With a unique service approach focused on building a long-term relationship with your IT team and collaborative support within Oracle’s support and engineering teams, Oracle ACS delivers a highly integrated, end-to-end service offering. A single contact for all Oracle and SAP issues and access to Oracle and

SAP experts allows problems to be resolved faster and more efficiently. Proactive, preventative support services use diagnostic tools to help you increase system availability, optimize performance, reduce risk, and accelerate return-on-investment (ROI) across the Oracle and SAP stack. Planning, migration, configuration, and installation services allow you to take advantage of advanced features and new technologies faster and more effectively.

Customized workshops train you with best practices on how to operate and maintain your SAP environment for the maximum performance and availability. All of this adds up to services that allow you to focus on delivering business value, not on day-to-day IT support.

Oracle has the deep SAP expertise you need to get the most out of your SAP environment. With over 28 years of collaboration with SAP, Oracle is the top database provider for SAP deployments and has the longest experience with SAP R/3 and SAP NetWeaver of any database provider. Dedicated engineering and support resources from both companies work together on end-to-end development, integration, and optimization and ensure fast customer issue resolution, so you can operate your SAP and Oracle environment with confidence. Highest Availability for your SAP landscape with Oracle HA and DR development, integration, and optimization ensure fast customer issue resolution.

Oracle ACS Lifecycle Support Services for Oracle

Databases

Whether you need to migrate your database to stay upto-date with the latest technologies, consolidate legacy systems onto modern hardware, or improve the performance of your SAP workloads, Oracle ACS Lifecycle

Support Services help you optimize your Oracle Database for SAP.

Oracle ACS Lifecycle Migration Service for SAP Migration

Through automation, advanced support tools, and more than 10 years of Oracle Database migration experience,

Oracle ACS Lifecycle Migration Service delivers migration planning, validation, and execution services that allow you to migrate your SAP database faster, with lower costs and less downtime. Oracle experts assess your SAP environment, guide you in choosing from multiple migration approaches, resolve potential migration issues, perform migration test runs to reduce risk, and migrate your database through a secure online gateway. Oracle’s efficient process, based on the latest industry best practices, allows you to migrate your SAP database in a matter of days, not the weeks or months typically required for SAP migrations.

Oracle Consolidation Planning Service

Consolidating legacy systems onto modern hardware can reduce costs, improve performance, and simplify operations. The Oracle Consolidation Planning Service helps you quickly identify the most optimal consolidation and migration scenarios for consolidation onto Oracle’s hardware platforms and engineered systems. Oracle experts assess the current configuration, workloads, patch levels, and security requirements of your SAP environment to develop a comprehensive consolidation plan, including detailed projections and actionable recommendations to lower transition and operational risks.

Oracle Performance Tuning and Benchmarking Service

Through ongoing monitoring and quarterly assessments, the Oracle Performance Tuning and Benchmarking Service helps you maintain consistent, optimal performance for critical SAP databases. Key performance metrics are monitored to proactively identify issues before they impact operations. Quarterly performance assessments include recommendations based on industry standards, Oracle best practices, and ongoing experience with customers that have similar SAP database configurations and usage scenarios.

Adding the Oracle Load Testing and Analysis Service further increases uptime, lowers costs, and reduces risk through comprehensive database testing. Oracle Database load testing experts evaluate the performance impact of planned technology changes, recommend configurations to optimize performance, and identify and address issues before go-live.

Support Services for SAP Customers

65

Oracle ACS Lifecycle Support Services enable faster database migrations, reduce migration and consolidation risk and costs, and help you optimize database performance and availability. For more information on Oracle ACS Lifecycle Support

Services for SAP environments, visit:

http://www.oracle.com/us/support/advanced-customer-services/database/overview/index.html and

http://www.oracle.com/us/support/advanced-customer-services/lifecycle-support-services/overview/index.html

Oracle ACS Services for Oracle Servers, Storage, and Engineering System

For SAP environments based on Oracle hardware, Oracle

ACS provides planning, deployment, optimization, and support services based on deep expertise for servers, storage, and engineered systems. These services improve the performance and availability and reduce new hardware implementation times for your SAP environment.

Oracle ACS Services for Servers

Oracle ACS offers several services to help you improve the performance and availability of your Oracle servers and reduce deployment time for new systems. Installation and configuration assistance includes pre-production readiness reviews to speed deployment of new Oracle systems and ensure your resulting SAP environment is stable and supportable. Tailored services for server performance tuning and availability configuration optimize your SAP environment. And, customized workshops address best practices and knowledge transfers so you can operate your servers with confidence.

Oracle ACS Services for Storage

As with servers, Oracle ACS offers installation and configuration assistance to speed deployment of new Oracle storage systems. Storage optimization services include configuration and performance reviews and advanced monitoring and resolution services to maximize the availability and performance of storage systems in your SAP environment.

To learn more about Oracle ACS services for servers and storage, visit:

http://www.oracle.com/us/support/advanced-customer-services/servers-storage/overview/index.html

.

Oracle ACS Services for Engineered Systems

Through a complete lifecycle approach, Oracle ACS delivers mission-critical support for Oracle engineered systems, including Oracle Exadata, that help you maximize the return on your engineered systems investment.

Advisory and planning, design and build, and deployment services ensure a smooth migration to Oracle engineered systems and operational readiness within your

SAP environment. Ongoing production support reduces risk and gives you a single point of contact for both

Oracle and SAP issue resolution. The Oracle Exadata

Start-Up Pack for SAP provides an integrated service package for end-to-end support coverage, including the following services:

• Oracle Exadata Start-Up Advisory Service

• Oracle Exadata Installation and Configuration Service

• Oracle Exadata Production Support Readiness Service

• Data migration services

• Oracle Exadata Quarterly Patch Deployment Service

(including Oracle and SAP patching)

For more information on Oracle ACS services for engineered systems, visit:

http://www.oracle.com/us/ support/advanced-customer-services/engineered-systems/ overview/index.html

Oracle Business Critical Service for Systems

Oracle Business Critical Service delivers enhanced preventative support and accelerated response times for your mission-critical SAP systems. Priority response with service-level agreements (SLAs) for response time and time-to-replace and on-site assistance for high-severity incidents ensures faster problem resolution. Continuous system monitoring with automated service request generation detects faults and starts the resolution process before they impact operations. The preventative services with regular system reviews and proactive patching optimizes performance and availability of critical systems in your SAP environment. To learn more about Oracle

Business Critical Services for systems, visit:

http://www.oracle.com/us/support/premier/business-critical- service/overview/index.html

.

66

Support Services for SAP Customers

Oracle Platinum Services for SAP Environments

Through a special entitlement under the standard Oracle

Premier Support program, Oracle Platinum Services offers customers additional, enhanced support features for their

SAP environments. Using the secure Oracle Advanced

Support Gateway, continuous, remote fault monitoring of your entire Oracle and SAP environment – hardware, database, operating system, and networking – enables accelerated response times. Notification of faults is delivered within 5 minutes of occurrence, with restoration or escalation to development within 15 minutes. Joint debugging of escalated faults starts within 30 minutes of occurrence. The result it decreased downtime through the prevention of critical issues and faster issue resolution.

In fact, Oracle Platinum Services customers experience

50% fewer high-severity issues and 31% faster response times, on average, and reduce support-related workloads within their organization. Additionally, quarterly patch deployment services, including both Oracle and SAP patches, ensure your SAP environment is always up-to-date.

Oracle Platinum Services are included with Platinum- certified configurations of Oracle Exadata, Oracle Exalogic, and Oracle SuperCluster with Oracle Premier Support contracts. For more information about Oracle Platinum

Services for SAP environments, visit:

http://www.oracle.

com/us/support/premier/engineered-systems-solutions/ platinum-services/overview/index.html

.

Oracle Workshops for SAP Customers

Oracle provides customized workshops for SAP customers to help you better maintain and operate your Oracle and

SAP environment. These onsite workshops are tailored to your business needs and delivered by Oracle professionals with deep expertise in optimizing Oracle Database deployments for SAP. Live, hands-on demonstrations and practitioner-oriented documentation cover a variety of topics to help you get the most out of your Oracle and

SAP environment.

Oracle SuperCluster M7 for SAP Customers

67

O R A C L E S U P E R C L U S T E R M 7 F O R S A P C U S T O M E R S

Oracle SuperCluster M7 combines revolutionary Oracle

Database efficiency and performance with near-zero-overhead secure multitenancy and private-cloud management tools to create a complete, secure, cloud infrastructure for database and applications. Elastic configurations allow you to start with a small system and easily scale your cloud as demand grows over time. The Oracle M7 high-performance processor architecture delivers better enterprise

Java application and Oracle Database performance per-core than any comparable x86 systems. Oracle VM Server for

SPARC and Oracle Solaris near-zero-overhead virtualization work in tandem with an ultra-fast InfiniBand fabric to allow for maximum performance and scalability with no wasted space, power, compute, memory, human, or software resources.

Today’s SAP landscapes can be described as some of the most complex data center landscapes requiring applications, databases, operating systems, cluster software, servers, networking, and storage to be integrated, expertly managed, and able to ensure business-critical high availability.

Oracle SuperCluster M7 is the only architecture for SAP customers that uniquely provides Oracle’s secure private cloud infrastructure optimized for database and applications with integrated compute, storage, and networking resources as well as virtualization, OS, and management

– making it the ideal infrastructure for SAP landscapes.

Oracle SuperCluster M7 is the best platform for running all tiers of SAP. With new Oracle SuperCluster M7 engineered optimizations – including the performance of

Oracle’s SPARC M7 processor, the industry’s strongest security, end-to-end integration with Oracle Solaris Cluster for high availability, and optimizations for Oracle Solaris

– there is no other comparable solution on the market.

Validated and supported by SAP, Oracle provides an innovative way to accelerate deployment and reduce operational costs throughout the SAP architecture lifecycle. Oracle and

SAP’s joint development for decades has led to tighter engineering and integrations of Oracle SuperCluster and

Oracle Database for SAP. Oracle SuperCluster M7 integrates SAP security compliance extensions as part of the

SAP compliance framework.

Oracle SuperCluster has been successfully implemented and deployed for the consolidation of the complete SAP landscape, simplifying and accelerating deployments, consolidating infrastructure, accelerating performance, and providing a high-availability mission-critical Oracle cloud platform. Oracle SuperCluster customer use cases running SAP demonstrate the breadth of the scope of this solution.

Key Benefits of Oracle SuperCluster M7 for SAP

Customers

Oracle SuperCluster M7 has been engineered as Oracle’s secure cloud infrastructure with the industry’s most advanced security, extreme performance, and a complete suite of efficiency enhancements, tools, and automation that work together to dramatically lower cost and complexity.

In the areas of security, performance, and efficiencies specific technologies are integrated and optimized in Oracle

SuperCluster M7, including the SPARC M7 processor,

Oracle Solaris, Oracle Solaris Cluster, Oracle Database, and SAP.

SAP landscapes are complex, with many layers of infrastructure benefiting from consolidation to reduce total cost of ownership and improve SAP application performance, manageability and availability. Traditional SAP landscapes evolve to complex, segregated infrastructures for production, development, and quality assurance.

Oracle SuperCluster provides a simplified, consolidated cloud infrastructure for SAP landscapes as an architectural foundation. Oracle SuperCluster combines compute, networking, and storage hardware with virtualization, operating system and management software in a complete, high-performance infrastructure that is extremely secure and easy to deploy, manage, and maintain.

68

Oracle SuperCluster M7 is engineered for performance and optimized across all layers of the Oracle and SAP stack (Figure 1). Joint development and co-engineering with SAP is part of Oracle’s product strategy and performance optimization process.

Overview of Oracle SuperCluster M7 Technology

Oracle SuperCluster combines highly available and scalable technologies, such as Oracle Database 12c, Oracle

Database 11g, and Oracle Real Application Clusters

(Oracle RAC) with industry-standard hardware. All the integrated and optimized hardware – including Oracle’s

SPARC M7 servers, Oracle Exadata Storage Servers, and the Oracle ZFS Storage ZS3 appliance – are integrated through the QDR InfiniBand unified network. All components are preconfigured, tested, integrated, tuned, and performance optimized, and they are designed with no single point of hardware failure (Figure 2).

Oracle SuperCluster M7 for SAP Customers

69

Oracle SuperCluster M7 Features:

The following list describes some of the most prominent feature of Oracle SuperCluster M7:

•

Unmatched Performance:

Oracle SuperCluster M7 features the world’s fastest processor for general-purpose computing: SPARC M7. Enhancements for cryptographic acceleration and Oracle Database 12c query acceleration are integrated directly into the processor’s design. SPARC M7 In-Line Decompression combined with SPARC M7 SQL acceleration for Oracle Database

In-Memory 12c increase performance of resource-intensive SAP applications.

•

Advanced Security:

Oracle SuperCluster M7 features the industry’s most advanced security, incorporating a number of unique runtime security technologies, documented and tested system-wide security controls and best practices, and integrated automated compliance verification tools. Unique technologies include SPARC

M7 Silicon Secured Memory, SPARC M7 cryptographic acceleration, read-only virtual machines, and end-to-end audit trails.

•

Scalability:

Oracle SuperCluster M7 also offers unmatched scalability for SAP environments. Designed for highly efficient and secure multitenancy, Oracle SuperCluster integrates scale-up virtualization and a scale-out

InfiniBand fabric to provide maximum flexibility in provisioning system resources to tenant databases and applications. This is done while maintaining maximum isolation from other tenants’ workloads, with optimal performance and no wasted compute, memory, or software resources.

•

Secure Multitenancy:

Secure multitenancy allows a high degree of isolation between multiple concurrent entities that are permitted to operate and manage their own services on a single, physical

Oracle SuperCluster. Applications may have varied security, reliability, and performance requirements.

Workloads are isolated in Oracle Solaris Zones, and resource management and user account management are centrally managed. Oracle SuperCluster provides centralized management of hardware isolation between groupings of CPU, memory, and I/O for higher availability within the node.

Conclusion

Oracle SuperCluster M7 is the only architecture for SAP that uniquely provides Oracle’s secure private cloud infrastructure optimized for database and applications with integrated compute, storage, networking resources as well as virtualization, OS, and management – making it the ideal infrastructure for SAP landscapes.

With new Oracle SuperCluster M7 engineered optimizations, including the performance of Oracle’s SPARC M7 processor, the industry’s strongest security, end-to-end integration with Oracle Solaris Clusters for high availability, and optimizations for Oracle Solaris, there is no other comparable combined platform on the market.

Oracle provides the extensive comprehensive technology and services uniquely able to provide a high-availability mission-critical Oracle cloud platform for SAP. This paper provided a high-level introduction to the Oracle

SuperCluster M7 technology as it relates to SAP.

More information:

http://www.oracle.com/us/solutions/sap/engineered- systems/supercluster/index.html

70

S A P C U S T O M E R S B E N E F I T I N G O F E X A D A T A T E C H N O L O G Y

Performance Boosts and other important benefits right out-of-the-box, no changes required

Oracle Exadata Database Machines deliver extreme performance boosts for all customer workloads like SAP

Business Suite (i.e. SAP ECC 6.0, SAP CRM 7.x) and SAP

BW 7.x. Oracle Exadata customers can also run Oracle

Databases with multiple workloads, SAP and non-SAP, on a single Oracle Exadata Database Machine. The fact is: It is simple and fast to implement, the Exadata Database

Machine is ready to tackle the largest and most important database applications and often run them 10 times faster or more. The key is system engineering, using industry standard hardware from Sun and the intelligent database and storage software from Oracle.

Oracle Exadata Database Machine is certified by SAP since

July 2011 and SAP customers can use Oracle Exadata

Database Machine for their SAP applications. Exadata is an easy-to-deploy solution for hosting the Oracle Database and runs SAP unchanged providing better performance out-of-the-box, consolidates SAP NetWeaver applications, and reduces the number of vendors to just two;

SAP and Oracle. Oracle Exadata also allows better support, fast online migration, DBaaS deployment platform, advantages of the Enterprise Database Cloud Solution with a rapid deployment of its infrastructure, and lower costs through consolidation.

Over time many more SAP customers worldwide have purchased and deployed Exadata Database Machines. The following shows some customers around the world that have implemented Oracle Exadata Database Machine across different industries and highlights some challenges and solutions they faced in various environments.

Expansion requires a “Datacenter of the Future”

The challenges for a chemical and fertilizer company in

India with approximately half a billion USD in revenue listed the following: implementing a new future oriented and scalable solution that helps to force planned expansion into the APAC region. Hardware reaching end of life and was not supporting growth. In addition, the need for increased storage requirements was also an issue.

So, the company realized a detailed comparison of traditional systems versus engineered systems was required.

A PoC which focuses on SAP ECC and BW running on

Exadata Database Machine cleared up any last doubts and the benefits for the company are enormous. A company spokesman said, “Oracle Exadata Database Machine is central for us building up a datacenter of the future. As a high performance platform to support our user growth we are able to fulfill our plans ideally”. Other benefits include an efficient database consolidation, storage savings and significant performance gains.

Next example, a core consumer finance company in

Japan found advantages by deploying Exadata Database

Machine. In this case the management expects cost reduction in IT through consolidation of databases and a migration from Unix to Linux for SAP ECC. A smooth migration process to Oracle Exadata (with R/3 Load) is in the plan and also the replacement of the Itanium HP UX system. It is clear that with the new platform the finance company is able to continue the growth and consolidation of SAP, increasing the performance of processes and enabling more complex data queries.

SAP Customers benefiting of Exadata Technology

71

Why more SAP Customers worldwide deploy Oracle

Exadata Database

Another customer example in Japan involves the import and export sales of Japanese chemicals, plastics, electronic materials, cosmetics and health foods. The Oracle Exadata

Database Machine was first used successfully for the company’s non-SAP environment and now is also used for the SAP environments. “Due to very good results in non-

SAP decision was made to go for SAP ECC with Exadata

Database Machine with X3 Half Rack”, a spokesman said. The main goal was to consolidate all databases and to benefit from the return of investment through cost reduction and replacement of the Windows platform. In summary the ECC system was facing various demands to increase performance, minimize downtime and ensure business growth.

Customer requires Real-Time Business

Meanwhile, in North America, a US media and entertainment company has different challenges which Oracle

Exadata Database Machine perfectly solved. First the customer requires a kind of real-time business. Second there are I/O problems or issues with the current infrastructure and especially demanding SLAs. The customer was looking for a suitable IT architecture with a future growth path, inclusive private cloud offering DBaaS with charge-back and rapid provisioning. “Before making our final decision we checked SAP HANA as an alternative.

We clearly saw that Oracle Exadata Database Machine fulfills all important demands, which we built up”, a spokesman from the company said.

Another US customer from the health care sector chose the same solution. In this example a technology refresh for

SAP BW was needed. The IT staff wanted to make sure they had a very dense database consolidation platform that would scale for a global roll-out. The company is extremely happy with their choice with implementing

Oracle Exadata. Not only was the performance of the application exceptional, but it fit within the strategic corporate goals to provide the optimal platform for consolidation and standardization.

Next example in the US, a global consumer packaged goods company selected Exadata for their SAP BW. There were significant performance problems running BW on x86 and Microsoft Windows. The IT team from the

Fortune 500 Company evaluated Oracle AWR reports and recommended Exadata for SAP BW. The statement from the company spokesperson: “Now we are able to continue the growth and can consolidate SAP workloads, increase the performance of business processes and reduce the overall platform cost.”

In other parts of the Americas, SAP customers deploy the

Oracle Exadata Database Machine to solve other challenges and requirements. For example, a company from the energy sector in Brazil is using Exadata to deliver better performance and provide a smoother integration of their

SAP environment. Query time improved by a factor of 25 and the load time decreased by a factor of 10 as compared to the same activities ran on the previous hardware.

Faster Time-to-Market

EMEA Region, a large insurance and financial services company wants faster time-to-market with new products. From an IT perspective they needed to reduce the complexity of dozens of databases running on multiple operating systems (IBM AIX, Linux, MS Windows and

Solaris). With Exadata Database Machine the customer is now able to realize database consolidation of their SAP and non-SAP systems, with less effort and a decreased number of licenses. Oracle Exadata helps the company to achieve greater success by requiring less time-to-market and reducing IT complexity.

Another example from EMEA, a B2B retailer with

10,000 employees has the task to reduce IT costs and to solve business problems. The company minimized costs by consolidating 46 databases into two Exadata

Machines. User I/O is no longer a major wait event and batch jobs now run in one-third the time. All of this with no application changes required. The retailer now gets, as a spokesperson said, “much better performance of the out-of-the-box”.

The last example from our many SAP customers, which buy and deploy Exadata Database Machine, is a large French company from the electricity sector. The main point being that the company had performance issues while running

ECC batch jobs. Trying to solve this problem Oracle

Exadata and two other alternatives were evaluated. A PoC to validate Exadata convinced the customer. The SAP customer is clearly benefiting from the new Oracle IT infrastructure, “Thanks to Exadata for SAP the IT landscape is now highly consolidated and optimized and also compatible with our future demands”, a spokesman stated.

72

H I G H A V A I L A B I L I T Y F O R S A P R E S O U R C E S B Y S A P C T L

When an application, process, or server fails in a cluster, you want the disruption to be as short as possible, if not completely unknown to users. For example, when an application fails on a server, that application can be restarted on another server in the cluster, minimizing or negating any disruption in the use of that application. Similarly, if a server in a cluster fails, then all of the applications and processes running on that server must be able to fail over to another server to continue providing service to the users.

Typically, customers use built-in generic_application resource types or customizable scripts and application agent programs with resource attributes that are assigned to applications and processes, Oracle Clusterware can manage all these entities to ensure high availability.

SAP customers are usually very keen to run a highly available infrastructure and deliver a non-disruptive service to

SAP end users. This can be a challenging task with many components from many vendors operated by one or many organizations all having to get the products’ infrastructure/ecosystem under control. Many SAP customers are trying to reduce the complexity and increasing efficiency by migrating to Oracle Engineered Systems like Exadata and Super Cluster, but others are willing to run the current environment as highly available as possible with minimum effort. An SAP environment has a well known challenge with high availability that includes among others the

SAP Enqueue service whose failure could lead to a restart of the entire SAP system.

The SAP Enqueue Service provides distributed lock management for SAP application server instances. It must be available whenever an SAP system uses more than one

SAP instance. In order to support SAP application high availability, the Enqueue Service together with the Message

Service builds up the “Standalone Enqueue Service” (ASCS) for SAP WebAS ABAP. In case of SAP WebAS JAVA, the

Enqueue Service together with the Message Service forms the “Central Services Instance” (SCS). This SCS instance is always required for the JAVA stack of SAP. SAP uses an active/passive approach to enable high availability for the respective Enqueue Service. There is exactly one

Enqueue Service for application type ABAP and one for application type JAVA running in the SAP system. The

SAP system comprises multiple application instances on different nodes. One or more SAP Replication Services run on the node on which the active Enqueue Service for

ABAP and/or JAVA falls over in the event of a failure or planned outage. The term ‘service’ is used to signify the SAP process that provides either Enqueue or Replication. The nodes that host these services are termed the

‘Enqueue Server’ and the ‘Replication Server’.

SAP on Oracle Database customers have the choice to use any of the SAP certified failover software depending on their preferred vendor and OS platform. Even better is the usage of Oracle Clusterware which helps to reduce the number of software vendors, complexity, administration effort and even software license costs. Oracle Clusterware is a portable cluster software that allows clustering of single servers so that they cooperate as a single system.

Oracle Clusterware also provides the required infrastructure for Oracle Real Application Clusters (RAC). In addition

Oracle Clusterware enables the protection of any Oracle application or any other kind of application like SAP within a cluster.

Oracle Clusterware can provide high availability for SAP resources just as it does for Oracle resources. Oracle has created an Oracle Clusterware tool, SAP Control (SAPCTL) to enable customers to easily manage SAP high availability resources. SAPCTL provides an easy-to-use interface to administer the resources, scripts, and dependencies of

Oracle Clusterware and SAP high availability components.

SAPCTL consolidates the functionality of the Oracle command-line tools by enabling SAP customers to easily manage the SAP Enqueue Service, the SAP Replication

Service, and the additional virtual IP addresses used by the

SAP Enqueue Service for ABAP and JAVA.

High Avaiability for SAP Resources by SAPCTL

73

In addition to the critical SAP high availability components, namely the SAP Enqueue and SAP Replication Service,

SAPCTL Version 8 provides an interface for the protection of arbitrary number of SAP application instances. The SAP

Central Instance (CI) or SAP application instances (DV) are possible candidates to run under SAPCTL supervision.

The SAPCTL tool supports SAP Standalone Gateway (GW) and SAP WebDispatcher (W) as independent SAP instances as well.

For all supported SAP instance types, SAPCTL in addition monitors the associated SAP Start Service (sapstartsrvdaemon process) with an always co-located CRS resource. The SAP Start Service process is started automatically by SAPCTL if the SAP instance gets started on a cluster node or relocated to another node in the cluster.

There is no need to bring up all SAP Start Processes on system boot by sapinit procedure as this task is performed by SAPCTL after startup of Oracle Clusterware.

Oracle Exadata, Oracle SuperCluster and Oracle Database Appliance are certified to run SAP Central Services

(SCS and ASCS instances and the ER instances) and

SAPCTL supports these services when running on above mentioned Engineered Systems. SAP kernels starting with kernel version 7.00 are supported by SAPCTL on

LINUX, Solaris and AIX operating system. SAPCTL has been certified for integration with SAP NetWeaver via the SAP integration scenario NW-HA-CLU 7.40.

SAP customers who implemented SAPCTL on top of

Oracle Clusterware and RAC can get rid of 3rd party high availability software like IBM PowerHA and HP

Service Guard, etc. You save additional money since

SAPCTL is free of charge and can dramatically reduce the administration effort. While Oracle Real Application

Clusters (RAC) removes the Oracle Database instance as

Single Point of failure (SPOF), Oracle SAPCTL removes one more SPOF (Enqueue Service) but this time on the

SAP application level. It is the foundation that provides the SAP infrastructure a much higher availability level and better respond to restrictive SLA’s. Oracle technology also provides comprehensive disaster recovery solutions by using Data Guard on top of physical standby database.

Solutions such as these can replace storage mirroring and again reduce infrastructure costs.

The SAPCTL tool supports SAP Standalone Gateway

(GW) and SAP WebDispatcher (W) as independent SAP instances as well.

The implementation guide and software needed for SAP-

CTL is attached to the SAP Note “1496927 – Protection of SAP instances through Oracle Clusterware.”

74

E N G I N E E R E D F O R I N N O V A T I O N , E F F I C I E N C Y A N D

S I M P L I C I T Y : O R A C L E E N G I N E E R E D S Y S T E M S F O R S A P

Companies need to optimize their IT infrastructure to achieve best performance at attractive cost. Oracle innovates at every layer of the stack to design engineered systems that reduce the cost and complexity of IT infrastructures while increasing productivity and performance.

Oracle Engineers Systems that are integrated across the entire technology stack, – so you don’t have to this.

Reduced IT complexity frees up time and money, leaving more to spend on innovation and new opportunities.

The Oracle Exadata Database Machine, the Exalogic

Elastic Cloud, Oracle Database Appliance, Private Cloud

Appliance and the Oracle SuperCluster are designed to achieve enterprise performance levels that are unmatched in the industry.

Oracle’s Engineered Systems combine best-of-breed hardware and software components with game-changing technical innovations that simplify operations and lower total cost of ownership (TCO). With Oracle Engineered

Systems for SAP, that extreme performance is optimized for SAP applications.

Where competitors stop with “ultra”, “highly” or “xy” converged systems, Oracle does not stop there, but moves one step ahead by really engineering all layers and integration of all layers into one solution which is designed, tested, built and delivered based on own IP and industry standards.

Extreme Performance at Every Layer of the

Technology Stack

• Extreme performance means getting the job done faster, better, and more efficiently than it has been done before. It‘s the hallmark of

Oracle‘s Engineered Systems and the ultimate embodiment of Oracle‘s drive to simplify IT

Oracle starts with the world’s most complete, open, and integrated technology stack – including database technology, management software, operating systems, servers, and storage.

Oracle Engineered Systems

• While each of the IT infrastructure layers provide leading-edge technology in itself, Oracle went one step further and designed engineered systems that are pre-integrated to reduce the cost and complexity of

IT infrastructures while increasing productivity and performance

• Only Oracle can innovate and optimize at every layer

of the stack to simplify data center operations, drive

down costs, and accelerate business innovation

• Each system integrates Oracle‘s applications-to-disk technology stack – servers and storage, operating systems, database software, middleware, networking, and built-in virtualization features – to reduce the time and cost associated with purchasing, provisioning, deploying, and maintaining SAP infrastructure

• Oracle and SAP have jointly tested and certified

Oracle’s Engineered Systems for SAP, making them available as a family of engineered systems that are pre-integrated, pre-tested, and pre-configured to simplify data center operations, ensure fast and easy SAP infrastructure deployment, and accelerate business innovation

• Optimized for Oracle Database and SAP applications,

Oracle’s Engineered Systems for SAP reduce the time needed to get SAP landscapes up and running

Oracle Engineered Systems in the Datacenter

• Once deployed, consolidating SAP landscapes on

Oracle’s Engineered Systems reduces data center management complexity

Oracle Engineered Systems for SAP

75

• Administrators can use SAP’s BR*Tools and Oracle

Enterprise Manager Ops Center to manage SAP landscapes and SAP infrastructure. Built-in automation features simplify administration tasks and reduce day-to-day management demands.

The Oracle Exadata Database Machine, the Oracle Database Appliance, the Exalogic Elastic Cloud, the Oracle

SuperCluster and the Private Cloud Appliance are designed to achieve enterprise performance levels that are unmatched in the industry.

Oracle Engineered Systems for SAP

• A massively parallel grid architecture using RAC and

Exadata storage delivers extreme performance with linear I/O scalability, dramatically increasing data bandwidth between the database server and storage.

Intensive query processing and data mining scoring are offloaded to storage servers, bringing processing closer to SAP data to improve query performance and concurrency

• All servers, storage, and networking components are pre-cabled in racks, and the complete package is pre-integrated and pre-tested, cutting weeks or

Designed to deliver extreme performance to data warehousing, online transaction processing (OLTP), and mixed-load database applications, the Oracle Exadata

Database Machine is tailor-made to improve SAP performance and manageability.

A “data center in a box”, the Exadata Database Machine is an easy-to-deploy system that includes all the hardware needed for running the Oracle Database. From there, it adds Oracle Real Application Clusters (RAC), Oracle

Grid Infrastructure, storage management tools, and administration software – and optimizes the entire system for extreme performance, mission-critical availability, and reliability.

Using Exadata in SAP Environments

The Oracle Exadata Database Machine is the perfect choice for SAP environments on several levels.

• It delivers outstanding I/O and SQL processing performance for online transaction processing, (SAP

ERP), business warehouse, (SAP BW) and consolidation of mixed workloads months from deployment schedules. It cuts management and maintenance chores by simplifying tasks such as patching with single vendor bundled patch sets, and provides high availability and disaster recovery out-of-the-box

• SAP customers can easily migrate their database to Exadata, which runs SAP applications unchanged.

Depending on the source platform, the migration could be as smooth as an operating system platform upgrade

Designed for private clouds, the Oracle Exalogic Elastic

Cloud delivers virtually unlimited scalability, unbeatable performance, and previously unimagined management simplicity to SAP applications.

Engineered and balanced for the compute-intensive workloads of middleware and packaged applications, each pre-assembled, pre-configured system contains fully integrated, hot-swappable x86 compute nodes, a high-performance Oracle ZFS Storage Appliance, high-bandwidth communications fabric, and switches.

76

Oracle Exalogic Elastic Cloud for SAP

Exalogic is designed to simplify application management and improve operational efficiency.

• By offering modular building blocks that are designed, integrated, tested, shipped, installed, configured and operated as a whole, Exalogic radically reduces complexity for SAP environments. For SAP customers, this means a quick, efficient, and easy-to-deploy infrastructure for SAP landscapes

• All Exalogic configurations are fully redundant at every level and are designed with no single point of failure.

Together with SAP‘s and Oracle‘s own high availability techniques, this offers unprecedented levels of reliability for SAP infrastructure deployments

• Exalogic’s highly standardized, factory-integrated, certified, and tested components feature a single point of contact for all storage, server, OS, and system management service needs, greatly simplifying set up and deployment, substantially reducing risk of errors, simplifying diagnosis, and standardizing operations

All SAP products based on SAP NetWeaver 7.x that are available on the Oracle Linux 6 platform can now be used in a virtual Exalogic configuration.

Oracle SuperCluster

Oracle innovations such as next-generation SPARC T5/

M7 servers, Oracle Solaris 10 and Solaris 11, Oracle Database 11g and 12c, and Exadata storage come together in this scalable, engineered system that is optimized and tuned for consolidating enterprise SAP applications.

Oracle’s Optimized Solution for SAP based on Oracle

SuperCluster is engineered to run SAP applications in conjunction with a wide range of complementary enterprise applications at the highest levels of performance and reliability. Users can greatly simplify their SAP landscape by consolidating their SAP application instances, central services, and database software onto an Oracle SuperCluster

M7 system.

Running an SAP Landscape on Oracle SuperCluster

Oracle SuperCluster is supported by SAP. It runs the

Oracle parallel database, the SAP central instance, application, or web server, Oracle Enterprise Manager management software, and all your SAP applications.

This is especially suited for SAP customers who need a multi-purpose system to run SAP as well as additional enterprise applications, or have multi-tiered applications to consolidate and virtualize within their datacenter.

• With the Oracle Optimized Solution for SAP, enterprises can modernize their infrastructure, consolidate

SAP landscapes, and manage more workloads in a reduced data center footprint to achieve significantly better performance and productivity, reduced risk, and lower total cost of ownership

• The Oracle Optimized Solution for SAP provides a complete architecture that is designed, tested, and tuned to address the demands of mission-critical enterprise SAP application environments

• Customers can consolidate landscapes, including development, testing, and production, onto a highly available and scalable platform to improve SAP application performance and availability

• Built-in virtualization technologies securely isolate

SAP workloads and offer the fine-grained resource control needed to safely consolidate SAP onto a single platform. Compute, memory, and I/O resources can be managed to ensure applications have access to an appropriate amount of resources and that no workload consumes the entire platform. Built-in management streamlines operations and eliminates the need for different skills

Oracle MiniCluster

Oracle MiniCluster S7-2 is an extremely simple and efficient engineered system designed to run enterprise databases and applications with uncompromising security.

Its simplicity, out-of-the-box performance and reliability, and small form factor make it an excellent choice for remote offices, small offices, and agile software development environments. It is ideal for highly security-sensitive applications, such as managing patient medical records, processing financial transactions, handling secure communications, running mission-critical enterprise resource planning (ERP) applications, and hosting security-related services.

Oracle Engineered Systems for SAP

77

Private Cloud Appliance is an engineered system that

radically simplifies the way customers install, deploy, and manage converged infrastructures for Oracle Linux or

Oracle Solaris applications.

It offers a highly available, fully redundant converged infrastructure system combining networking, compute, management, and storage elements. It comes with one price for all the hardware in the system and all needed software. And supports Oracle Trusted Partitions that allows you the flexibility to license Oracle software on a virtual CPU basis. And it connects to your existing or new Oracle storage or third-party storage. It provides

Software-Defined Network Infrastructure with Oracle Fabric Interconnect and Oracle SDN. You will benefit from a single point of support for the entire stack, including

Oracle hardware and software.

Private Cloud Appliance is Certified by SAP

All SAP products based on SAP NetWeaver 7.x available on Oracle Linux 5 and Oracle Linux 6 can now be used on the Oracle Engineered System designed for virtualization – the Private Cloud Appliance.

Three-Tier and Two-Tier installations (Oracle Database and SAP applications) are supported to run on the Oracle

Private Cloud Appliance.

Private Cloud Appliance can be used in SAP environments when the following conditions are met:

• Minimum use of Private Cloud Appliance

Release 1.1.3.

• Private Cloud Appliance is based on Oracle VM.

Please follow the related Oracle VM information

from SAP Note 1808268.

• The following Operating Systems in VMs are certified and supported for the use in SAP environments.

• Oracle Linux Release 5.x with UEK

• Oracle Linux Release 6.x with UEK

• Oracle Solaris

The Oracle Database Appliance is a 4U rack-mountable system specifically designed to run Oracle Database

Enterprise Edition. It supports high availability and accelerated database performance requirements with redundant and hot swappable components, and triplemirrored and shared disk and flash storage. Pre-installed with Oracle Linux and Oracle appliance manager software, this appliance saves time and money by simplifying deployment, maintenance, and support of a highly available database solution.

Using Oracle Database Appliance in SAP Environments

The Oracle Database Appliance provides the following capabilities for an SAP environment:

• Highly available active-active clustered data

base server for SAP applications

• Highly available file server for SAP-required shared file systems

• Complete clustering solution for SAP

high-availability resources such as central

services for both ABAP and JAVA stack

78

What will the migration to S/4 HANA cost ?

What will the migration to S/4HANA cost?

IG SAP CH is warning and demanding that the migration to S/4HANA should be free for existing SAP customers as a simple version change.

The SAP user advocacy group IG SAP CH is known as a strong critic of the German software giant.

The group, in which around 80 companies are involved, vehemently called for SAP to adjust prices for software maintenance to currency trends . Bernd Brandl, who has been holding the reins at SAP

Switzerland for two years, was however unwilling to listen to this appeal, as our readers will know . The group recently announced in a newsletter that it is continuing to use every possible means of swaying SAP. It states that because the euro conversion rate for maintenance costs for SAP systems is fi xed between CHF 1.17 and CHF 1.60, Swiss SAP users still pay up to 50 percent more than customers in other countries.

Is S/4HANA a completely new product?

In the newsletter, IG SAP CH raises another extremely important question.

Is the latest version of SAP‘s business software something completely new and must therefore be purchased by existing customers or is S/4HANA a new version already paid for through ongoing maintenance charges?

It is known that SAP is currently offering good prices to customers who opt for

S/4HANA. SAP is using subscription offers to encourage the “premature purchase“ of S/4HANA licenses, the group writes.

But it argues that it would be impossible to put a fi gure on the scope and costs involved in a migration concept like this.

SAP itself clearly sees S/4HANA as a completely new product, which must be paid for accordingly. This at least is how one can interpret the introduction in the white paper “Simplifi cation List for SAP S/4HANA“ , which states: „S/4HANA (...) is not a legal successor of any SAP Business Suite product.“

The group is demanding that existing customers should not have to pay license fees over again for S/4HANA. “We say NO – the migration to S/4HANA must be available as an upgrade to change versions as part of normal maintenance,“ the newsletter says.

http://www.inside-it.ch/articles/42944

Oracle DB related Notes for SAP

79

For Oracle Solaris and latest DB Notes please see: service.sap.com

Note Number Note Title

DB : General : Licensing Information

581312

Oracle Database Licensing Restrictions

740897

1028068

Oracle License Scope & Required Oracle Options

Required Oracle Options for DBA Cockpit

DB : General : Version Support

1174136 Oracle: End of Support Dates

2098258 Oracle 11.2 Extended Support Free of Charge until May 31, 2017

DB : General : Feature Support

105047

1914631

2133079

Support for Oracle Functions in the SAP Environment

Central Technical Note for Oracle Database 12c Release 1 (12.1)

Oracle Database 12c: Integration in SAP Environment

1398634

1430669

1431800

1434131

Oracle Database 11g Integration in SAP Environment

BR*Tools support for Oracle 11g

Oracle 11.2 Central Technical Note

Oracle Database 11.2 for older SAP versions

DB : General : Oracle Support for HANA-Related SAP Application

1835008

Activate Database Performance Optimizations for SAP ERP

1951491

Minimal DB Platform Requirements for SAP NetWeaver 7.4 SP08

DB : General : File System Support

1416773

Oracle Direct NFS

1550133 Automatic Storage Management (ASM)

1598594

1627541

BR*Tools Configuration for Oracle Installation under „oracle“ User

BR*Tools Support for Oracle ASM and Exadata

1738053

SAPinst for Oracle ASM Installation

1825328

Oracle ASM and SAP NetWeaver Master Data Management (MDM)

DB : General : Tool Support

355770

386413

Oracle Enterprise Manager Database Control

Oracle Enterprise Manager (OEM) in the SAP Environment

DB : Features : Data Storage & Compression

1109743

Use of Index Key Compression for Oracle Databases

1464156

1426979

1583303

Support for Index Compression in BRSPACE 7.20

SecureFiles – The New Way to Store LOB Data

Deferred Segment Creation

1842044

1856270

Dataload Without Dropping Bitmap Indexes

Performance Improvements for Tables with Single Unique Index

DB : Options : Advanced Compression

1289494 FAQ Oracle Compression

2138262

1431296

1436352

Oracle Database 12c Advanced Compression for SAP Systems

LOB Conversion and Table Compression with BRSPACE 7.20

Advanced Compression for SAP Systems

DB Version

All DB Versions

All DB Versions

All DB Versions

All DB Versions

Oracle DB 11g

All DB Versions

Oracle DB 12c

Oracle DB 12c

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

All DB Versions

All DB Versions

All DB Versions

All DB Versions

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

All DB Versions

Oracle DB 12c

Oracle DB 11g

Oracle DB 11g

80

Note Number Note Title

1915299

1915301

1915302

1915315

1915317

2064206

1431793

1431794

1949451

1431796

1431797

DB Option: Partitioning

742243

1859841

General Table Partitioning

Deinstallation of Oracle Partitioning Option (SAP BW)

1333328

Partitioning Engine for Oracle

DB Option: Real Application Clusters (RAC)

527843

Oracle RAC Support in the SAP Environment

1431241

RAC with TAF

1496927

1977463

2059515

Protecting SAP instances through Oracle Clusterware (SAPCTL)

Using Shared or Local Oracle Homes with RAC

Database Upgrade to Release 11.2.0.4 on Unix with RAC or ASM

DB Option: Real Application Testing (RAT)

1426980

The Real Application Testing Option

DB Features: Security

157499

OPS$ Connect and Security Aspects

1622837

Secure Connection of AS ABAP to Oracle via SSFS

1623922

1710997

Connect to Oracle Database

Using Personalized Database Administrator Accounts

1755636

Database Administrators Segregation

1764043

Support for Secure Storage in BR*Tools

1868094

Overview: Oracle Security SAP Notes

DB Option: Advanced Security

973450

974876

Advanced Security – Network Encryption

Advanced Security – Transparent Data Encryption

1324684

1597194

Advanced Security – Backup Encryption

DB Option: Database Vault

1355140

Using Oracle Database Vault in an SAP Environment

Installing Oracle Database Vault in an SAP Environment

1502374

Database Vault for SAP Policy Scripts

1716939

SAP System Copies with Database Vault

Deployment: Software: Installation & Upgrade

Troubleshooting Software Installation for 12.1.0.2

Database Software 12.1.0.2 Installation on Unix

Database Software 12.1.0.2 Installation on Windows

Database Upgrade Scripts for 12.1.0.2

Migrating to Software Owner ‚oracle‘

Database Upgrade to 12.1.0.2 with Grid Infrastructure

Upgrade Scripts

Instant Client

Database Upgrade to Release 11.2.0.4 on Unix (Quick Reference)

Troubleshooting the Software Installation

Troubleshooting the Database Upgrade

DB Version

All DB Versions

All DB Versions

All DB Versions

All DB Versions

Oracle DB 11g

All DB Versions

Oracle DB 12c

Oracle DB 12c

Oracle DB 11g

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

Oracle DB 11g

Oracle DB 11g

All DB Versions

Oracle DB 12c

Oracle DB 12c

Oracle DB 12c

Oracle DB 12c

Oracle DB 12c

Oracle DB 12c

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB related Notes for SAP

81

For Oracle Solaris and latest DB Notes please see: service.sap.com

Note Number Note Title

Deployment: Software: Patches

1027012

2011199

1915313

1915316

2145572

1696869

1431799

1949250

MOPatch – Install Multiple Oracle Patches in One Run

SAP Bundle Patches – Structure Changes Starting June 2014

Current Patch Set for Oracle Database 12c Release 1 (12.1)

Database: Patches for 12.1.0.2

Grid Infrastructure: Patches for 12.1.0.2

Patching of Oracle Homes with Minimal Downtime

Oracle 11.2.0: Current Patch Set

Database Patches/Patch Collections (11.2.0.4)

1968502 Grid Infrastructure Patches/Patch Collections (11.2.0.4)

Deployment : Instance Configuration

1888485

1431751

1431798

Database Parameters 12.1.0.2

Quick Reference for ADRCI and ADR

Database Parameter Settings 11.2.0.x

SAP Workload Management via Oracle Resource Manager

Deployment : Software : BR*Tools

1428529

1838850

1844380

2086966

1882182

Corrections in BR*Tools Version 7.20

Corrections in BR*Tools Version 7.40

Minor Functional Enhancements in BR*Tools (5)

Minor Functional Enhancements in BR*Tools (6)

Functional Enhancements in BRARCHIVE 7.40

Deployment : Data

646681

937492

966117

Reorganizing Tables with BRSPACE

Oracle Flashback FAQ

Oracle Flashback Database Technology

Database: Services

1508271 Oracle Lifecycle Migration Service (formerly O2O/Triple-O)

DB Version

All DB Versions

All DB Versions

Oracle DB 12c

Oracle DB 12c

Oracle DB 12c

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

Oracle DB 12c

Oracle DB 11g

Oracle DB 11g

Oracle DB 11g

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

All DB Versions

82

Imprint

83

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores,

CA 94065

U.S.A.

Published by

Oracle Corporation,

Oracle Database for SAP

Global Technology Center

Albrecht Haug [email protected]

Altrottstr. 31

69190 Walldorf, Germany

Tel. ++49 (0) 6227 356-0

Fax++49 (0) 6227-3847366

Photos: Gross Art,

Shutterstock, USA

Internet: www.oracle.com/sap http://scn.sap.com/ community/oracle

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the

AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of

The Open Group. 0615

SAP® is a registered trademark of SAP

SAP NetWeaver is a registered trademark of SAP

SAP HANA® is a registered trademark of SAP

84