grid infrastructure installation and upgrade guide · 2019. 11. 4. · the information contained...

Oracle® Grid InfrastructureGrid Infrastructure Installation and UpgradeGuide

19c for Oracle SolarisE96273-04November 2019

Oracle Grid Infrastructure Grid Infrastructure Installation and Upgrade Guide, 19c for Oracle Solaris

E96273-04

Copyright © 2014, 2019, Oracle and/or its affiliates. All rights reserved.

Primary Author: Subhash Chandra

Contributing Authors: Aparna Kamath, Douglas Williams, Mark Bauer, Prakash Jashnani

Contributors: Jonathan Creighton, Mark Fuller, Rajesh Dasari, Pallavi Kamath, Donald Graves, DharmaSirnapalli, Allan Graves, Barbara Glover, Aneesh Khandelwal, Saar Maoz, Markus Michalewicz, IanCookson, Robert Bart, Lisa Shepherd, James Spiller, Binoy Sukumaran, Preethi Vallam, Neha Avasthy, PeterWahl

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense 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 forinteroperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou 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 onbehalf 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 agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of theprograms, 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 thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.

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

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused 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 MicroDevices. 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 expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not beresponsible 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.

Contents

PrefaceAudience xv

Documentation Accessibility xv

Set Up Java Access Bridge to Implement Java Accessibility xvi

Related Documentation xvi

Conventions xvi

1 Oracle Grid Infrastructure Installation ChecklistServer Hardware Checklist for Oracle Grid Infrastructure 1-1

Operating System Checklist for Oracle Grid Infrastructure on Oracle Solaris 1-2

Server Configuration Checklist for Oracle Grid Infrastructure 1-3

Network Checklist for Oracle Grid Infrastructure 1-3

User Environment Configuration Checklist for Oracle Grid Infrastructure 1-6

Storage Checklist for Oracle Grid Infrastructure 1-7

Cluster Deployment Checklist for Oracle Grid Infrastructure 1-9

Installer Planning Checklist for Oracle Grid Infrastructure 1-10

2 Checking and Configuring Server Hardware for Oracle GridInfrastructure

Logging In to a Remote System Using X Window System 2-1

Checking Server Hardware and Memory Configuration 2-2

3 Automatically Configuring Oracle Solaris with Oracle DatabasePrerequisites Packages

About the Oracle Database Prerequisites Packages for Oracle Solaris 3-1

Checking the Oracle Database Prerequisites Packages Installation 3-2

Installing the Oracle Database Prerequisites Packages for Oracle Solaris 3-3

iii

4 Configuring Oracle Solaris Operating Systems for Oracle GridInfrastructure

Guidelines for Oracle Solaris Operating System Installation 4-2

Reviewing Operating System and Software Upgrade Best Practices 4-2

General Upgrade Best Practices 4-2

New Server Operating System Upgrade Option 4-3

Oracle ASM Upgrade Notifications 4-4

Reviewing Operating System Security Common Practices 4-4

About Installation Fixup Scripts 4-4

About Operating System Requirements 4-5

Operating System Requirements for Oracle Solaris on SPARC (64-Bit) 4-5

Supported Oracle Solaris 11 Releases for SPARC (64-Bit) 4-6

Operating System Requirements for Oracle Solaris on x86–64 (64-Bit) 4-7

Supported Oracle Solaris 11 Releases for x86-64 (64-Bit) 4-8

Additional Drivers and Software Packages for Oracle Solaris 4-8

Installing Oracle Messaging Gateway 4-9

Installation Requirements for ODBC and LDAP 4-9

About ODBC Drivers and Oracle Database 4-10

Installing ODBC Drivers for Oracle Solaris 4-10

About LDAP and Oracle Plug-ins 4-10

Installing the LDAP Package 4-10

Installation Requirements for Programming Environments for Oracle Solaris 4-10

Installation Requirements for Web Browsers 4-11

Checking the Software Requirements for Oracle Solaris 4-12

Verifying Operating System Version on Oracle Solaris 4-12

Verifying Operating System Packages on Oracle Solaris 4-13

About Oracle Solaris Cluster Configuration on SPARC 4-13

Running the rootpre.sh Script on x86 with Oracle Solaris Cluster 4-14

Enabling the Name Service Cache Daemon 4-15

Setting Network Time Protocol for Cluster Time Synchronization 4-15

Using Automatic SSH Configuration During Installation 4-17

5 Configuring Networks for Oracle Grid Infrastructure and OracleRAC

About Oracle Grid Infrastructure Network Configuration Options 5-2

Understanding Network Addresses 5-2

About the Public IP Address 5-3

About the Private IP Address 5-3

About the Virtual IP Address 5-4

iv

About the Grid Naming Service (GNS) Virtual IP Address 5-4

About the SCAN 5-5

About Shared SCAN 5-6

Network Interface Hardware Minimum Requirements 5-6

Private IP Interface Configuration Requirements 5-7

IPv4 and IPv6 Protocol Requirements 5-8

Oracle Grid Infrastructure IP Name and Address Requirements 5-9

About Oracle Grid Infrastructure Name Resolution Options 5-10

Cluster Name and SCAN Requirements 5-11

IP Name and Address Requirements For Grid Naming Service (GNS) 5-11

IP Name and Address Requirements For Multi-Cluster GNS 5-11

About Multi-Cluster GNS Networks 5-12

Configuring GNS Server Clusters 5-12

Configuring GNS Client Clusters 5-13

Creating and Using a GNS Client Data File 5-13

IP Name and Address Requirements for Manual Configuration of Cluster 5-14

Confirming the DNS Configuration for SCAN 5-15

Broadcast Requirements for Networks Used by Oracle Grid Infrastructure 5-16

Multicast Requirements for Networks Used by Oracle Grid Infrastructure 5-16

Domain Delegation to Grid Naming Service 5-16

Choosing a Subdomain Name for Use with Grid Naming Service 5-17

Configuring DNS for Cluster Domain Delegation to Grid Naming Service 5-17

Configuration Requirements for Oracle Flex Clusters 5-18

Understanding Oracle Flex Clusters 5-18

About Oracle Flex ASM Clusters Networks 5-19

General Requirements for Oracle Flex Cluster Configuration 5-20

Oracle Flex Cluster DHCP-Assigned Virtual IP (VIP) Addresses 5-21

Oracle Flex Cluster Manually-Assigned Addresses 5-21

Grid Naming Service Cluster Configuration Example 5-22

Manual IP Address Configuration Example 5-23

Network Interface Configuration Options 5-24

6 Configuring Users, Groups and Environments for Oracle GridInfrastructure and Oracle Database

Creating Groups, Users and Paths for Oracle Grid Infrastructure 6-1

Determining If an Oracle Inventory and Oracle Inventory Group Exist 6-2

Creating the Oracle Inventory Group If an Oracle Inventory Does Not Exist 6-3

About Oracle Installation Owner Accounts 6-3

Restrictions for Oracle Software Installation Owners 6-4

Identifying an Oracle Software Owner User Account 6-5

v

About the Oracle Base Directory for the grid User 6-5

About the Oracle Home Directory for Oracle Grid Infrastructure Software 6-6

Oracle Installations with Standard and Job Role Separation Groups and Users 6-7

About Oracle Installations with Job Role Separation 6-8

Standard Oracle Database Groups for Database Administrators 6-9

Extended Oracle Database Groups for Job Role Separation 6-9

Creating an ASMSNMP User 6-10

Oracle Automatic Storage Management Groups for Job Role Separation 6-10

Creating Operating System Privileges Groups 6-11

Creating the OSASM Group 6-12

Creating the OSDBA for ASM Group 6-12

Creating the OSOPER for ASM Group 6-12

Creating the OSDBA Group for Database Installations 6-13

Creating an OSOPER Group for Database Installations 6-13

Creating the OSBACKUPDBA Group for Database Installations 6-13

Creating the OSDGDBA Group for Database Installations 6-14

Creating the OSKMDBA Group for Database Installations 6-14

Creating the OSRACDBA Group for Database Installations 6-14

Creating Operating System Oracle Installation User Accounts 6-14

Creating an Oracle Software Owner User 6-15

Modifying Oracle Owner User Groups 6-15

Identifying Existing User and Group IDs 6-16

Creating Identical Database Users and Groups on Other Cluster Nodes 6-16

Example of Creating Role-allocated Groups, Users, and Paths 6-18

Example of Creating Minimal Groups, Users, and Paths 6-21

Configuring Grid Infrastructure Software Owner User Environments 6-22

Environment Requirements for Oracle Software Owners 6-23

Procedure for Configuring Oracle Software Owner Environments 6-23

Checking Resource Limits for Oracle Software Installation Users 6-26

Setting Remote Display and X11 Forwarding Configuration 6-27

Preventing Installation Errors Caused by Terminal Output Commands 6-28

About Using Oracle Solaris Projects 6-29

Enabling Intelligent Platform Management Interface (IPMI) 6-29

Requirements for Enabling IPMI 6-30

Configuring the IPMI Management Network 6-30

Configuring the BMC 6-31

7 Supported Storage Options for Oracle Database and Oracle GridInfrastructure

Supported Storage Options for Oracle Grid Infrastructure 7-1

vi

Oracle ACFS and Oracle ADVM 7-3

Oracle ACFS and Oracle ADVM Support on Oracle Solaris 7-3

Restrictions and Guidelines for Oracle ACFS 7-4

