enterprise hybrid cloud 4.1 - dell emc us · solution overview ... patching oracle in enterprise...

[DOCUMENT TYPE]

ENTERPRISE HYBRID CLOUD 4.1.1

Oracle Database as a Service

March 2017

Abstract

This solution guide describes how to quickly and effectively provision, manage, patch,

and migrate Oracle Database 12c as a service on Enterprise Hybrid Cloud. This

includes single-instance and RAC configurations.

H15813R

This document is not intended for audiences in China, Hong Kong, and Taiwan.

Copyright

2 Enterprise Hybrid Cloud 4.1.1 Oracle Database as a Service Solution Guide

The information in this publication is provided as is. Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.

Use, copying, and distribution of any software described in this publication requires an applicable software license.

Copyright © 2017 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA March 2017 Solution Guide H15813R.

Dell Inc. believes the information in this document is accurate as of its publication date. The information is subject to change without notice.

Contents

3 Enterprise Hybrid Cloud 4.1.1 Oracle Database as a Service

Solution Guide

Contents

Chapter 1 Executive Summary 5

Business case ....................................................................................................... 6

Solution overview .................................................................................................. 6

Document purpose ................................................................................................ 8

Audience ............................................................................................................... 8

Essential reading .................................................................................................. 8

We value your feedback ........................................................................................ 8

Chapter 2 Solution Architecture 9

Overview ............................................................................................................. 10

Key components ................................................................................................. 11

Software resources ............................................................................................. 12

Chapter 3 Provisioning Oracle DBaaS 14

Overview ............................................................................................................. 15

Preparing the Oracle DBaaS service ................................................................... 15

Deploying Oracle DBaaS .................................................................................... 15

Chapter 4 Oracle DBaaS Maintenance Operations 20

Overview ............................................................................................................. 21

Adding storage capacity for Oracle DBaaS ......................................................... 21

Adding and removing Oracle Enterprise Manager monitoring targets .................. 26

Adding vCPU to a virtual machine ....................................................................... 27

Adding memory to a virtual machine ................................................................... 28

Chapter 5 Monitoring Oracle DBaaS 29

Overview ............................................................................................................. 30

Oracle Enterprise Manager Database Express 12c ............................................. 30

Oracle Enterprise Manager Cloud Control 12c .................................................... 30

vRealize Operations Manager ............................................................................. 31

Chapter 6 PDB Migration 34

Overview ............................................................................................................. 35

PDB copy preparation ......................................................................................... 36

PDB migration without data ................................................................................. 37

PDB migration with data ...................................................................................... 39

Contents


Chapter 7 Automated Oracle Patching 42

Overview ............................................................................................................. 43

Patching mechanisms ......................................................................................... 43

Patching Oracle in Enterprise Hybrid Cloud ........................................................ 43

Chapter 8 Conclusion 45

Summary ............................................................................................................ 46

Features .............................................................................................................. 46

Chapter 9 References 48

Enterprise Hybrid Cloud documentation .............................................................. 49

VMware documentation ...................................................................................... 49

Oracle documentation ......................................................................................... 49

Other documentation ........................................................................................... 49

Chapter 1: Executive Summary


Solution Guide

Chapter 1 Executive Summary

This chapter presents the following topics:

Business case ..................................................................................................... 6

Solution overview ............................................................................................... 6

Document purpose ............................................................................................. 8

Audience .............................................................................................................. 8

Essential reading ................................................................................................ 8

We value your feedback ..................................................................................... 8



Business case

While many organizations have successfully introduced virtualization as a core technology

within their data centers, the benefits have largely been restricted to the IT infrastructure.

Business units, application owners, end users, developers, and database administrators

(DBAs) have yet to experience the full benefits of virtualization, including increased agility,

mobility, and control.

These organizations must also manage a growing and fragmented database

infrastructure. In addition to supporting an increased number of production databases,

DBAs and development teams must be able to create and copy multiple database

environments to meet business needs such as development and testing, reporting, and

troubleshooting.

Public cloud providers have built technology and business models to meet end-user

needs for agility and control. Organizations are now under pressure to provide the same

service levels within the secure and compliant confines of the on-premises data center. As

a result, IT departments need to deliver cost-effective alternatives to public clouds that do

not compromise enterprise requirements for data protection, disaster recovery, and

guaranteed service levels.

Traditional on-premises infrastructure gives IT teams more control, but provisioning of

database environments can take weeks. Public clouds speed up provisioning, but do not

always meet business requirements for data protection, disaster recovery, and service

levels. For this Oracle database-as-a-service (DBaaS) solution, Enterprise Hybrid Cloud

4.1.1 provides on-premises cloud services to meet these business requirements.

Solution overview

This Oracle DBaaS solution enables customers to use Enterprise Hybrid Cloud to perform

the following tasks:

Self-provision Oracle DBaaS on Enterprise Hybrid Cloud as:

A single-instance Oracle Database 12c on Oracle Automatic Storage Management (ASM)

A single-instance Oracle Database 12c on file system storage

An Oracle Database 12c with Oracle Real Application Clusters (RAC) on Oracle ASM

This creates an Oracle 12c container database (CDB) with an optional pluggable

database (PDB) in a single-tenant configuration.

Maintenance operations:

Add disks to Oracle ASM disk groups for both single-instance and RAC databases

Add disks to file system-based single-instance Oracle databases

Add vCPU to a virtual machine (VM)

Add memory to a virtual machine

Add or removing Oracle Enterprise Manager monitoring



Solution Guide

