HPE Reference Configuration for Oracle 12c on HPE Synergy composable infrastructure

Technical white paper

Technical white paper

Contents Executive summary .................................................................................................................................................................................................................................................................................................................................3 Introduction ....................................................................................................................................................................................................................................................................................................................................................3 HPE Synergy for Oracle ..................................................................................................................................................................................................................................................................................................................... 4 HPE Synergy Composer .................................................................................................................................................................................................................................................................................................................... 5 Solution overview ..................................................................................................................................................................................................................................................................................................................................... 5 Solution components ............................................................................................................................................................................................................................................................................................................................ 7

Software ..................................................................................................................................................................................................................................................................................................................................................... 8 Best practices and configuration guidance for the Oracle Database solution ................................................................................................................................................................................. 8 Capacity and sizing ................................................................................................................................................................................................................................................................................................................................ 9

Workload description ..................................................................................................................................................................................................................................................................................................................... 9 Workload results ...............................................................................................................................................................................................................................................................................................................................10 Analysis and recommendations .......................................................................................................................................................................................................................................................................................... 11

Summary ......................................................................................................................................................................................................................................................................................................................................................... 11 Implementing a proof-of-concept ........................................................................................................................................................................................................................................................................................... 12 Appendix A: Bill of materials ........................................................................................................................................................................................................................................................................................................ 12 Appendix B: Oracle configuration parameters – HPE Synergy 480 Gen9 ........................................................................................................................................................................................ 13 Appendix C: Oracle configuration parameters – HPE Synergy 660 Gen9 ........................................................................................................................................................................................ 13 Appendix D: Linux kernel configuration ........................................................................................................................................................................................................................................................................... 13 Appendix E: D3940 udev rules .................................................................................................................................................................................................................................................................................................. 14 Resources and additional links .................................................................................................................................................................................................................................................................................................. 15

Technical white paper Page 3

Executive summary The demands of database implementations continue to escalate. Faster transaction processing speeds, scalable capacity, and increased flexibility are required to meet the needs of today’s business. At the same time, enterprises are looking for cost-effective, open-architecture, industry standard solutions that don’t include vendor lock-in or carry the high price tag attached to proprietary solutions.

HPE Synergy is a single infrastructure of pools of compute, storage, and fabric resources, along with a single management interface that allows IT to rapidly assemble, disassemble and re-assemble resources in any configuration. HPE Synergy architecture eliminates hardware and operational complexity so IT can deliver infrastructure to applications faster and with greater precision and flexibility.

The introduction of the HPE Synergy composable infrastructure products simplify this model by reducing the quantity of components and required skillsets needed for deployment. Deployment is accelerated by using HPE Synergy Composer for all interactions with the infrastructure. Pools of resources consisting of compute, storage and fabric can be deployed, managed and reconfigured using templates that outline the resources required for each server in a solution. Once the initial template has been built, servers can be deployed quickly by specifying the template, a unique host name and network address. This allows many steps in the configuration chain to be completed in a consistent and quick manner allowing the entire infrastructure to be built out with as little administrative action as possible. For database solutions like Oracle 12c which use the same configuration for every server, the overall deployment process can be expedited and the possibility of administrative error reduced significantly. Additionally, tiered applications can each have their own template that can be applied to different classes of compute modules. For example, we might deploy an HPE Synergy 660 Compute Module as the Oracle database server and use the HPE Synergy 480 Compute Module as the application tier.

This Reference Configuration will demonstrate the ease of reconfiguring HPE Synergy to bring to bear resources at the time they are needed. It will further provide a proof point regarding the elasticity of HPE Synergy that allows an enterprise to provision exactly what’s needed and expand or contract based on changes in the business’ environment, eliminating the need to over provision at the time of purchase.

Target audience: This Hewlett Packard Enterprise white paper is designed for IT professionals who use, program, manage, or administer large databases that require high availability and high performance. Specifically, this information is intended for those who evaluate, recommend, or design new IT high performance architectures.