Storage Considerations for Oracle Grid Infrastructure and Oracle RAC 7-5

Guidelines for Using Oracle ASM Disk Groups for Storage 7-6

Guidelines for Using a Network File System with Oracle ASM 7-7

Using Logical Volume Managers with Oracle Grid Infrastructure and Oracle RAC 7-7

About NFS Storage for Data Files 7-8

About Direct NFS Client Mounts to NFS Storage Devices 7-8

8 Configuring Storage for Oracle Grid InfrastructureConfiguring Storage for Oracle Automatic Storage Management 8-2

Identifying Storage Requirements for Oracle Automatic Storage Management 8-2

Oracle Clusterware Storage Space Requirements 8-7

About the Grid Infrastructure Management Repository 8-10

Using an Existing Oracle ASM Disk Group 8-11

About Upgrading Existing Oracle Automatic Storage Management Instances 8-12

Selecting Disks to use with Oracle ASM Disk Groups 8-12

Specifying the Oracle ASM Disk Discovery String 8-13

Creating Files on a NAS Device for Use with Oracle Automatic StorageManagement 8-13

Configuring Storage Device Path Persistence Using Oracle ASMFD 8-15

About Oracle ASM with Oracle ASM Filter Driver 8-15

Guidelines for Installing Oracle ASMFD on Oracle Solaris 8-16

Using Disk Groups with Oracle Database Files on Oracle ASM 8-16

Identifying and Using Existing Oracle Database Disk Groups on Oracle ASM 8-16

Creating Disk Groups for Oracle Database Data Files 8-17

Creating Directories for Oracle Database Files 8-17

Configuring File System Storage for Oracle Database 8-18

Configuring NFS Buffer Size Parameters for Oracle Database 8-19

Checking TCP Network Protocol Buffer for Direct NFS Client 8-19

Creating an oranfstab File for Direct NFS Client 8-20

Enabling and Disabling Direct NFS Client Control of NFS 8-23

Enabling Hybrid Columnar Compression on Direct NFS Client 8-23

Creating Member Cluster Manifest File for Oracle Member Clusters 8-23

Configuring Oracle Automatic Storage Management Cluster File System 8-25

9 Installing Oracle Grid InfrastructureAbout Image-Based Oracle Grid Infrastructure Installation 9-2

Setup Wizard Installation Options for Creating Images 9-3

vii

Understanding Cluster Configuration Options 9-3

About Oracle Standalone Clusters 9-4

About Oracle Cluster Domain and Oracle Domain Services Cluster 9-4

About Oracle Member Clusters 9-5

About Oracle Extended Clusters 9-7

Installing Oracle Grid Infrastructure for a New Cluster 9-8

About Oracle Grid Infrastructure Installation 9-8

Installing Oracle Standalone Cluster 9-9

Installing Oracle Domain Services Cluster 9-15

Installing Oracle Member Clusters 9-21

Installing Oracle Grid Infrastructure Using a Cluster Configuration File 9-26

Installing Only the Oracle Grid Infrastructure Software 9-28

Installing Software Binaries for Oracle Grid Infrastructure for a Cluster 9-29

Configuring Software Binaries for Oracle Grid Infrastructure for a Cluster 9-30

Configuring the Software Binaries Using a Response File 9-30

Setting Ping Targets for Network Checks 9-31

About Deploying Oracle Grid Infrastructure Using Oracle Fleet Patching andProvisioning 9-31

Confirming Oracle Clusterware Function 9-33

Confirming Oracle ASM Function for Oracle Clusterware Files 9-34

Understanding Offline Processes in Oracle Grid Infrastructure 9-34

10

Oracle Grid Infrastructure Postinstallation Tasks

Required Postinstallation Tasks 10-1

Downloading and Installing Release Update Patches 10-2

Recommended Postinstallation Tasks 10-2

Configuring IPMI-based Failure Isolation Using Crsctl 10-3

Creating a Backup of the root.sh Script 10-4

Updating the Oracle ORAchk Health Check Tool 10-4

Creating a Fast Recovery Area 10-5

About the Fast Recovery Area and the Fast Recovery Area Disk Group 10-5

Creating the Fast Recovery Area Disk Group 10-6

Checking the SCAN Configuration 10-6

Setting Resource Limits for Oracle Clusterware and Associated Databases andApplications 10-7

About Changes in Default SGA Permissions for Oracle Database 10-7

Using Earlier Oracle Database Releases with Oracle Grid Infrastructure 10-8

General Restrictions for Using Earlier Oracle Database Releases 10-8

Configuring Earlier Release Oracle Database on Oracle ACFS 10-9

Making Oracle ASM Available to Earlier Oracle Database Releases 10-10

Using ASMCA to Administer Disk Groups for Earlier Database Releases 10-10

viii

Using the Correct LSNRCTL Commands 10-10

Modifying Oracle Clusterware Binaries After Installation 10-11

11

Upgrading Oracle Grid Infrastructure

Understanding Out-of-Place Upgrade 11-2

About Oracle Grid Infrastructure Upgrade and Downgrade 11-2

Options for Oracle Grid Infrastructure Upgrades 11-3

Restrictions for Oracle Grid Infrastructure Upgrades 11-4

Preparing to Upgrade an Existing Oracle Clusterware Installation 11-6

Upgrade Checklist for Oracle Grid Infrastructure 11-6

Checks to Complete Before Upgrading Oracle Grid Infrastructure 11-9

Moving Oracle Clusterware Files from NFS to Oracle ASM 11-10

Running the Oracle ORAchk Upgrade Readiness Assessment 11-11

Using CVU to Validate Readiness for Oracle Clusterware Upgrades 11-11

About the CVU Upgrade Validation Command Options 11-12

Example of Verifying System Upgrade Readiness for Grid Infrastructure 11-13

Using Dry-Run Upgrade Mode to Check System Upgrade Readiness 11-13

About Oracle Grid Infrastructure Dry-Run Upgrade Mode 11-13

Performing Dry-Run Upgrade Using Oracle Universal Installer 11-14

Understanding Rolling Upgrades Using Batches 11-15

Performing Rolling Upgrade of Oracle Grid Infrastructure 11-16

Upgrading Oracle Grid Infrastructure from an Earlier Release 11-16

Completing an Oracle Clusterware Upgrade when Nodes Become Unreachable11-18

Joining Inaccessible Nodes After Forcing an Upgrade 11-19

Changing the First Node for Install and Upgrade 11-19

About Upgrading Oracle Grid Infrastructure Using Oracle Fleet Patching andProvisioning 11-20

Applying Patches to Oracle Grid Infrastructure 11-20

About Individual Oracle Grid Infrastructure Patches 11-21

About Oracle Grid Infrastructure Software Patch Levels 11-21

Patching Oracle Grid Infrastructure to a Software Patch Level 11-22

Applying Patches During an Oracle Grid Infrastructure Installation or Upgrade 11-22

Updating Oracle Enterprise Manager Cloud Control Target Parameters 11-23

Updating the Enterprise Manager Cloud Control Target After Upgrades 11-23

Updating the Enterprise Manager Agent Base Directory After Upgrades 11-24

Registering Resources with Oracle Enterprise Manager After Upgrades 11-24

Unlocking and Deinstalling the Previous Release Grid Home 11-25

Checking Cluster Health Monitor Repository Size After Upgrading 11-26

Downgrading Oracle Clusterware to an Earlier Release 11-26

Options for Oracle Grid Infrastructure Downgrades 11-27

ix

Restrictions for Oracle Grid Infrastructure Downgrades 11-28

Downgrading Oracle Clusterware to 18c 11-28

Downgrading Oracle Standalone Cluster to 18c 11-29

Downgrading Oracle Domain Services Cluster to 18c 11-30

Downgrading Oracle Member Cluster to 18c 11-33

Downgrading Oracle Grid Infrastructure to 18c when Upgrade Fails 11-35

Downgrading Oracle Clusterware to 12c Release 2 (12.2) 11-36

Downgrading Oracle Standalone Cluster to 12c Release 2 (12.2) 11-36

Downgrading Oracle Domain Services Cluster to 12c Release 2 (12.2) 11-38

Downgrading Oracle Member Cluster to 12c Release 2 (12.2) 11-41

Downgrading Oracle Grid Infrastructure to 12c Release 2 (12.2) whenUpgrade Fails 11-43

Downgrading to Oracle Grid Infrastructure 12c Release 1 (12.1) 11-43

Downgrading to Oracle Grid Infrastructure 11g Release 2 (11.2) 11-45

Downgrading Oracle Grid Infrastructure Using Online Abort Upgrade 11-46

Completing Failed or Interrupted Installations and Upgrades 11-48

Completing Failed Installations and Upgrades 11-48

Continuing Incomplete Upgrade of First Node 11-49

Continuing Incomplete Upgrades on Remote Nodes 11-49

Continuing Incomplete Installation on First Node 11-50

Continuing Incomplete Installation on Remote Nodes 11-50

Converting to Oracle Extended Cluster After Upgrading Oracle Grid Infrastructure 11-51

12

Removing Oracle Database Software

About Oracle Deinstallation Options 12-2

Oracle Deinstallation (Deinstall) 12-3

Deinstallation Examples for Oracle Database 12-5

Deinstallation Response File Example for Oracle Grid Infrastructure for a Cluster 12-6

Migrating Standalone Oracle Grid Infrastructure Servers to a Cluster 12-9