Monitor the complete Oracle DBaaS solution using Oracle Enterprise Manager Cloud Control 12c (OEM) and VMware vRealize Operations Manager

Migrate a PDB between Oracle 12c CDBs, with or without data

Automated patching of Oracle grid infrastructure and database

Enterprise Hybrid Cloud is an enterprise-class, multitenant, multisite, scalable platform

enabling IT organizations to deploy an on-premises hybrid cloud that delivers

infrastructure as a service (IaaS) to their business quickly. It also provides a framework

and foundation for add-on modules such as application services, database as a service

(DBaaS), platform as a service (PaaS), and cloud brokering.

This solution uses VMware vRealize Automation and VMware vRealize Orchestrator. It

provides configurable workflows to enable the automated deployment and management of

Oracle DBaaS.

Enterprise Hybrid Cloud is designed to deliver multitenancy and secure separation of

resources. Cloud computing requires the ability to isolate resources and deliver secure

access. Enterprise Hybrid Cloud is structured so that, if required, each tenant can be:

Logically separated using vRealize Automation business groups. In this solution, the Oracle business group is assigned dedicated compute, storage, and network resources for software license compliance.

Physically separated in a dedicated Workload Pod. In this solution, Oracle is restricted to dedicated VMware vSphere clusters with High Availability (vSphere HA)/Distributed Resource Scheduler (DRS). The Workload Pod can have its own servers, network, and storage resources, separate from all other tenants.

These dedicated, physically separate, clustered Workload Pods are mapped to the

compute resource available to the vRealize Automation business group through a

VMware vCenter endpoint (either dedicated or shared). This improves service availability,

and helps ensure software license compliance by restricting where the virtual machines

and software are running or installed.

vRealize Orchestrator integrates with vRealize Automation and enables process

automation when interfacing with third-party systems. Further, vRealize Orchestrator

workflows can be deployed as custom services or actions in vRealize Automation to

enable complex deployment and maintenance operations for Oracle DBaaS.

Oracle Database 12c delivers industry-leading performance, scalability, security, and

reliability on a choice of clustered or single servers running Microsoft Windows, Linux, or

UNIX. It introduces a new architecture, Oracle Multitenant, where one or more PDBs are

created inside a CDB.

The multitenant architecture supports the following configurations:

A single-tenant configuration, with one PDB plugged into a CDB, is available for no extra cost in all editions.

A multitenant option for up to 252 PDBs per CDB is an extra-cost option of Oracle 12c Enterprise Edition.

Enterprise

Hybrid Cloud

Oracle Database



Oracle Grid Infrastructure combines Oracle ASM and Oracle Clusterware into a single set

of binaries, separate from the database software. This provides all the cluster and storage

services required to run an Oracle RAC or single-instance database.

This solution uses the ASMLib support library for Oracle ASM running on Oracle Linux 6.x

using the Unbreakable Enterprise Kernel (UEK) Release 3.

Document purpose

This guide describes a solution that allows you to quickly and effectively provision Oracle

DBaaS on Enterprise Hybrid Cloud. It introduces the main features and functionality of the

solution and describes the architecture and key components required to provision,

manage, and monitor Oracle DBaaS on Enterprise Hybrid Cloud.

Audience

This guide is intended for Dell EMC customers and qualified Dell EMC partners. The

guide assumes that users who intend to deploy this Oracle DBaaS solution have the

necessary training and background to install and configure an end-user computing

solution based on Enterprise Hybrid Cloud and Oracle Database 12c. Users should also

be familiar with the infrastructure and database security policies of the customer

installation.

Essential reading

The following guides provide further information about various aspects of Enterprise

Hybrid Cloud:

Enterprise Hybrid Cloud 4.1.1: Administration Guide

Enterprise Hybrid Cloud 4.1.1: Concepts and Architecture Guide

Enterprise Hybrid Cloud 4.1.1: Reference Architecture Guide

Enterprise Hybrid Cloud 4.1.1: Security Management Guide

Enterprise Hybrid Cloud 4.1.1: Infrastructure and Operations Management Guide

Enterprise Hybrid Cloud 4.1.1 Availability and Data Protection for Oracle Database Solution Guide

We value your feedback

Dell EMC and the authors of this document welcome your feedback on the solution and

the solution documentation. Contact [email protected] with your

comments.

Authors: Allan Robertson, Ed Spaenij, Tom Hudgins, Liam Buckley, Reed Tucker

Oracle Grid

Infrastructure

mailto:[email protected]?subject=Feedback:%20EHC%204.1.1%20Oracle%20DBaaS%20Solution%20Guide

Chapter 2: Solution Architecture


Solution Guide

Chapter 2 Solution Architecture


Overview ............................................................................................................ 10

Key components ............................................................................................... 11

Software resources ........................................................................................... 12



Overview

This Oracle DBaaS solution provides the following application-specific functions:

Automated deployment and management of Oracle Database 12c

Single-instance Oracle Database with Oracle ASM

Single-instance Oracle Database on file system

Oracle Database with Oracle RAC and ASM

Oracle DBaaS maintenance operations

Add capacity to Oracle Database

Add or remove Oracle Enterprise Manager 12c Agent

Hot-add vCPU to an Oracle Server

Hot-add memory to an Oracle Server

Oracle DBaaS monitoring

Oracle Enterprise Manager Database Express 12c

Oracle Enterprise Manager Cloud Control 12c

vRealize Operations Manager

PDB migration

Copy PDB with or without data between Oracle CDBs

Automated patching of Oracle grid infrastructure and database

This Oracle DBaaS solution has been built and validated on a number of iterations and

