Oracle X6-2-HA Owner's Manual

Download

Page 1

Oracle® Database Appliance

X6-2-HA Deployment and User's Guide

Release 18.3 for Linux x86-64

F10531-03 May 2019

Page 2

Oracle Database Appliance X6-2-HA Deployment and User's Guide, Release 18.3 for Linux x86-64

F10531-03

Primary Author: Aparna Kamath

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Page 3

Preface

Audience xxv

Documentation Accessibility xxv

List of Examples

4-1 Example of a Bonded Configuration 4-2

4-2 Example of a Non-Bonded Configuration 4-2

4-3 Example of Configuring VLAN 4-3

8-1 Options for the Secure Erase Tool 8-5

12-1 Example of Showing the Status of All Shared Repositories 12-10

12-2 Example of Showing the Status of a Selected Shared Repository 12-10

12-3 Example of Starting a Shared Repository 12-11

12-4 Example of Stopping a Shared Repository 12-11

12-5 Example of Deleting a Shared Repository 12-12

12-6 Example of Increasing the Size of a Shared Repository 12-12

12-7 Example of Creating a Shared Virtual Disk 12-13

12-8 Example of Displaying the Information for All Vdisks 12-13

12-9 Example of Displaying Information for a Single Vdisk 12-14

12-10 Example of Cloning a Virtual Disk 12-14

12-11 Example of Attaching a Virtual Disk To a Virtual Machine 12-15

12-12 Example of Deleting a Virtual Disk from a Shared Repository 12-15

12-13 Example of Importing Virtual Machine Templates from an External Repository

Assembly File 12-18

12-14 Example of Importing a Virtual Machine Template from Dom0 12-18

12-15 Example of Importing a Virtual Machine Template Using an External Repository URL 12-18

12-16 Example of Creating a Virtual Machine Clone from a Virtual Machine Template 12-22

12-17 Example of Creating a Snap Clone From a Virtual Machine Template 12-22

12-18 Example of Creating a Snap Clone From an Existing Virtual Machine 12-22

12-19 Example of Configuring a Virtual Machine 12-27

12-20 Example of Migrating a Virtual Machine from the Currently Running Node to Another

Node 12-31

12-21 Example of Showing CPU Pools on a Node 12-44

12-22 Example of Creating a New CPU Pool on Oracle Database Appliance Virtualized

Platform Nodes 12-45

12-23 Example of Showing CPUs Assigned to Defined CPU Pools on Oracle Database

Appliance Virtualized Platform Nodes 12-46

12-24 Example of Changing the Number of CPUs Assigned to a CPU Pool on Oracle

Database Appliance Virtualized Platform Nodes 12-46

12-25 Example of Assigning a Virtual Machine to a CPU Pool on Oracle Database

Appliance Virtualized Platform 12-47

xvi

Page 17

13-1 Command-Line Interface Syntax 13-3

13-2 SUDO Example 1: Allow a User to Perform Any ODACLI Operation 13-6

13-3 SUDO Example 2: Allow a User to Perform Only Selected ODACLI Operations 13-7

13-4 Configuring the First Network as a Bonded Network 13-8

13-5 Configuring the First Network as a Non-Bonded Network 13-9

13-6 Displaying Patch Details for Components 13-12

13-7 List DB Home Details 13-12

13-8 List the Server Components and Versions 13-12

13-9 Listing the Latest Supported Versions 13-13

13-10 Creating Pre-Check Report 13-14

13-11 Displaying the Patch Pre-Checks Report 13-15

13-12 Example of a Successful Patch Pre-Checks Report 13-16

13-13 Setting Multiple Parameters 13-18

13-14 Example Command 13-19

13-15 Displaying All Patch Pre-Checks Reports 13-20

13-16 Displaying All Patch Pre-Checks Reports 13-21

13-17 Deleting A Patch Pre-Checks Report 13-22

13-18 Updating an Oracle Database Home 13-23

13-19 Updating the Agent 13-24

13-20 Updating the Repository 13-26

13-21 Updating the Server 13-27

13-22 Updating the Storage 13-28

13-23 Displaying Appliance Details 13-29

13-24 Example Command to View the Bill of Materials from the Command Line for Bare

Metal Deployments 13-30

13-25 Example Command to View the Features Report from the Command Line 13-33

13-26 Create a Manual Database Backup 13-38

13-27 Create a Level 0 Database Backup 13-38

13-28 Create a Backup Configuration for Disk 13-39

13-29 Create a Backup Configuration for NFS Location 13-39

13-30 Delete a Level 0 or Level 1 Backup 13-41

13-31 Delete a Long Term Backup Report 13-41

13-32 Deleting a Backup Configuration 13-41

13-33 Deleting the Oracle Object Store Credentials 13-42

13-34 Display Details of a Specific Backup Report 13-43

13-35 Display Schedule Details 13-44

13-36 Restoring a Database to the Same System 13-46

xvii

Page 18

13-37 Restoring a Database to a Different System 13-46

13-38 Display a List of all Backup Reports 13-46

13-39 Displaying a List of Backup Configuration 13-47

13-40 Displaying a List of ObjectStore Swift Credentials 13-48

13-41 Display a List of Scheduled Database Backups 13-48

13-42 Recovering a Database to a Point-in-Time 13-49

13-43 Recovering a Database to the Latest 13-49

13-44 Recovering a Database to an SCN 13-49

13-45 Revise a Backup Configuration for Disk 13-50

13-46 Associating a Backup Configuration with a Database 13-51

13-47 Updating an Existing Database Using the Resource ID 13-52

13-48 Updating an Existing Database Using the Resource Name 13-52

13-49 Changing the Oracle Casper ObjectStore Password 13-53

13-50 Changing the Oracle ObjectStore User Name 13-53

13-51 Change What Time the Backup Occurs 13-54

13-52 Disable Scheduled Database Backups 13-54

13-53 Displaying a List of Cores 13-55

13-54 Displaying the Current Core Configuration 13-55

13-55 Enabling CPU Cores 13-56

13-56 Displaying a List of Databases 13-57

13-57 Displaying Database Details 13-58

13-58 Creating a Database in Interactive Mode 13-62

13-59 Creating a Database Against a Different Version 13-62

13-60 Cloning a Database 13-63

13-61 Modifying a Database 13-64

13-62 Registering a Migrated Database 13-66

13-63 Upgrading an Oracle Database 13-68

13-64 Deleting a Database Named hrmsdb 13-69

13-65 Displaying a List of Oracle Home Directories 13-71

13-66 Displaying Oracle Database Home Details 13-72

13-67 Creating an Oracle Database Home 13-73

13-68 Deleting an Empty Database Home 13-74

13-69 Displaying a List of all Database Storage 13-75

13-70 Displaying Database Oracle ACFS Storage Details 13-76

13-71 Displaying Database Oracle ASM Storage Details 13-76

13-72 Creating Database Storage 13-77

13-73 Deleting Empty Database Storage 13-78

xviii

Page 19

13-74 Displaying Disk Group Storage 13-79

13-75 Displaying Disk Group Storage 13-81

13-76 Displaying a List of Jobs 13-84

13-77 Displaying Specified Number of Older Jobs 13-84

13-78 Displaying Jobs in a Date Range 13-84

13-79 Displaying Details for a Job 13-86

13-80 Displaying a List of Scheduled and Executed Jobs 13-87

13-81 Displaying a List of Networks 13-88

13-82 Displaying Network Details 13-89

13-83 Creating a Network 13-90

13-84 Creating a VLAN Network 13-91

13-85 Updating a Network 13-91

13-86 Deleting a Network 13-92

13-87 Displaying Network Details 13-94

13-88 Displaying a List of Network Interfaces 13-94

13-89 Masking Sensitive Data in Log Collection 13-96

13-90 Displaying a List of Logs 13-97

13-91 Creating Jobs to Purge Logs 13-98

13-92 Listing Jobs to Purge Logs 13-99

13-93 Displaying Log Cleanup Jobs 13-100

13-94 Creating Automatic Jobs to Purge Logs 13-101

13-95 Listing Jobs to Purge Logs 13-102

13-96 Configuring Oracle ASR with a Proxy Server 13-104

13-97 Configuring an External Oracle ASR 13-104

13-98 Updating Oracle ASR with a New Proxy Server 13-106

13-99 Displaying Oracle ASR Details 13-106

13-100 Testing the Oracle ASR Configuration 13-107

13-101 Deleting Oracle ASR From the System 13-108

13-102 Displaying a List of Configured and Suggested Memlock and HugePage Configurations 13-109

13-103 Updating the HugePage and Memlock Parameters to the Suggested Values 13-110

13-104 Displaying Environment and Hardware Details 13-112

13-105 Displaying Filesystem Details 13-113

13-106 Display Memory Details 13-114

13-107 Showing Network Details 13-115

13-108 Displaying Power Supply Details 13-115

13-109 Displaying Processor Details 13-116

13-110 Displaying Server Details 13-117

xix

Page 20

13-111 Displaying the Status of All Disks 13-119

13-112 Displaying the Status of a Single Disk 13-119

13-113 Listing All Diskgroups 13-121

13-114 Displaying DATA Configurations 13-121

13-115 Showing Controller Details 13-122

13-116 Displaying the RAID SYNC Status 13-122

13-117 Displaying Storage Devices 13-123

13-118 Displaying NVMe Details 13-124

13-119 Powering a Disk Off 13-125

13-120 Checking the Disk Status 13-125

13-121 Resetting the oda-admin Password in Interactive Mode 13-126

14-1 Preparing a Copy of the Configuration File 14-13

14-2 Creating a New Database Showing Prompts 14-16

14-3 Creating a New Database in an Existing Oracle Home 14-17

14-4 Creating a New Database from a Template 14-17

14-5 Deploying the Complete Oracle Database Appliance 14-25

14-6 Running the Configurator 14-25

14-7 Running the Offline Configurator with Advance Mode 14-25

14-8 Preloading an Existing Configuration File 14-25

14-9 Changing a User Group Name or ID 14-25

14-10 Viewing the Log File 14-26

14-11 Expanding Storage 14-26

14-12 Displaying the Write Cache Status of Disks 14-27

14-13 Locating an Oracle ASM Disk by Turning on the Disk’s LED 14-28

14-14 Example Command to View the Bill of Materials from the Command Line for

Virtualized Platforms Deployments 14-29

14-15 Modifying the Database Type 14-30

14-16 Modifying the Database Size 14-30

14-17 Viewing the Current and Suggested Kernel Parameters 14-32

14-18 Reconfiguring the Kernel Based on Available RAM 14-33

14-19 Increasing the Size of the DATA Volume 14-34

14-20 Displaying Database Details 14-39

14-21 Displaying Database Details for Four Databases 14-39

14-22 Displaying DB Home Details 14-41

14-23 Displaying DB Home Details 14-41

14-24 Oracle Database Appliance with Non-CDB Databases 14-41

14-25 Displaying Information About the Local Disks 14-42

Page 21

14-26 Displaying Information About the Shared Disks 14-42

14-27 Displaying Information About a Specific Shared Disk 14-43

14-28 Determining Which Node is the Master Node 14-44

14-29 Displaying Power Supply Information 14-46

14-30 Displaying the Available Virtual Machine Repositories 14-47

14-31 Displaying Details About a Specific Shared Repository 14-48

14-32 Determining if Storage Validation is Enabled 14-49

14-33 Starting ODA_BASE on the Local Node 14-52

14-34 Starting a Shared Repository on Node 0 14-52

14-35 Forcing a Virtual Machine to Stop 14-53

14-36 Stopping a Shared Repository 14-53

14-37 Stopping the Local ODA_Base 14-53

14-38 Running Diagnostic Tests on a Disk in the Expansion Storage Shelf 14-54

14-39 Unpacking Packages into the Oracle Appliance Manager Repository 14-55

14-40 Verify the Contents of a Patch Bundle 14-56

14-41 Enabling 12 CPU Cores for Oracle Database Appliance 14-58

14-42 Enabling All CPU Cores for Oracle Database Appliance 14-58

14-43 Cloning a Virtual Disk 14-64

14-44 Displaying Information for All Virtual Disks 14-65

14-45 Displaying Information for a Single Virtual Disk 14-65

14-46 Creating a Virtual Machine Image 14-68

14-47 Creating a Virtual Machine Image in Driver Domain Mode 14-68

14-48 Sending a Message to a Running Virtual Machine 14-72

14-49 Displaying Details for All Virtual Machines 14-73

14-50 Displaying Information for a Single Virtual Machine 14-73

14-51 Opening a Virtual Machine Console 14-74

14-52 Starting a Virtual Machine on Node 0 14-75

14-53 Importing a Virtual Machine Template from Dom0 14-79

14-54 Importing a Virtual Machine Template from a Remote Server 14-79

14-55 Importing Virtual Machine Templates from an Assembly on a Remote Server 14-79

14-56 Importing Virtual Machine Templates Into a Shared Repository From an Assembly on

a Remote Server 14-79

14-57 Modifying the Network Defined in a Virtual Machine Template 14-80

14-58 Display Information About a Virtual Template 14-80

14-59 Displaying Details of Available Virtual Area Networks (VLANs) 14-83

15-1 Example Command to View the Bill of Materials from the Command Line for Bare

Metal Deployments 15-2

xxi

Page 22

15-2 Example Command to View the Bill of Materials from the Command Line for

Virtualized Platforms 15-4

15-3 Example Command to View the Bill of Materials Report from the Stored Location 15-4

C-1 Oracle ACFS Storage Space C-3

C-2 Determining Storage on the DATA Disk Group C-4

D-1 JSON File to Create a Single Node Oracle Database Appliance with Role Separation D-3

D-2 JSON File to Create a Single Node Oracle Database Appliance without Role Separation D-5

D-3 JSON File to Create a Multi-Node Oracle Database Appliance with Role Separation D-8

xxii

Page 23

List of Figures

12-1 Oracle Database Appliance Virtualized Platform Architecture 12-3

12-2 Architecture Overview of Oracle Database Appliance Virtualized Platform Shared

Repositories 12-6

12-3 Basic Virtual Machine Local Area Network 12-8

12-4 Oracle Database Appliance Virtualized Platform with Virtual Local Area Networks 12-9

xxiii

Page 24

List of Tables

1-1 Software for Oracle Database Appliance 1-3

2-1 Checklist for System Configuration Information for Oracle Database Appliance 2-9

2-2 Minimum IP Address Requirements for Oracle Database Appliance Bare Metal

Deployment 2-10

2-3 Minimum IP Address Requirements for Oracle Database Appliance Virtualized

Platform Deployment 2-11

3-1 Description of Callouts for Cabling Oracle Database Appliance X6-2-HA with a Single

Storage Shelf 3-3

3-2 Description of Callouts for Cabling Oracle Database Appliance Storage Expansion Shelf 3-6

3-3 Peripheral Device Connections for Oracle Database Appliance 3-8

3-4 Description of Callouts for Powering On Oracle Database Appliance 3-9

8-1 Command Options for Cleanup Utility 8-2

9-1 Operating System Groups and Users on Oracle Database Appliance 9-2

12-1 Parameters Available for Configuring a Virtual Machine 12-26

15-1 Command Options for tfactl Tool 15-9

B-1 Default Operating System Groups and Users Configuration for Oracle Database

Appliance B-3

C-1 Oracle ACFS Mount Points and Related Oracle ASM Disk Groups and Volume

Information C-2

C-2 Usable Disk Capacity on Oracle Database Appliance X6-2-HA C-4

C-3 Oracle ASM Calculations C-6

C-4 Definition of Terminology C-6

E-1 Oracle Database Appliance OLTP Database Template Sizes E-3

E-2 Oracle Database Appliance DSS Database Template Sizes E-3

E-3 Oracle Database Appliance In-Memory Database Template Size E-3

xxiv

Page 25

Preface

Audience

Oracle Database Appliance is an optimized, prebuilt database system that is easy to deploy, operate, and manage. By integrating hardware and software, Oracle Database Appliance eliminates the complexities of nonintegrated, manually assembled solutions. Oracle Database Appliance reduces the installation and software deployment times from weeks or months to just a few hours while preventing configuration and setup errors that often result in suboptimal, hard-to-manage database environments.

• Audience

• Documentation Accessibility

• Related Documents

• Conventions