Relinking Oracle Grid Infrastructure for a Cluster Binaries 12-11

Changing the Oracle Grid Infrastructure Home Path 12-12

Unconfiguring Oracle Clusterware Without Removing Binaries 12-13

Unconfiguring Oracle Member Cluster 12-14

A Installing and Configuring Oracle Database Using Response FilesHow Response Files Work A-1

Reasons for Using Silent Mode or Response File Mode A-2

Using Response Files A-2

Preparing Response Files A-3

Editing a Response File Template A-3

x

Recording Response Files A-5

Running Oracle Universal Installer Using a Response File A-6

Running Configuration Assistants Using Response Files A-7

Running Oracle DBCA Using Response Files A-8

Running Net Configuration Assistant Using Response Files A-9

Postinstallation Configuration Using Response File Created During Installation A-10

Using the Installation Response File for Postinstallation Configuration A-10

Running Postinstallation Configuration Using Response File A-11

Postinstallation Configuration Using the ConfigToolAllCommands Script A-13

About the Postinstallation Configuration File A-13

Creating a Password Response File A-14

Running Postinstallation Configuration Using a Password Response File A-15

B Completing Preinstallation Tasks ManuallyConfiguring SSH Manually on All Cluster Nodes B-1

Checking Existing SSH Configuration on the System B-1

Configuring SSH on Cluster Nodes B-2

Create SSH Directory and Create SSH Keys On Each Node B-2

Add All Keys to a Common authorized_keys File B-3

Enabling SSH User Equivalency on Cluster Nodes B-4

Configuring Kernel Parameters on Oracle Solaris B-5

Minimum Parameter Settings for Installation B-6

Checking Shared Memory Resource Controls B-7

Configuring Additional Shared Memory Identifiers Limit B-7

Displaying and Changing Kernel Parameter Values B-8

Setting UDP and TCP Kernel Parameters Manually B-10

Configuring Shell Limits for Oracle Solaris B-10

C Deploying Oracle RAC on Oracle Solaris Cluster Zone ClustersAbout Oracle RAC Deployment in Oracle Solaris Cluster Zone Clusters C-1

Prerequisites for Oracle RAC Deployment in Oracle Solaris Cluster Zone Clusters C-2

Deploying Oracle RAC in the Global Zone C-3

Deploying Oracle RAC in a Zone Cluster C-4

D Optimal Flexible ArchitectureAbout the Optimal Flexible Architecture Standard D-1

About Multiple Oracle Homes Support D-2

About the Oracle Inventory Directory and Installation D-3

Oracle Base Directory Naming Convention D-4

xi

Oracle Home Directory Naming Convention D-5

Optimal Flexible Architecture File Path Examples D-5

Index

xii

List of Figures

9-1 Oracle Cluster Domain 9-5

xiii

List of Tables

1-1 Server Hardware Checklist for Oracle Grid Infrastructure 1-2

1-2 Operating System General Checklist for Oracle Grid Infrastructure on Oracle Solaris 1-2

1-3 Server Configuration Checklist for Oracle Grid Infrastructure 1-3

1-4 Network Configuration Tasks for Oracle Grid Infrastructure and Oracle RAC 1-4

1-5 User Environment Configuration for Oracle Grid Infrastructure 1-6

1-6 Oracle Grid Infrastructure Storage Configuration Checks 1-8

1-7 Oracle Grid Infrastructure Cluster Deployment Checklist 1-9

1-8 Oracle Universal Installer Checklist for Oracle Grid Infrastructure Installation 1-10

4-1 Oracle Solaris 11 Releases for SPARC (64-Bit) Minimum Operating System

Requirements 4-6

4-2 Oracle Solaris 11 Releases for x86-64 (64-Bit) Minimum Operating System Requirements 4-8

4-3 Requirements for Programming Environments for Oracle Solaris 4-11

5-1 Grid Naming Service Cluster Configuration Example 5-22

5-2 Manual Network Configuration Example 5-23

6-1 Installation Owner Resource Limit Recommended Ranges 6-26

7-1 Supported Storage Options for Oracle Grid Infrastructure 7-2

7-2 Platforms That Support Oracle ACFS and Oracle ADVM 7-3

8-1 Minimum Available Space Requirements for Oracle Standalone Cluster With GIMR

Configuration 8-7

8-2 Minimum Available Space Requirements for Oracle Standalone Cluster Without

GIMR Configuration 8-8

8-3 Minimum Available Space Requirements for Oracle Member Cluster with Local ASM 8-9

8-4 Minimum Available Space Requirements for Oracle Domain Services Cluster 8-9

9-1 Image-Creation Options for Setup Wizard 9-3

9-2 Oracle ASM Disk Group Redundancy Levels for Oracle Extended Clusters with 2

Data Sites 9-7

11-1 Upgrade Checklist for Oracle Grid Infrastructure Installation 11-7

A-1 Response Files for Oracle Database and Oracle Grid Infrastructure A-4

B-1 Minimum Oracle Solaris Resource Control Parameter Settings B-6

B-2 Requirement for Resource Control project.max-shm-memory B-7

B-3 Granule Size for SGA Values B-8

B-4 Oracle Solaris Shell Limit Recommended Ranges B-11

D-1 Examples of OFA-Compliant Oracle Base Directory Names D-4

D-2 Optimal Flexible Architecture Hierarchical File Path Examples D-6

xiv

Preface

This guide explains how to configure a server in preparation for installing andconfiguring an Oracle Grid Infrastructure installation (Oracle Clusterware and OracleAutomatic Storage Management).

It also explains how to configure a server and storage in preparation for an OracleReal Application Clusters (Oracle RAC) installation.

• Audience

• Documentation Accessibility

• Set Up Java Access Bridge to Implement Java AccessibilityInstall Java Access Bridge so that assistive technologies on Microsoft Windowssystems can use the Java Accessibility API.

• Related Documentation

• Conventions

AudienceThis guide provides configuration information for network and system administrators,and database installation information for database administrators (DBAs) who installand configure Oracle Clusterware and Oracle Automatic Storage Management in anOracle Grid Infrastructure for a cluster installation.

For users with specialized system roles who intend to install Oracle RAC, this book isintended to be used by system administrators, network administrators, or storageadministrators to configure a system in preparation for an Oracle Grid Infrastructure fora cluster installation, and complete all configuration tasks that require operatingsystem root privileges. When Oracle Grid Infrastructure installation and configuration iscompleted successfully, a system administrator should only need to provideconfiguration information and to grant access to the database administrator to runscripts as root during an Oracle RAC installation.

This guide assumes that you are familiar with Oracle Database concepts.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the OracleAccessibility 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 supportthrough My Oracle Support. For information, visit http://www.oracle.com/pls/topic/

xv

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

lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trsif you are hearing impaired.

Set Up Java Access Bridge to Implement Java AccessibilityInstall Java Access Bridge so that assistive technologies on Microsoft Windowssystems can use the Java Accessibility API.

Java Access Bridge is a technology that enables Java applications and applets thatimplement the Java Accessibility API to be visible to assistive technologies onMicrosoft Windows systems.

Refer to Java Platform, Standard Edition Accessibility Guide for information about theminimum supported versions of assistive technologies required to use Java AccessBridge. Also refer to this guide to obtain installation and testing instructions, andinstructions for how to use Java Access Bridge.

Related Topics

• Java Platform, Standard Edition Java Accessibility Guide

Related DocumentationFor more information, see the following Oracle resources:

Related Topics

• Oracle Real Application Clusters Installation Guide for Linux and UNIX

• Oracle Database Installation Guide

• Oracle Clusterware Administration and Deployment Guide

• Oracle Real Application Clusters Administration and Deployment Guide

• Oracle Database Concepts

• Oracle Database New Features Guide

• Oracle Database Licensing Information

• Oracle Database Release Notes

• Oracle Database Examples Installation Guide

• Oracle Database Administrator's Reference for Linux and UNIX-Based OperatingSystems

• Oracle Automatic Storage Management Administrator's Guide

• Oracle Database Upgrade Guide

• Oracle Database 2 Day DBA

• Oracle Application Express Installation Guide

ConventionsThe following text conventions are used in this document:

Preface

xvi

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

Convention Meaning

boldface Boldface type indicates graphical user interface elements associatedwith an action, or terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables forwhich you supply particular values.

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

Preface

xvii

Changes in this Release for Oracle GridInfrastructure

The following are changes in Oracle Grid Infrastructure Installation Guide for OracleGrid Infrastructure 19c.

• New FeaturesReview new features available with Oracle Grid Infrastructure 19c.

• Deprecated FeaturesReview features that are deprecated starting with Oracle Grid Infrastructure 19c.

• Desupported FeaturesReview features that are desupported with Grid Infrastructure 19c.

• Other ChangesReview other changes for Oracle Grid Infrastructure 19c.

Related Topics


New FeaturesReview new features available with Oracle Grid Infrastructure 19c.

• Support for Dry-Run Validation of Oracle Clusterware Upgrade

• Multiple ASMB

• Parity Protected Files

• Zero-Downtime Oracle Grid Infrastructure Patching

• Zero-Downtime Oracle Grid Infrastructure Patching Using Oracle Fleet Patchingand Provisioning

• Resupport of Direct File Placement for OCR and Voting Disks

• Optional Install for the Grid Infrastructure Management Repository

Related Topics