configurations of Enterprise Hybrid Cloud. The underlying physical environment is

abstracted from the application layer by virtual and software-defined components. The

architecture shown in Figure 1 is representative of the architecture and environments

where the Oracle DBaaS solution is deployed. It shows the main components in the

Automation Pod that are relevant to this solution.



Solution Guide

Figure 1. Enterprise Hybrid Cloud reference architecture with Oracle Workload Pod

Figure 1 also shows the Oracle Workload Pod, which is a dedicated VMware ESXi cluster

with vSphere HA, and with its own compute, storage, and network resources. This

provides improved service availability and restricts where the virtual machines and

software are running or installed, which in turn ensures software license compliance.

vRealize Orchestrator contains a workflow library and a workflow engine to create and run

workflows that automate orchestration processes. You run workflows on the objects of

different technologies that vRealize Orchestrator accesses through a series of plug-ins.

vRealize Orchestrator also presents an open architecture to allow you to plug in external

third-party applications to the orchestration software. The resulting extensibility is known

as Anything-as-a-Service (XaaS). You can access vRealize Orchestrator, the vRealize

Orchestrator workflows, and the objects that vRealize Orchestrator exposes through its

client interface, or through Web services.

This solution leverages these capabilities to provide Oracle DBaaS.

Key components

The following components of Enterprise Hybrid Cloud are essential in this Oracle DBaaS

solution:

VMware ESXi and VMware vCenter Server

VMware vRealize Suite:

VMware vRealize Automation

VMware vRealize Operations Manager

VMware vRealize Orchestrator



For this solution, when used with Oracle Database 12c, these VMware vRealize

components deliver the following functionality:

Provisioning of Oracle DBaaS—RAC or single-instance—using vRealize Orchestrator packages as XaaS blueprints in the vRealize Automation portal

Service maintenance operations using vRealize Orchestrator packages as service blueprints and resource actions in the vRealize Automation portal

Optional monitoring of Oracle DBaaS using OEM Cloud Control 12c Release 2, which can be integrated with vRealize Operations Manager using a third-party plug-in for full stack monitoring

Note: For a full overview of components, refer to the Enterprise Hybrid Cloud 4.1.1: Reference

Architecture Guide.

Software resources

Table 1 lists the application software components and supporting services used in this

Oracle solution for Enterprise Hybrid Cloud. For a complete list of Enterprise Hybrid Cloud

software requirements, refer to the relevant Dell EMC E-Lab EMC Simple Support Matrix

at elabnavigator.emc.com.

Table 1. Software resources

Software Version Description

Operating system software

Oracle Linux Server 6.6

UEK3

Oracle Linux is a Linux distribution based on Red Hat Enterprise Linux (RHEL), repackaged and distributed by Oracle.

Application software

Oracle Database 12c Release 1 12.1.0.2.0 Oracle Database software including Oracle Enterprise Manager Database Express 12c

Oracle Grid Infrastructure 12c Release 1

12.1.0.2.0 Oracle Clusterware is shipped with Oracle Grid Infrastructure, which is a suite of software packages that includes Oracle ASM for databases. Oracle Clusterware is a generic, general purpose clustering solution for all applications.

Application monitoring software


12.1.0.4 Oracle integrated Enterprise IT Management solution

Third party management software

https://elabnavigator.emc.com/



Solution Guide

Software Version Description

vRealize Operations Management Pack for Oracle Enterprise Manager

6.0.1.0 This management pack, available from Blue Medora, extends vRealize Operations Manager by integrating with Oracle Enterprise Manager and providing comprehensive visibility and insights into the health, capacity, and performance of Oracle Databases, Oracle Middleware, and Oracle business critical applications. It helps to detect capacity and performance issues so they can be corrected before they cause a major impact.

Note: This solution uses Oracle Linux Server 6.6, which is supported by both VMware and Oracle.

Chapter 3: Provisioning Oracle DBaaS


Chapter 3 Provisioning Oracle DBaaS


Overview ............................................................................................................ 15

Preparing the Oracle DBaaS service ............................................................... 15

Deploying Oracle DBaaS .................................................................................. 15



Solution Guide

Overview

Enterprise Hybrid Cloud provides a foundation for the successful and consistent

deployment of Oracle DBaaS. This chapter describes the high-level process and

methodology required to successfully deploy the applications by using vRealize

Orchestrator with the vRealize Automation Service Catalog and the Enterprise Hybrid

Cloud self-service portal. The Oracle DBaaS solution delivers a fully automated product to

install and configure:

Single-instance Oracle Database with Oracle ASM

Single-instance Oracle Database on file system

Oracle Database with Oracle RAC and Oracle ASM

Preparing the Oracle DBaaS service

Before provisioning a VMware virtual machine with an Oracle Database from the vRealize

Automation Service Catalog, an Enterprise Hybrid Cloud administrator configures storage

policies, default disk sizes, and other configuration settings that are unique to each

Enterprise Hybrid Cloud environment.

Storage policies provide the means for an Enterprise Hybrid Cloud administrator to

classify different types of storage based on characteristics such as performance or

protection. For example, a Gold storage policy might provide higher performance than a

Silver storage policy. After the storage policies are configured, the end-user can select a

particular storage policy when requesting an Oracle service.

A database consists of several data groups: for example, DATA, REDO, and FRA. Each

data group has a number of disks of a certain size. The solution provides configuration

options to allow the Enterprise Hybrid Cloud administrator to control the number and size

of these disks, based on the requested database size. If the chosen storage type is ASM,