This white paper describes testing completed in February 2016.

Document purpose: The purpose of this document is to describe a Reference Configuration, highlighting recognizable benefits to technical audiences.

Introduction This Reference Configuration is one in a series of white papers that demonstrate the use of the HPE Synergy composable infrastructure to support enterprise applications. Composable infrastructure is designed around three core principles:

• A pool of resources including compute, storage and network that can be deployed, managed and reconfigured as business and application needs change.

• The ability to use templates or profiles to simply and quickly provision infrastructure resources in a repeatable and consistent manner.

• A unified API that provides access to all infrastructure components and hardware resources and allows for the management of hardware in an integrated manner.

This series of projects demonstrates the concepts and solution designs used to place applications such as Oracle Database, Microsoft® Exchange Server, SQL Server, and other applications on the HPE composable infrastructure pools of compute, storage and fabric.

Technical white paper Page 4

HPE Synergy for Oracle HPE Synergy offers a variety of capabilities to provide a better experience with Oracle Database server lifecycle management. The following criteria is used in choosing the infrastructure for database servers.

• High Performance

Databases are configured to support a variety of workloads. Infrastructure has to be set up to meet these workload’s performance needs. To process a large number of transactions, OLTP database servers must support a high number of Input/Output operations. HPE Synergy with its ability to scale the number of disk drives in the internal storage or with external SAN storage can meet the IOPS needs.

For those environments focusing on In-memory databases, the critical requirement is the high end-to-end memory access speeds and memory density. By using the latest Intel® processor technology, with up to 24 DIMMs per socket support, large databases can be stored in memory and performance targets can be achieved.

In OLAP configurations, bandwidth is the key requirement. With the midplane supporting multiple Tb/s, and support for multiple 40 Gb/s external ports, DAS as well as SAN performance can meet large OLAP performance needs.

With the supporting infrastructure for both OLAP and OLTP environments, one can cohost applications that need these two database technologies and can take advantage of the high performance infrastructure.

• Minimal downtime

Database servers are expected to be available all the time. HPE Synergy offers that reliability with its robust design – solid mechanical design, efficient electrical design and smart thermal and power management. The goal is not only to minimize planned downtime but also to ensure that the system is highly available even in the case of component failures.

HPE Synergy has redundant components – fabric, management modules and others, ensuring that the system is functional even when one of the components fails. During planned maintenance updates, HPE Synergy upgrades its infrastructure, including all the components, ensuring that the services are available without any disruption. The only time a system has to be booted is in those cases where an operating system driver update needs reboot.

In High Availability environments, updated compute modules can be added to a cluster so that the reboot happens while the cluster is running. Using this scenario, the only application interruption to service would happen during a switch event, which would shorten the time period for a service outage.

• Ease of management

HPE Synergy’s composable infrastructure offers compelling benefits for the database environment:

– Reduces overprovisioning of resources

The HPE Synergy 12000 Frame is flexible in supporting compute, storage and network resources. Users can add any combination of those resources depending on their needs. With HPE Synergy’s software defined intelligence, one can pick the right amount of resources optimized for the database workload and can deploy the needed resources only, i.e., the right amount of compute, storage and network.

– Faster deployment

Typically, once a first server is defined with the right set of resources, then additional servers are deployed with the same configuration. With a template optimized for a database workload defined, deploying the server is very fast with HPE Synergy Composer for infrastructure, and Insight Control Server Provisioning or Image Streamer for the upper stack. With all of these capabilities integrated, the deployment experience is very simple and you can start using the new infrastructure in minutes.

In the day-to-day management, administrators have to support their end users by adding new servers for scale-out performance or for temporary test environments. They may also update servers with a new database version for testing, upgrade the processing capability for scale-up performance, or update storage capacity as the database needs change. All of these activities are disruptive and need long lead times. With HPE Synergy’s composable infrastructure adding compute modules, upgrading from a two socket to four socket compute module or increasing storage or network capacity is simple and quick.