Support for Dry-Run Validation of Oracle Clusterware UpgradeStarting with Oracle Grid Infrastructure 19c, the Oracle Grid Infrastructure installationwizard (gridSetup.sh) enables you to perform a dry-run mode upgrade to checkyour system’s upgrade readiness.

In dry-run upgrade mode, the installation wizard performs all of the system readinesschecks that it would perform in an actual upgrade and enables you to verify whetheryour system is ready for upgrade before you start the upgrade. This mode does notperform an actual upgrade. It helps anticipate potential problems with the systemsetup and avoid upgrade failures.

New Features

18

Related Topics

• Using Dry-Run Upgrade Mode to Check System Upgrade ReadinessUse dry-run upgrade mode of Oracle Grid Infrastructure installation wizard,gridSetup.sh, to check readiness for Oracle Clusterware upgrades.

Multiple ASMBGiven that +ASM1 has dg1 mounted but not dg2, and +ASM2 has dg2 mounted butnot dg1, the Multiple ASMB project allows for the Database to use both dg1 and dg2by connecting to both ASM instances simultaneously. Instead of having just ASMB, wecan now have ASMBn.

This feature increases the availability of the Real Application Clusters (RAC) stack byallowing DB to use multiple disk groups even if a given ASM instance happens not tohave all of them mounted.

Parity Protected FilesThe REDUNDANCY file type property specifies the redundancy for a file group.The PARITY value specifies single parity for redundancy. The parity setting is intendedfor write-once files, such as archive logs and backup sets.

A great deal of space is consumed when two or three way ASM mirroring is used forfiles associated with database backup operations. Backup files are write-once files,and this feature allows parity protection for protection rather than conventionalmirroring. Considerable space savings are the result.

Related Topics

• About Oracle ASM File Group Properties

Zero-Downtime Oracle Grid Infrastructure PatchingZero-Downtime Oracle Grid Infrastructure Patching enables patching of Oracle GridInfrastructure without interrupting database operations. Patches are applied out-of-place and in a rolling fashion, with one node being patched at a time, while thedatabase instances on the node remain operational. Zero-Downtime Oracle GridInfrastructure Patching supports Oracle Real Application Clusters (Oracle RAC)databases on clusters with two or more nodes.

Zero-Downtime Grid Infrastructure Patching significantly increases databaseavailability by allowing customers to perform a rolling patch of Oracle GridInfrastructure without interrupting database operations on the node being patched andwithout impacting capacity or performance on those database instances.

Related Topics


Zero-Downtime Oracle Grid Infrastructure Patching Using Oracle FleetPatching and Provisioning

Zero-Downtime Oracle Grid Infrastructure Patching enables the application of one-offOracle Grid Infrastructure patches without impacting the Oracle RAC databaseinstances. Use Oracle Fleet Patching and Provisioning (Oracle FPP) to apply patches

New Features

19

in a rolling fashion across the cluster. This functionality is available for all Oracle RealApplication Clusters with two or more nodes, but currently applies only to one-offpatches (not the RU's and RUR's).

Using Oracle Fleet Patching and Provisioning to apply one-off Oracle GridInfrastructure patches with zero database instance downtime reduces the impact onusers and interruptions of service from the Oracle RAC database instances to nil. Withprior database releases, you must shut down the database instance before applyingan Oracle Grid Infrastructure patch, clearly impacting enterprise operations.

Related Topics


Resupport of Direct File Placement for OCR and Voting Disks

Starting with Oracle Grid Infrastructure 19c, the desupport for direct OCR and votingdisk file placement on shared file systems is rescinded for Oracle Standalone Clusters.For Oracle Domain Services Clusters the requirement to place OCR and voting files inOracle Automatic Storage Management (Oracle ASM) on top of files hosted on sharedfile systems and used as ASM disks remains.

In Oracle Grid Infrastructure 12c Release 2 (12.2), Oracle announced that it would nolonger support the placement of the Oracle Grid Infrastructure Oracle Cluster Registry(OCR) and voting files directly on a shared file system. This desupport is nowrescinded. Starting with Oracle Grid Infrastructure 19c (19.3), with Oracle StandaloneClusters, you can again place OCR and voting disk files directly on shared filesystems.

Related Topics

• Using Cluster File System for Oracle Clusterware Files

Optional Install for the Grid Infrastructure Management Repository

Starting with Oracle Grid Infrastructure 19c, the Grid Infrastructure ManagementRepository (GIMR) is optional for new installations of Oracle Standalone Cluster.Oracle Domain Services Clusters still require the installation of a GIMR as a servicecomponent.

The data contained in the GIMR is the basis for preventative diagnostics based onapplied Machine Learning and can help to increase the availability of Oracle RealApplication Clusters (Oracle RAC) databases. Having an optional installation for theGIMR allows for more flexible storage space management and faster deployment,especially during the installation of test and development systems.

Related Topics

• About the Grid Infrastructure Management RepositoryEvery Oracle Domain Services Cluster contains a Grid Infrastructure ManagementRepository (GIMR), but GIMR configuration is optional for Oracle StandaloneCluster.

Deprecated FeaturesReview features that are deprecated starting with Oracle Grid Infrastructure 19c.

Deprecated Features

20

For more information about deprecated features, parameters, and views, refer toOracle Database Upgrade Guide

• Deprecation of Addnode Script

The addnode script is deprecated in Oracle Grid Infrastructure 19c. Thefunctionality of adding nodes to clusters is available in the installer wizard.The addnode script can be removed in a future release. Instead of using theaddnode script (addnode.sh or addnode.bat), add nodes by using the installerwizard. The installer wizard provides many enhancements over the addnode script.Using the installer wizard simplifies management by consolidating all softwarelifecycle operations into a single tool.

• Deprecation of Clone.pl Script

The clone.pl script is deprecated in Oracle Database 19c. The functionality ofperforming a software-only installation, using the gold image, is available in theinstaller wizard.The clone.pl script can be removed in a future release. Instead of using theclone.pl script, Oracle recommends that you install the extracted gold image as ahome, using the installer wizard.

Related Topics


Desupported FeaturesReview features that are desupported with Grid Infrastructure 19c.

For more information about desupported features, parameters, and views, refer toOracle Database Upgrade Guide

• Desupport of Leaf Nodes in Flex Cluster Architecture

Leaf nodes are no longer supported in the Oracle Flex Cluster Architecture inOracle Grid Infrastructure 19c.In Oracle Grid Infrastructure 19c (19.1) and later releases, all nodes in an OracleFlex Cluster function as hub nodes. The capabilities offered by Leaf nodes in theoriginal implementation of the Oracle Flex Cluster architecture can as easily beserved by hub nodes. Therefore, leaf nodes are no longer supported.

• Desupport of Oracle Real Application Clusters for Standard Edition 2 (SE2)Database Edition

Starting with Oracle Database 19c, Oracle Real Application Clusters (Oracle RAC)is not supported in Oracle Database Standard Edition 2 (SE2).Upgrading Oracle Database Standard Edition databases that use Oracle RealApplication Clusters (Oracle RAC) functionality from earlier releases to OracleDatabase 19c is not possible. To upgrade those databases to Oracle Database19c, either remove the Oracle RAC functionality before starting the upgrade, orupgrade from Oracle Database Standard Edition to Oracle Database EnterpriseEdition. For more information about each step, including how to reconfigure yoursystem after an upgrade, see My Oracle Support Note 2504078.1: "Desupport ofOracle Real Application Clusters (RAC) with Oracle Database Standard Edition19c."

Related Topics


Desupported Features

21

• My Oracle Support Document 2504878.1

Other ChangesReview other changes for Oracle Grid Infrastructure 19c.

• Rapid Home Provisioning (RHP) Name Change

Starting with Oracle Database 19c and Oracle Grid Infrastructure 19c, RapidHome Provisioning is renamed to Fleet Patching and Provisioning (FPP).

Other Changes

22

https://support.oracle.com/rs?type=doc&id=2504078.1

1Oracle Grid Infrastructure InstallationChecklist

Use checklists to plan and carry out Oracle Grid Infrastructure (Oracle Clusterwareand Oracle Automatic Storage Management) installation.

Oracle recommends that you use checklists as part of your installation planningprocess. Using this checklist can help you to confirm that your server hardware andconfiguration meet minimum requirements for this release, and to ensure you carry outa successful installation.

• Server Hardware Checklist for Oracle Grid InfrastructureReview server hardware requirements for Oracle Grid Infrastructure installation.

• Operating System Checklist for Oracle Grid Infrastructure on Oracle SolarisUse this checklist to check minimum operating system requirements for OracleDatabase.

• Server Configuration Checklist for Oracle Grid InfrastructureUse this checklist to check minimum server configuration requirements for OracleGrid Infrastructure installations.

• Network Checklist for Oracle Grid InfrastructureReview this network checklist for Oracle Grid Infrastructure installation to ensurethat you have required hardware, names, and addresses for the cluster.

• User Environment Configuration Checklist for Oracle Grid InfrastructureUse this checklist to plan operating system users, groups, and environments forOracle Grid Infrastructure installation.

• Storage Checklist for Oracle Grid InfrastructureReview the checklist for storage hardware and configuration requirements forOracle Grid Infrastructure installation.

• Cluster Deployment Checklist for Oracle Grid InfrastructureReview the checklist for planning your cluster deployment Oracle GridInfrastructure installation.