This guide is intended for anyone who configures, maintains, or uses Oracle Database Appliance:

• System administrators

• Network administrators

• Database administrators

• Application administrators and users

This book does not include information about Oracle Database architecture, tools, management, or application development that is covered in the main body of Oracle Documentation, unless the information provided is specific to Oracle Database Appliance. Users of Oracle Database Appliance software are expected to have the same skills as users of any other Linux-based Oracle Database installations.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?

ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/

lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

if you are hearing impaired.

xxv

Page 26

Conventions

The following text conventions are used in this document:

http://

xxvi

Page 27

Preface

Convention Meaning

boldface Boldface type indicates graphical user interface elements associated

with an action or terms defined in the text.

italic Italic type indicates book titles, emphasis, or placeholder variables for

which you supply particular values.

monospace

# prompt The pound (#) prompt indicates a command that is run as the root user.

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

xxvii

Page 28

Introduction to Oracle Database Appliance

Oracle Database Appliance saves time and money by simplifying deployment, maintenance, and support of database solutions for organizations of every size. Oracle Database Appliance hardware models are optimized to run Oracle Database Standard Edition and Enterprise Edition.

• About Oracle Database Appliance

Understand Oracle Database Appliance hardware models, deployment plans, and database options.

• Oracle Database Appliance Software Terminology

Understand the software patches available for Oracle Database Appliance.

• About the Web Console

Use the Oracle Appliance Manager Web Console to deploy and manage the appliance, databases, networks, and jobs.

About Oracle Database Appliance

Understand Oracle Database Appliance hardware models, deployment plans, and database options.

About Oracle Database Appliance Hardware Models

Choose the Oracle Database Appliance hardware model that suits your business needs.

Oracle Database Appliance Hardware Model

Oracle Database Appliance X7-2S, X7-2M, X7-2-HA

Oracle Database Appliance X6-2S, X6-2M, X6-2L

Deployment Use Case

• Oracle Database Appliance X7-2S is a

small configuration designed for smaller or entry-level deployments.

• Oracle Database Appliance X7-2M is a

medium-sized configuration designed for performance.

• Oracle Database Appliance X7-2-HA is a

large configuration designed for larger databases and high-availability.

• Oracle Database Appliance X6-2S is a

small configuration designed for smaller or entry-level deployments.

• Oracle Database Appliance X6-2M is a

medium-sized configuration designed for performance.

• Oracle Database Appliance X6-2L is a

large configuration designed for larger databases.

1-1

Page 29

Chapter 1

About Oracle Database Appliance

Oracle Database Appliance Hardware Model

Oracle Database Appliance X6-2-HA Highly-available two-node Oracle RAC

Oracle Database Appliance X5-2, X4-2, and X3-2

Deployment Use Case

clusters that can support both Oracle RAC and single-instance databases.

Highly-available two-node Oracle RAC clusters that can support both Oracle RAC and single-instance databases.

You cannot expand or reconfigure Oracle Database Appliance to a different configuration. For example, you cannot expand Oracle Database Appliance X7-S to Oracle Database Appliance X7-2M. For Oracle Database Appliance hardware configuration details, see the Oracle Database Appliance Owner's Guide.

About Oracle Database Appliance Deployment Plans

Oracle Database Appliance X7-2S and X7-2M are single node systems that you deploy as a bare metal platform.

Oracle Database Appliance X7-2-HA is a two-node system with the option to deploy as a bare metal platform or a virtualized platform.

Oracle Database Appliance X6-2S, X6-2M, X6-2L are single node systems that you deploy as a bare metal platform.

Oracle Database Appliance X6-2-HA is a two-node system with the option to deploy as a bare metal platform or a virtualized platform. Starting with with Oracle Database Appliance release 18.3, systems deployed as bare metal are migrated from oakcli to odacli (the DCS software stack). Virtualized systems continue to use the oakcli software stack.

Oracle Database Appliance X5-2, X4-2, and X3-2 are two-node systems with the option to deploy as a bare metal platform or a virtualized platform. Starting with with Oracle Database Appliance release 18.3, systems deployed as bare metal are migrated from oakcli to odacli (the DCS software stack). Virtualized systems continue to use the oakcli software stack.

About Database Deployment Options for Oracle Database Appliance

The following Oracle Database editions are available:

Database Edition Supported Releases Description

Oracle Database Enterprise Edition

Oracle Database Standard Edition Two

Oracle Database Release 18c,

12.2.0.1, 12.1.0.2, and

11.2.0.4

Oracle Database Release 18c,

12.2.0.1, 12.1.0.2, and

11.2.0.4

Supports Oracle Real Application Clusters (Oracle RAC) and single-instance Oracle Databases.

Supports Oracle Real Application Clusters (Oracle RAC), Oracle RAC One, and single-instance Oracle Databases.

1-2

Page 30

Oracle Database Appliance Software Terminology

Database Edition Supported Releases Description

Oracle Database Standard Edition One

Oracle Database Standard Edition

Oracle Database Release

11.2.0.4

Oracle Database Release

11.2.0.4

Supports Oracle Real Application Clusters (Oracle RAC), Oracle RAC One, and single-instance Oracle Databases.

Note:

It is important to understand your Oracle Database licensing before you create databases. You cannot provision Oracle Database Enterprise Edition and Standard Edition databases in the same bare metal platform, or the same ODA_BASE virtualized deployment, subject to Oracle Database licensing requirements. Review the Database Licensing Information User Manual for the Oracle Database release to review supported options and products.

Chapter 1

Oracle Database Appliance Software Terminology

Understand the software patches available for Oracle Database Appliance.

The table describes the Oracle Database Appliance patches that are available for download and the purpose of the patch.

Note:

Some hardware models may not use the patches listed in the table.

Table 1-1 Software for Oracle Database Appliance

Patch Description

Oracle Database Appliance patch bundle (quarterly patch release)

Oracle Database Appliance GI/ RDBMS Clone

Use the patch bundle to update to the latest release after Oracle Database Appliance is deployed. The patch updates the Oracle Database Appliance server, storage, and database components.

Use to perform an initial deployment of Oracle Database Appliance.

The bundle contains the latest Grid Infrastructure and RDBMS components, Oracle Database Appliance Manager software, Oracle Linux and hardware drivers for deployment on an Oracle Database Appliance that is shipped from factory state.

If you reimage Oracle Database Appliance with the Bare Metal ISO Image, download the GI/RDBMS Clone patch to deploy Oracle Database Appliance.

1-3

Page 31

Chapter 1

Oracle Database Appliance Software Terminology

Table 1-1 (Cont.) Software for Oracle Database Appliance

Patch Description

RDBMS Clone Use the RDBMS Software Clone files to get the latest RDBMS clone binaries

for Oracle Database releases 18c, 12.2.0.1, 12.1.0.2, and 11.2.0.4. The RDBMS clone files are needed to create Oracle databases and database homes.

Bare Metal ISO Image Use to reimage the appliance and reset the system back to the factory

configuration.

VM ISO Image (DOM0) (Virtualized Platform ISO Image)

ODA_BASE Template (Virtualization Template)

Use to re-image Oracle Database Appliance before deploying the ODA_Base Template and virtualized platform. The Oracle Database Appliance virtualized operating system image contains the following:

• Oracle Database Appliance Manager oakcli command-line interface

• Oracle Database Appliance Manager Configurator

• Oracle Linux

• Hardware drivers

Required for Virtualized Platform deployments on multi-node high availability (HA) systems.

Use to create the ODA_Base virtual machine for a virtualized database appliance. The template contains the following:

• Oracle Virtual Machine template

• Oracle Database clone binaries

• Oracle Database templates, customized for Oracle Database Appliance

deployments

• Oracle Grid Infrastructure clone binaries

Required for Virtualized Platform deployments on multi-node HA systems.

Note:

See the Oracle Database Appliance Release Notes for the patch numbers and download locations and the component versions available in the patch bundle.

1-4

Page 32

Chapter 1

About the Web Console

Note:

Starting with Oracle Database 18c, Oracle provides quarterly updates in the form of Release Updates (Updates) and Release Update Revisions (Revisions). Oracle no longer releases patch sets. For more information, see My Oracle Support Note 2285040.1.

Oracle Database releases are of type The

version

The major release version is based on the last two digits of the year in which an Oracle Database version is released for the first time. The release is an update of a version release and is designated based on the major release version, the quarterly release update version (Update), and the quarterly release update revision version (Revision).

Prior to Oracle Database release 18c, changing the first or second digit in the release number was an upgrade, and changing the fourth digit indicated an update. With 18c and later releases, changing the first digit is an upgrade, and changing the second indicates an update.

release is designated in the form major release version.0.0.0.0.

About the Web Console

Use the Oracle Appliance Manager Web Console to deploy and manage the appliance, databases, networks, and jobs.

The Web Console assists you in deploying Oracle Databases that follow Optimal Flexible Architecture guidelines. The Optimal Flexible Architecture standard provides best practices configurations to ensure database deployments that are easier to support and maintain. Optimal Flexible Architecture includes the following:

version

and

version_full

releases.

version_full

• Structured organization of directories and files, and consistent naming for critical

database files, such as control files, redo log files, and other critical files, which simplifies database administration

• Separation of tablespace contents to minimize tablespace free space

fragmentation, and maximize administrative flexibility

• Stripe and Mirror Everything (SAME) deployment, which safeguards against

storage failures

Note:

Create Oracle Databases using the Web Console or command-line interface to ensure that your database is configured optimally for Oracle Database Appliance.

The Web Console provides a user-friendly option to quickly view and perform many of the tasks needed to deploy, patch, and manage your system.

Use the links in the side navigation to view and manage the following:

• Appliance

1-5

Page 33

About the Web Console

– Appliance information

– System information

– Disk group information

– All the patches and hardware and software components installed on the

appliance

– List of RPMs and RPM Drift information

• Network

– View network details

– Create, update, and delete networks

– View interface details

• Oracle ASR

– View Oracle Auto Service Request (Oracle ASR) configuration details

– Configure, update, test, and delete Oracle ASR

• Patch Manager

Chapter 1

– Update the patch repository with Oracle Database Appliance patches

– View component details of the patch and versions that are installed on the

appliance

– View component details of the patch and versions that are available, but not

yet installed, on the appliance

– Run patch prechecks before applying the patch

– Update the server and storage components

Use the links in the top navigation to view and manage the following:

• Database

– Create a database

– View database details

– Apply a backup policy for the database

– Create a manual backup

– Recover a database from a backup

– View and update the database backup schedule and update the archive log

backup schedule for the database

– Create, update, and delete backup policies

– Create, update, and delete database homes

– Create and delete database homes

– Patch database homes

• Object Store

– Create Object Store Credentials for backup and recovery

– View the details for Object Store Credentials, including the endpoint URL, user

name, and tenant

1-6

Page 34

Chapter 1

About the Web Console

– Update and delete Object Store Credentials

• Monitoring

– View the status of hardware, physical disks, and network

– Click the hardware image to view details

• Activity

– View a list of jobs, details, and status

– Click a job description to view job details

Update ILOM and User Settings

Expand About in the upper right corner of the Web Console to perform the following tasks:

• Click About to view the Oracle Database Appliance release that is installed on the

appliance.

• Click Update ILOM Setting to change the root password. To enable first-time

• Click Update User Settings to change the

• Click Sign Out to sign out of the Web Console. If you do not sign out, the system

automatically signs you out after a period of inactivity. A warning will appear 2 minutes before the session expires.

oda-admin

password.

1-7

Page 35

Preparing for Oracle Database Appliance Installation and Deployment

Complete these setup tasks before Oracle Database Appliance is delivered.

Tasks:

• Registering Your Support Identifier on My Oracle Support

Add your hardware Support Identifier (SI) to your My Oracle Support account profile.

• Planning Oracle Database Appliance Configuration Options

Use these topics to help you to make decisions about your Oracle Database Appliance configuration.

• Gathering System Requirement Information

Use these checklists to collect information before deploying Oracle Database Appliance.

Registering Your Support Identifier on My Oracle Support

Add your hardware Support Identifier (SI) to your My Oracle Support account profile.

Your hardware SI is supplied when you purchase Oracle Database Appliance. If you acquire new software licenses, then you must also register your new software SIs. The SI registration process can take up to 24 hours to complete.

Note:

You cannot obtain support or software from Oracle without registered SIs.

Planning Oracle Database Appliance Configuration Options

Use these topics to help you to make decisions about your Oracle Database Appliance configuration.

These topics help you to select the correct Oracle Database Appliance and plan for deployment. Record your decisions and the information that you require before you proceed to complete system configuration checklists.

2-1

Page 36

Planning Oracle Database Appliance Configuration Options

Caution:

Do not use Oracle Database Configuration Assistant (DBCA) to create databases on Oracle Database Appliance. Only use Oracle Appliance Manager for database configuration. Deploying Oracle Database instances using Oracle Appliance Manager ensures that these databases are properly configured, optimized, and supported on Oracle Database Appliance.

Topics:

• Selecting Oracle Database Appliance Bare Metal Options

Oracle Database Appliance is shipped from the factory to deploy as bare metal.

• Selecting Oracle Database Appliance Virtualized Platform Options

Review Virtualized Platform options, and requirements for these options, such as shared disks and virtual local area networks.

• Selecting Database Configuration Options

Select the database templates and configuration options to properly size and configure your initial database.

Chapter 2

Selecting Oracle Database Appliance Bare Metal Options

Oracle Database Appliance is shipped from the factory to deploy as bare metal.

Review the systems requirements, database configuration, and software downloads to continue with a bare metal deployment.

Selecting Oracle Database Appliance Virtualized Platform Options

Review Virtualized Platform options, and requirements for these options, such as shared disks and virtual local area networks.

Before you implement virtual machines, you must decide how and where you want them to run. Based on your requirements, you can select High Availability options, or you can select options to reduce interference between competing virtual machines for CPU and network access. You can also select options to provide more storage space, or enable automatic startup for virtual machines. Some of these options require additional network configuration beyond the configuration required for the Oracle Database Appliance servers.

By default, Oracle Database Appliance includes one local repository on each node. The maximum size of that repository depends on your Oracle Database Appliance hardware. The maximum size is 350 GB for Oracle Database Appliance X6-2-HA Virtualized Platform.

When you create virtual machines in the default repositories, the virtual machines can run only on the node where they are located. Because they run on only one node, they have no failover capability.

To obtain the most flexible shared machine environment, use a shared repository with Virtual Local Area Networks (VLANs). Shared repositories provide High Availability options, more storage capacity, and reduced local storage use. VLANs help you partition network traffic for your virtual machines.

2-2

Page 37

Chapter 2

Planning Oracle Database Appliance Configuration Options

When you use a shared repository hosted on shared disks, the virtual machines consume space in Oracle Automatic Storage Management (Oracle ASM) disk groups, DATA and RECO. When you use shared disks, you can convert virtual machines to do the following:

• Start automatically whenever the repository becomes available

• Run on a preferred node

• Start or fail over to the other node, if the preferred node is unavailable

Oracle Database Appliance Virtualized Platform deployments support multiple VLANs on the same network interface card (NIC) port. Each VLAN is essentially an independent logical network that operates with other VLANs over the same physical connection.

Use VLANs to minimize the number of required physical connections and NICs while concurrently separating traffic. Each VLAN is assigned a distinct VLAN identification (ID). The network switch uses VLAN IDs to segregate traffic among the different VLANs operating on the same link. When a VLAN is configured, the VLAN functions exactly like a separate physical connection.

Note:

You must configure virtual LANs on the physical switches before you use them.

Selecting Database Configuration Options

Select the database templates and configuration options to properly size and configure your initial database.

Review the database configuration options and select the templates for Oracle Real Application Clusters (Oracle RAC), and Oracle RAC One Node databases needed to configure your initial database. This information is relevant to you if you plan to configure an initial database during Bare Metal or Virtualized Platform deployments.

Record your decisions and the information that you require for your database templates before you proceed to complete system configuration checklists.

Caution:

Topics:

2-3

Page 38

Planning Oracle Database Appliance Configuration Options

• Selecting Database Deployment Options for Oracle Database Appliance

If you plan to create an initial database during deployment, then use these lists to select an Oracle Database deployment option, and prepare for the deployment.

• Selecting Database Templates for Oracle Database Appliance