then the disks are Oracle ASM disks. If the storage type is file system, then the disks are

LVM Logical Volumes.

The solution provides a number of other configuration options that are used to tie the

solution to the current environment.

When the Enterprise Hybrid Cloud administrator has configured the Oracle DBaaS

solution, it is ready for end users to deploy the Oracle Database service.

Deploying Oracle DBaaS

Deploying an Oracle database server involves many steps. Performing these steps

reliably and repeatedly is a challenge. The process is even more involved if a RAC

configuration is required. This solution automates these steps so that users can easily

request an Oracle database server–either single-instance or RAC–with just a few mouse

clicks.

Storage policies

Disk sizing

Other system

settings



Figure 2 shows an Oracle DBaaS Request Form that has been requested from the service

catalog. In this example, the user has requested a 200 GB Oracle 12c CDB with PDB,

deployed on a two-node RAC on Oracle ASM. In Figure 3, the user has requested the

same options but deployed a single-instance Oracle Database on file system.

Figure 2. Deployment request for a 2-node Oracle RAC

Figure 3. Deployment request for a single-instance Oracle Database server

The automated Oracle DBaaS provisioning process includes the following steps, all driven

from vRealize Orchestrator:

1. Collect request inputs.

The service collects inputs from the user that will drive the installation and

configuration of the Oracle Database service.

Oracle DBaaS deployment inputs include:



Solution Guide

System or cluster (RAC) name

Requested storage space (GB)

Passwords for the Oracle and grid users

Set up automatic backup? – Yes/No

Storage policy

Storage type – ASM/FS

Is this a RAC cluster – if storage type ASM was selected? – Yes/No

Number of nodes – if RAC

Create a PDB? – Yes/No

PDB name, if PDB is requested

Protect the VM (with RP4VM)? – if single-instance – Yes/No

Email address for notification

This user input controls the setup of the Oracle DBaaS service in the subsequent

steps.

2. Provision virtual machines.

A virtual machine is cloned from the blueprint template by requesting the

published blueprint from the vRealize Automation Service Catalog.

If this is an Oracle RAC deployment, the required number of virtual machines is

cloned based on the number of requested nodes.

3. Create database storage.

The storage policy selected dictates which vCenter Server datastores are

allocated to the system. Using this mapping along with the requested storage

size, virtual disks are created for each data group–DATA, REDO, and FRA–

independent of storage type. For a RAC deployment, the additional disk group

CRS is created. In a RAC deployment, the virtual disks are created on the first

node of the cluster as “multi-writer” and are then shared with the other nodes of

the cluster.

All disk groups are configured to have one disk controller, except the DATA disk

group, which is configured to have two controllers. The DATA disks are balanced

over the two disk controllers.

For each disk group, the solution calculates the required size and number of disks

based on the overall database size.

4. Install Oracle Grid software.

Oracle Grid software provides the platform for the single-instance restart and the

RAC clustering environment.

If the chosen storage type is file system, the disks created in the previous step are

formatted and added as logical volumes in a volume group in the Logical Volume

Manager.

If the chosen storage type is ASM, the disks created in the previous step are

formatted and labeled for their respective ASM disk group. In a RAC deployment,



the disks are scanned on the other nodes so that their ASM instances can see

them as well.

The grid software is then installed and configured, which includes running post-

installation scripts as the root user.

5. Install Oracle Database software.

The Oracle Database software is installed next and configured to use the

provisioned disk groups. Post-installation root scripts are also run to complete the

configuration.

6. Create database.

A CDB is created after the database software has been installed. If, in the

request, the user chose to create a PDB, then it is created inside the CDB.

7. Enable local monitoring with Oracle 12c EM Express.

8. Enable data protection.

If the user set up Automatic Backup in step 1, the Oracle system will be added to

the default backup schedule in Dell EMC Avamar.

If the user chose protection by RecoverPoint for Virtual Machines, the Oracle

System will be added to a consistency group in RP4VMs.

9. Notify the user.

When the service is ready for use, the user receives an email with the

configuration details. For example:

System Information:

Cluster Name: devcluster Number of Nodes: 2 DB Size: 200 GB Storage Policy: Silver Storage Type: Oracle ASM SCAN Name: devcluster-scan SCAN IP: 1.2.3.210 SCAN IP: 1.2.3.213 Domain Name: company.com Node 1: ora-125 Public IP: 1.2.3.207 Public VIP: 1.2.3.219 Private IP: 192.168.1.3 Node 2: ora-124 Public IP: 1.2.3.205 Public VIP: 1.2.3.220 Private IP: 192.168.1.2 GRID_BASE: /u01/app/grid GRID_HOME: /u01/app/12.1.0/grid



Solution Guide

ORACLE_BASE: /u01/app/oracle ORACLE_HOME: /u01/app/oracle/product/12.1.0/dbhome_1 CDB Name: devcluster PDB Name: salesdb

Chapter 4: Oracle DBaaS Maintenance Operations


Chapter 4 Oracle DBaaS Maintenance Operations


Overview ............................................................................................................ 21

Adding storage capacity for Oracle DBaaS ..................................................... 21

Adding and removing Oracle Enterprise Manager monitoring targets ......... 26

Adding vCPU to a virtual machine ................................................................... 27

Adding memory to a virtual machine ............................................................... 28



Solution Guide

Overview

After the Oracle Database service has been provisioned, environment and service

changes are sometimes required. These activities, sometimes known as Day 2

operations, include routine maintenance tasks and changes to the virtual infrastructure.

These activities can be as simple as restarting the virtual machine, but they might also