• Installer Planning Checklist for Oracle Grid InfrastructureReview the checklist for planning your Oracle Grid Infrastructure installation beforestarting Oracle Universal Installer.

Server Hardware Checklist for Oracle Grid InfrastructureReview server hardware requirements for Oracle Grid Infrastructure installation.

1-1

Table 1-1 Server Hardware Checklist for Oracle Grid Infrastructure

Check Task

Server makeandarchitecture

Confirm that server makes, models, core architecture, and host bus adaptors(HBA) are supported to run with Oracle Grid Infrastructure and Oracle RAC.

Runlevel 3

Server DisplayCards

At least 1024 x 768 display resolution for Oracle Universal Installer. Confirmdisplay monitor.

MinimumRandomAccessMemory(RAM)

At least 8 GB RAM for Oracle Grid Infrastructure installations.

IntelligentPlatformManagementInterface(IPMI)

IPMI cards installed and configured, with IPMI administrator accountinformation available to the person running the installation.

Ensure baseboard management controller (BMC) interfaces are configured,and have an administration account username and password to provide whenprompted during installation.

Operating System Checklist for Oracle Grid Infrastructure onOracle Solaris

Use this checklist to check minimum operating system requirements for OracleDatabase.

Table 1-2 Operating System General Checklist for Oracle Grid Infrastructure onOracle Solaris

Item Task

Operating systemgeneralrequirements

• OpenSSH installed manually, if you do not have it installed alreadyas part of a default Oracle Solaris installation

• The following Oracle Solaris on SPARC (64-Bit) kernels aresupported:

Oracle Solaris 11.4 (Oracle Solaris 11.4.2.0.1.3.0) or laterSRUs and updatesOracle Solaris 11.3 SRU 31 (Oracle Solaris 11.3.31.6.0) orlater SRUs and updates

• The following Oracle Solaris on x86–64 (64-Bit) kernels aresupported:

Solaris 11.4 (Oracle Solaris 11.4.2.0.1.3.0) or later SRUs andupdatesOracle Solaris 11.3 SRU 31 (Oracle Solaris 11.3.31.6.0) orlater SRUs and updates

Review the system requirements section for a list of minimum packagerequirements.

Chapter 1Operating System Checklist for Oracle Grid Infrastructure on Oracle Solaris

1-2

Server Configuration Checklist for Oracle Grid InfrastructureUse this checklist to check minimum server configuration requirements for Oracle GridInfrastructure installations.

Table 1-3 Server Configuration Checklist for Oracle Grid Infrastructure

Check Task

Disk space allocated to thetemporary file system

At least 1 GB of space in the temporary disk space (/tmp)directory

Swap space allocationrelative to RAM Between 4 GB and 16 GB: Equal to the size of the RAM

More than 16 GB: 16 GBNote: Configure swap for your expected system loads.This installation guide provides minimum values forinstallation only. Refer to your Oracle Solarisdocumentation for additional memory tuning guidance.

Mount point paths for thesoftware binaries

Oracle recommends that you create an Optimal FlexibleArchitecture configuration as described in the appendix "OptimalFlexible Architecture" in Oracle Grid Infrastructure Installationand Upgrade Guide for your platform.

Ensure that the Oracle home(the Oracle home path youselect for Oracle Database)uses only ASCII characters

The ASCII character restriction includes installation owner usernames, which are used as a default for some home paths, aswell as other directory names you may select for paths.

Set locale (if needed) Specify the language and the territory, or locale, in which youwant to use Oracle components. A locale is a linguistic andcultural environment in which a system or program is running.NLS (National Language Support) parameters determine thelocale-specific behavior on both servers and clients. The localesetting of a component determines the language of the userinterface of the component, and the globalization behavior, suchas date and number formatting.

Set Network Time Protocolfor Cluster TimeSynchronization

Oracle Clusterware requires the same time zone environmentvariable setting on all cluster nodes.

Ensure that you set the time zone synchronization across allcluster nodes using either an operating system configurednetwork time protocol (NTP) or Oracle Cluster TimeSynchronization Service.

Related Topics

• Optimal Flexible ArchitectureOracle Optimal Flexible Architecture (OFA) rules are a set of configurationguidelines created to ensure well-organized Oracle installations, which simplifiesadministration, support and maintenance.

Network Checklist for Oracle Grid InfrastructureReview this network checklist for Oracle Grid Infrastructure installation to ensure thatyou have required hardware, names, and addresses for the cluster.

Chapter 1Server Configuration Checklist for Oracle Grid Infrastructure

1-3

During installation, you designate interfaces for use as public, private, or Oracle ASMinterfaces. You can also designate interfaces that are in use for other purposes, suchas a network file system, and not available for Oracle Grid Infrastructure use.

If you use a third-party cluster software, then the public host name information isobtained from that software.

Table 1-4 Network Configuration Tasks for Oracle Grid Infrastructure andOracle RAC

Check Task

Public networkhardware

• Public network switch (redundant switches recommended)connected to a public gateway and to the public interface ports foreach cluster member node.

• Ethernet interface card (redundant network cardsrecommended, trunked as one Ethernet port name).

• The switches and network interfaces must be at least 1 GbE.• The network protocol is Transmission Control Protocol (TCP) and

Internet Protocol (IP).

Private networkhardware for theinterconnect

• Private dedicated network switches (redundant switchesrecommended), connected to the private interface ports for eachcluster member node.

Note: If you have more than one private network interface card foreach server, then Oracle Clusterware automatically associatesthese interfaces for the private network using Grid InterprocessCommunication (GIPC) and Grid Infrastructure RedundantInterconnect, also known as Cluster High Availability IP (HAIP).

• The switches and network interface adapters must be at least 1GbE.

• The interconnect must support the user datagram protocol (UDP).• Jumbo Frames (Ethernet frames greater than 1500 bits) are not

an IEEE standard, but can reduce UDP overhead if properlyconfigured. Oracle recommends the use of Jumbo Frames forinterconnects. However, be aware that you must load-test yoursystem, and ensure that they are enabled throughout the stack.

Oracle Flex ASMNetwork Hardware

Oracle Flex ASM can use either the same private networks as OracleClusterware, or use its own dedicated private networks. Each networkcan be classified PUBLIC or PRIVATE+ASM or PRIVATE or ASM.Oracle ASM networks use the TCP protocol.

Chapter 1Network Checklist for Oracle Grid Infrastructure

1-4

Table 1-4 (Cont.) Network Configuration Tasks for Oracle Grid Infrastructureand Oracle RAC

Check Task

Cluster Names andAddresses

Determine and configure the following names and addresses for thecluster:

• Cluster name: Decide a name for the cluster, and be prepared toenter it during installation. The cluster name should have thefollowing characteristics:

Globally unique across all hosts, even across different DNSdomains.

At least one character long and less than or equal to 15characters long.

Consist of the same character set used for host names, inaccordance with RFC 1123: Hyphens (-), and single-bytealphanumeric characters (a to z, A to Z, and 0 to 9). If you usethird-party vendor clusterware, then Oracle recommends that youuse the vendor cluster name.

• Grid Naming Service Virtual IP Address (GNS VIP): If you planto use GNS, then configure a GNS name and fixed address inDNS for the GNS VIP, and configure a subdomain on your DNSdelegated to the GNS VIP for resolution of cluster addresses.GNS domain delegation is mandatory with dynamic publicnetworks (DHCP, autoconfiguration).

• Single Client Access Name (SCAN) and addressesUsing Grid Naming Service Resolution: Do not configure SCANnames and addresses in your DNS. SCAN names are managedby GNS.

Using Manual Configuration and DNS resolution: Configure aSCAN name to resolve to three addresses on the domain nameservice (DNS).

Node Public, Privateand Virtual IP namesand Addresses

If you are not using GNS, then configure the following for each node:

• Public node name and address, configured in the DNS andin /etc/hosts (for example, node1.example.com, address192.0.2.10). The public node name should be the primary hostname of each node, which is the name displayed by thehostname command.

• Private node address, configured on the private interface foreach node.

The private subnet that the private interfaces use must connect allthe nodes you intend to have as cluster members. Oraclerecommends that the network you select for the private networkuses an address range defined as private by RFC 1918.

• Public node virtual IP name and address (for example, node1-vip.example.com, address 192.0.2.11).

If you are not using dynamic networks with GNS and subdomaindelegation, then determine a virtual host name for each node. Avirtual host name is a public node name that is used to rerouteclient requests sent to the node if the node is down. OracleDatabase uses VIPs for client-to-database connections, so theVIP address must be publicly accessible. Oracle recommends thatyou provide a name in the format hostname-vip. For example:myclstr2-vip.

Chapter 1Network Checklist for Oracle Grid Infrastructure

1-5

User Environment Configuration Checklist for Oracle GridInfrastructure

Use this checklist to plan operating system users, groups, and environments forOracle Grid Infrastructure installation.

Table 1-5 User Environment Configuration for Oracle Grid Infrastructure

Check Task

Review Oracle Inventory(oraInventory) and OINSTALLGroup Requirements

The Oracle Inventory directory is the central inventory ofOracle software installed on your system. It should be theprimary group for all Oracle software installation owners. Userswho have the Oracle Inventory group as their primary groupare granted the OINSTALL privilege to read and write to thecentral inventory.

• If you have an existing installation, then OUI detects theexisting oraInventory directory from the /etc/oraInst.loc file, and uses this location.