– Simplifies lifecycle management

HPE Synergy Composer offers appropriate tools to manage the infrastructure lifecycle management – through deployment, and on-going management and monitoring. With software defined intelligence, deployment is simple and quick. It offers a comprehensive view of all the

Technical white paper Page 5

resources and the ability to monitor and troubleshoot the infrastructure from a single console. Firmware and device drivers are integrated into a single package for all the components and updating these is automated, minimizing downtime due to human errors.

– Easy to integrate with the current environment

HPE Synergy offers a unified API for all the resources. Due to the simplicity and ability to address all the resources in the same way, developing scripts for various workflows is made easy. Now, integrating HPE Synergy with the current environment has become an easy task.

• Low TCO

HPE Synergy provides the ability to move an application’s personality from server to server quickly, seamlessly and easily. The ability to rapidly move applications means that an enterprise doesn’t need to acquire equipment specifically for peak utilization requirements, but rather flex the environment during times when the peak need is present. With the right provisioning of resources, capital expenses can be reduced with the initial purchase, as well as ongoing hardware purchases. Ease of management, and the ability to have an end-to-end view through the management console, reduces operational expenses.

With all these benefits from HPE Synergy and its ability to compose the infrastructure to meet various application needs, HPE Synergy provides the ideal platform for database servers and other applications.

HPE Synergy Composer To eliminate infrastructure complexity, HPE Synergy Composer powered by OneView automates the delivery and operation of IT services—transforming everyday management of compute, storage, and network resources in physical and virtual environments. HPE Synergy Composer improves IT administrator efficiency by converging management of HPE compute, storage, and networking resources. It speeds IT service roll-outs and helps actively prevent error-induced downtime through a template-based, software defined approach to management. HPE Synergy Composer also saves time by acting as an automation hub that performs infrastructure configuration and management tasks at the request of other applications.

HPE Synergy Composer reduces OPEX and improves agility, so you can free-up resources to focus on new initiatives that will help grow your business.

You can use HPE Synergy Composer to automate the deployment, update, and ongoing management of HPE Synergy components. The customizable HPE Synergy Composer dashboard provides an easy-to-understand summary/status of servers, storage pools, and enclosures. Color-coded icons tell you which systems are functioning properly and which ones need help—whether you manage five systems or 500.

• One platform manages HPE Synergy Compute Modules, storage modules and networking, and HPE 3PAR StoreServ storage.

• Smart Search instantly finds what you are looking for without forcing you to search through long and complicated tree views.

• 3D Power/Thermal Mapping provides intuitive power management.

• Pre-configured reports help catalogue inventory and alerts, facilitating asset management and creation of internal status reports to IT and business leadership.

• Email event notification alerts administrators of potential problems in real time.

Solution overview This white paper outlines the architecture and performance you can expect from a solution built on HPE Synergy Compute Modules and Storage Module running Oracle 12c and Red Hat® Enterprise Linux® 7.1.

The HPE Synergy 12000 Frame offers the following composable infrastructure for deploying Oracle:

• Two or four socket compute modules – Intel Xeon® E5 and E7 platforms

• HPE Synergy Network Interconnects. HPE Synergy offers many different network switch options. The HPE Virtual Connect SE 40Gb F8 Module for HPE Synergy was chosen for this set of tests.

• The HPE Synergy D3940 12Gb SAS Storage Module supports up to 40 hot-pluggable 12 Gb small form factor drives with dual port connectivity including traditional hard drives and solid state drives.

Technical white paper Page 6

Figure 1. HPE Synergy Compute Modules, left to right the two socket 480 Gen9, four socket 660 Gen9 and the four socket 680 Gen9

Figure 2. HPE Virtual Connect SE 40Gb F8 Module for HPE Synergy

Figure 3. HPE Synergy D3940 Storage Module

Technical white paper Page 7