include changes that can affect the availability or cost of the service, such as adding

vCPU, memory, or disks.

You can run or schedule all these machine actions from the Items tab in vRealize

Automation, assuming that the correct entitlements have been assigned. If an approval

policy has been created against a specific action, then that change is not applied until an

approver has authorized the change.

Using vRealize Automation Advanced Services, you can deploy customized vRealize

Orchestrator workflows as resource actions. These resource actions extend the

functionality of the standard machine actions to deliver complex automated processes

against the deployed virtual machine.

This solution uses vRealize Orchestrator workflows, configured as resource actions, to

provide the following capabilities:

Adding storage capacity

Adding or removing Oracle Enterprise Manager monitoring

Hot-adding vCPU to a virtual machine

Hot-adding memory to a virtual machine

Adding storage capacity for Oracle DBaaS

For this solution, you can add new disks for single-instance databases or for RAC

database deployments. If the database is running on ASM, add the disks to the selected

ASM disk group, which increases the capacity of that disk group. If the database is

running on the file system, add the disks as physical volumes to the logical volume that

stores the selected data type.

For this solution, the term “data group” is used to describe either the ASM disk group or

LVM volume group that stores a specific type of database data (DATA, REDO, FRA).

Manually adding storage to a database is not straightforward. Adding disks to an existing

ASM disk group involves a number of steps using different tools and commands, as

follows:

1. Provision new virtual disks to the virtual machine (the first node in the case of RAC). Log in to vCenter Server and create virtual disks on the datastore that corresponds to the disk group being modified. Create “thick” (eager zero) disks and, in the case of RAC, enable them as multi-writer.

2. Format and label the new disks. When the disks have been provisioned, log in to the virtual machine as root, identify the newly added disks, and format and partition them. Then label the disks properly so that they can be discovered as candidate disks by ASM.



3. Scan the disks on other RAC nodes. In the case of a RAC deployment, the ASM driver on each node must scan the newly formatted and labeled disks so that they are visible to the ASM instance.

4. Add the new disks to the designated ASM disk group by running a command as the grid user.

Similar steps are required when adding disks that are managed by a Logical Volume

Manager.

Performing these steps manually involves running many complex commands and can be

tedious and error-prone. The Oracle DBaaS solution automates this process and provides

a portal interface that lets you simply request additional storage and leaves the details to

underlying workflows.

When adding new disks to a data group of an Oracle deployment, you are prompted for

the following information:

Data group name

The additional amount of storage desired

For clarity, the entry form shows the current storage size. When you enter the amount of

additional storage, the form shows the new total amount of storage that will be available.

The actual storage size might be greater than requested because the system adds fixed

size disks, determined by the administrator, to provide the requested storage.

Figure 4 shows an example of the request form.

Figure 4. Adding new disks to a disk group

The new disks are the same size as the existing disks in the data group.

The workflow creates the requested disks and, in the case of a RAC deployment, makes

them visible to all the nodes of the cluster. The disks are then formatted, labeled, and

added to the data group.

In the case of ASM, when the disks are added, data on the disks in the disk group is

automatically rebalanced across all the disks.

You can use the asmcmd tool to show the composition of ASM disk groups. Figure 5 and

Figure 6 show the configuration of the DATA disk group before and after new disks are

added to the group.



Solution Guide

After the initial build of the Oracle server, the composition of the ASM disk groups shows

that there are two disks in the DATA disk group and the storage size is 20 GB.

Figure 5. Two disks in the DATA ASM disk group



After requesting an additional 10 GB be added to the DATA disk group, the list of ASM

disks reflects the change.

Figure 6. Two disks added to the DATA ASM disk group

Since disks are added in multiples of two and the disk size, determined by the

administrator, is 10 GB, two additional disks were added and the total storage size

increased to 40 GB.

If the database is stored on the file system, you can use LVM commands to show the

composition of the volume groups, as shown in Figure 7.



Solution Guide

Figure 7. Disks currently in the DATA data group

After requesting another 10 GB of storage space for the DATA data group, the logical

volume information is as shown in Figure 8. Note that storage for the DATA data group is

added in multiples of two disks (because two SCSI controllers are used); therefore, two

additional disks were added.



Figure 8. Two disks added to the DATA data group

Adding and removing Oracle Enterprise Manager monitoring targets

You can add or remove an Oracle Database server from Oracle Enterprise Manager

(OEM) through a maintenance operation, as shown in Figure 9. The solution installs or

removes the Oracle Management Agent on the server and it adds or removes appropriate

monitoring targets. Chapter 5 provides further information about Oracle Database

monitoring.



Solution Guide

Figure 9. Adding or removing OEM 12c Agents

This process is fully automated and does not require further information from the user to

complete the action.

Adding vCPU to a virtual machine

You can hot-add extra vCPU resources to a virtual machine without restarting the virtual

machine.

To hot-add vCPU to a virtual machine in vRealize Automation:

1. In the Items tab, select the machine to which you want to add new vCPU.

2. From the Actions menu, select Add vCPU.

3. From the list box, select the new total number of vCPUs for the machine, as shown in Figure 10, and then click Submit.



Figure 10. Adding vCPU to a machine

The preceding steps reconfigure the virtual machine with the new vCPU count, as shown.

The Oracle Database instance recognizes the change and reflects the new value of the

initialization parameter CPU_COUNT.

Adding memory to a virtual machine

You can hot-add extra memory to a virtual machine without restarting the virtual machine.

To hot-add memory to a virtual machine in vRealize Automation:

On the Items tab, select the machine to which you want to add memory.

