My Oracle Support Banner

18.1.0.0 Grid Infrastructure and Database Upgrade steps for Exadata Database Machine running 11.2.0.4 and later on Oracle Linux (Doc ID 2369422.1)

Last updated on JUNE 05, 2019

Applies to:

Oracle Exadata Storage Server Software - Version 18.1.4.0.0 and later
Oracle Exadata Hardware
Information in this document applies to any platform.

Purpose

This document provides step-by-step instructions for upgrading Oracle Database and Oracle Grid Infrastructure from Oracle Database and Grid Infrastructure (GI) Version 11.2.0.4 and higher to DB and GI version Release 18.1 on Exadata Database Machine on Linux.

This document may not be used for upgrade on Oracle SuperCluster running Oracle Solaris SPARC of Oracle Database and Oracle Grid Infrastructure to 18.1.0.0.0.

 

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Details
 Oracle Exadata Database Machine Maintenance
 Grid Infrastructure or Database 11.2.0.4, 12.1.0.1, 12.1.0.2 or 12.2.0.1 upgrade to 18.1.0.0
 Latest Exadata Upgrade and Life Cycle Management News
 Overview
 Conventions
 Assumptions
 References
 Oracle Documentation
 My Oracle Support Documents
 Phase 1 - Prepare the Existing Environment
 Step 1.1 - Planning
 Step 1.1.1 - Graceful application switchover between RAC nodes with no application interruption.
 Step 1.1.2 - Testing on non-production first
 Step 1.1.3 - Implement SQL Plan Management to preserve SQL Performance After Upgrade
 Step 1.1.4 - Backup and Fallback
 Step 1.1.5 - Obtain Required Database and Operating System Account Access Account Access
 Step 1.2 - Review 18.1.0.0 Upgrade Prerequisites
 Step 1.3 - Preparations for upgrades on Exadata Bare Metal configuration
 Step 1.3.1 - Download and staging Required Files
 Step 1.3.2 - Update OPatch in existing 11.2, 12.1 and 12.2 Grid Home and Database Homes on All Database Servers:
 Step 1.3.3 - Prepare installation software
 Step 1.3.3.1 - Create the new 18.1 Grid Infrastructure (GI_HOME)
 Step 1.3.3.2 - Unzip Grid installation software
 Step 1.3.3.3 - Unzip Oneoff Patch 27535098 into the staging area
 Step 1.3.3.4 - Unzip  latest RU patches into the staging area if available
 Step 1.4 - Preparations for upgrade on Exadata Oracle Virtual Machine (OVM)
 Step 1.4.1 - Download the most recent gold images patch sets for 18.1
 Step 1.4.2 - Download required Exadata Deployment Assistant (OEDA) release
 Step 1.5 - Validate Environment
 Step 1.5.1 - Run Exachk
 Step 1.5.2 - Download and Run Pre-Upgrade Information Tool to analyze databases to be upgraded
 Step 1.5.3 - Validate Readiness for Oracle Clusterware upgrade using CVU
 Phase 2 - Upgrade Grid Infrastructure to 18.1.0.0
 Step 2.1 - Understand how MGMTDB is handled during upgrade
 Step 2.2 - Validate memory configuration for new ASM SGA requirements
 Step 2.3 -Create a snapshot based backup of the database server partitions
 Step 2.4 - Actions to take before executing gridSetup.sh on each database server
 Step 2.4.1 - Change SGA memory settings for ASM
 Step 2.4.2 - Verify values for memory_target, memory_max_target and use_large_pages
 Step 2.4.3 - Reset CSS misscount on RAC Cluster
 Step 2.4.4 - Diasble DiagSnap
 Step 2.4.5 - Verify no active rebalance is running
 Step 2.4.6 - Verify stack size setting
 Step 2.4.7 - Verify ACFS Supported Replication.
 Step 2.4.8 - Drain connections gracefully
 Step 2.5 - Exadata Bare Metal configurations
 Step 2.5.1 - Apply 18.1.0.0 RU or OneOff Patches to the Grid Infrastructure Home
 Step 2.5.2 - Select configuration options from the installer screens
 Step 2.5.3 - Validate oracle binary is relinked with RDS
 Step 2.5.4 - Execute rootupgrade.sh on each database server
 Step 2.5.5 - Continue with 18.1.0..0 GI installation in wizard
 Step 2.5.6 - Verify cluster status
 Step 2.6 - Exadata Oracle Virtual Machine (OVM)
 Step 2.6.1 - Discover current Exadata configuration
 Step 2.6.2 - Upgrade Cluster to 18.1.0.0
 Step 2.6.3 - Verify cluster status
 Step 2.7 - Verify Flex ASM Cardinality is set to "ALL"
 Step 2.8 -Change Custom Scripts and environment variables to Reference the 18.1.0.0 Grid Home
 Step 2.9 - PostUpgrade Step when Upgrading Grid Infrastructure from 11.2.0.4 to 18.1.0.0
 Step 2.10 - DBFS only - Perform DBFS Required Updates
 Step 2.10.1 - Obtain latest mount-dbfs.sh script from Document 1054431.1
 Step 2.10.2 - Edit mount-dbfs.conf script and Oracle Net files for the new 18.1.0.0 environment
 Step 2.11 - Using earlier Oracle Database Releases with Oracle Grid Infrastructure 18.1.0.0
 Step 2.12 - Disable Diagsnap for Exadata
 Step 2.13 - Advance COMPATIBLE.ASM diskgroup attribute
 Phase 3 - Install Database 18.1.0.0 Software
 Step 3.1 - Exadata Bare Metal configuration
 Step 3.1.1. - Create the new Oracle DB Home directory on all primary and standby database server nodes
 Step 3.1.2 - Extract the image to the database home
 Step 3.1.3 - Register 18.1.0.0 Database Software Installation with the Oracle Universal Installer (OUI) on both primary and standby servers
 Step 3.1.4 - Select configuration options from the installer screens
 Step 3.1.5 - If necessary: Install Latest OPatch 18.1 in the Database Home on All Database Servers
 Step 3.1.6 - When available: Install the latest 18.1.0.0 GI RU (which includes the DB RU) to the Database Home when available - Do Not Perform Post-Installation Steps
 Step 3.1.7 - Stage the patch
 Step 3.1.8 - Patch 18.1.0.0 database home
 Step 3.1.9 - Apply Customer-specific 18.1.0.0 One-Off Patches
 Step 3.1.0 - Verify relink of Oracle Executable in Database Home with RDS
 Step 3.2 - Exadata Oracle Virtual Machine (OVM)
 Step 3.2.1 - Add Database Home to the cluster(s)
 Step 3.2.2 - Validate the new database home are created
 Step 3.2.3 - Verify relink of Oracle Executable in Database Home with RDS
 Phase 4 - Upgrade Database to 18.1.0.0
 Step 4.1 - Backing up the database and creating a Guaranteed Restore Point
 Step 4.1.1 - Ensure the Primary SCN is ahead of the standby.
 Step 4.1.2 - Cancel Managed Recovery on Standby
 Step 4.1.3 - Ensure Standby database is OPEN READ ONLY
 Step 4.1.4 - Create GRP first on Standby and Validate.
 Step 4.1.5 - Create GRP on Primary and Validate
 Step 4.1.6 - Enable Managed Recovery
 Step 4.2 - Copy Transparent Encryption Oracle Wallets
 Step 4.3 - Analyze the Database to Upgrade with the Pre-Upgrade Information Tool
 Step 4.3.1 - Run Pre-Upgrade Information Tool for Non-CDB or CDB database
 Step 4.3.2 - Handle obsolete and underscore parameters
 Step 4.3.3 - Review PreUpgrade information tool output
 Step 4.3.4 - Execute Preupgrade Fixups for Non-CDB
 Step 4.3.5 - Execute PreUpgrade Fixups fro CDB
 Step 4.3.6 - Requirements for Upgrading Databases That Use Oracle Label Security and Oracle Database Vault
 Step 4.4 - Data Guard only - Synchronize Standby and Change the Standby Database to use the new 18.1.0.0 Database Home
 Step 4.4.1 - Flush all redo generated on the primary and disable the broker
 Step 4.4.2 - Data Guard only - Disable Fast-Start Failover and Data Guard Broker
 Step 4.4.3 - Shutdown the primary database.
 Step 4.4.4 - Shutdown the standby database and restart it in the 18.1.0.0 database home
 Step 4.5 - Restart Non-CDB and CDB database  before Upgrade
 Step 4.5.1 - Start all Non-CDB primary instances in restricted mode
 Step 4.5.2 - Start all Container databases(CDB) primary in normal Read/Write mode
 Step 4.5.3 - Change preference for concurrent statistics gathering
 Step 4.5.4 - Before starting the Database Upgrade Assistant (DBUA) stop and disable all services with PRECONNECT as option for 'TAF Policy specification'
 Step 4.6 - Oracle Application Express (Apex) manual Upgrade
 Step 4.6.1 - Install Apex component
 Step 4.6.2 - Check the old schema for Apex
 Step 4.6.2 - Remove old APEX schema for Non-CDB
 Step 4.6.3 - Remove old Apex schema for CDB and all PDB's
 Step 4.7 - Upgrade the Database with Database Upgrade Assistant (DBUA)
 Step 4.7.1 - Running DBUA on Non-CDB, Container database(CDB), and Pluggable database (PDB) :  
 Step 4.7.2 - Select configuration options from the installer screens
 Step 4.7.3 - Validate component versions and status after upgrade
 Step 4.7.4 - Complete the steps on Non-CDB  database, required by the pre-upgrade information tool. Take action on areas identified in the output.
 Step 4.7.5 - Execute PostUpgrade Fixups fro CDB. Take action on areas identified in the output.
 Step 4.7.6 - Open the Standby database to READ ONLY( if ADG)
 Step 4.8 - Using Unplug/Plug method Pluggable database(PDB) sequential upgrades (Optional)
 Step 4.8.1 - Unplug the database
 Step 4.8.2 - Plug the database
 Step 4.8.3 - Upgrade Pluggable Database 
 Step 4.8.4 - Update the TimeZone for the plugged-in PDB3.
 Step 4.8.5 - Validate component versions and status after upgrade
 Step 4.9 - Completing remaining tasks for Oracle Database
 Step 4.9.1 - Review and perform steps in Oracle Upgrade Guide, Chapter 4 'Post-Upgrade Tasks for Oracle Database'
 Step 4.9.2 - Change Custom Scripts and environment variables to Reference the 18.1.0.0 Database Home
 Step 4.9.3 - Initialization Parameters 
 Step 4.9.4 - When available: run 18.1.0.0 Bundle Patch Post-Installation Steps
 Step 4.9.5 - Data Guard only - Enable Fast-Start Failover and Data Guard Broker
 Step 4.9.6 - Remove Guaranteed Restore Point
 Step 4.9.7 - Re-configure RMAN Media Management Library
 Step 4.9.8 - Restore settings for concurrent statistics gathering
 Phase 5 - Post-upgrade Steps
 Step 5.1 - Run Exachk
 Step 5.2 - Deinstall the 11.2.0.4, 12.1.0.1, 12.1.0.2 or 12.2.0.1 Database and Grid Homes
 Step 5.2.1 - Exadata Bare Metal configurations
 Step 5.2.2 - Exadata Oracle Virtual Machine (OVM)
 Troubleshooting
 Revision History
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.