Oracle Database Appliance software includes preconfigured templates that incorporate Oracle best practices with optimization for different classes of databases.

• Calculating Required Cores

After you select templates for your planned Oracle Database, identify your workload type, and determine the total number of CPUs that you require to support the templates.

Selecting Database Deployment Options for Oracle Database Appliance

If you plan to create an initial database during deployment, then use these lists to select an Oracle Database deployment option, and prepare for the deployment.

Oracle Appliance Manager installs Oracle Database software on mirrored disks that are internal to Oracle Database Appliance. During the initial deployment, you can either create a database or you can defer database creation to a later time.

Chapter 2

Options:

• Enterprise Edition: Oracle Database 18c Enterprise Edition (no automated

failover), with the following characteristics:

– Single-instance Oracle Database Enterprise Edition home

– Oracle Database software installation on both nodes

• Oracle Real Application Clusters (Oracle RAC) One Node: Oracle RAC One

Node 18c, with the following characteristics:

– Oracle RAC One Node has a designated Oracle Database Appliance home

node

– Oracle RAC One Node software is installed on both servers

– Automated failover is configured

– Enterprise Edition license is required

– Oracle RAC One Node license on each server is required

Exception: If you designate one server as a backup server, then you can use that server without a license, in accordance with the 10-day rule.

• Oracle RAC: Oracle Real Application Clusters 18c, with the following

characteristics:

– Oracle RAC home

– Oracle RAC software is installed on both servers

– Enterprise Edition license is required

– Oracle RAC license on each server is required (not eligible for the 10-day rule)

2-4

Page 39

Planning Oracle Database Appliance Configuration Options

Note:

For information about the 10-day rule, see the Oracle Software Investment Guide at https://www.oracle.com/corporate/pricing/.

Selecting Database Templates for Oracle Database Appliance

Oracle Database Appliance software includes preconfigured templates that incorporate Oracle best practices with optimization for different classes of databases.

Because of differences in CPU counts, memory size, and other resources available with different Oracle Database Appliance models, some templates are not supported on all models.

Each Oracle Database template has different workload profile and performance characteristics:

• Memory requirements, which are calculated from the System Global Area (SGA),

and Program Global Area (PGA) sizes

Chapter 2

• Processing requirements, which are calculated from the number of processes

• Logging requirements, which are based on log buffer size, and online redo log size

1. Review the types of database templates for guidelines and sizing information.

2. Determine the template that you want to use. The following templates are

available for Oracle Database Appliance X6-2-HA:

• Odb-01s

• Odb-01

• Odb-02

• Odb-04

• Odb-06

• Odb-12

• Odb-16

• Odb-20

Note:

Oracle strongly recommends that you use the Oracle Database Appliance templates. These templates implement best practices, and are configured specifically for Oracle Database Appliance.

On Oracle Database Appliance Virtualized Platform, if you only plan to deploy one Oracle Database, then Oracle recommends that you use a template for your ODA_BASE that has the same name as the template that you choose for your Oracle Database.

2-5

Page 40

Chapter 2

Gathering System Requirement Information

You do not have to select database templates with the same size category as the ODA_BASE template. For example, you can use a small ODA_BASE template to host two very small databases, and you can use a large ODA_BASE template to host either one large with one small database, or host one medium database with one small and two very small databases.

Caution:

The total requirements for your selected database templates must not exceed the capacity of your ODA_BASE template. You can adjust the size of ODA_BASE after the initial deployment, so can expand ODA_BASE to accommodate more databases in ODA_BASE.

Calculating Required Cores

After you select templates for your planned Oracle Database, identify your workload type, and determine the total number of CPUs that you require to support the templates.

Oracle Database Appliance templates are configured and tuned for specific types of Oracle Database workloads:

• Generic templates

• Online analytic transaction templates (OLTP)

• Decision support services templates (DSS)

• In-Memory database templates

These templates are designed to run on a specific number of cores. Caging ensures that each database workload is restricted to the set of cores allocated by the template, enabling multiple databases to run concurrently with no performance degradation, up to the capacity of Oracle Database Appliance. You can select database template sizes larger than your current needs to provide for planned growth, which you accommodate later by adjusting System Global Area (SGA) and Program Global Area (PGA) sizes, as well as the number of cores.

List of Information You Need Before Deployment

Collect security, storage, and network information required to prepare for deploying Oracle Database Appliance.

Chapter 2

Review your security requirements for requirements and network administration requirements, and complete any required configuration before your Oracle Database Appliance hardware is delivered.

Security Requirements

• What root password should you use for Oracle Database Appliance? Root

passwords should comply with your system security requirements.

• Secure operating systems are an important basis for general system security.

Ensure that your operating system deployment is in compliance with common security practices.

Storage Administration Requirements

Storage administration is integrated into Oracle Database Appliance. No additional storage configuration is required.

Oracle Database Appliance includes integrated storage for operational files (operating system, Oracle Grid Infrastructure home, Oracle Database homes, tools), user data (database files), and log files (database redo logs). Operational files are stored on mirrored internal system disks in each server. Data and database redo log files are stored on shared disks in the storage shelf.

The Oracle Database Appliance X6-2-HA storage shelf contains ten 1.6 TB SSDs (partitioned to 1.2 TB to improve performance) for data, which are configured as a DATA ASM disk group. Four 200 GB SSDs are used for the database redo logs, which are configured as a REDO ASM disk group.

root

passwords, determine your storage

Note:

Disk hardware capacity is measured using the formula that 1 KB equals 1,000 bytes; software storage requirements are based on 1 KB equals 1,024 bytes.

2-7

Page 42

Chapter 2

Gathering System Requirement Information

Network Administration Requirements

Ensure that the names and addresses that you provide for network configuration are configured in your Domain Name System (DNS) servers. The addresses that you provide are configured in the resolution, even if a DNS server is not available.

You have the option to connect either to a copper, or to a fiber public network. Ensure that your network planning is based on the correct type of public network.

Oracle recommends that you resolve addresses using a DNS server, so that you can use Single Client Access Names (SCANs). Having a single name to access the cluster enables the client to use the EZConnect client and the simple JDBC thin URL to access any Oracle Database running in the cluster, independent of the active servers in the cluster. The SCAN provides load-balancing and failover for client connections to these databases. The SCAN works as a cluster alias for Oracle Databases in the cluster.

If you deploy without using a DNS server, then you can add a DNS server later, and add SCANs. If you add SCANs, then you must specify additional VIP addresses for those SCANs.

/etc/hosts

file to provide IP name and address

A correctly configured Oracle Database Appliance requires at least six public addresses on the same subnet for the nodes:

• A public IP name and address for each node

• A virtual IP name and address for each node

• Two addresses that resolve to the SCAN for the cluster.

All names must conform to the RFC 952 standard, which permits alphanumeric characters and hyphens ("-"), but does not allow underscores ("_").

Provide an IP address for the public interface for each node. This interface is

Eth1

on Oracle Database Appliance Virtualized Platform, (a bond of Eth2 and Eth3),

which is used for the host IP address for the node.

Use

bond1

and

bond2

for management, backup, disaster recovery, or other options where you require a network interface. Be prepared to provide a netmask and a gateway for each interface, as both are required when you configure network connections for Oracle Database Appliance. If you select a Custom installation, then provide names and addresses for the

Also determine answers to the following questions:

• Do you have a Network Time Protocol (NTP) service configured for each server,

so that the local system time for each server is synchronized?

If you have NTP servers, and you want to synchronize time between Oracle Database Appliance nodes using NTP, then be prepared to provide the addresses for the servers. If you do not provide addresses for NTP servers, then Oracle Grid Infrastructure software configures time synchronization between nodes using Cluster Time Synchronization Service (CTSS).

bond1

optional interface.

bond0

, or

• Do you want to plug in the public IP address cables to redundant switches, so that

you can avoid a single point of failure for Oracle Database Appliance? Oracle recommends that you use redundant switches for High Availability.

2-8

Page 43

Checklist for System Details

Use the checklist to gather system information that you need to obtain for Oracle Database Appliance. Record the values for your system.

Table 2-1 Checklist for System Configuration Information for Oracle Database Appliance

System Information Description

Host Name The name for the Oracle Database Appliance System. The name must

Domain Name

Master Password The password set for the root password of the system, OS users,

DNS Server (Optional) DNS server details.

NTP Server (Optional) Network Time Protocol (NTP) service details.

Region The region where you plan to operate the Oracle Database Appliance

Timezone Select the time zone where you plan to operate the Oracle Database

Database Edition Select an Oracle Database edition, either Enterprise Edition or

Backup Location Determine the backup location setting. The setting determines how the

Percentage of Storage Reserved for Data

Diskgroup Redundancy

Chapter 2

Gathering System Requirement Information

conform with the RFC 952 standard, which allows alphanumeric characters and hyphens ( - ), but does not allow underscores ( _ ). The name should not begin with a numeral or hyphen and should not end in a hyphen. Oracle recommends that you use all lowercase characters for the host name.

Your domain name. For example:

database users, and pdbadmin. The password is also used to set the database provide is in compliance with common security practices.

system.

Appliance system.

Standard Edition. You cannot mix editions. The database edition you select determines the database editions that you create in the appliance. To change editions, you must redeploy Oracle Database Appliance.

NVMe Disks are partitioned between DATA and RECO. Select External, Internal, or Custom:

• External reserves 80% of the storage for DATA and 20% for

• Internal reserves 40% of the storage for DATA and 60% for

• Custom reserves anywhere from 10% to 90% of the storage for

If you select a Custom backup location, determine the amount of reserves for DATA storage. The percentage must be a whole number between 10 and 90.

Determine the redundancy level for DATA, RECO, and FLASH:

If there are up to two disk groups, then you can select the disk group redundancy as Normal or Flex. A quorum disk must exist, if you want to select Flex redundancy. If there are more than two disk groups, then you can select the redundancy as Normal (two way mirror), High (three way mirror), or Flex.

If you select High redundancy, then DATA, RECO, and FLASH are all High redundancy.

SYS

and

SYSTEM

RECO.

DATA, and the remainder is reserved for RECO.

example.com

passwords. Ensure that the password you

2-9

Page 44

Chapter 2

Gathering System Requirement Information

Table 2-1 (Cont.) Checklist for System Configuration Information for Oracle Database Appliance

System Information Description

Network Information Obtain network information:

• Public network

• (Optional) Additional network

• (Optional) Oracle Integrated Lights Out Manager (Oracle ILOM)

network

Initial Database Details (if you want to create one during deployment)

• Database name

• Normal or container database

• Class (database template)

• Database characterset

• Database language

• Database version

• Shape (for example: odb1 or odb2)

• Storage (Oracle ASM or Oracle ACFS)

• Configure Oracle Enterprise Manager console

Checklist for Custom Node Network Address Configuration

Use the checklists in this topic to identify the IP addresses required for Oracle Database Appliance.

By default, names for network interfaces are derived from the Oracle Database Appliance system name, which you provide during installation. Also, when you use Oracle Appliance Manager Configurator, the addresses for the public IP addresses can be automatically assigned in a sequence starting with the address you provide for the public IP address for Node 0. The other IP addresses generated are, in order, the public address for Node 1; the virtual IP address for Node 0; the virtual IP address for Node 1; and the SCAN addresses.

You can retain the default values, or you can use addresses provided by your system administrator to perform a custom configuration. Ensure that all addresses listed as "Yes” in the "Same Subnet" column are on the same subnet as each other.

Minimum IP Address Requirements for Oracle Database Appliance Bare Metal Deployment

Table 2-2 Minimum IP Address Requirements for Oracle Database Appliance Bare Metal Deployment

Type of IP Minimum IP

Address Counts

Host Public Addresses

2 No default No default Yes

IP Address Default Values

Your Values As Applicable Same

Subnet

2-10

Page 45

Gathering System Requirement Information

Table 2-2 (Cont.) Minimum IP Address Requirements for Oracle Database Appliance Bare Metal Deployment

Chapter 2

Type of IP Minimum IP

Address Counts

Host Private Addresses

Oracle RAC VIP 2 No default No default Yes

Single Client Access Name (SCAN)

Oracle Integrated Lights Out Manager (ILOM)

User Virtual Machine

4 192.168.16.2

2 No default No default Yes

2 No default No default No

Not Applicable No default No default No

IP Address Default Values

192.168.16.2 5

192.168.17.2 4

192.168.17.2 5

Your Values As Applicable Same

Subnet

Not applicable: the private addresses are defined before deployment and should not be changed.

If you are using InfiniBand, IP addresses 192.168.17.24 and

192.168.17.25 are not used

Yes

Minimum IP Address Requirements for Oracle Database Appliance Virtualized Platform Deployment

Table 2-3 Minimum IP Address Requirements for Oracle Database Appliance Virtualized Platform Deployment

Type of IP Minimum IP

Address Counts

Host Public Addresses

Host Private Addresses

Oracle RAC VIP 2 No default No default Yes

2 (for ODA_BASE)

2 (for Dom0)

(Total of 4)

2 192.168.16.24

IP Address Default Values

No default No default

(for Dom0)

192.168.16.25 (for Dom0)

192.168.16.27 (for ODA_BASE)

192.168.16.28 (for ODA_BASE)

Your Values As Applicable

If you are using InfiniBand, IP addresses

192.168.17.24 and

192.168.17.25 are not used

Not applicable: the private addresses are defined before deployment and should not be changed.

Same Subnet

Yes

2-11

Page 46

Gathering System Requirement Information

Table 2-3 (Cont.) Minimum IP Address Requirements for Oracle Database Appliance Virtualized Platform Deployment

Chapter 2

Type of IP Minimum IP

Address Counts

Single Client Access Name (SCAN)

Oracle Integrated Lights Out Manager (ILOM)

User Virtual Machine

2 No default No default Yes

2 No default No default No

At least 1 for each Virtual Machine

IP Address Default Values

No default No default No

Your Values As Applicable

Same Subnet

2-12

Page 47

Readying Oracle Database Appliance for Deployment

Complete these tasks to prepare to deploy Oracle Database Appliance.

Topics:

• About Interconnect Cabling

Interconnect is reserved for Oracle Grid Infrastructure (GI) and Oracle Relational Database Management System (RDBMS).

• Attaching Supplied Cables for Oracle Database Appliance

If you are using Oracle Database Appliance with a single storage shelf, attach the interconnect cables.

• Attaching a Storage Expansion Shelf to Oracle Database Appliance

Review these topics to install and cable a storage expansion shelf for Oracle Database Appliance.

• Attaching Peripheral Devices

Complete this task if you have direct access to Oracle Database Appliance and you intend to use a locally connected monitor, keyboard and mouse.

• First Startup of Oracle Database Appliance

Use this procedure to start up either a newly-installed Oracle Database Appliance, or to start up the appliance after you power it down.

• Configuring Oracle Integrated Lights Out Manager

Configure Oracle Integrated Lights Out Manager (Oracle ILOM) to manage Oracle Database Appliance independent of the operating system.

About Interconnect Cabling

Interconnect is reserved for Oracle Grid Infrastructure (GI) and Oracle Relational Database Management System (RDBMS).

Oracle GI includes Oracle Clusterware, Oracle Automatic Storage Management (Oracle ASM), and Oracle Restart. Even if you do not use Oracle Real Application Clusters (RAC) , Oracle Database Appliance uses the interconnect for RAC ASM and Oracle GI.

Note:

Do not use interconnect for other applications.

When you power on Oracle Database Appliance for the first time, the system automatically defines your public network interface based on the interconnect. If you use the InfiniBand cards, then the InfiniBand network is used for the interconnect. If you ordered the configuration that contains the 10GbE SFP+ (fiber) cards instead of

3-1

Page 48

Node 1

Node 0

Storage Shelf

21 53

Chapter 3

Attaching Supplied Cables for Oracle Database Appliance

InfiniBand cards, then the onboard 10GBase-T (Copper) ports are used for the interconnect.

Attaching Supplied Cables for Oracle Database Appliance

If you are using Oracle Database Appliance with a single storage shelf, attach the interconnect cables.

Topics:

• Attaching Cables for Oracle Database Appliance X6-2-HA

Use the diagram in this topic to understand how to attach cable connections between ports on Oracle Database Appliance X6-2-HA.

• Cabling Oracle Database Appliance to Connect to Fiber Public Networks