The HPE Synergy 12000 Frame includes a comprehensive management environment running on a redundant pair of HPE Synergy Composer Modules powered by HPE OneView. Frame Link Modules connect up to 20 frames that define the management domain. The HPE Synergy Composer is an environment where all the components of a specific solution are defined.

The use of the HPE Synergy composable infrastructure for applications allows the deployment and management of a set of hardware and subsequent adjustment of the balance of compute, storage and fabric using HPE Synergy Composer in a simple and straightforward manner, by either licensing the desired feature or the installation of additional compute modules or storage modules and drives. The wire-once model combined with the ability to expand compute, fabric and storage gives the user the ability to maintain the balance of hardware needs as application requirements change over time, thus driving faster business results, more agile IT environments and reducing the cost and complexity to deploy and support applications running in support of the enterprise.

Solution components The HPE Synergy components used in this solution are based on a balanced architecture that uses components that fit within a single HPE Synergy 12000 Frame. The use of components that reside within the HPE Synergy Frame allow for a simplification of design by using the fewest number of components necessary while maximizing the composability within the HPE Synergy Frame to deliver a high performance Oracle environment. The use of HPE Synergy’s unique internal storage capability allows it to meet the needs of a high performance Oracle environment without an external storage requirement.

The HPE Synergy 12000 Frame had the following components:

• 1 X HPE Synergy 480 Gen9. This is a two socket compute module and was populated with 16-core processors for a total of 32 cores.

• 1 X HPE Synergy 660 Gen9. This is a four socket compute module and it was populated with 20-core processors for a total of 80 cores. We used this compute module as a target to move our HPE Synergy 480 Gen9 environments when we needed additional throughput provided by the additional sockets and cores.

• 1 X HPE Synergy D3940 Storage Module that contained four SSDs and 34 spinning disks, configured as shown in Figure 4.

FrontPanel

Bay16

Bay6

Bay7

Bay1

ApplianceBay 2

ApplianceBay 1

Synergy12000Frame

UID

OneViewUID

Active

Power

Synergy Composer

UID

Synergy D3940Storage Module

2

4

1

3

UID

Synergy660

Gen9

OneViewUID

Active

Power

Synergy Composer

HPE Synergy 480 Gen9HPE Synergy D3940o 4 X 200GB SSD RAID-5o 34 X 450GB 15K RPM drives

• 2 X RAID-1 for OS• 16 X RAID-1 for Redo • 16 X Raid-1 for Undo

HPE Synergy 660 Gen9HPE Synergy Composer

HPE Synergy 12000

UID

Synergy480

Gen9

Figure 4. Logical diagram of HPE Synergy environment

Technical white paper Page 8

4 X 200GB SSDs• 1 X RAID-5 LUN• Tablespaces and Indexes

16 X 450GB 15K RPM SAS• 8 X RAID-1 LUNs• Redo Logs

16 X 450GB 15K RPM SAS• 8 X RAID-1 LUNs• Undo Tablespace

2 X 450GB 15K RPM SAS• 1 X RAID-1 LUN• OS Boot

Figure 5. Logical diagram of D3940 storage layout

Software • Red Hat Enterprise Linux version 7.1

• Oracle 12c Enterprise Edition

Best practices and configuration guidance for the Oracle Database solution HPE Synergy Compute Module BIOS • Hyper-Threading—Enabled

• Intel Turbo Boost—Enabled

• HPE Power Profile—Maximum Performance

Storage configuration best practices – HPE Synergy D3940 • Database, tablespaces and indexes on SSD configured in one RAID-5 LUN

• Redo logs isolated to their own RAID-1 spinning media LUNs

• Undo tablespace isolated to its own RAID-1 spinning media LUNs

Technical white paper Page 9

Oracle configuration best practices For specific Oracle database parameter settings, see Appendix B and C.

• Disable RHEL automatic NUMA balancing (see Appendix D).

• Disable automatic memory management if applicable.

• Set buffer cache memory size large enough per your implementation to avoid physical reads.