• If you are installing Oracle software for the first time, thenOUI creates an Oracle base and central inventory, andcreates an Oracle inventory using information in thefollowing priority:– In the path indicated in the ORACLE_BASE

environment variable set for the installation owneruser account.

– In an Optimal Flexible Architecture (OFA) path (u[01–99]/app/owner where owner is the name of the useraccount running the installation), if that user accounthas permissions to write to that path.

– In the user home directory, in the path /app/owner,where owner is the name of the user account runningthe installation.

Ensure that the group designated as the OINSTALL group isavailable as the primary group for all planned Oracle softwareinstallation owners.

Create operating systemgroups and users for standardor role-allocated systemprivileges

Create operating system groups and users depending on yoursecurity requirements, as described in this installation guide.

Set resource limits settings and other requirements for Oraclesoftware installation owners.

Group and user names must use only ASCII characters.

Note:

Do not delete an existingdaemon user. If a daemon userhas been deleted, then you mustadd it back.

Chapter 1User Environment Configuration Checklist for Oracle Grid Infrastructure

1-6

Table 1-5 (Cont.) User Environment Configuration for Oracle GridInfrastructure

Check Task

Unset Oracle SoftwareEnvironment Variables

If you have an existing Oracle software installation, and youare using the same user to install this installation, then unsetthe following environmentvariables: $ORACLE_HOME; $ORA_NLS10; $TNS_ADMIN.

If you have set $ORA_CRS_HOME as an environment variable,then unset it before starting an installation or upgrade. Do notuse $ORA_CRS_HOME as a user environment variable, exceptas directed by Oracle Support.

Configure the Oracle SoftwareOwner Environment

Configure the environment of the oracle or grid user byperforming the following tasks:

• Set the default file mode creation mask (umask) to 022 inthe shell startup file.

• Set the DISPLAY environment variable.

Determine root privilegedelegation option forinstallation

During installation, you are asked to run configuration scriptsas the root user. You can either run these scripts manually asroot when prompted, or during installation you can provideconfiguration information and passwords using a root privilegedelegation option.

To run root scripts automatically, select Automatically runconfiguration scripts. during installation. To use theautomatic configuration option, the root user credentials for allcluster member nodes must use the same password.

• Use root user credentialsProvide the superuser password for cluster member nodeservers.

• Use sudosudo is a UNIX and Linux utility that allows members ofthe sudoers list privileges to run individual commands asroot. Provide the user name and password of an operatingsystem user that is a member of sudoers, and isauthorized to run sudo on each cluster member node.

To enable sudo, have a system administrator with theappropriate privileges configure a user that is a member ofthe sudoers list, and provide the user name andpassword when prompted during installation.

Storage Checklist for Oracle Grid InfrastructureReview the checklist for storage hardware and configuration requirements for OracleGrid Infrastructure installation.

Chapter 1Storage Checklist for Oracle Grid Infrastructure

1-7

Table 1-6 Oracle Grid Infrastructure Storage Configuration Checks

Check Task

Minimum disk space(local or shared) forOracle GridInfrastructureSoftware

• At least 12 GB of space for the Oracle Grid Infrastructurefor a cluster home (Grid home). Oracle recommends thatyou allocate 100 GB to allow additional space for patches.At least 9 GB for Oracle Database Enterprise Edition

• Allocate additional storage space as per your clusterconfiguration, as described in Oracle Clusterware Storage SpaceRequirements.

Select Oracle ASMStorage Options

During installation, based on the cluster configuration, you are askedto provide Oracle ASM storage paths for the Oracle Clusterware files.These path locations must be writable by the Oracle Grid Infrastructureinstallation owner (Grid user). These locations must be shared acrossall nodes of the cluster on Oracle ASM because the files in the OracleASM disk group created during installation must be available to allcluster member nodes.

• For Oracle Standalone Cluster deployment, shared storage, eitherOracle ASM or shared file system, is locally mounted on each ofthe cluster nodes.

• For Oracle Domain Services Cluster deployment, OracleASM storage is shared across all nodes, and is available toOracle Member Clusters.

Oracle Member Cluster for Oracle Databases can eitheruse storage services from the Oracle Domain ServicesCluster or local Oracle ASM storage shared across all thenodes.

Oracle Member Cluster for Applications always use storageservices from the Oracle Domain Services Cluster.

Before installing Oracle Member Cluster, create a MemberCluster Manifest file that specifies the storage details.

Voting files are files that Oracle Clusterware uses to verify clusternode membership and status. Oracle Cluster Registry files (OCR)contain cluster and database configuration information for OracleClusterware.

Chapter 1Storage Checklist for Oracle Grid Infrastructure

1-8

Table 1-6 (Cont.) Oracle Grid Infrastructure Storage Configuration Checks

Check Task

Select GridInfrastructureManagementRepository (GIMR)Storage Option

Depending on the type of cluster you are installing, you can choose toeither host the Grid Infrastructure Management Repository (GIMR) fora cluster on the same cluster or on a remote cluster.

Note:

Starting with Oracle Grid Infrastructure19c, configuring GIMR is optional forOracle Standalone Cluster deployments.

For Oracle Standalone Cluster deployment, you can specify the sameor separate Oracle ASM disk group for the GIMR.

For Oracle Domain Services Cluster deployment, the GIMR must beconfigured on a separate Oracle ASM disk group.

Oracle Member Clusters use the remote GIMR of the Oracle DomainServices Cluster. You must specify the GIMR details when you createthe Member Cluster Manifest file before installation.

Remove encryption ofOracle ACFS FileSystems BeforeInstallation

To avoid data corruption, ensure that encryption of Oracle ACFS filesystems is removed before installation.

Related Topics

• Oracle Clusterware Storage Space RequirementsUse this information to determine the minimum number of disks and the minimumdisk space requirements based on the redundancy type, for installing OracleClusterware files for various Oracle Cluster deployments.

Cluster Deployment Checklist for Oracle Grid InfrastructureReview the checklist for planning your cluster deployment Oracle Grid Infrastructureinstallation.

Table 1-7 Oracle Grid Infrastructure Cluster Deployment Checklist

Check Task

Configure an OracleCluster that hosts allOracle GridInfrastructure servicesand Oracle ASMlocally and accessesstorage directly

Deploy an Oracle Standalone Cluster.

Use the Oracle Extended Cluster option to extend an Oracle RACcluster across two, or more, separate sites, each equipped with its ownstorage.

Chapter 1Cluster Deployment Checklist for Oracle Grid Infrastructure

1-9

Table 1-7 (Cont.) Oracle Grid Infrastructure Cluster Deployment Checklist

Check Task

Configure an OracleCluster Domain tostandardize,centralize, andoptimize your OracleReal ApplicationClusters (Oracle RAC)deployment

Deploy an Oracle Domain Services Cluster.

To run Oracle Real Application Clusters (Oracle RAC) or Oracle RACOne Node database instances, deploy Oracle Member Cluster forOracle Databases.

To run highly-available software applications, deploy Oracle MemberCluster for Applications.

Installer Planning Checklist for Oracle Grid InfrastructureReview the checklist for planning your Oracle Grid Infrastructure installation beforestarting Oracle Universal Installer.

Table 1-8 Oracle Universal Installer Checklist for Oracle Grid InfrastructureInstallation

Check Task

Read the Release Notes Review release notes for your platform, which are available foryour release at the following URL:

http://www.oracle.com/technetwork/indexes/documentation/index.html

Review the LicensingInformation

You are permitted to use only those components in the OracleDatabase media pack for which you have purchased licenses.For more information, see:

Oracle Database Licensing Information User Manual

Run OUI with CVU and usefixup scripts

Oracle Universal Installer is fully integrated with ClusterVerification Utility (CVU), automating many CVU prerequisitechecks. Oracle Universal Installer runs all prerequisite checksand creates fixup scripts when you run the installer.

You can also run CVU commands manually to check systemreadiness. For more information, see:

Oracle Clusterware Administration and Deployment Guide

Download and run OracleORAchk for runtime andupgrade checks, or runtimehealth checks

The Oracle ORAchk utility provides system checks that canhelp to prevent issues after installation. These checks includekernel requirements, operating system resource allocations,and other system requirements.

Use the Oracle ORAchk Upgrade Readiness Assessment toobtain an automated upgrade-specific system health check forupgrades. For example:

./orachk -u -o pre

The Oracle ORAchk Upgrade Readiness Assessmentautomates many of the manual pre- and post-upgrade checksdescribed in Oracle upgrade documentation.

Oracle ORAchk is supported on Windows platforms in aCygwin environment only. For more information, see:

https://support.oracle.com/rs?type=doc&id=1268927.1

Chapter 1Installer Planning Checklist for Oracle Grid Infrastructure

1-10

http://www.oracle.com/technetwork/indexes/documentation/index.htmlhttp://www.oracle.com/technetwork/indexes/documentation/index.htmlhttps://support.oracle.com/rs?type=doc&id=1268927.1

Table 1-8 (Cont.) Oracle Universal Installer Checklist for Oracle GridInfrastructure Installation

Check Task

Ensure cron jobs do not runduring installation

If the installer is running when daily cron jobs start, then youmay encounter unexplained installation problems if your cronjob is performing cleanup, and temporary files are deletedbefore the installation is finished. Oracle recommends that youcomplete installation before daily cron jobs are run, ordisable daily cron jobs that perform cleanup until after theinstallation is completed.

Obtain Your My OracleSupport account information