(Optional)

You can configure Oracle Database Appliance X6-2-HA to use 10GbE SFP+ (fiber) connections for the public network if you ordered the configuration that contains 10GbE SFP+ (fiber) cards instead of InfiniBand cards.

Attaching Cables for Oracle Database Appliance X6-2-HA

Use the diagram in this topic to understand how to attach cable connections between ports on Oracle Database Appliance X6-2-HA.

Single Shelf

The back panel of each node contains three PCIe generation 3 terminal slots, with two sockets in each slot. The PCIe slots are labeled X PCIe3, where X is the PCIe slot number.

The following figure illustrates the cable connections between ports on Oracle Database Appliance X6-2-HA in a single storage shelf. The cables are color-coded. Match the colors of the labels at the ends of each cable with the colored line shown in the following illustration. Also match the cable colors to the background colors of the socket identification labels.

3-2

Page 49

Chapter 3

Attaching Supplied Cables for Oracle Database Appliance

Table 3-1 Description of Callouts for Cabling Oracle Database Appliance X6-2HA with a Single Storage Shelf

Callout Number Description

1 Green InfiniBand Cable

• From: Node 0, PCIe slot 1, PORT2

• To: Node 1, PCIe slot 1, PORT2

2 Yellow InfiniBand Cable

• From: Node 0, PCIe slot 1, PORT1

• To: Node 1, PCIe slot 1, PORT1

3 Dark blue SAS cable:

• From: Node 0, PCIe slot 2, SAS0

• To: Storage shelf, top I/O port 0

4 Light blue SAS cable:

• From: Node 0, PCIe slot 3, SAS1

• To: Storage shelf, bottom I/O port 0

5 Dark red SAS cable:

• From: Node 1, PCIe slot 2, SAS1

• To: Storage shelf, top I/O port 1

6 Light red SAS cable:

• From: Node 1, PCIe slot 3, SAS0

• To: Storage shelf, bottom I/O port 1

Cabling Oracle Database Appliance to Connect to Fiber Public Networks (Optional)

To use fiber connections between Oracle Database Appliance and your public network, you must cable the interconnect by using the green and yellow copper ports (onboard ports cables for these ports ship with the base system.

The following describes how to connect the ports:

• Plug the green Cat 6 cable into the onboard NET 1 port on each node, as shown

in callout 1 in the figure.

• Plug the yellow Cat 6 cable into the onboard NET 0 port on each node, as shown

in callout 2 in the figure.

net0

and

net1

). The green and yellow Category 6 (

Cat 6

) interconnect

3-3

Page 50

Chapter 3

Attaching a Storage Expansion Shelf to Oracle Database Appliance

The following sections show the cabling options for 10 GbE SFP+ PCI cards.

Fiber Cables

For optical cables, you must purchase either Short Range (SR) or Long Range (LR) SFP+ transceivers for each of the network ports, and then plug in the appropriate optical cable. Currently, Oracle sells both the SR and LR SFP+ transceivers. In addition to these transceivers, you must purchase the appropriate LC-LC terminated fiber optic cables from a third-party vendor.

Name Part Number

10 GbE Transceiver SR (SFP+) X2129A-N

10 GbE Transceiver LR (SFP+) X5562A-Z

Copper Cables

You can purchase the following copper cables from Oracle. These cables have built-in SFP+ connectors:

Name Length Part Number

TwinAx 1m 1m X2130-1M-N

TwinAx 3m 3m X2130-3M-N

TwinAx 5m 5m X2130-3M-N

Attaching a Storage Expansion Shelf to Oracle Database Appliance

Review these topics to install and cable a storage expansion shelf for Oracle Database Appliance.

Topics:

• About Attaching and Cabling Storage Shelves

Review these options and best practices for adding storage shelves for Oracle Database Appliance X6-2-HA.

• Installing and Cabling a Storage Expansion Shelf

Use this procedure to install and cable a storage expansion shelf for Oracle Database Appliance

3-4

Page 51

Attaching a Storage Expansion Shelf to Oracle Database Appliance

About Attaching and Cabling Storage Shelves

Review these options and best practices for adding storage shelves for Oracle Database Appliance X6-2-HA.

Storage Shelf Options for Oracle Database Appliance X6-2-HA

Oracle Database Appliance X6-2-HA can be shipped with one or two storage shelves. You can obtain the second shelf at a later time to double your storage capacity.

If you originally deployed Oracle Database Appliance with one storage shelf, then you can add a storage expansion shelf at any time without having to shut down your databases or applications.

Best Practice Guidelines for Adding Storage Expansion Shelves

Oracle recommends that you add a storage expansion shelf when you have relatively little activity on your databases. When the system discovers the new storage, Oracle ASM automatically rebalances the disk groups. The rebalance operation may degrade database performance until the operation completes.

Chapter 3

Caution:

Review cabling instructions to ensure that you have carried out cabling correctly. Incorrect connections can cause data loss when adding a storage expansion shelf to Oracle Database Appliance with existing databases.

Do not attach cables to Ethernet ports in the I/O modules labeled "SERVICE ONLY" when cabling the system. These ports are intended for use by service engineers only.

How to Cable a Storage Expansion Shelf

The following figure shows you how to insert the required cables into the storage expansion shelf of Oracle Database Appliance. The cables for the two nodes and the original storage shelf are included in the illustration for reference.

The cables are color-coded. Match the colors of the labels at the ends of each cable with the colored line shown in the illustration. Also match the cable colors to the background colors of the socket identification labels. You can also use the callouts in the diagram to identify the cables and ports. Because all cables with the same terminations are interchangeable, you can ignore the color coding. The back panel of each node contains three PCIe generation 3 terminal slots, with two sockets in each slot. The PCIe slots are labeled X PCIe3, where X is the PCIe slot number. Review the callout table that follows the figure for more information.

3-5

Page 52

Storag e Expansio n Shelf

Nod e 1

Nod e 0

Storag e Shelf

7 9 8

Chapter 3

Attaching a Storage Expansion Shelf to Oracle Database Appliance

The cables identified with callout numbers in the preceding figures are included with each shipped Oracle Database Appliance storage expansion shelf. These cables are all black, but have colored labels at each end that match the references to cable colors in the text and the label colors on the back panels.

Table 3-2 Description of Callouts for Cabling Oracle Database Appliance Storage Expansion Shelf

Callout Number Description

7 Dark blue SAS cable:

• From: Node 1, PCIe slot 2, SAS0

• To: Storage expansion shelf, top I/O port 0

8 Light blue SAS cable:

• From: Node 1, PCIe slot 3, SAS1

• To: Storage expansion shelf, bottom I/O port 0

9 Dark red SAS cable:

• From: Node 0, PCIe slot 2, SAS1

• To: Storage expansion shelf, top I/O port 1

10 Light red SAS cable:

• From: Node 0, PCIe slot 3, SAS0

• To: Storage expansion shelf, bottom I/O port 1

Caution:

Do not attach cables to Ethernet ports in the I/O modules labeled "SERVICE ONLY" when cabling the system. These ports are intended for use by service engineers only.

3-6

Page 53

Installing and Cabling a Storage Expansion Shelf

Use this procedure to install and cable a storage expansion shelf for Oracle Database Appliance

1. Place the storage expansion shelf below your Oracle Database Appliance, if

possible, or else close enough to connect the provided cables.

The storage expansion shelf normally sits at the bottom of Oracle Database Appliance, beneath the storage shelf. However, because racks should always be provisioned from the bottom up, that space may be unavailable. In that case, to avoid re-rack mounting the entire system, you can position the storage expansion shelf above the server nodes, or in a different, but adjacent, rack.

2. Install the extension storage shelf in exactly the same manner as the original

storage shelf. To review information about installing optional components for Oracle Database Appliance, see the section "Optional Component Installation" in Chapter 4 of Oracle Database Appliance Owner’s Guide.

3. Use the figures in this topic to assist you to cable the storage expansion shelf for

your Oracle Database Appliance model.

Chapter 3

Attaching Peripheral Devices

Caution:

Incorrect connections can cause data loss when adding a storage expansion shelf to Oracle Database Appliance with existing databases.

4. Attach the supplied power cords. Refer to the section "Attaching Power Cords and

Initializing Components" to obtain information and see figures showing how to attach power cords.

Attaching Peripheral Devices

Complete this task if you have direct access to Oracle Database Appliance and you intend to use a locally connected monitor, keyboard and mouse.

Oracle Database Appliance is not equipped with human-computer interface devices, such as a monitor or keyboard. If you want to log in locally, instead of through a network, then you must attach interface devices.

Attach a monitor to the graphics card port, and attach a keyboard and a mouse to the USB ports. Refer to the figure and table to identify the ports.

3-7

Page 54

First Startup of Oracle Database Appliance

In the figure, callout 1 identifies the ports for the keyboard and mouse. Callout 2 identifies the monitor port.

Table 3-3 Peripheral Device Connections for Oracle Database Appliance

Chapter 3

Callout Number

1 USB ports for the keyboard and mouse

2 Graphics card port for the monitor

Description

First Startup of Oracle Database Appliance

Use this procedure to start up either a newly-installed Oracle Database Appliance, or to start up the appliance after you power it down.

To ready Oracle Database Appliance for the powering on the first time, you need to attach all of the required power cords and confirm that initialization completes successfully. You can then start up the system by pushing the power button once.

• Attaching Power Cords and Initializing Components

Attach power cords for Oracle Database Appliance.

• Powering On Oracle Database Appliance the First Time

Use this procedure the first time you power on Oracle Database Appliance.

Attaching Power Cords and Initializing Components

Attach power cords for Oracle Database Appliance.

Caution:

Before plugging in the power cords, ensure that the electrical outlets providing the power are grounded.

If you use only a single AC circuit, then connect both power cords for each component to that circuit. If you want to maintain N+1 power supply redundancy, then use two separate AC circuits. Connect one power cord from each AC circuit into each component.

For more information about cabling with the supplied Cable Management Arm, refer to Oracle Database Appliance Owner’s Guide.

3-8

Page 55

1 2 3

First Startup of Oracle Database Appliance

Powering On Oracle Database Appliance the First Time

Use this procedure the first time you power on Oracle Database Appliance.

Note:

After you connect power cords, the green SP OK light-emitting diode (LED) lights blink for a few minutes, and then turn to steady ON. The cooling fans also may turn on. However, these events do not indicate that the system is started. You must complete all of the steps in this section to turn on the appliance properly. Read through the entire section to understand the sequence required for initial system startup.

1. Turn on the attached storage shelf, or shelves, before powering on the server

nodes.

2. After turning on the storage in the rear of each storage shelf, push the recessed

power button to turn on the server nodes.

Chapter 3

Note:

The fully-initialized state is indicated by the green SP OK LEDs staying steadily lit. If any of the green LED lights on the server are still blinking, then wait for them to complete their initialization steps.

The figure is an image of the front of the power panel, see the following callout table to identify the power button and the system initialization status indicator lights.

Table 3-4 Description of Callouts for Powering On Oracle Database Appliance

Callout Function

1 Recessed On/Off power button, which is located on the front panel

of the appliance. Push this button only once. Do not repeatedly push the power button.

2 SP OK LED light, located on the front panel of the appliance.

3-9

Page 56

Configuring Oracle Integrated Lights Out Manager

Table 3-4 (Cont.) Description of Callouts for Powering On Oracle Database Appliance

Callout Function

3 Green Power OK LED, located on the front panel. These lights

must be in the steady ON position (Green light does not blink) before you log on to the system.

3. Wait for Oracle Database Appliance to complete startup.

Note:

Do not repeatedly push the power buttons. Startup can take several minutes to complete.

Oracle Database Appliance is ready for use when the green Power OK LEDs (callout 3) on the front of the system remains steadily on.

Chapter 3

Configuring Oracle Integrated Lights Out Manager

Configure Oracle Integrated Lights Out Manager (Oracle ILOM) to manage Oracle Database Appliance independent of the operating system.

Oracle ILOM provides alternate ways to restart and troubleshoot Oracle Database Appliance.

You must set up the following items first to configure Oracle ILOM:

• A name and IP address

• A password to replace the default Oracle ILOM password

• Access to a management network, using an assigned netmask

• An Ethernet cable connected from the NET MGT port to the management network

In the default configuration, Dynamic Host Configuration Protocol (DHCP) is enabled in Oracle ILOM and the DHCP server automatically assigns network settings. To determine the IP address or host name assigned by the DHCP server, use the network tools provided with the DHCP server.

If you do not use DHCP, then use the custom option in Oracle Database Appliance Manager Configurator to assign IP addresses and host names to Oracle ILOM when you deploy your database.

Note:

If you have not enabled DHCP, then you must complete Oracle Database Appliance configuration to access Oracle ILOM.

To connect to the Oracle ILOM, use one of the following two methods:

1. Log in using a web interface by completing these steps:

3-10

Page 57

Chapter 3

Configuring Oracle Integrated Lights Out Manager

a. Using a client system's browser, enter the IP address or host name assigned

by DHCP into the browser address field and press Enter.

b. At the login page, enter the default user name,

changeme

root

and the default password,

The Oracle ILOM web interface appears.

2. Log in using a command-line interface (CLI) by completing these steps:

a. Using a client system, establish a secure shell (SSH) connection by entering

the following on the command line:

ssh -l root sp_ip_address

where

sp_ip_address

b. Enter the default user name,

is the IP address assigned by DHCP.

root

, and the default password,

changeme

The Oracle ILOM CLI prompt appears.

Troubleshooting the ILOM Configuration

If the ILOM is not working, then ensure that the ILOM NIC is enabled and that

ipv4

enabled.

You can configure the ILOM with the IPMI tool or through the BIOS. The following describes how to use the IPMI tool:

1. Open the IPMI tool.

# ipmitool –I open sunoem cli

2. Go to

SP/network

and verify that the port is enabled:

cd /SP/network

3. If the port is not enabled, then enable the port.

set state=enabled

4. In

5. If

SP/network

ipv6

is enabled, then disable

, verify that

ipv4

is enabled.

ipv6

and enable

ipv4

# ipmitool -I open sunoem cli "set /SP/network/ipv6 state=disabled" # ipmitool -I open sunoem cli "set /SP/network/ipv4 state=enabled"

3-11

Page 58

Provisioning Oracle Database Appliance Baremetal System

Understand the process to configure Oracle Database Appliance baremetal system.

The Web Console is the preferred method of deploying your bare metal platform configuration. The Web Console provides all of the fields necessary to provision Oracle Database Appliance, including configuring the system, network, database, and Oracle Auto Service Request (Oracle ASR). If you prefer to use the command-line interface, you must create a JSON file to configure the deployment options.

• Plumbing the Network

Plumb the Oracle Database Appliance network with the public internet protocol (IP) information assigned to a node, to enable upload of the Oracle Database Appliance software.

• Verifying Cabling and Network Connections

After powering on Oracle Database Appliance, verify that the network connections are set up correctly.

• Downloading Oracle Database Appliance Software

Download Oracle Database Appliance software and copy to a temporary location before applying updates to your appliance.

• Installing Oracle Database Appliance Software

Install Oracle Database Appliance software, before creating the appliance.

• Creating the Appliance

Create the appliance using the Web Console.

Plumbing the Network

Plumb the Oracle Database Appliance network with the public internet protocol (IP) information assigned to a node, to enable upload of the Oracle Database Appliance software.

1. Connect to Oracle ILOM remote console, then log into Oracle Database Appliance

root

2. Run the command

# /opt/oracle/dcs/bin/odacli/configure-firstnet Using bonding public interface (yes/no) [yes]: Select the Interface to configure the network on (btbond1) [btbond1]: Configure DHCP on btbond1 (yes/no) [no]: INFO: You have chosen Static configuration Use VLAN on btbond1 (yes/no) [no]:

3. Complete the network configuration as prompted and configure the public network

interface. Also provide the netmask and gateway IP address.

configure-firstnet

on Node0.

4-1

Page 59

Chapter 4

Plumbing the Network

You use this network connection to transfer the software to the server node.

Example 4-1 Example of a Bonded Configuration

For a bonded configuration, answer yes to using a bonding public interface and configure the first network to use a

# opt/oracle/dcs/bin/odacli/configure-firstnet