1. From the Actions menu, select Add Memory.

2. Select the New total amount of memory value, as shown in Figure 11, and click Submit.

Figure 11. Adding memory to a machine

The preceding steps reconfigure the virtual machine with the new memory.

Chapter 5: Monitoring Oracle DBaaS


Solution Guide

Chapter 5 Monitoring Oracle DBaaS


Overview ............................................................................................................ 30

Oracle Enterprise Manager Database Express 12c ........................................ 30

Oracle Enterprise Manager Cloud Control 12c ............................................... 30

vRealize Operations Manager .......................................................................... 31



Overview

This chapter describes Oracle Database environment monitoring, including stand-alone

and extended solutions for monitoring Oracle Database 12c, the guest OS, and the full

stack for the Oracle Workload Pod.

Oracle Enterprise Manager Database Express 12c

OEM Database Express 12c (EM Express) is a web-based tool for managing Oracle

Database 12c. It is built into the database and runs in the XDB schema inside the

database. EM Express is easy to configure and offers support for basic database

administration tasks such as storage and user management. When licensed to provide

features beyond those for basic administration, EM Express provides comprehensive

solutions for performance diagnostics and tuning. Figure 12 shows the EM Express

Database Home screen.

Figure 12. EM Express Database Home screen

For this solution, EM Express is enabled by default as part of the Oracle Database 12c

deployment process.


OEM Cloud Control 12c is Oracle’s integrated enterprise IT management product line,

which is widely used for managing and monitoring the Oracle Database estate. It is highly

configurable and has a number of partner plug-ins such as the DELL EMC Storage Plug-

in for Oracle Enterprise Manager (OEM) 12c.

Using standard Oracle Enterprise Manager procedures, the database server can be

registered with OEM Cloud Control 12c, as shown in Figure 13.



Solution Guide

Figure 13. Host, database, and listener targets after Oracle Database 12c deployment

vRealize Operations Manager

vRealize Operations Manager is the main operations management component of

Enterprise Hybrid Cloud. It provides a simplified approach to operations management of

physical and cloud infrastructures. vRealize Operations Manager includes prebuilt and

configurable dashboards that use colored badges to provide insights and visibility into the

health, risk, and efficiency of your infrastructure. vRealize Operations Manager provides

realtime performance management and capacity optimization capabilities, as shown in

Figure 14.



Figure 14. Oracle relationships for virtual machine in vRealize Operations Manager

Blue Medora offers the vRealize Operations Management Pack for Oracle Enterprise

Manager, which you can use to monitor the Oracle DBaaS solution.

vRealize Operations Management Pack for Oracle Enterprise Manager is an embedded

adapter that uses Oracle OEM data to monitor Oracle environments and maps the

relationships between the interconnected Oracle and VMware layers.

Obtaining OEM metrics using vRealize Operations Manager

OEM metrics are available under Administration > Inventory Explorer > Adapter

Instances > OEM – Adapter Instance > OEM Adapter. Click the “start collecting” (green

arrow) icon highlighted in Figure 15 to show metrics. The overview information presented

shows the status of data collection through the OEM adapter.

Figure 15. OEM adapter data collection in vRealize Operations Manager

Select Oracle EM Managed Environment from the Oracle dashboards list to display heat

maps, which provide an overall quick visual health status of the Oracle Database instance

and related objects such as virtual machines, host systems, and datastores.

OEM integration

with vRealize

Operations

Manager



Solution Guide

You can view Health, Risk, and Efficiency badges for individual objects by clicking the

heat map for the database instances, as shown in Figure 16.

Figure 16. vRealize Operations Manager badge icons

Figure 17 shows the compliance of the database instance, as reported in OEM, against

the environment rules using the color of the badge. It also gives an overview of the

database resources and metrics.

Figure 17. OEM Managed Environment dashboard

Chapter 6: PDB Migration


Chapter 6 PDB Migration


Overview ............................................................................................................ 35

PDB copy preparation ...................................................................................... 36

PDB migration without data ............................................................................. 37

PDB migration with data ................................................................................... 39



Solution Guide

Overview

After a database server is created in Enterprise Hybrid Cloud, there are many ongoing

maintenance tasks to perform and operational requirements to fulfill.

This chapter shows how you can use a vRealize Orchestrator workflow to migrate an

Oracle 12c PDB from any source to an Oracle 12c CDB running in Enterprise Hybrid

Cloud.

The options available to a DBA for copying a PDB are:

Copy a PDB over DB Link, no data (metadata only: users, schema, and code)

Copy a PDB over DB Link, including data

Use a transportable tablespace

Clone a PDB from an RMAN CDB backup set

Duplicate a PDB using RMAN on an active CDB

Unplug a PDB from source and plug-in a PDB to destination using manifest file (XML)

In deciding which method to use, there are several factors to consider, such as:

Is all or part of the source database available during the process?

How accessible is the data on the source (read-only or read-write) during the process?

Are other tools needed (datapump, RMAN, SQL*Plus, SSH)?

What is the impact on performance?

What is the complexity?

Do data governance, privacy, protection, and ownership allow copying this data?

In most business environments, different teams or projects have a copy of a data set – for

example for development, testing, QA, and so on. However, to comply with governance,

privacy, and protection rules, this data usually needs to be restricted (subsetted) and

masked. Organizations have their own tools and procedures for these specific tasks,

which are outside the scope of this document.

Copying a PDB and optionally including the data is supported by the Oracle DBaaS

solution and made available to the end user through the VRealize Automation service

catalog.