During installation, you require a My Oracle Support username and password to configure security updates, downloadsoftware updates, and other installation tasks. You can registerfor My Oracle Support at the following URL:

https://support.oracle.com/

Check running Oracleprocesses, and shut downprocesses if necessary

• On a node with a standalone database not using OracleASM: You do not need to shut down the database whileyou install Oracle Grid Infrastructure.

• On a node with a standalone Oracle Database usingOracle ASM: Stop the existing Oracle ASM instances. TheOracle ASM instances are restarted during installation.

• On an Oracle RAC Database node: This installationrequires an upgrade of Oracle Clusterware, as OracleClusterware is required to run Oracle RAC. As part of theupgrade, you must shut down the database one node at atime as the rolling upgrade proceeds from node to node.

Chapter 1Installer Planning Checklist for Oracle Grid Infrastructure

1-11

https://support.oracle.com/

2Checking and Configuring ServerHardware for Oracle Grid Infrastructure

Verify that servers where you install Oracle Grid Infrastructure meet the minimumrequirements for installation.

This section provides minimum server requirements to complete installation of OracleGrid Infrastructure. It does not provide system resource guidelines, or other tuningguidelines for particular workloads.

• Logging In to a Remote System Using X Window SystemUse this procedure to run Oracle Universal Installer (OUI) by logging on to aremote system where the runtime setting prohibits logging in directly to a graphicaluser interface (GUI).

• Checking Server Hardware and Memory ConfigurationUse this procedure to gather information about your server configuration.

Logging In to a Remote System Using X Window SystemUse this procedure to run Oracle Universal Installer (OUI) by logging on to a remotesystem where the runtime setting prohibits logging in directly to a graphical userinterface (GUI).

OUI is a graphical user interface (GUI) application. On servers where the runtimesettings prevent GUI applications from running, you can redirect the GUI display to aclient system connecting to the server.

Note:

If you log in as another user (for example, oracle or grid), then repeat thisprocedure for that user as well.

1. Start an X Window System session. If you are using an X Window System terminalemulator from a PC or similar system, then you may need to configure securitysettings to permit remote hosts to display X applications on your local system.

2. Enter a command using the following syntax to enable remote hosts to display Xapplications on the local X server:

# xhost + RemoteHost

RemoteHost is the fully qualified remote host name. For example:

# xhost + somehost.example.comsomehost.example.com being added to the access control list

2-1

3. If you are not installing the software on the local system, then use the sshcommand to connect to the system where you want to install the software:

# ssh -Y RemoteHost

RemoteHost is the fully qualified remote host name. The -Y flag ("yes") enablesremote X11 clients to have full access to the original X11 display. For example:

# ssh -Y somehost.example.com

4. If you are not logged in as the root user, and you are performing configurationsteps that require root user privileges, then switch the user to root.

Note:

For more information about remote login using X Window System, refer toyour X server documentation, or contact your X server vendor or systemadministrator. Depending on the X server software that you are using, youmay have to complete the tasks in a different order.

Checking Server Hardware and Memory ConfigurationUse this procedure to gather information about your server configuration.

1. Use the following command to report the number of memory pages and swap-filedisk blocks that are currently unused:

# sar -r n i

For example:

# sar -r 2 10

If the size of the physical RAM installed in the system is less than the requiredsize, then you must install more memory before continuing.

2. Determine the swap space usage and size of the configured swap space:

# /usr/sbin/swap -s

If necessary, see your operating system documentation for information about howto configure additional swap space.

3. Determine the amount of space available in the /tmp directory:

# df -kh /tmp

If the free space available in the /tmp directory is less than what is required, thencomplete one of the following steps:

Chapter 2Checking Server Hardware and Memory Configuration

2-2

• Delete unnecessary files from the /tmp directory to meet the disk spacerequirement.

• When you set the Oracle user's environment, also set the TMP and TMPDIRenvironment variables to the directory you want to use instead of /tmp.

4. Determine the amount of free disk swap space on the system:

# df -kh

5. Determine the RAM size:

# /usr/sbin/prtconf | grep "Memory size"

6. Determine if the system architecture can run the software:

# /bin/isainfo -kv

This command displays the processor type. For example:

64-bit sparcv9 kernel modules

64-bit amd64 kernel modules

If you do not see the expected output, then you cannot install the software on thissystem.

Chapter 2Checking Server Hardware and Memory Configuration

2-3

3Automatically Configuring Oracle Solariswith Oracle Database PrerequisitesPackages

Use the Oracle Database prerequisites group package to simplify Oracle Solarisoperating system configuration in preparation for Oracle software installations.

Oracle recommends that you install the Oracle Database prerequisites group packageoracle-database-preinstall-19c in preparation for Oracle Database and OracleGrid Infrastructure installations.

• About the Oracle Database Prerequisites Packages for Oracle SolarisInstalling the Oracle Database prerequisites group package simplifies operatingsystem configuration and ensures that you have the required packages.

• Checking the Oracle Database Prerequisites Packages InstallationUse this procedure to gather information about the Oracle Database prerequisitesgroup package configuration.

• Installing the Oracle Database Prerequisites Packages for Oracle SolarisUse this procedure to install the Oracle Database prerequisites group package foryour Oracle software.

About the Oracle Database Prerequisites Packages forOracle Solaris

Installing the Oracle Database prerequisites group package simplifies operatingsystem configuration and ensures that you have the required packages.

Use the Oracle Database prerequisites group package group/prerequisite/oracle/oracle-database-preinstall-19c to ensure that all the necessary packages requiredfor an Oracle Database and Oracle Grid Infrastructure installation are present on thesystem.

The oracle-database-preinstall-19c package also creates the oracle user with ahome directory of /export/home/oracle, and creates the oraInventory (oinstall)and OSDBA (dba) groups for that user.

The oracle-database-preinstall-19c package consists of two packages—one thatinstalls extra packages needed on the operating system and one that creates usersand groups. The users and groups are created by the package oracle-database-os-configuration. If you have the oracle user and other user groups already defined,then you can chose not to change them.

You can install oracle-database-preinstall-19c even if you installed Oracle Solarisusing any of the server package groups, such as solaris-minimal-server, solaris-small-server, solaris-large-server, or solaris-desktop. Oracle recommends that

3-1

you install the solaris-minimal-server group package and then install oracle-database-preinstall-19c.

Configuring a server using Oracle Solaris and the Oracle Database prerequisitesgroup package consists of the following steps:

1. Install the recommended Oracle Solaris version for Oracle Database.

2. Install the Oracle Database prerequisites group package oracle-database-preinstall-19c.

3. If you do not want the Oracle Database prerequisites group package to create thedefault users and groups for you, then manually create the role-allocated groupsand users.

4. Complete network interface configuration for each cluster node candidate.

5. Complete system configuration for shared storage access as required for eachstandard or core node cluster candidate.

After these steps are complete, you can proceed to install Oracle Database, OracleGrid Infrastructure, or Oracle RAC.

Related Topics

• Oracle Solaris 11.3 Package Group Lists

Checking the Oracle Database Prerequisites PackagesInstallation

Use this procedure to gather information about the Oracle Database prerequisitesgroup package configuration.

1. To check if oracle-database-preinstall-19c is already installed:

$ pkg list oracle-database-preinstall-19c

2. To check for the latest version of oracle-database-preinstall-19c:

$ pkg list -n oracle-database-preinstall-19c

3. Before you install oracle-database-preinstall-19c:

a. Use the -n option to check for errors:

$ pkg install -n oracle-database-preinstall-19c

Note:

Use the -n option to check for installation errors. If -n does notdisplay any errors, then omit the -n option when you install oracle-database-preinstall-19c.

Chapter 3Checking the Oracle Database Prerequisites Packages Installation

3-2

https://docs.oracle.com/cd/E53394_01/html/E54814/index.html

b. If there are no errors, then log in as root, and install the group package:

# pkg install oracle-database-preinstall-19c

c. If you have the oracle user and other user groups already defined, and do notwant to change them:

# pkg avoid oracle-database-os-configuration

4. To view what packages will be installed by oracle-database-preinstall-19c:

$ pkg contents -ro type,fmri -t depend oracle-database-preinstall-19c

A sample output of this command:

TYPE FMRIconditional pkg:/service/oracle-rdbms-statsgroup pkg:/group/prerequisite/oracle/oracle-database-os-configurationgroup pkg:/system/font/truetype/arphic-uminggroup pkg:/system/font/truetype/hanyang-ko-coregroup pkg:/system/headergroup pkg:/system/kernel/orackagroup pkg:/system/piclgroup pkg:/x11/diagnostic/x11-info-clientsgroup pkg:/x11/library/libxigroup pkg:/x11/library/libxtstgroup pkg:/x11/session/xauthrequire pkg:/compress/unziprequire pkg:/developer/assemblerrequire pkg:/developer/build/makerequire pkg:/system/dtracerequire pkg:/system/library/openmp

Related Topics

• Adding and Updating Software in Oracle Solaris

Installing the Oracle Database Prerequisites Packages forOracle Solaris

Use this procedure to install the Oracle Database prerequisites group package for yourOracle software.

The group/prerequisite/oracle/oracle-database-preinstall-19c group packageinstalls all the packages required for an Oracle Database and Oracle GridInfrastructure installation. It also creates the oracle user and the oinstall and dbagroups for that user.

Chapter 3Installing the Oracle Database Prerequisites Packages for Oracle Solaris

3-3