• Create two large redo log file spaces of 450GB each to minimize log file switching and reduce log file waits.1

• Create an undo tablespace of 512GB.2

• Configure huge pages (see Appendix D) and set Oracle to only use huge pages.

Capacity and sizing One of the more compelling features of HPE Synergy is frictionless movement of resources from one application to another. When additional resources are required, the profile of a two socket compute module can be moved to a four socket compute module to easily configure more compute capacity. This allows a customer to provide the right sized server to the Oracle Database and then when peak amounts of resources are required (perhaps at the end of the month or year), they can apply the same server profile to a more robust compute module and have the resources needed. When the peak resource requirement has passed, simply move the profile back to the original compute module and return to a normal run rate. There is no need to over size or over provision compute or storage resources for the worst case scenario.

This feature also opens up a number of options. As an example, you could have a primary Oracle Database server that replicates to a read-only database that is used for reporting or decision support during the day. Then when it is backup time, you could apply a profile for a server specifically tuned to perform backups or even shift the storage to another backup-specific server. When the backup is complete, you simply shift back to the original read-only database configuration and continue on with processing.

Workload description The Oracle workload was tested using HammerDB, an open-source tool. The tool implements an OLTP-type workload (60 percent read and 40 percent write) with small I/O sizes of a random nature. The transaction results have been normalized and are used to compare test configurations. Other metrics measured during the workload come from the operating system and/or standard Oracle Automatic Workload Repository (AWR) statistics reports.

The OLTP test, performed on a 500GB database, was both highly CPU and moderately I/O intensive. The environment was tuned for maximum user transactions. After the database was tuned, the transactions were recorded at different connection levels. Because customer workloads vary so much in characteristics, the measurement was made with a focus on maximum transactions.

Oracle Enterprise Database version 12.1.0.1 was used in this test configuration.

The databases used several different Oracle Automatic Storage Management (ASM) disk groups with a combination of RAID-5 and multiple RAID-1 LUNs. The single RAID-5 SSD LUN was used for tablespaces and indexes. Eight RAID-1 LUNs were used for the redo logs and another eight RAID-1 LUNs were used for the undo tablespace.

We used several different Oracle connection counts for our tests, and found the optimal number to be 150 connections for the two socket compute modules. The optimal number of connections was twice that number on the four socket compute module because it had more memory and more than double the number of cores.

1 During our testing, we used redo log file spaces of 350GB, 400GB and 450GB. We found no performance difference. It is, however, important that the size and quantity of redo log

file spaces be large enough so that a constraint is not encountered when closing one redo log and opening another, such as the new redo log has not had enough time to have been flushed since it was last used.

2 During our testing we used undo tablespace sizes of 300GB and 512GB. We saw no performance difference as long as the size was sufficiently large enough that it didn’t cause the queries to throw errors.

Technical white paper Page 10

Workload results We tested an HPE Synergy 480 Gen9, two socket compute module and compared the results with those delivered by an HPE Synergy 660 Gen9, four socket compute module.

The HPE Synergy 480 Gen9 two socket compute module had 32 cores and 256GB of memory. The HPE Synergy 660 Gen9, four socket compute module had 80 cores and 1TB of memory.

Both the HPE Synergy 480 Gen9 and HPE Synergy 660 Gen9 were tested with the same storage configuration, in order to demonstrate the performance improvement achieved when replacing the HPE Synergy 480 Gen9 with the HPE Synergy 660 Gen9.

The following graph shows the results from the tests. The number of connected users is the count of users that drove the test. Each user had no think time and as a result, represented hundreds of actual users. The results have been normalized such that the 25 User result on the HPE Synergy 480 Gen9 Compute Module was set to 100%. All other results are relative to the initial result.

As you can see from the graph, HPE Synergy provided a good scaling factor when moving from a two socket compute module to a four socket compute module.

050

100150200250300350400

25 Users 50 Users 75 Users 100 Users 150 Users 200 Users 250 Users

Perc

enta