Using bonding public interface (yes/no) [yes]: yes Select the Interface to configure the network on (btbond1): btbond1 Configure DHCP on btbond1 (yes/no): no INFO: You have chosen Static configuration Enter the IP address to configure: 10.1.10.2 Enter the Netmask address to configure: 255.255.255.0 Enter the Gateway address to configure: 10.1.10.1 INFO: Plumbing the IPs now INFO: Restarting the network Shutting down interface btbond1: bonding: btbond1: Removing slave em2. bonding: btbond1: releasing active interface em2 bonding: btbond1: making interface em3 the new active one. bonding: btbond1: Removing slave em3. bonding: btbond1: releasing active interface em3 ::::::::::

btbond1

interface without configuring DHCP.

Example 4-2 Example of a Non-Bonded Configuration

To create a non-bonded configuration and disable VLAN capabilities, answer using a bonding public interface.

# opt/oracle/dcs/bin/odacli/configure-firstnet

Using bonding public interface (yes/no) [yes]: no INFO: Breaking the bonding on btbond1 INFO: remove bonding module: rmmod bonding INFO: remove slave setup in /etc/sysconfig/network-scripts/ifcfg-em2 INFO: remove slave setup in /etc/sysconfig/network-scripts/ifcfg-em3 INFO: Restarting the network Shutting down interface em1: [ OK ] Shutting down interface p1p1: [ OK ] Shutting down interface p1p2: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface em1: [ OK ] Bringing up interface em2: [ OK ] Bringing up interface em3: [ OK ] Bringing up interface p1p1: Determining if ip address 192.168.16.24 is already in use for device p1p1... [ OK ] Bringing up interface p1p2: Determining if ip address 192.168.17.24 is already in use for device p1p2... [ OK ] INFO: Restarting the network Select the Interface to configure the network on (em2 em3) [em2]: Configure DHCP on em2 (yes/no) [no]:

4-2

Page 60

Chapter 4

Plumbing the Network

INFO: You have chosen Static configuration Enter the IP address to configure : 10.1.10.2 Enter the Netmask address to configure : 255.255.255.0 Enter the Gateway address to configure[10.1.10.1] : INFO: Plumbing the IPs now /usr/share/system-config-network/netconfpkg/NCHostsList.py:100: DeprecationWarning: BaseException.message has been deprecated as of Python

2.6

badlines.append((num, value_exception.message)) /usr/share/system-config-network/netconfpkg/NCHostsList.py:105: DeprecationWarning: BaseException.message has been deprecated as of Python

2.6