The option that is the most efficient, the least complex, has the least impact, and is the

fastest for copying the PDB is the ”Copy a PDB over DB Link, …” option. It creates a

database link to the source database, and it copies the PDB metadata (and optionally the

data) over the link. It can be implemented in Oracle 12c by using only SQL.

PDB copy

options and

choice



PDB copy preparation

You must prepare the source PDB for the copy process. The source PDB can be on an

Enterprise Hybrid Cloud-managed server, or it can be on a non-Enterprise Hybrid Cloud-

managed server.

You can enable or disable the source PDB for the copy process. If you choose to enable

the source PDB for copying, a special user is created in the source CDB specifically for

the copy process. If you choose to disable the source PDB for copying, the user is

dropped from the source CDB.

When the Copy PDB function runs, the special user can log in and copy the metadata.

Additionally, if the copy is requested to include the data itself, the special user can bring

the source PDB temporarily into read-only mode for the duration of the actual data copy.

The Copy PDB: Enable-Disable source CDB workflow is made available in the Enterprise

Hybrid Cloud Service Catalog, as shown in Figure 18.

Figure 18. Source PDB preparation

The notification email address is used to confirm that the source database has been

prepared, as shown in Figure 19:

Overview

Request



Solution Guide

Figure 19. Notification email

PDB migration without data

After you enable a source PDB, you can request a Copy PDB operation. When you

request the copy excluding the data, the source PDB will stay unchanged in read-write

mode. Any pre-existing database connections remain connected during this operation.

Figure 20 and Figure 21 show examples of the input forms.

Figure 20. PDB Migration Source Server Information Form

Overview

Request



Figure 21. PDB Migration Target Server Form

When you submit the request, the PDB is migrated to the target CDB within Enterprise

Hybrid Cloud. Because this request excluded the data, only the metadata is copied. This

operation is very fast and efficient.

The source pluggable database contains a schema owner ‘TESTER’, with two table

objects with data:

salesserv1$ sqlplus / as sysdba

SQL> alter session set container=sales1;

Session altered.

SQL> select owner, table_name, tablespace_name, status

2 from all_tables

3 where owner='TESTER';

OWNER TABLE_NAME TABLESPACE_NAME STATUS

---------- ---------- --------------- ----------

TESTER DEPT USERS VALID

TESTER EMP USERS VALID

SQL> select 'dept' as "TABLE", count(*) as count from tester.dept

2 union all

3 select 'emp',count(*) from tester.emp;

TABLE COUNT

----- ----------

dept 3

emp 6

Verification



Solution Guide

You can verify that the newly created target pluggable database contains the matching

schema owner and objects, now without data, as follows:

ora-ch164$ sqlplus / as sysdba


Session altered.

SQL> select username from all_users where username='TESTER';

USERNAME

--------------------------------------------------------------------------

TESTER


2 from all_tables



---------- ---------- --------------- ----------




2 union all


TABLE COUNT

----- ----------

dept 0

emp 0

PDB migration with data

After you enable a source PDB, you can request a Copy PDB operation. When the copy is

requested to include the data, this process temporarily brings the source PDB into read-

only mode. This happens only when the copy is being made, and only if it is requested to

include the data. The mode is changed back after the data copy has finished. Any pre-

existing database connections remain connected during this operation.

Figure 20 and Figure 21 show examples of the input forms.

Overview

Request



Figure 22. PDB migration source server form

Figure 23. PDB migration target server form

When you submit the request, the PDB–including data–is migrated to the target CDB

within Enterprise Hybrid Cloud. This transfers the data over a database link that is created

in the target database. This is fast and efficient for smaller databases.

The source pluggable database contains a schema owner ‘TESTER’, with two table

objects with data:

salesserv1$ sqlplus / as sysdba


Session altered.


Verification



Solution Guide

2 from all_tables



---------- ---------- --------------- ----------




2 union all


TABLE COUNT

----- ----------

dept 3

emp 6

You can verify that the newly created target pluggable database contains the matching

schema owner and objects, with their data, as follows:

ora-ch164$ sqlplus / as sysdba


Session altered.

SQL> select username from all_users where username='TESTER';

USERNAME

--------------------------------------------------------------------------

TESTER


2 from all_tables



---------- ---------- --------------- ----------




2 union all


TABLE COUNT

----- ----------

dept 3

emp 6

Chapter 7: Automated Oracle Patching


Chapter 7 Automated Oracle Patching


Overview ............................................................................................................ 43

Patching mechanisms ...................................................................................... 43

Patching Oracle in Enterprise Hybrid Cloud ................................................... 43



Solution Guide

Overview

Patching an Oracle database is an essential task, but it can be daunting given the myriad

patches and updates released on a regular basis. Since Oracle DBaaS end users may not

have experience in identifying and implementing a patch strategy, critical patches could

be ignored, putting systems and data at risk.

Oracle DBaaS includes functionality that lets you easily apply Oracle quarterly patches to

your deployed systems.

Patching mechanisms

Oracle provides both proactive and reactive patches with multiple delivery methods.

Proactive patches generally follow a scheduled release cycle—normally quarterly—and

supply a cumulative collection of fixes. Reactive patches are normally interim or single

fixes that are usually included in the next relevant proactive patch.

For our purposes, the main proactive patching methods include:

Security Patch Update (SPU)—(formerly called Critical Patch Update) this patch provides security fixes for Oracle products.

Patch Set Update (PSU)—a collection of patches that have been tested together and include SPUs as well as high-impact/low-risk critical bug fixes. Separate PSUs are supplied for the Oracle Database and Grid Infrastructure software.