ge

Number of Oracle Connections

Performance results using HPE D3940 internal SAS Storage

SY480 SY660

Technical white paper Page 11

The following graph represents the transactional latency incurred during the test run.

Analysis and recommendations HPE Synergy is a new computing paradigm, and a new paradigm introduces options that were heretofore unavailable.

The testing has demonstrated that an organization does not have to purchase compute and storage resources based on a worst case scenario and leave those resources underutilized or lying idle. Being able to quickly and easily bring additional compute and storage options to bear, allows an organization to right-size the environment for the typical deployment scenario, while being able to flex the environment when additional resources are required to fulfil the customer’s needs.

Being able to change the personality of a server on the fly by applying different profiles at the touch of a button, means that each server profile can be specifically tuned for its unique job requirements. There is no longer the requirement to make compromises to satisfy two different workloads as long as those workloads are not concurrent.

Additionally, being able to tailor a server profile to the unique requirements and then being able to apply that profile to multiple compute modules means that we could add or delete Oracle RAC servers in minutes rather than hours or days. This allows the organization to be able to flex the environment as the needs of the organization change.

As our performance results demonstrate, HPE Synergy is a highly performant, highly scalable, highly available environment that will perform well in any Oracle environment, even if the business is stable, and as a result Hewlett Packard Enterprise recommends HPE Synergy in those environments. Hewlett Packard Enterprise also recommends HPE Synergy for Oracle environments where business needs fluctuate.

Summary The deployment of the Oracle Database on the HPE Synergy composable infrastructure provides options that have not existed before now, with the ability to use large quantities of direct attached storage within the HPE Synergy 12000 Frame as well as more traditional array-based storage. The use of integrated networking interconnect modules allows the deployment of a simple networking model with a reduced number of components.

The composable infrastructure allows the deployment of a modular design that can be deployed quickly and modified easily as needs change due to new application requirements or a change in user demands or business needs.

0

1

2

3

4

5

6

25 Users 50 Users 75 Users 100 Users 150 Users 200 Users 250 Users

Milli

seco

nds

Number of Oracle Connections

Transaction Latency

SY480 SY660

Technical white paper Page 12

Implementing a proof-of-concept As a matter of best practice for all deployments, HPE recommends implementing a proof-of-concept using a test environment that matches as closely as possible the planned production environment. In this way, appropriate performance and scalability characterizations can be obtained. For help with a proof-of-concept, contact an HPE Services representative (hpe.com/us/en/services/consulting.html) or your HPE partner.

Appendix A: Bill of materials

Note The bill of materials does not include complete support options or rack and power requirements. For questions regarding ordering, please consult with your HPE Reseller or HPE Sales Representative for more details. hpe.com/us/en/services/consulting.html

Table 1. Bill of materials

QTY DESCRIPTION

Rack and Network Infrastructure

1 HPE 642 1200 mm Shock Intelligent Rack

1 HPE 42U 1200mm Side Panel Kit

1 HPE Air Flow Optimization Kit

3 HPE 1U Black Universal 10-pk Filler Panel

HPE Synergy Frame Components

1 HPE Synergy 12000 Configure-to-order Frame with 1x Frame Link Module 10x Fans

1 HPE 6X 2650W AC Titanium Hot Plug FIO Power Supply Kit

1 HPE Synergy Composer

1 HPE VC SE 40Gb F8 Module

2 HPE Synergy 12Gb SAS Connection Module with 12 Internal Ports

HPE Synergy Compute Module Components

1 HPE Synergy 480 Gen9 Configure-to-order Compute Module

2 HPE Synergy 480 Gen9 Intel Xeon 16-core processors

16 HPE 16GB (1x16GB) Dual Rank x4 DDR4-2133 RDIMMs

1 HPE Synergy Smart Array P542D Controller

1 HPE Synergy 3820C 10/20Gb Converged Network Adapter

1 HPE Synergy 660 Gen9 Configure-to-order Compute Module