http://docs.oracle.com/cd/E36784_01/html/E36802/tspkginstall.html

Caution:

If you have the oracle user and other user groups already defined, and donot want to change them, then ensure that you run the following commandbefore you install the Oracle Database prerequisites group package:

# pkg avoid oracle-database-os-configuration

To install the oracle-database-preinstall-19c group packages, log in as root, andrun the following command on Oracle Solaris 11.3 and later systems:

# pkg install oracle-database-preinstall-19c

Note the following guidelines about the preceding command:

• For more information about the history of the preceding command, use the pkghistory command. See pkg (1).

• You do not have to specify the entire package name, only the trailing portion of thename that is unique. See pkg(5).

• Oracle recommends that you install the solaris-minimal-server group packageand then install oracle-database-preinstall-19c.

Related Topics

• Oracle Solaris Documentation

Chapter 3Installing the Oracle Database Prerequisites Packages for Oracle Solaris

3-4

http://docs.oracle.com/en/operating-systems/solaris.html

4Configuring Oracle Solaris OperatingSystems for Oracle Grid Infrastructure

Complete operating system configuration requirements and checks for Oracle Solarisoperating systems before you start installation.

• Guidelines for Oracle Solaris Operating System InstallationDecide how you want to install Oracle Solaris.

• Reviewing Operating System and Software Upgrade Best PracticesThese topics provide general planning guidelines and platform-specific informationabout upgrades and migration.

• Reviewing Operating System Security Common PracticesSecure operating systems are an important basis for general system security.

• About Installation Fixup ScriptsOracle Universal Installer detects when the minimum requirements for aninstallation are not met, and creates shell scripts, called fixup scripts, to finishincomplete system configuration steps.

• About Operating System RequirementsDepending on the products that you intend to install, verify that you have therequired operating system kernel and packages installed.

• Operating System Requirements for Oracle Solaris on SPARC (64-Bit)The kernels and packages listed in this section are supported for this release onSPARC 64-bit systems for Oracle Database and Oracle Grid Infrastructure.

• Operating System Requirements for Oracle Solaris on x86–64 (64-Bit)The kernels and packages listed in this section are supported for this release onx86–64 (64-bit) systems for Oracle Database and Oracle Grid Infrastructure.

• Additional Drivers and Software Packages for Oracle SolarisInformation about optional drivers and software packages.

• Checking the Software Requirements for Oracle SolarisCheck the software requirements of your Oracle Solaris operating system to see ifthey meet minimum requirements for installation.

• About Oracle Solaris Cluster Configuration on SPARCReview the following information if you are installing Oracle Grid Infrastructure onSPARC processor servers.

• Running the rootpre.sh Script on x86 with Oracle Solaris ClusterOn x86 (64-bit) platforms running Oracle Solaris, if you install Oracle SolarisCluster in addition to Oracle Clusterware, then complete the following task.

• Enabling the Name Service Cache DaemonTo allow Oracle Clusterware to better tolerate network failures with NAS devicesor NFS mounts, enable the Name Service Cache Daemon (nscd).

• Setting Network Time Protocol for Cluster Time SynchronizationOracle Clusterware requires the same time zone environment variable setting onall cluster nodes.

4-1

• Using Automatic SSH Configuration During InstallationTo install Oracle software, configure secure shell (SSH) connectivity between allcluster member nodes.

Guidelines for Oracle Solaris Operating System InstallationDecide how you want to install Oracle Solaris.

Refer to your Oracle Solaris documentation to obtain information about installingOracle Solaris on your servers. You may want to use Oracle Solaris 11 installationservices, such as Oracle Solaris Automated Installer (AI), to create and manageservices to install the Oracle Solaris 11 operating system over the network.

Related Topics

• Oracle Solaris Documentation

• Installing Oracle Solaris 11 Guide

• Resources for Running Oracle Database on Oracle Solaris

Reviewing Operating System and Software Upgrade BestPractices

These topics provide general planning guidelines and platform-specific informationabout upgrades and migration.

• General Upgrade Best PracticesBe aware of these guidelines as a best practice before you perform an upgrade.

• New Server Operating System Upgrade OptionYou can upgrade your operating system by installing a new operating system on aserver, and then migrating your database either manually, or by using Export/Import method.

• Oracle ASM Upgrade NotificationsUnderstand Oracle ASM upgrade options and restrictions.

General Upgrade Best PracticesBe aware of these guidelines as a best practice before you perform an upgrade.

If you have an existing Oracle Database installation, then do the following:

• Record the version numbers, patches, and other configuration information

• Review upgrade procedures for your existing installation

• Review Oracle Database upgrade documentation before proceeding withinstallation, to decide how you want to proceed

Caution:

Always create a backup of existing databases before starting anyconfiguration change.

Chapter 4Guidelines for Oracle Solaris Operating System Installation

4-2

http://docs.oracle.com/en/operating-systems/solaris.htmlhttp://www.oracle.com/technetwork/articles/servers-storage-admin/sol-why-os-matters-1961737.html

Refer to Oracle Database Upgrade Guide for more information about requiredsoftware updates, pre-upgrade tasks, post-upgrade tasks, compatibility, andinteroperability between different releases.

Related Topics


New Server Operating System Upgrade OptionYou can upgrade your operating system by installing a new operating system on aserver, and then migrating your database either manually, or by using Export/Importmethod.

Note:

Confirm that the server operating system is supported, and that kernel andpackage requirements for the operating system meet or exceed the minimumrequirements for the Oracle Database release to which you want to migrate.

Manual, Command-Line Copy for Migrating Data and Upgrading Oracle Database

You can copy files to the new server and upgrade it manually. If you use thisprocedure, then you cannot use Oracle Database Upgrade Assistant. However, youcan revert to your existing database if you encounter upgrade issues.

1. Copy the database files from the computer running the previous operating systemto the one running the new operating system.

2. Re-create the control files on the computer running the new operating system.

3. Manually upgrade the database using command-line scripts and utilities.

See Also:

Oracle Database Upgrade Guide to review the procedure for upgrading thedatabase manually, and to evaluate the risks and benefits of this option

Export/Import Method for Migrating Data and Upgrading Oracle Database

You can install the operating system on the new server, install the new OracleDatabase release on the new server, and then use Oracle Data Pump Export andImport utilities to migrate a copy of data from your current database to a new databasein the new release. Data Pump Export and Import are recommended for higherperformance and to ensure support for new data types.

Chapter 4Reviewing Operating System and Software Upgrade Best Practices

4-3

See Also:

Oracle Database Upgrade Guide to review the Export/Import method formigrating data and upgrading Oracle Database

Oracle ASM Upgrade NotificationsUnderstand Oracle ASM upgrade options and restrictions.

• You can upgrade Oracle Automatic Storage Management (Oracle ASM) 11grelease 2 (11.2) and later without shutting down an Oracle RAC database byperforming a rolling upgrade either of individual nodes, or of a set of nodes in thecluster. However, if you have a standalone database on a cluster that uses OracleASM, then you must shut down the standalone database before upgrading.

• The location of the Oracle ASM home changed in Oracle Grid Infrastructure 11grelease 2 (11.2) so that Oracle ASM is installed with Oracle Clusterware in theOracle Grid Infrastructure home (Grid home).

• Two nodes of different releases cannot run in the cluster. When upgrading fromOracle Grid Infrastructure 11g release 2 (11.2) or Oracle Grid Infrastructure 12crelease 1 (12.1) to a later release, if there is an outage during the rolling upgrade,then when you restart the upgrade, ensure that you start the earlier release ofOracle Grid Infrastructure and bring the Oracle ASM cluster back in the rollingmigration mode.

Reviewing Operating System Security Common PracticesSecure operating systems are an important basis for general system security.

Ensure that your operating system deployment is in compliance with common securitypractices as described in your operating system vendor security guide.

About Installation Fixup ScriptsOracle Universal Installer detects when the minimum requirements for an installationare not met, and creates shell scripts, called fixup scripts, to finish incomplete systemconfiguration steps.

If Oracle Universal Installer detects an incomplete task, then it generates fixup scripts(runfixup.sh). You can run the fixup script and click Fix and Check Again. The fixupscript modifies both persistent parameter settings and parameters in memory, so youdo not have to restart the system.

The Fixup script does the following tasks:

• Sets kernel parameters, if necessary, to values required for successful installation,including:

– Shared memory parameters.

– Open file descriptor and UDP send/receive parameters.

• Creates and sets permissions on the Oracle Inventory (central inventory) directory.

Chapter 4Reviewing Operating System Security Common Practices

4-4

• Creates or reconfigures primary and secondary group memberships for theinstallation owner, if necessary, for the Oracle Inventory directory and theoperating system privileges groups.

• Sets shell limits, if necessary, to required values.

Note:

Using fixup scripts does not ensure that all the prerequisites for installingOracle Database are met. You must still verify that all the preinstallationrequirements are met to ensure a successful installation.

Oracle Universal Installer is fully integrated with Cluster Verification Utility (CVU)automating many prerequisite checks for your Oracle Grid Infrastructure or OracleReal Application Clusters (Oracle RAC) installation. You can also manually performvarious CVU verifications by running the cluvfy command.

Related Topics

• Oracle Clusterware Administration and Deployment Guide

About Operating System RequirementsDepending on the products that you intend to install, verify

grid infrastructure installation and upgrade guide · 2019. 11. 4. · the information contained...

Documents