Bundle Patch—in this case, the Database Proactive Bundle Patch (DPBP) is a collection of patches and is a superset of the PSU, spanning the Oracle Database and Grid Infrastructure software stack.

Each patch in these collections of patches has specific prerequisites and installation steps

that must be followed to apply the patch correctly. Patching methods cannot be mixed in

the same ORACLE_HOME. Changing the patching method requires a full roll-back of the

previous mechanism’s patches.

For this Oracle DBaaS solution, the DPBP has been chosen as the patching method. The

solution provides workflows to download and apply a selected DPBP. For a single-

instance Oracle database, this requires an outage. For RAC systems, patches are applied

in a rolling fashion, one node at a time, with little or no database downtime.

To have complete patching control, the DBA needs to understand the available patching

mechanisms and implement a process to manually apply the required compatible patches.

Patching Oracle in Enterprise Hybrid Cloud

As a best practice, perform a database and virtual machine backup before applying

patches.

To apply the latest quarterly DPBP to a deployed Oracle DBaaS system, just select the

system – a standalone system or any of the nodes of a RAC system – and choose the

Apply Quarterly Patch Bundle option, as shown in Figure 24.



Figure 24. Selecting the quarterly patch option

Select the desired quarterly patch version and enter your Oracle Support login credentials,

as shown in Figure 25. The requested DPBP is downloaded and automatically applied to

the system, patching the grid infrastructure and the Oracle database, depending on the

content of the DPBP.

Figure 25. Applying the quarterly patch option

When a RAC system is patched, the patch is applied in a rolling fashion so that the cluster

remains up during the process.

When the process completes, you receive an email summarizing the steps taken during

the application of the patch including the location of log files generated.

The Automated Oracle Patching capability of Oracle DBaaS significantly simplifies this

challenging task and helps keep deployed Oracle systems secure and operational.

Chapter 8: Conclusion


Solution Guide

Chapter 8 Conclusion


Summary ........................................................................................................... 46

Features ............................................................................................................. 46



Summary

Enterprise Hybrid Cloud enables customers to build an enterprise-class, scalable platform

for complete infrastructure service lifecycle management.

This solution incorporates the following concepts:

Self-service and automation

Workload-optimized storage

Security and compliance

Monitoring and service assurance

The integration of Oracle DBaaS into Enterprise Hybrid Cloud fully supports Oracle users

with a self-service environment. For IT, this results in an automated, repeatable process

that reduces errors and improves time-to-value.

For the end-user to be able to request a multi-node clustered database on-demand, using

the self-service portal is highly beneficial. It reduces significant time and effort otherwise

required to deploy a cluster manually. The user simply makes the request and then

receives an automated email with deployment details when the request is complete.

Features

This solution enables the deployment of Oracle DBaaS on Enterprise Hybrid Cloud. The

key features of this solution are as follows:

The Workload Pod for Oracle DBaaS improves management of Oracle licensing compliance.

Application developers and service users can self-provision Oracle DBaaS on Enterprise Hybrid Cloud as:

A single-instance Oracle Database with Oracle Automatic Storage Management (ASM) or on file system.

An Oracle Database with Oracle Real Application Clusters (RAC) and ASM.

This creates an Oracle 12c Container Database (CDB) with an optional Pluggable

Database (PDB) in a single-tenant configuration. The deployed system can be

optionally added to an automatic backup schedule.

The solution enables users to perform Oracle DBaaS maintenance operations:

Add storage capacity to the Oracle database – single-instance and RAC.

Migrate a PDB to an Oracle 12c CDB deployed on Enterprise Hybrid Cloud with or without data.

Add and remove Oracle DBaaS monitoring.

Hot-add virtual CPU and memory.

Apply Oracle Patch Set Updates (quarterly patch bundles) automatically on single-instance and RAC databases on file system or ASM storage.



Solution Guide

Enable monitoring of the complete Oracle DBaaS solution by using Oracle Enterprise Manager Cloud Control 12c (OEM) and VMware vRealize Operations Manager.

Chapter 9: References


Chapter 9 References


Enterprise Hybrid Cloud documentation ......................................................... 49

VMware documentation .................................................................................... 49

Oracle documentation ...................................................................................... 49

Other documentation ........................................................................................ 49

Chapter 9: References


Solution Guide

Enterprise Hybrid Cloud documentation

See Essential reading for a complete list of Enterprise Hybrid Cloud documentation.

VMware documentation

Refer to the following on the VMware website:

VMware vRealize Automation documentation

VMware vRealize Operations Manager documentation

Oracle documentation

Refer to the following on the Oracle website:

Oracle Enterprise Manager Cloud Control 12c Advanced Installation and Configuration Guide

Oracle Database 12c Release 1 (12.1) Documentation:

Database Installation Guide for Linux

Grid Infrastructure Installation Guide for Linux

Real Application Clusters Installation Guide for Linux and UNIX

Automatic Storage Management Administrator's Guide

My Oracle Support documentation:

Oracle Database - Overview of Database Patch Delivery Methods (Doc ID 1962125.1)

Other documentation

Refer to the following documentation on the Blue Medora website:

vRealize Operations Management Pack for Oracle Enterprise Manager (OEM) Installation and Configuration Guide

vRealize Operations Management Pack for Oracle Enterprise Manager User Guide

http://www.vmware.com/

http://docs.oracle.com/en/

http://www.bluemedora.com/

enterprise hybrid cloud 4.1 - dell emc us · solution overview ... patching oracle in enterprise...

Documents