4 HPE Synergy 660 Gen9 Intel Xeon 20-core processors

32 HPE 32GB Dual Rank DDR4-2133 RDIMMs

1 HPE Synergy Smart Array P542D Controller

1 HPE Synergy 3820C 10/20Gb Converged Network Adapter

HPE Synergy Storage Module Components

1 HPE Synergy D3940 Storage Module

1 HPE Synergy D3940 Redundant I/O Adapter

4 200GB SSD

34 450GB 15K RPM Disk Drives

Technical white paper Page 13

Appendix B: Oracle configuration parameters – HPE Synergy 480 Gen9 pga_aggregate_target=51546M processes=1500 result_cache_max_size=794304K sga_target=155136M _high_priority_processes='VKTM*|LG*' lock_sga=TRUE use_large_pages='ONLY' _max_outstanding_log_writes=4

Appendix C: Oracle configuration parameters – HPE Synergy 660 Gen9 pga_aggregate_target=103173M processes=3000 result_cache_max_size=1585984K sga_target=309760M _high_priority_processes='VKTM*|LG*' lock_sga=TRUE use_large_pages='ONLY' _max_outstanding_log_writes=4

Appendix D: Linux kernel configuration kernel.sem = 250 32000 100 128 kernel.shmall = 4294967295 kernel.shmmax = 332859965440 fs.file-max = 6815744 kernel.shmmni = 4096 fs.aio-max-nr = 1048576 net.ipv4.ip_local_port_range = 9000 65500 net.core.rmem_default = 262144 net.core.rmem_max = 4194304 net.core.wmem_default = 262144 net.core.wmem_max = 1048586 vm.nr_hugepages = 77572 vm.hugetlb_shm_group = 1003 kernel.numa_balancing=0

Notes 1. The vm.nr_hugepages is dependent on the amount of memory installed in the server. We had 256GB in the HPE Synergy 480 Gen9, so we

set it to 77572. However, when we had 1TB of memory in the HPE Synergy 660 Gen9, we set it to 155144. This is required by Oracle if you wish to set the sga_target higher, which we did when we were running more connected users and higher throughput numbers.

2. For RHEL 7, automatic NUMA balancing should be disabled (by setting kernel.numa_balancing=0) for optimal Oracle performance. This resulted in a significant performance improvement for our testing.

Technical white paper Page 14

Appendix E: D3940 udev rules For D3940 storage configurations, a udev rules file /etc/udev/rules.d/99-oracleasm.rules was created to set the required ownership of the Oracle ASM LUNs:

ACTION=="add|change", KERNEL=="sdb",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdc",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdd",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sde",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdf",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdg",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdh",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdi",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdj",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdk",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdl",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdm",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdn",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdo",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdp",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdq",OWNER="oracle",GROUP="dba",MODE="0660" ACTION=="add|change", KERNEL=="sdr",OWNER="oracle",GROUP="dba",MODE="0660"

Technical white paper Page 15

Sign up for updates

Rate this document

© Copyright 2016 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for HPE products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial errors or omissions contained herein.

Oracle is a registered trademark of Oracle and/or its affiliates. Microsoft is either a registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. Intel and Xeon are trademarks of Intel Corporation in the U.S. and other countries. Red Hat is a registered trademark of Red Hat, Inc. in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

4AA6-4732ENW, March 2016

Resources and additional links HPE & Oracle Alliance http://h22168.www2.hpe.com/us/en/partners/oracle/

HPE & Oracle Alliance Technical page http://h17007.www1.hpe.com/us/en/enterprise/converged-infrastructure/info-library/index.aspx?app=oracle

HPE Synergy hpe.com/info/synergy

HPE Composable Infrastructure hpe.com/info/composableinfrastructure

HPE Enterprise Information Library hpe.com/info/convergedinfrastructure

HPE Technology Consulting Services hpe.com/us/en/services/consulting.html

To help us improve our documents, please provide feedback at hpe.com/contact/feedback.