""" % (value_exception.message, num) /usr/share/system-config-network/netconfpkg/NCProfileList.py:142: DeprecationWarning: BaseException.message has been deprecated as of Python

2.6

self.error = e.message INFO: Restarting the network Shutting down interface em1: [ OK ] Shutting down interface em2: [ OK ] Shutting down interface em3: [ OK ] Shutting down interface p1p1: [ OK ] Shutting down interface p1p2: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface em1: [ OK ] Bringing up interface em2: Determining if ip address 10.1.10.2 is already in use for device em2... [ OK ] Bringing up interface em3: [ OK ] Bringing up interface p1p1: Determining if ip address 192.0.2.24 is already in use for device p1p1... [ OK ] Bringing up interface p1p2: Determining if ip address 192.0.2.25 is already in use for device p1p2... [ OK ]

Example 4-3 Example of Configuring VLAN

# configure-firstnet Using bonding public interface (yes/no) [yes]: Select the Interface to configure the network on (btbond1) [btbond1]: Configure DHCP on btbond1 (yes/no) [no]: INFO: You have chosen Static configuration Use VLAN on btbond1 (yes/no) [no]:yes Configure VLAN on btbond1, input VLAN ID [2 - 4094] 122 INFO: using network interface btbond1.122 Enter the IP address to configure : 192.0.2.24 Enter the Netmask address to configure : 192.0.2.24 Enter the Gateway address to configure[192.0.2.24] : INFO: Restarting the network Shutting down interface btbond1: [ OK ] Shutting down interface em1: [ OK ]

4-3

Page 61

Chapter 4

Verifying Cabling and Network Connections

Shutting down interface p1p1: [ OK ] Shutting down interface p1p2: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface btbond1: Determining if ip address 192.0.2.24 is already in use for device btbond1... [ OK ] Bringing up interface em1: [ OK ] Bringing up interface p1p1: Determining if ip address 192.0.2.24 is already in use for device p1p1... [ OK ] Bringing up interface p1p2: Determining if ip address 192.0.2.24 is already in use for device p1p2... [ OK ] Bringing up interface btbond1.122: Determining if ip address 192.0.2.24 is already in use for device btbond1.122... [ OK INFO: Restarting the DCS agent initdcsagent stop/waiting initdcsagent start/running, process 32104

Verifying Cabling and Network Connections

After powering on Oracle Database Appliance, verify that the network connections are set up correctly.

Run the validation scripts only on Oracle Database Appliance HA models.

1. Log into the Oracle Database Appliance console and access the server node with

user name as

2. Run validation scripts on both nodes, to verify cabling:

# /opt/oracle/dcs/bin/odacli validate-storagetopology

root

and password

welcome1

4-4

Page 62

Chapter 4

Verifying Cabling and Network Connections

SUCCESS : Cable check for port 1 on controller 0 SUCCESS : Overall Cable check for controller 0 INFO : Check for External Controller 1 SUCCESS : Cable check for port 0 on controller 1 SUCCESS : Cable check for port 1 on controller 1 SUCCESS : Overall Cable check for controller 1 INFO : Check for overall status of cable validation on Node0 SUCCESS : Overall Cable Validation on Node0 SUCCESS : JBOD0 Nickname set correctly SUCCESS : JBOD1 Nickname set correctly

3. If there is a storage expansion shelf connected to the appliance, then power it on.

Run the

storagetopology

command on both nodes to make sure the cabling is

correct:

# /opt/oracle/dcs/bin/odacli validate-storagetopology

INFO : ODA Topology Verification INFO : Running on Node0 INFO : Check hardware type SUCCESS : Type of hardware found : X7-2 INFO : Check for Environment(Bare Metal or Virtual Machine) SUCCESS : Type of environment found : Bare Metal INFO : Check number of Controllers SUCCESS : Number of ahci controller found : 1 SUCCESS : Number of External SCSI controllers found : 2 INFO : Check for Controllers correct PCIe slot address SUCCESS : Internal RAID controller : SUCCESS : External LSI SAS controller 0 : 3b:00.0 SUCCESS : External LSI SAS controller 1 : 5e:00.0 INFO : Check if JBOD powered on SUCCESS : 2JBOD : Powered-on INFO : Check for correct number of EBODS(2 or 4) SUCCESS : EBOD found : 4 INFO : Check for External Controller 0 SUCCESS : Cable check for port 0 on controller 0 SUCCESS : Cable check for port 1 on controller 0 SUCCESS : Overall Cable check for controller 0 INFO : Check for External Controller 1 SUCCESS : Cable check for port 0 on controller 1 SUCCESS : Cable check for port 1 on controller 1 SUCCESS : Overall Cable check for controller 1 INFO : Check for overall status of cable validation on Node0 SUCCESS : Overall Cable Validation on Node0 SUCCESS : JBOD0 Nickname set correctly SUCCESS : JBOD1 Nickname set correctly

4. Verify the interconnect network:

# ethtool p1p1

Settings for p1p1: Supported ports: [ FIBRE ] Supported link modes: 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full

4-5

Page 63

Downloading Oracle Database Appliance Software

10000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 25000Mb/s <<<<<<<<<<<<<<<<<<<<<<< check speed Duplex: Full Port: Direct Attach Copper PHYAD: 1 Transceiver: internal Auto-negotiation: on Current message level: 0x00000000 (0) Link detected: yes

# ethtool p1p2

Settings for p1p2: Supported ports: [ FIBRE ] Supported link modes: 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full 10000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 25000Mb/s <<<<<<<<<<<<<<<<<<<<<<< check speed Duplex: Full Port: Direct Attach Copper PHYAD: 1 Transceiver: internal Auto-negotiation: on Current message level: 0x00000000 (0) Link detected: yes

Chapter 4

Downloading Oracle Database Appliance Software

Download Oracle Database Appliance software and copy to a temporary location before applying updates to your appliance.

1. Download the software files from My Oracle Support to a temporary location on an

external client. Refer to the release notes for details about the software for the latest release.

For example, download the Oracle Database Appliance GI Clone for ODACLI/DCS stack (patch 27604593) and Oracle Database Appliance RDBMS Clone for ODACLI/DCS stack (patch 27604558) for 18.3:

p27604593_183000_Linux-x86-64.zip p27604558_183000_Linux-x86-64.zip

2. Unzip the software — it contains README.html and one or more zip files for the

patch.

unzip p27604593_183000_Linux-x86-64.zip unzip p27604558_183000_Linux-x86-64.zip

4-6

Page 64

Chapter 4

Installing Oracle Database Appliance Software

The GI and RDBMS Clone files for release 18.3 are extracted.

odacli-dcs-18.3.0.0.0-181205-GI-18.3.0.0.zip odacli-dcs-18.3.0.0.0-180905-DB-18.0.0.0.zip

3. Copy the software files from the external client to Oracle Database Appliance. Use

the

scp

sftp

protocol to copy the bundle.

Example using

scp software_file root@oda_host:/tmp

Example using

sftp root@oda_host

Enter the

put software_file

For example, for release 18.3:

put odacli-dcs-18.3.0.0.0-181205-GI-18.3.0.0.zip put odacli-dcs-18.3.0.0.0-180905-DB-18.0.0.0.zip

The GI and RDBMS Clone files are copied to the temporary location on the appliance. You can update the repository, and create the appliance, as explained in the next topic.

scp

command:

sftp

command:

root

password, and then copy the file.

Installing Oracle Database Appliance Software

Install Oracle Database Appliance software, before creating the appliance.

1. Verify the current system version by running the following command on both

nodes:

# /opt/oracle/dcs/bin/odacli describe-component -v

2. Update the repository with Oracle Grid Infrastructure and Database software.

[root@oda1 opt]# /opt/oracle/dcs/bin/odacli update-repository

-f /tmp/GI_clone_file,/tmp/DB_clone_file

For example, for release 18.3

# /opt/oracle/dcs/bin/odacli update-repository -f /tmp/odacli-dcs-18.3.0.0.0-181205-GI-18.3.0.0.zip, /tmp/odacli-dcs-18.3.0.0.0-180905-DB-18.0.0.0.zip

4-7

Page 65

3. Confirm that the repository update is successful:

[root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID

4. Delete the software zip files from the temporary location on the appliance to save

space:

[root@oda1 opt]# rm software_file rm: remove regular file software_file? y

You have now updated the repository with the Oracle Database Appliance software, and can create your appliance, as described in the next topic.

Creating the Appliance

Create the appliance using the Web Console.

Ensure that ports 7070 and 7093 on the network between ODA and the client machine, are open.

Chapter 4

Creating the Appliance

1. Navigate to the Web Console. You are prompted to set the password for the

admin

user.

oda-

https://ODA-host-ip-address:7093/mgmt/index.html

2. Log into the Web Console with the new password.

When you launch the Web Console on an unconfigured appliance, the Appliance page notifies you that the appliance is not configured and provides a link to the pages needed to configure and create the appliance.

3. Click Create Appliance.

4. In the Create Appliance page, if you want to create the appliance from a saved

configuration, click Browse, and select the JSON file. The information from the saved configuration file is loaded. You can retain or edit the fields. Otherwise, manually, provide the values to create the appliance.

5. In the System Information section, specify the values as follows.

a. Host Name: Enter the host name.

The host name can contain alphanumeric characters and dashes (-), but cannot start with a number or dash (-) or end with dash (-). Do not exceed 30 characters.

b. Domain Name: Enter the domain name.

c. Region: Select the region of the world where the Oracle Database Appliance

is located.

d. Time Zone: Select the time zone where the Oracle Database Appliance is

located.

e. (Optional) DNS Servers: Enter addresses for one or more DNS servers.

f. (Optional) NTP Servers: Enter addresses for one or more NTP servers.

g. Diskgroup Redundancy: If there are up to two disk groups, then you can

select the disk group redundancy as Normal or Flex. A quorum disk must exist, if you want to select Flex redundancy. If there are more than two disk

4-8

Page 66

Creating the Appliance

groups, then you can select the redundancy as Normal, High, or Flex. Select Normal, High, or Flex, as per your deployment requirement.

The Flex parameter defines the disk group redundancy. For Oracle ASM storage, when you select Flex as the disk group redundancy, you can set the database redundancy to either Mirror or High. You can set the disk group redundancy only during appliance creation. The database redundancy can be set anytime you create the database.

The redundancy level is for DATA, RECO, and FLASH. If you select High redundancy, then DATA, RECO, and FLASH are all High redundancy. If the system has less than five (5) NVMe storage devices, then redundancy is automatically set to Normal.

If the system has more than three (3) NVMe storage devices, then you can choose the Flex redundancy option.

The redundancy level for REDO can be set to Flex, but the file groups created in REDO are all High redundancy.

h. Data Storage Percentage: Enter a whole number between 10 and 90 to

define the percentage of storage reserved for DATA, the remainder is reserved for RECO. For example, if you enter 80, then 80% of the storage for DATA and 20% for RECO.

Chapter 4

i. System Password and Confirm Password: Enter the system password in

both fields.

The system password is the password set for UNIX and

root

users. The password must begin with an alpha character and cannot contain quotation marks. Do not exceed 30 characters.

6. In the Network Information section, configure the primary client access network,

virtual networks, and an Oracle Integrated Lights Out Manager (ILOM) network. You are only required to configure the client access network. The ILOM configuration is optional if you already configured the ILOM for the appliance and you do not need to make changes.

Specify the following, depending on whether it is a single-node or multi-node Oracle Database Appliance deployment:

a. Client Access Network Host Name: For Node0, enter the host name for the

primary client access network.

b. Client Access Network IP Address: For Node0, enter the IP address for the

primary client access network.

c. VIP Name for Node0: Enter the name of the virtual IP network for Node0.

d. VIP IP Address for Node0: Enter the virtual IP address that resides on Node0

and is shared between the nodes.

e. VIP Name for Node1: Enter the name of the virtual IP network for Node0.

f. VIP IP Address for Node1: Enter the virtual IP address that resides on Node1

and is shared between the nodes.

g. (Optional) ILOM Host Name: Enter the name of the Oracle ILOM host for

Node0 and Node1.

h. (Optional) ILOM Network IP Address: Enter the IP address for the ILOM for

Node0 and Node1.

4-9

Page 67

Chapter 4

Creating the Appliance

i. (Optional) ILOM Network Subnet Mask: Enter the subnet mask address for

the ILOM.

j. (Optional) ILOM Network Gateway: Enter the gateway address for the ILOM.

k. Client Access Network Subnet Mask: Enter the subnet mask address for the

primary client access network.

l. Client Access Network Gateway: Enter the gateway address for the primary

client access network.

m. Client Access Network Interface: Enter the interface for the primary client

access network.

7. Determine how you want to configure your users and groups and whether or not

you want to allow operating system role separation:

• Two users with six groups: Customize Users and Groups, select No. Allow OS

Role Separation, select Yes. This is the default configuration.

• Two customized users with six customized groups: Customize Users and

Groups, select Yes. Allow OS Role Separation, select Yes.

• Single user with two groups: Customize Users and Groups, select No. Allow

OS Role Separation, select No

• Single user with six groups: Customize Users and Groups, select Yes. Allow

OS Role Separation, select No. SAP deployments use this configuration.

8. Do you want to create an initial database? Select Yes and go to Step 9 or select

No and go to Step 10.

9. Enter the following information to configure an initial database:

a. DB Name: Enter a name for the database.

The name must contain alphanumeric characters and cannot exceed 8 characters.

b. (Optional) DB Unique Name: Enter a globally unique name for the database.

Databases with the same DB Name within the same domain (for example, copies of a database created for reporting or a physical standby) must have a different DB Unique Name that is unique within the enterprise. The name must contain alphanumeric, underscore (_), dollar ($), and pound (#) characters, but must begin with an alphabetic character. No other special characters are permitted in a database name. The unique name cannot exceed 30 characters.

c. DB Version: Select a database bundle patch number.

d. CDB: Select Yes or No to specify whether or not you want a Container

Database (CDB).

e. PDB Name: Enter a name for the pluggable database (PDB).

The name must begin with an alphanumeric character. The following characters are valid: alphanumeric characters, and underscore (_).

f. PDB Admin User: Enter an Admin user name for the pluggable database

(PDB).

g. Database Edition: Select the Oracle Database edition, either Standard

Edition and Enterprise Edition. Your license determines which database edition you are eligible to create in the appliance.

4-10

Page 68

Chapter 4

Creating the Appliance

h. Password: Provide a password for the database.

i. Deployment: Select a deployment type from the list. The options are RAC,

RAC-One, or SI (single instance database). If you select a single instance database, then select the node for the SI database deployment.

If you select a single instance database, then you have the option to create the database on either Node0 or Node1. The default is Node0.

j. Shape: Select a database shape from the list.

k. In the Database Class field, select a database class from the drop-down list. If

an option is not available in the list, it is not supported for the database edition on the Oracle Database Appliance or the version that you selected. The default is OLTP.

l. In the Storage field, select ACFS or ASM from the drop-down list. The default

is Oracle ASM.

Only Oracle 18c, 12.2, and 12.1 databases can use Oracle ASM storage. Oracle Database 11.2 is only supported on Oracle ACFS.

m. If you select the storage as ASM, and the Database Version is 12.2 or later,

and you specified the disk group redundancy as Flex, then you can select the Database Redundancy value as Mirror or High.

You can choose Oracle ACFS storage for all database versions, but if you select Oracle ACFS storage, then you cannot specify the database redundancy. If your disk group redundancy is Flex, and you choose Oracle ACFS storage for the database, then the database redundancy is set to Mirror.

n. Storage: Select ACFS or ASM.

o. Data Files on Flash Storage: Select Yes or No.

This option is only available if the HA system has HDD storage drives.

p. Configure EM Express: Select Yes or No.

Select Yes to configure the Oracle Enterprise Manager Database Express (EM Express) console for Oracle Database 12.2.1.0 or 12.1.0.2 or the Database Control Console for Oracle Database 11.2.0.4. Selecting Yes enables you to use the console to manage the database.

q. Characterset: Select a characterset.

r. National Characterset: Select a national characterset.

s. Language: Select the database language.

t. Territory: Select a territory or location from the list.

10. (Optional) Configure and enable Oracle ASR on the ASR page.

You can configure and enable Oracle Auto Service Request (Oracle ASR) now or later:

• To not enable Oracle ASR during deployment, select No and click Submit.

After deployment, you can configure an internal Oracle ASR or register with an external Oracle ASR Manager from either the Web Console or command-line interface.

– Internal Oracle ASR: choose to configure Oracle ASR Manager on Oracle

Database Appliance or use Oracle ASR Manager configured on another server in the same network as your appliance.

4-11

Page 69

Chapter 4

Creating the Appliance

– External Oracle ASR: If you already have Oracle ASR Manager configured

elsewhere, you can register Oracle Database Appliance with your existing Oracle ASR Manager.

• To enable Oracle ASR, select Yes and complete the fields:

a. ASR User Name: Enter the e-mail address associated with the My Oracle

Support account under which the server is registered.

b. Password: Enter the password associated with the My Oracle Support

account under which the server is registered.

c. SNMP Version: Select V2 or V3. V2 is the default and recommended version.

d. HTTP Proxy used for Upload to ASR: Select Yes or No.

e. Proxy Server Name: If you are using a proxy for upload, enter the proxy

server name.

f. Proxy Port: If you are using a proxy for upload, enter the proxy port.

g. (Optional) HTTP Proxy Requires Authentication: If you are using a proxy

for upload, select Yes if you require authentication. If you do not require authentication, select No.

h. Proxy User Name: If you are using a proxy for upload, enter the proxy user

name.

i. (Optional) Proxy Password: If you are using a proxy for upload and require

authentication, enter the proxy password.

11. Click Submit. When prompted, click Yes to confirm that you want to start the job

to deploy the appliance.

12. Verify that the appliance is deployed. Run the

odacli describe-appliance

command. For multi-node deployments, run the command on both nodes.

[root@oda1 opt]# /opt/oracle/dcs/bin/odacli describe-appliance

Appliance Information

---------------------------------------------------------------ID: 618dfa94-35ff-4f81-8aab-e93810bc2c45 Platform: Odav6 Data Disk Count: 48 CPU Core Count: 36 Created: July 24, 2018 1:55:57 PM MDT System Information

---------------------------------------------------------------Name: odax7-2ha Domain Name: example.com Time Zone: America/Denver DB Edition: EE DNS Servers: 192.1.1.1 192.1.1.2 NTP Servers: 192.1.1.3 192.1.1.4 Disk Group Information

---------------------------------------------------------------DG Name Redundancy Percentage

------------------------- ------------------------- -----------Data High 80 Reco High 20

4-12

Page 70

Chapter 4

Creating the Appliance

Redo High 100 Flash High 100

The job to create the appliance takes time to complete. To monitor the job progress, click the Activity tab. Click the job number to view the tasks. After deployment, the the system password. The password. Change these passwords to comply with your user security protocols.

root

and database users

oracle

and

SYS, SYSTEM

grid

passwords are set to the default

, and

PDBADMIN

are set to

4-13

Page 71

Provisioning an Oracle Database Appliance Virtualized Platform

Oracle Database Appliance provides you with the option to reimage the system and configure the appliance as a virtualized platform.

Note:

You can provision Standard Edition and Standard Edition 2 Oracle Real Application Cluster (Oracle RAC) databases, but you must use Oracle VM virtualization on a virtualized platform on Oracle Database Appliance and follow the single socket per server licensing restriction. The single socket restriction means that you can use a maximum of 18 cores per server, in multiples of two. You can use the remaining cores for applications.

• Determining if the System is Configured with a Virtualized OS Image

Before deploying a Virtualized Platform on Oracle Database Appliance, determine if the system has the Virtualized OS ISO image.

• Setting Up the Virtualized Platform

Set up the initial public network.

• Installing Virtualized Platform Software and Deploying the Appliance

Deploy the ODA_BASE domain for a virtualized platform and then deploy the appliance.

• Creating a Configuration File for a Virtualized Platform

If you want to use the Configurator to create a virtualized platform configuration file before your Oracle Database Appliance system is delivered, then review these topics.

dom0

virtualized operating system on both nodes and configure the

Determining if the System is Configured with a Virtualized OS Image

Before deploying a Virtualized Platform on Oracle Database Appliance, determine if the system has the Virtualized OS ISO image.

Oracle Database Appliance ships from the factory with a bare metal ISO image installed. To use the virtualization features, you must reimage the system with the Virtualized OS ISO image.

A bare metal system uses the uses the

oakcli

commands.

odacli

and

odaadmcli

commands. A virtualized system

Perform the following steps to determine if you need to re-image Oracle Database Appliance and install the Virtualization Platform ISO image:

5-1

Page 72

Chapter 5

Setting Up the Virtualized Platform

1. Log in as

2. To verify that a system is a virtualized platform, enter the command

env_hw

root

# oakcli show env_hw VM-ODA_BASE ODA X7-2-HA

The system is configured as a virtualized system when the command is valid and returns output that is prefixed with the string VM-ODA_BASE. For example, the output of the following command shows that the platform is configured with a virtual machine environment (VM-ODA_BASE) and identifies the hardware platform (ODA X7-2-HA).

If the system is configured as a bare metal platform, then the command

show env_hw

is invalid.

Setting Up the Virtualized Platform

Set up the public network.

You must provision the virtualized operating system image on both nodes, either at the same time, or one after another.

dom0

virtualized operating system on both nodes and configure the initial

oakcli show

oakcli

1. Download the Oracle Database Appliance 18.3 Virtualized OS ISO Image.

a. From an external client machine, log on to My Oracle Support.

b. Locate the patch for the Oracle Database Appliance Virtualized OS ISO

Image. Refer to the Oracle Database Appliance Release Notes for the patch number.

c. Select the patch version for release 18.3.

d. Click Download to download the zip file onto your external client. Unzip the

zip file onto external client to get the ISO image.

2. Open a browser and connect to Oracle Integrated Lights Out Manager (ILOM) on

Node0 as root.

The Summary home page appears.

3. Launch the Remote Console.

a. Expand Remote Control in the left navigation.

b. Click the Redirection tab.

c. Click Launch Remote Console.

The state of the system determines what appears on the Console page.

4. Add the Virtualized OS ISO Image.

a. Click the Devices tab, then select CD-ROM.

A file browser on the local client opens.

b. Browse to the Oracle Database Appliance Virtualized OS ISO Image, highlight

the image, then click Open.

5. Configure the CD-ROM as the next boot device.

5-2

Page 73

Setting Up the Virtualized Platform

a. Expand Host Management in the left menu of the ILOM Remote Console tab.

b. Click Host Control.

c. Select CDROM from the Next Boot Device menu, then click Save.

6. Power cycle the system.

a. Click Power Control in the Host Management menu.

b. Select Power Cycle.

When the node comes back after the power cycle, reimaging starts automatically.

It can take a couple of hours to reimage. The Running Post-Install scripts page is a static page and might give the impression that the reimaging process is not progressing. The post-install process during reimaging will wait until the synchronization between the partitions of the two mirrored local hard disks is complete, which can take 15 to 20 minutes to complete.

To check the progress of resynchronization, press the ALT-F2 key combination to open a second console and enter the following command:

# cat /proc/mdstat

Chapter 5

When the resynchronization is complete, reimaging is completed and the machine restarts.

7. Repeat Steps 1 through 6 for Node1.

Reimaging is node-specific. You must reimage both nodes. You can reimage both nodes at the same time.

8. Verify that the host name in the Console is

If the host name is something other than

oak1

for Node0 and

oak1

oak2

for Node1.

oak2

, then reboot the node. You

might need to reboot more than once.

Once the image is completed on both nodes, you will see the screen with

oak1

Node0 (sc0). Note: Ensure that you provide the node numbers for both nodes during the reboot. Specify node number 0 for the first node and node number 1 for the second node.

9. Use the command oakcli configure firstnet to configure a

global

network. For local network, run the command on both nodes. For global

local

network, run the command on any one node.

The global configuration sets the initial public network for both the nodes on Oracle Database Appliance, enabling you to download the deployment software onto the appliance.

# oakcli configure firstnet

Configure the network for the node(s)(local, global) [global]: The network configuration for both nodes: Domain Name: test.com DNS Server(s): Primary Dns Server: 192.0.2.18 Secondary Dns Server: 192.0.2.19 Tertiary Dns Server: Node Name Host Name 0 node1 1 node2 Choose the network interface to configure (net1, net2) [net1]:

for

5-3

Page 74

Chapter 5

Installing Virtualized Platform Software and Deploying the Appliance

Configure DHCP on net1 (yes/no) [no]: INFO: You have chosen static configuration on net1 Enter the IP address for net1 on Node 0: 192.0.2.20 Enter the IP address for net1 on Node 1: 192.0.2.21 Netmask for net1: 192.0.2.20 Gateway Address for net1 [192.0.2.20]: INFO: Plumbing the IPs now on Node 0 ... INFO: Restarting the network now on Node 0 ... Determining if ip address 192.0.2.20 is already in use for device net1... ::::::::::::::::::::::::::::::::::: INFO: Plumbing the IPs now on Node 1 ... INFO: Restarting the network now on Node 1 ... :::::::::::::::::::::::::::::::::::

10. Check the IP addresses to the nodes with the command oakcli show

firstnet.

# oakcli show firstnet

Node: 0 Host Name: odax7-2ha-brm06-a-n0 Domain Name: example.com Network BootProto IP Address Subnet Gateway

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

-----------net1 static 192.0.2.18 255.255.252.0 192.0.2.1

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

-----------Node: 1 Host Name: odax7-2ha-brm06-a-n1 Domain Name: example.com Network BootProto IP Address Subnet Gateway

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

-----------net1 static 192.0.2.18 255.255.252.0 192.0.2.1

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

-----------DNS Address: 192.0.2.18,192.0.2.19

Installing Virtualized Platform Software and Deploying the Appliance

Deploy the ODA_BASE domain for a virtualized platform and then deploy the appliance.

1. Download and copy the template files to the /OVS directory on

a. From an external client machine, log on to My Oracle Support and download

the Oracle Database Appliance VM Template.

b. Select the latest version from the menu.

c. Click Download for each of the zip files to download the current Oracle

Database Appliance template onto your external client.

dom0

(Node 0).

5-4

Page 75

Installing Virtualized Platform Software and Deploying the Appliance

2. Copy the template files to the /OVS directory on Node 0 (oak1-dom0).

a. Use either a Secure Copy (scp) command or a USB storage device to copy

the ODA_BASE template from the external client to

dom0

on Node 0. Use

the /OVS directory on Node 0 (test0-dom0) as the target location.

Note:

If you use a USB drive to transfer the file, then format it first as

FAT32, ext3

, or

ext4

. NTFS file formats are not supported.

Chapter 5

b. Log into

logged in to

c. From the /OVS directory, use the unzip command to extract the zip files.

dom0

root

on Node 0 of Oracle Database Appliance. Remain

dom0

while you complete the remaining steps in this task.

unzip p16186172_183000_Linux-x86-64_1of4.zip unzip p16186172_183000_Linux-x86-64_2of4.zip unzip p16186172_183000_Linux-x86-64_3of4.zip unzip p16186172_183000_Linux-x86-64_4of4.zip

When extracted, you will have the following files:

oda_base_18.3.gz02, oda_base_18.3.gz03

d. Use the cat command to concatenate the files into a single file.

oda_base_18.3.gz01

, and

oda_base_18.3.gz04

The file name is determined by the version. Ensure that you use the correct file name from the download. Do not change the file name.

cat oda_base_18.3.gz01 oda_base_18.3.gz02 oda_base_18.3.gz03

oda_base_18.3.gz04

oda_base_18.3.tar.gz

Make a note of the file name and location. You need to specify the following in the next step:

/OVS/oda_base_18.3.tar.gz

3. (Optional) Define the virtual local area network (VLAN) and deploy ODA_BASE

from the /opt/oracle/oak/bin/ directory. When prompted, enter the absolute path and file name for the template file that you created in the previous step, core licensing, and the base domain memory allocation.

The

deploy oda_base

option automatically deploys ODA_BASE on both nodes.

Values, such as the number of available CPU cores and default memory, differ between Oracle Database Appliance Virtualized Platform hardware platforms. The following excerpt is an example that creates a VLAN named v1200 with a vlanID of 200 using the bond0 interface. The example defines 20 CPU cores, which means that 20 CPU cores are licensed on each node for a total of 40 CPU cores, and uses the default memory.

# /opt/oracle/oak/bin/oakcli create vlan vl200 -vlanid 200 -if bond0 Created vlan vl200

# /opt/oracle/oak/bin/oakcli deploy oda_base Enter the template location: /OVS/oda_base_18.3.tar.gz

5-5

Page 76

Chapter 5

Installing Virtualized Platform Software and Deploying the Appliance

Core Licensing Options:

1. 2 CPU Cores

2. 4 CPU Cores

3. 6 CPU Cores

4. 8 CPU Cores

5. 10 CPU Cores

6. 12 CPU Cores

7. 14 CPU Cores

8. 16 CPU Cores

9. 18 CPU Cores

10. 20 CPU Cores

11. 22 CPU Cores

12. 24 CPU Cores <continued ...> Selection[1 .. 37] (default 74 CPU Cores): 10 INFO: Using the 20 cores DA base domain memory in GB(min 16, max 244)[default 244]: 244 INFO: Using default memory size i.e. 244 GB Additional vlan networks to be assigned to oda_base ? (y/n) [n]: INFO: Deployment in non local mode INFO: Verifying active cores on local node INFO: Verified active cores on local node INFO: Verifying active cores on remote node NFO: Verified active cores on remote node INFO: Running the command to copy the template /OVS/ oda_base_18.3.tar.gz to remote node 1

oda_base_18.3.tar.gz 100% 7475MB 62.8MB/s 01:59 INFO: Spawned the process 17728 in the deployment node 0 INFO: Spawned the process 17729 in the node 1 INFO: Validating LSI HBA PCI Cards on node 0 INFO: Validating LSI HBA PCI Cards on node 0 INFO: Validating LSI HBA PCI Cards on node 1 INFO: Validating LSI HBA PCI Cards on node 1 INFO: Deployment in local mode INFO: Deployment in local mode templateBuild-2017-02-14-23-51/swap.img templateBuild-2017-02-14-23-51/swap.img templateBuild-2017-02-14-23-51/System.img templateBuild-2017-02-14-23-51/System.img templateBuild-2017-02-14-23-51/u01.img templateBuild-2017-02-14-23-51/u01.img INFO: Extracted the image files on node 1 INFO: The VM Configuration data is written to /OVS/Repositories/ odabaseRepo/VirtualMachines/oakDom1/vm.cfg file INFO: Running /sbin/losetup /dev/loop0 /OVS/Repositories/odabaseRepo/ VirtualMachines/oakDom1/System.img command to mount the image file INFO: Mount is successfully completed on /dev/loop0 INFO: Extracted the image files on node 0 INFO: Validated dom0 and odabase version INFO: Making change to the /OVS/Repositories/odabaseRepo/ VirtualMachines/oakDom1 /tmpmnt/boot/grub/grub.conf file INFO: Assigning IP to the second node... INFO: The VM Configuration data is written to /OVS/Repositories/

5-6

Page 77

Chapter 5

Installing Virtualized Platform Software and Deploying the Appliance

odabaseRepo/VirtualMachines/oakDom1/vm.cfg file INFO: Running /sbin/losetup /dev/loop0 /OVS/Repositories/odabaseRepo/ VirtualMachines/oakDom1/System.img command to mount the image file INFO: Mount is successfully completed on /dev/loop0 INFO: Created oda base pool INFO: Validated dom0 and odabase version INFO: Making change to the /OVS/Repositories/odabaseRepo/ VirtualMachines/oakDom1 /tmpmnt/boot/grub/grub.conf file INFO: Assigning IP to the first node... INFO: Created oda base pool INFO: Starting ODA Base... INFO: Starting ODA Base... Using config file "/OVS/Repositories/odabaseRepo/VirtualMachines/ oakDom1/vm.cfg" . Started domain oakDom1 (id=1) INFO: Storing the odabase configuration information Using config file "/OVS/Repositories/odabaseRepo/VirtualMachines/ oakDom1/vm.cfg" Started domain oakDom1 (id=1) INFO: Storing the odabase configuration information #

The ODA_BASE setup is complete.

4. Verify that your deployment of ODA_BASE is valid and that ODA_BASE is

configured.

• Run the command xm list to confirm that ODA_BASE is configured. When

properly deployed,

oakDom1

appears in the output with your configured

memory and vcpus.

# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 4096 40 r----- 482672.4 oakDom1 2 32768 4 b---- 132134.6

• Run the command oakcli show oda_base

# /opt/oracle/oak/bin/oakcli show oda_base ODA base domain ODA base CPU cores :2 ODA base domain memory :32 ODA base template :/OVS/oda_base_18.3.tar.gz ODA base vlans :[ 'priv1', 'net1'] ODA base current status :Running

5-7

Page 78

Chapter 5

Installing Virtualized Platform Software and Deploying the Appliance

5. (Optional) After deployment of oda_base, if you want to change CPU or memory of

ODA_BASE, run oakcli configure oda_base:

# oakcli configure oda_base

Core Licensing Options:

1. 2 CPU Cores

2. 4 CPU Cores

3. 6 CPU Cores

4. 8 CPU Cores

5. 10 CPU Cores

6. 12 CPU Cores

7. 14 CPU Cores

8. 16 CPU Cores Current CPU Cores :10 Selection[1 .. 8](default 16 CPU Cores) : 5 ODA base domain memory in GB(min 16, max 244)(Current Memory 160G)[default 160] : 100 Additional vlan networks to be assigned to oda_base ? (y/n) [n]: n Vlan network to be removed from oda_base ? (y/n) [n]: n

To ensure your changes are reflected in the system, run the oakcli restart oda_base command.

6. Validate that the cabling is connected correctly.

# oakcli validate -c storagetopology

The command displays errors if the cables between the two nodes and the storage shelf or shelves are not in the correct sockets.

Caution:

Do not ignore any errors or warnings in the output. If the cabling validation fails, connect the cables correctly and rerun the command until the command runs without any errors or warnings. Do not deploy Oracle Database Appliance until the cabling is correct.

If the output includes a warning for jbod nickname, then run the command from the first node to correct the warning. Rerun the command again to verify that the command runs without the warning.

SUCCESS : Overall Cable Validation on Node1 WARNING : JBOD0 Nickname is incorrectly set to : Oracle Database Appliance - E1 WARNING : JBOD1 Nickname is incorrectly set to : Oracle Database Appliance - E0 INFO : Above details can also be found in log file=/tmp/StorageTopology-2015-05-13-15:03:36_29149_8856.log

7. Connect to ODA_BASE using vncviewer or vncsession using the

dom0

host name

and port 5900 (test0-dom0:5900).

8. Use the oakcli configure firstnet to configure an initial public network on

the first node (Node 0) to complete the ODA_BASE deployment.

5-8

Page 79

Installing Virtualized Platform Software and Deploying the Appliance

a. ssh to 192.168.16.27 from test0-dom0

Chapter 5

b. Log in as c. Run the command oakcli configure firstnet from the

oracle/oak/oakcli

root

user.

/opt/

directory. Enter the ODA_BASE (Node 0) network

information.

The command uses an interactive script and prompts you for the information needed to configure the network. Enter values based on your environment requirements.

When prompted to configure the network nodes, select the

local

option that

configures the network on the logged-on node. Configure net1 as the network interface.

# /opt/oracle/oak/bin/oakcli configure firstnet

Select the Interface to configure the network on (eth1 eth2) [eth1]: Configure DHCP on eth1 (yes/no) [no]: INFO: You have chosen Static configuration Enter the IP address to configure : ip_odabase_node Enter the Netmask address to configure : ip_netmask Enter the Gateway address to configure : ip_gateway

The IP address is plumbed and the network is restarted on the local node.

9. Check the firmware versions on both nodes with the following command:

[root@test0 ~]# oakcli show version -detail

10. If all the component versions are not either up-to-date or at a higher version, then

unpack the patch bundle on both nodes.

[root@test0 tmp]# oakcli unpack -package patch_number

11. Use the oakcli update command to update the server components such as

disks, ILOM, BIOS, and firmware.

[root@test0 tmp]# oakcli update -patch release_number --server

INFO: DB, ASM, Clusterware may be stopped during the patch if required INFO: Both Nodes may get rebooted automatically during the patch if required Do you want to continue: [Y/N]?: y INFO: User has confirmed for the reboot INFO: Patch bundle must be unpacked on the second Node also before applying the patch Did you unpack the patch bundle on the second Node? : [Y/N]? : y INFO: All the VMs except the oda_base will be shutdown forcefully if needed Do you want to continue : [Y/N]? : y INFO: Running pre-install scripts INFO: Running prepatching on node 0 INFO: Running prepatching on node 1 oakcli update -patch release_number --storage

[root@test0 ~]# oakcli update -patch release_number --storage

WARNING: OAKD is not running in foreground mode.

5-9

Page 80

Chapter 5

Installing Virtualized Platform Software and Deploying the Appliance

INFO: Cannot determine if VM's or shared repos are running. INFO: Patching may not shutdown all VMs/repos before patching Do you want to continue: [Y/N]?: y INFO: Proceeding with patching... INFO: DB, ASM, Clusterware may be stopped during the patch if required INFO: Both Nodes may get rebooted automatically during the patch if required Do you want to continue: [Y/N]?: y INFO: User has confirmed for the reboot Please enter the 'root' password : Please re-enter the 'root' password: INFO: Setting up the SSH

............Completed

INFO: Running pre-install scripts

............Completed

INFO: Running prepatching on node 0 INFO: Running prepatching on node 1 INFO: Completed pre-install scripts INFO: Shared Storage components need to be patched INFO: Patching storage on node 192.168.16.28

12. After the firmware patching is completed, confirm that all appropriate components

are updated

# oakcli show version -detail

13. Deploy the Oracle Grid Infrastructure and Oracle Database software on the

appliance.

a. Confirm you are in ODA_BASE:

For example:

# oakcli show env_hw

VM-oda_base ODA X7-2 HA # vncserver You will require a password to access your desktops. Password: Verify: New 'test0:1 (root)' desktop is test0:1 Creating default startup script /root/.vnc/xstartup Starting applications specified in /root/.vnc/xstartup Log file is /root/.vnc/test0:1.log

b. Connect to ODA_BASE (Node 0) in the vnc session.

c. Navigate to the

/opt/oracle/oak/bin

directory and execute the command

oakcli deploy to start the Oracle Database Appliance Manager Configurator.

# /opt/oracle/oak/bin/oakcli deploy

The Oracle Appliance Manager Welcome window is displayed.

14. Click Next on the Oracle Appliance Manager Welcome window.

15. Complete the Configuration Type.

5-10

Page 81

Chapter 5

Installing Virtualized Platform Software and Deploying the Appliance

• If you want to use a configuration file that you created earlier with this version

of the Configurator, then click Browse and locate the file on your client. Click Next.

• If you do not have a configuration file, select the Typical configuration type

and select the hardware model from the menu. Click Next.

16. Enter or review the configuration details for your system, network, and database

information. For details, see “Running the Standalone Oracle Database Appliance Configurator”.

17. Validate your network on the Network Validation page.

a. Click Run Validations to perform network validation.

b. Click Save Validation Output to save the validation output.

c. Click Next

18. On the Summary page, review your configuration options and deploy your

configuration.

a. (Optional) Click Save to save the configuration file.

b. Click Install to deploy the configuration.

The deployment can take an hour to complete. Monitor the install progress. When the deployment is complete, go to the next step.

19. Validate the deployment by executing the oakcli show version -detail

command on ODA_BASE (Node 0).

# /opt/oracle/oak/bin/oakcli show version -detail

The output displays the System Version, Component Name, Installed Version, and Supported Version for each of the components.

5-11

Page 82

Creating a Configuration File for a Virtualized Platform

20. If you configured ASR, then verify the deployment, by running the following the

command on Node0:

# oakcli test asr

Creating a Configuration File for a Virtualized Platform

If you want to use the Configurator to create a virtualized platform configuration file before your Oracle Database Appliance system is delivered, then review these topics.

• About the Standalone Oracle Database Appliance Configurator

Use the standalone Oracle Database Appliance Configurator to create an Oracle Database Appliance Virtualized Platform offline deployment plan and validate your network settings before the actual deployment.

• Running the Standalone Oracle Database Appliance Configurator

Download and run the standalone Oracle Database Appliance Configurator to create a configuration file for the Oracle Database Appliance Virtualization Platform.

Chapter 5

About the Standalone Oracle Database Appliance Configurator

If you prefer to configure your system at the time you deploy the virtualized platform, then you can wait and use the online Configurator that is part of virtualization image for Oracle Database Appliance.

The standalone Oracle Appliance Manager Configurator is a Java-based tool that enables you to generate your virtualized platform deployment plan and validate your network settings before the actual deployment. If you want to use this tool before deployment, then you must download and run the Configurator on a local client system. The local client can be a Linux, UNIX, MAC, or Windows system, and must be on the same network as the appliance.

The Configurator provides two types of configuration: Typical and Custom. The Typical configuration is recommended in most cases. Choose the Custom configuration option if you want to configure additional or alternate network interfaces, or if you want to override the default values for one or more of the following:

• Database block size, language, territory, backup file location, or disk redundancy

level for the DATA and RECO disk groups

• Oracle Integrated Lights Out Manager (Oracle ILOM) server.

• Oracle Auto Service Request (Oracle ASR) configuration. You can configure

Oracle ASR after deployment.

• Oracle Cloud File System mount point and file system size. Configure a Cloud FS

if you want a non-database file location accessible by both nodes.

• Network Time Protocol service server.

To see the default values for your version of Oracle Database Appliance software before choosing the Typical or Custom option, run the Configurator using the Custom option.

5-12

Page 83

Creating a Configuration File for a Virtualized Platform

Oracle recommends that you use the Network Validation page in the Configurator to test your network settings. To test the network settings, you must run the Configurator on a client server that is connected to same network subnet that you intend to use for Oracle Database Appliance. If you do not do this, then the validation fails, regardless of whether or not you have completed required configuration.

At the end of an offline Configurator session, you can save your deployment plan in a configuration file. You can use the Configurator to edit your settings. When you are ready to deploy Oracle Database Appliance, copy this configuration file to the appliance, and run the online Oracle Appliance Manager Configurator to import and deploy your saved plan. You can also print the file's content and use the printout to review your configuration entries for deployment planning purposes and as a checklist for setting up your external network configuration.

Running the Standalone Oracle Database Appliance Configurator

Download and run the standalone Oracle Database Appliance Configurator to create a configuration file for the Oracle Database Appliance Virtualization Platform.

In most cases, Oracle recommends that you select the typical configuration. Select the custom option if you want to configure additional or alternate network interfaces, or if you want to override the default values. To see the default values for your version of Oracle Database Appliance software before choosing the Typical or Custom option, run the Configurator using the Custom option.

Chapter 5

The steps described here enable you to create a typical virtualized platform configuration file.

1. Download the standalone Oracle Database Appliance Manager Configurator

software to a client.

a. Go to the following URL

database-appliance/overview/index.html

b. Click the Downloads tab.

c. Review the License Agreement, then select Accept License Agreement.

d. Download the latest version of the Oracle Database Appliance Manager

Configurator zip file to a client.

e. Extract the files from the zip.

2. Start the Configurator using the command

command Appliance Manager Welcome page appears, click Next.

3. Select the Custom configuration type and select the hardware model from the

menu. Click Next.

The Browse option is not useful during the initial run, because there are no configuration files to load. If you have an existing configuration file created with this version of the Configurator that you want to load and edit, then click Browse and locate the file on your client.

./config.sh

http://www.oracle.com/technetwork/database/

config.bat

on a Linux or UNIX client. When the Oracle Database

on a Windows client, or the

5-13

Page 84

Chapter 5

Creating a Configuration File for a Virtualized Platform

4. On the System Information page, provide the system name, and select the correct

value from the lists for your region and time zone. In the New Root Password and New Root Password (confirm) fields, enter a new password for the

root

user.

Click Next.

The password is encrypted in the configuration file. It is temporarily decrypted to reset the password during deployment.

5-14

Page 85

Creating a Configuration File for a Virtualized Platform

5. On the Network Information page, provide your domain name, DNS server

addresses, public and VIP addresses for your two nodes, SCAN name and addresses, and netmask and Gateway addresses. Click Next.

Chapter 5

As you enter data on this page, some fields are automatically filled with values derived from earlier entries. For example, if the address that you provide for the Node 0 public IP address is 192.0.2.18, then the default node addresses generate as follows:

• Node 0 public IP address: 192.0.2.18

• Node 1 public IP address: 192.0.2.19

• Node 0 virtual IP (VIP) address: 192.0.2.20

• Node 1 virtual IP (VIP) address: 192.0.2.21

• SCAN addresses (two addresses resolving to the SCAN VIP name):

192.0.2.22, 192.0.2.23

6. (Optional) On the Database Information page, determine if you want to create an

initial database.

• If you do not want to configure an initial database, then click Next. Go to Step

• If you want to configure an initial database, select the check box for Create

Initial Database, complete the fields, then click Next.

To configure an initial database, provide the following database details:

• Database Name. Enter a name for the database.

• Is Container Database. The default is false. If you leave the default value,

then the Configurator builds a non-container database.

5-15

Page 86

Chapter 5

Creating a Configuration File for a Virtualized Platform

• Database Type. The default type is OLTP. You can also select DSS, or select

In-Memory.

• Database Class. Select the database class that you want to deploy. Not all

options are available for all models of Oracle Database Appliance; the default class is odb-06.

• Database Language. The default language is AMERICAN

• Database Deployment. Select one of the following, where RAC is the default:

– Oracle RAC

– Oracle RAC One Node

– Oracle Database Enterprise Edition (no Oracle RAC)

• Data File Size (GB). If you indicate that you want to build a container

database, then provide a database data file size in the final field on this page. (This field does not accept input unless the Is Container Database selection is True.)

• Data Files on Flash Storage. This option is not available on the X7-2-HA

model.

7. On the Network Validation page, validate your network settings and save the

validation output in a file, or bypass the validation step, then click Next to go to the next step.

The following options are available:

• Click Run Validations to perform network validation.

5-16

Page 87

Chapter 5

Creating a Configuration File for a Virtualized Platform

Note:

Oracle recommends that you validate your network before you use the configuration file to configure an appliance. However, you must run Oracle Database Appliance Manager Configurator on a server attached to the network subnet that is configured for your appliance. If you do not do this, then the validation fails, regardless of whether or not you have completed required configuration.

• Click Save Validation Output to save the validation output. If the validation

fails, it is useful to save the output to review with your network administrator later.

• Select Skip Network Validations to by-pass the validation step. If the network

validation fails, and you want to continue with the configuration, then select this option.

8. On the Summary page, review the configuration options that you have selected.

Click Save to save the configuration file. Click Finish.

Note the name and location of the configuration file. You can copy this configuration file to your Oracle Database Appliance for deployment. If you need to make corrections before deployment, then rerun the standalone Oracle Database Appliance Manager Configurator, load your configuration file, make the changes, and save the file again.

5-17

Page 88

Chapter 5

Creating a Configuration File for a Virtualized Platform

If you are running the Configurator on Oracle Database Appliance, and you have completed the preliminary steps to configure your initial network and install the software or deploy ODA_BASE, then you can click Install to deploy the configuration.

5-18

Page 89

Oracle Database Appliance Postinstallation Tasks

Complete these administrative tasks after you have deployed software, but before the system is operational.

• Configuring CPU Core Count

Oracle Database Appliance is delivered with all 36 cores on each server enabled. Follow this procedure to reduce the number of cores, if required.

• Securing Oracle ILOM Service Processors

Change the Oracle ILOM default password after completing Oracle Database Appliance deployment.

• Changing Oracle Database Appliance Passwords

After deploying your appliance, ensure that you change the following passwords for securing your system.

Configuring CPU Core Count

Oracle Database Appliance is delivered with all 36 cores on each server enabled. Follow this procedure to reduce the number of cores, if required.

1. To reduce the number of cores, run the following command on Node 0 only:

Set the cores in multiples of 2, for example, 12:

[root@oak1 opt]# /opt/oracle/dcs/bin/odacli update-cpucore --cores 12

2. Check if the job completed successfully:

[root@oak1 opt]# /opt/oracle/dcs/bin/odacli describe-job -i job_ID

3. Verify that the core count is updated on both nodes:

[root@oak1 opt]# /opt/oracle/dcs/bin/odacli describe-cpucore

Securing Oracle ILOM Service Processors

Change the Oracle ILOM default password after completing Oracle Database Appliance deployment.

Do not change the default password until after you have completed software deployment on the Oracle Appliance.

6-1

Page 90

Changing Oracle Database Appliance Passwords

Changing Oracle ILOM Password from the Console

1. In the Oracle ILOM console, from the Administration menu, select User

Management, and then navigate to the User Accounts subtab.

2. Select root user and click Edit.

Chapter 6

3. Change the

Changing Oracle ILOM Password Using CLI Commands

1. Connect to the Oracle ILOM console through SSH:

# ssh -l root SP-ipaddr

2. Set the new password:

# set /SP/users/root password=new_password Changing password for user /SP/users/root/password... Enter new password again: ********* New password was successfully set for user /SP/users/root

root

user password.

Changing Oracle Database Appliance Passwords

After deploying your appliance, ensure that you change the following passwords for securing your system.

Changing the Oracle Installation Owner Passwords

During deployment, the root and database users SYS, SYSTEM and PDBADMIN are set to the system password. After deployment, the oracle and grid passwords are also set to the system password. Change the passwords to comply with your enterprise user security protocols. Refer to the Oracle Database Appliance Security Guide and Oracle Database Security Guide for information about the required configuration and best practices to secure database systems.

Changing the oda-admin User Password through the Command-Line

1. Log in to the appliance as

2. Run the

new password when prompted.

# odacli-adm set-credential --password --username oda-admin Agent password: new password

Changing the the oda-admin User Password through the Web Console

1. Log into the Web Console using the user name

2. Click About, then User Settings in the upper right corner of the Web Console.

3. Enter the password in the Password field and the Password Confirmation field,

then click Submit.

A confirmation message is displayed.

odacli-adm set-credential

root

command to reset the password. Enter the

oda-admin

6-2

Page 91

Changing Oracle Database Appliance Passwords

4. Click About, then click Sign Out.

5. Log back into the Web Console with the new password.

Chapter 6

6-3

Page 92

Patching Oracle Database Appliance

To keep Oracle Database Appliance running with the latest software, check for and apply Oracle Database Appliance patch bundles when they are released.

• About Patching Oracle Database Appliance

Use the Oracle Database Appliance Patch Bundle to patch your appliance.

• About Migrating Oracle Database Appliance to the DCS Stack

When you apply the patches for this release, your bare metal deployments of Oracle Database Appliance are migrated from the OAK stack to the DCS stack.

• About Update Pre-Checks

Update pre-checks are designed to detect problems that might be encountered during patching and flag those issues.

• Running Update Pre-Checks Before Applying Patches

After updating the repository with patches, use the pre-checks to reduce potential update problems, and then apply patches.

• Patching Oracle Database Appliance Using the Web Console

Upload Oracle Database Appliance Patch Bundle to the patch repository, and deploy the patch bundle using the Web Console.

• Patching Database Homes to the Latest Release

Use the Web Console to upgrade database homes to the latest release.

• Patching Oracle Database Appliance Bare Metal Systems Using the Command-

Line

Follow these steps to apply patches to Oracle Database Appliance OAKCLI bare metal system using CLI commands.

• Patching Oracle Database Appliance Virtualized Platform

Follow these steps to apply patches to Oracle Database Appliance OAKCLI Virtualized Platform using CLI commands.

• Patching Trace File Analyzer (TFA) Collector

Trace File Analyzer (TFA) Collector simplifies diagnostic data collection on Oracle Cluster Ready Services (CRS), Oracle Grid Infrastructure, and Oracle RAC systems.

• Adding Repositories for Patch Updates

Add patch repositories to update operating system RPMs.

About Patching Oracle Database Appliance

Use the Oracle Database Appliance Patch Bundle to patch your appliance.

Patches offer new features and may improve the functionality of existing features.

About Oracle Database Appliance Patch Bundles

The Oracle Database Appliance Patch Bundle contains the latest patches for DCS Agent, DCS Controller, OAK, GI, RDBMS homes, enhancements, and fixes.

7-1

Page 93

Chapter 7

About Patching Oracle Database Appliance

The Oracle Database Appliance Release Notes include information about the latest Oracle Database Appliance patch bundle and a list of component versions in the patch bundle. Oracle recommends updating the appliance with the latest Oracle Database Appliance software version to take advantage of new features, fixes, and the latest supported component versions. See the Oracle Database Appliance Release Notes for the upgrade paths.

Caution:

Do not patch Oracle Database Appliance using individual patches for Oracle Grid Infrastructure, Oracle Database, or Oracle Linux. Also do not use individual infrastructure patches, such as firmware patches. You must only use Oracle Database Appliance patches. If you use patches that are not intended for Oracle Database Appliance, or if you use Opatch, or a similar patching tool, then Oracle Database Appliance inventory is not updated, and you cannot complete future patch updates.

The patch bundle provides all relevant patches for the entire system, including the following:

• BIOS

• Hardware drivers

• Hardware Management Pack (HWM), and firmware drivers for various

components

• Oracle Appliance Manager

• Oracle Linux

• Oracle VM Server

• Java Development Kit (JDK)

• Oracle Integrated Lights Out Manager (Oracle ILOM)

• Oracle Database Bundle Patch (BP) and Oracle Database Patch Set Update

(PSU)

• Oracle Auto Service Request (Oracle ASR)

• Oracle Grid Infrastructure

• Intelligent Platform Management Interface (IPMI)

• Network Card Patches for relevant hardware models

About Network Card and Firmware Patching

On Oracle Database Appliance X7-2 hardware models, when connected to 10G/Fiber network, the error "No Link" is encountered. To fix this issue, the network card patch is included in the Oracle Database Appliance Bundle Patch for 18.3. No separate update or patch is required.

About Updating Oracle Linux RPMs

While not recommended, you can update some Oracle Linux RPMs for database nodes. Do not update or customize Oracle Linux kernel, Oracle Optimal Flexible Architecture, Oracle InfiniBand, or related software. Other software may be installed,

7-2

Page 94

Chapter 7

About Migrating Oracle Database Appliance to the DCS Stack

updated, or customized. However, the Oracle Database Appliance update may not carry newer version dependencies of customized components. Therefore, you might be required to remove and subsequently reapply site-specific changes to successfully update Oracle Database Appliance in the future.

Caution:

For database nodes, do not update the following:

• Oracle Linux Kernel (kernel*)

• Oracle Optimal Flexible Architecture (ofa*)

• Oracle InfiniBand-related packages (ofed*)

For storage, do not apply any RPM updates.

About Using a Different Version of Java Development Kit (JDK)

Oracle Database Appliance depends on a specific version of JDK. If you want to use a different version of JDK for a specific application, then install it in a different directory and only point to it for that application.

About Migrating Oracle Database Appliance to the DCS Stack

When you apply the patches for this release, your bare metal deployments of Oracle Database Appliance are migrated from the OAK stack to the DCS stack.

No additional configuration steps are required. You migrate the Oracle Database Appliance bare metal system to the DCS stack when you apply the latest patches.

Note:

When you migrate Oracle Database Appliance bare metal system to the DCS stack, the Database Class is set to Online Transaction Processing (OLTP) and the Database Shape is set to

See ODACLI Command Reference for OAKCLI Migration for the equivalent ODACLI and OAKCLI commands.

odb1

, by default.

About Update Pre-Checks

Update pre-checks are designed to detect problems that might be encountered during patching and flag those issues.

The pre-checks view the state of the appliance, including the version and hardware specific upgrades, verify that the necessary conditions and checks are complete before attempting an upgrade, and identify conditions that might cause an upgrade to

7-3

Page 95

Chapter 7

About Update Pre-Checks

fail. You can avoid potential patching problems by correcting the conditions and resolving the issues before applying the patch.

The pre-checks commands are available on Oracle Database Appliance release

12.2.1.2.0 or later. Update the DCS agent to support the pre-checks commands.

Note:

Patching pe-checks are available only when patching ODACLI stack. If you are patching and migrating from OAKCLI to ODACLI stack for bare metal system, then follow the procedure in the topic Patching Oracle Database Appliance Bare Metal Systems Using the Command-Line. For patching Virtualized Platform, see the topic Patching Oracle Database Appliance Virtualized Platform.

Components Verified by Patching Pre-Checks

Check Component Verified

System update pre-checks Checks that the agent is online on all nodes

Checks that there is sufficient space for the update

Validates the minimum agent version and validates the patching tag

Confirms that a valid patch is in the repository and calculates the patch bundle

checksum

Server update pre-checks Confirms that Oracle Grid Infrastructure patch

is installed

Confirms that Oracle Clusterware is running on all nodes

Performs a check for required components using

opatch prereq checkcomponents

Analyzes the patch using

Performs a patch conflict check

Checks the available disk space

Confirms that the yum repository directory exists

Performs a

yum

check and

update

Performs a test (dry run) yum update to check for dependencies in the RPMS

md5

opatchauto

yum check-

7-4

Page 96

Chapter 7

Running Update Pre-Checks Before Applying Patches

Check Component Verified

DBHome update pre-checks Confirms that the Oracle Grid Infrastructure is

installed

Confirms that Oracle Clusterware is running on all nodes

Confirms that the Oracle Grid Infrastructure is upgraded before upgrading other components

Validates that there is sufficient space available in local mount

Performs a check for required components using

opatch prereq checkcomponents

Analyzes the patch using

Performs a patch conflict check and determines if a rollback of database patches is required

Storage pre-checks Validates storage patch location and tag

Validates Oracle ASM disk groups status

opatchauto

Running Update Pre-Checks Before Applying Patches

After updating the repository with patches, use the pre-checks to reduce potential update problems, and then apply patches.

Note:

Follow the procedure in this topic only when patching ODACLI stack. If you are patching and migrating from OAKCLI to ODACLI stack for bare metal system, then follow the procedure in the topic Patching Oracle Database Appliance Bare Metal Systems Using the Command-Line. For patching Virtualized Platform, see the topic Patching Oracle Database Appliance Virtualized Platform.

1. Run the

odacli create-prepatchreport -s -v release_number

2. Run the

odacli describe-prepatchreport -i job_ID

create-prepatchreport

describe-prepatchreport

command to generate a pre-check report.

command to display the pre-check report.

7-5

Page 97

Patching Oracle Database Appliance Using the Web Console

Upload Oracle Database Appliance Patch Bundle to the patch repository, and deploy the patch bundle using the Web Console.

Note:

Updating the Patch Repository Using the Web Console

Chapter 7

1. Download the Oracle Database Appliance patches from My Oracle Support and

save them in a directory on the appliance. See the Oracle Database Appliance Release Notes for a list of available patches and links to download the patches.

2. Log into the Web Console with the oda-admin user name and password.

https://Node0–host-ip-address:7093/mgmt/index.html

3. Click Patch Manager.

4. In the Update Patch Repository page, enter the absolute file path and patch name,

then click Update Repository to start the update repository job. You can list more than one file to update to the repository with a comma separated list, without spaces, or you can update each file, one at a time.

5. Click Activity to monitor the progress. When the job completes successfully, the

Patch Repository is updated.

Running Update Prechecks and Patching Agent, Server, and Storage Using the Web Console

Note:

If your appliance has two nodes, you have the option to update both nodes at the same time or individually. If updating individually, update Node0 before updating Node1.

1. Do not have any jobs running or pending during the update window.

2. Click the Appliance tab, and then click Patch Manager in the Web Console.

3. Wait for the Component Details to load. If you just updated the Patch Repository,

click Refresh in the Component Details section of the page.

7-6

Page 98

Chapter 7

Patching Database Homes to the Latest Release

After the patch is uploaded to the Patch Repository, the Component Details on the page are updated with the Installed Version and Available Version for each component.

4. Select Precheck, click Update Components, then click Submit to verify the

patches in the repository and check for conflicts.

When the job finishes, go to the next step. Click Activity for job status.

5. On the Patch Manager page, click Refresh to refresh the Component Details.

Select Update Server, click Update Components, then click Submit to begin the job to patch the server components.

For multi-node systems, select the node to update: All Nodes (default), Node0, or Node1.

The DCS agent is automatically updated whenever the Server or Storage components are updated.

When the job finishes, go to the next step. Click Activity for job status.

6. On the Patch Manager page, click Refresh to refresh the Component Details.

Select Update Storage, click Update Components, then click Submit to begin the job to patch the storage components.

For multi-node systems, select the node to update: All Nodes (default), Node0, or Node1.

For high-availability environment, you can select the Rolling check box to perform rolling patching of storage components.

7. Click Activity to monitor the progress, and verify that the job completes

successfully.

All patching-related information is logged in the

oracle/dcs/log/dcs-agent.log

dcs-agent

log file at

Patching Database Homes to the Latest Release

Use the Web Console to upgrade database homes to the latest release.

Note:

/opt/

Before upgrading to a different database home, upload the RDBMS Clone Files for the database version, to the repository and then create the database home. See Patching Oracle Database Appliance Using the CLI for the procedure to update the repository with the latest RDBMS Clone Files.

1. Log into the Web Console with the oda-admin user name and password.

https://Node0–host-ip-address:7093/mgmt/index.html

7-7

Page 99

Chapter 7

Patching Oracle Database Appliance Bare Metal Systems Using the Command-Line

2. Click the Database tab, and then click Patch on the left pane.

3. Click Patch, and then select the Action as Precheck to run pre-checks before

patching the database.

Click Activity for job status.

4. On the Patch page, for the database to be patched, click View and select Pre-

patch reports to view the pre-check report. Fix any errors, and then select Action as Apply to patch the database.

5. Verify that the patching job completes successfully.