12.2 Grid Infrastructure and Database Upgrade steps for Exadata Database Machine running 11.2.0.3 and later on Oracle Linux
(Doc ID 2111010.1)
Last updated on JUNE 13, 2023
Applies to:
Exadata Database Machine V2 - Version All Versions to All Versions [Release All Releases]Exadata Database Machine X2-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X5-8 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X3-8 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X6-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Purpose
This document provides step-by-step instructions for upgrading Oracle Database and Oracle Grid Infrastructure on Oracle Exadata Bare Metal configuration and Oracle Exadata Oracle Virtual Machine (OVM). The minimum version required to upgrade to Oracle 12.2.0.1 is 11.2.0.3 on Oracle Exadata Database Machine running Oracle Linux.
This document may also be used in conjunction with <Document 2186095.1> for upgrade of Oracle Database and Oracle Grid Infrastructure to 12.2.0.1 on Oracle Exadata Database Machine running Oracle Solaris x86-64 and Oracle SuperCluster running Oracle Solaris SPARC. <Document 2186095.1> contains Solaris-specific requirements, recommendations, guidelines, and workarounds that pertain to upgrade of Oracle Database and Oracle Grid Infrastructure to 12.2.0.1.
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 |
| Overview |
| Conventions |
| Assumptions |
| References |
| Oracle Documentation |
| My Oracle Support Documents |
| Prepare the Existing Environment |
| Planning |
| Testing on non-production first |
| SQL Plan Management |
| Recoverability |
| Account Access |
| Preparations for upgrades on Exadata Bare Metal configuration |
| Review 12.2.0.1 Upgrade Prerequisites |
| Exadata Storage Server and Database Server version 12.2.1.1.0 |
| Sun Datacenter InfiniBand Switch 36 is running software release 2.1.6-2 or later |
| Grid Infrastructure and Database Software |
| Generic Requirements |
| Do not place the new ORACLE_HOME under /opt/oracle. |
| Data Guard only - If there is a physical standby database associated with the databases being upgraded, then the following must be true |
| Download and staging Required Files |
| Apply required patches / updates where required before upgrading proceeds |
| Update OPatch in existing 11.2 and 12.1 Grid Home and Database Homes on All Database Servers: |
| For Exadata Storage Servers and Database Servers on releases earlier than Exadata 12.1.2.2.1 |
| For 11.2.0.3 Grid Infrastructure and Database |
| For 11.2.0.4 Grid Infrastructure and Database |
| For 12.1.0.1 Grid Infrastructure and Database |
| For 12.1.0.2 Grid Infrastructure and Database |
| Prepare installation software |
| Create the new Grid Infrastructure (GI_HOME) directory where 12.2.0.1 will be installed |
| Unzip installation software |
| Unzip latest RU patches into the staging area |
| Unzip latest RU OneOff patches into the staging area |
| Preparations for upgrade on Exadata Oracle Virtual Machine (OVM) |
| Download the most recent gold images patch sets for 12.2 |
| Prepare the gold disk image |
| Create User Domain(domU) specific reflinks |
| Add new devices to vm.cfg |
| Mount the new devices in domU |
| If available: For Exadata Oracle Virtual Machine (OVM) , Apply recommended patches to the Grid Infrastructure before running gridSetup.sh |
| Setup up Software on each domU before clusterware upgrade |
| Perform the exact steps as described below on the installer screens: |
| Adding devices to additional clusters in dom0 |
| Validate Environment |
| Run Exachk |
| Early stage pre-upgrade check: analyze your databases to be upgraded with the Pre-Upgrade Information Tool |
| Validate Readiness for Oracle Clusterware upgrade using CVU |
| Upgrade Grid Infrastructure to 12.2.0.1 |
| MGMTDB |
| No hugepage configuration for MGMTDB |
| Validate memory configuration for new ASM SGA requirements |
| Create a snapshot based backup of the database server partitions |
| Perform the 12.2.0.1 Grid Infrastructure software upgrade using Oracle Grid Infrastructure Setup wizard |
| Change SGA memory settings for ASM |
| Verify values for memory_target, memory_max_target and use_large_pages |
| Reset CSS misscount on RAC Cluster |
| Actions to take before executing gridSetup.sh on each database server |
| Exadata Bare Metal configurations |
| Apply Customer-specific 12.2.0.1 One-Off Patches to the Grid Infrastructure Home |
| Perform the exact steps as described below on the installer screens: |
| Exadata Oracle Virtual Machine (OVM) |
| Perform the exact steps as described below on the installer screens: |
| If necessary: Install Latest OPatch 12.2 |
| When required relink oracle binary with RDS |
| If ACFS is used in your environment, unmount and then run rootupgrade. |
| Execute rootupgrade.sh on each database server |
| Continue with 12.2.0.1 GI installation in wizard |
| Verify cluster status |
| Verify Flex ASM Cardinality is set to "ALL" |
| Change Custom Scripts and environment variables to Reference the 12.1.0.2 Grid Home |
| Modify the dbfs_mount cluster resource |
| Using earlier Oracle Database Releases with Oracle Grid Infrastructure 12.2 |
| Install Database 12.2.0.1 Software |
| Exadata Bare Metal configuration |
| Prepare Installation Software |
| Create the new Oracle DB Home directory on all primary and standby database server nodes |
| Perform 12.2.0.1 Database Software Installation with the Oracle Universal Installer (OUI) |
| Perform the exact actions as described below on the installer screens: |
| If necessary: Install Latest OPatch 12.2 in the Database Home on All Database Servers |
| When available: Install the latest 12.2.0.1 GI PSU (which includes the DB PSU) to the Database Home when available - Do Not Perform Post-Installation Steps |
| Stage the patch |
| OCM response file not required |
| Patch 12.2.0.1 database home |
| Skip patch post-installation steps |
| When available: Apply 12.2.0.1 Patch Overlay Patches to the Database Home as Specified in Document 888828.1 |
| Apply Customer-specific 12.2.0.1 One-Off Patches |
| When required relink Oracle Executable in Database Home with RDS |
| Exadata Oracle Virtual Machine (OVM) |
| Upgrade Database to 12.2.0.1 |
| Backing up the database and creating a Guaranteed Restore Point |
| Analyze the Database to Upgrade with the Pre-Upgrade Information Tool |
| Run Pre-Upgrade Information Tool for Non-CDB or CDB database |
| Handle obsolete and underscore parameters |
| Review pre-upgrade information tool output |
| Requirements for Upgrading Databases That Use Oracle Label Security and Oracle Database Vault |
| Data Guard only - Synchronize Standby and Change the Standby Database to use the new 12.2.0.1 Database Home |
| Flush all redo generated on the primary and disable the broker |
| Data Guard only - Disable Fast-Start Failover and Data Guard Broker |
| Shutdown the primary database. |
| Shutdown the standby database and restart it in the 12.2.0.1 database home |
| Start all Non-CDB primary instances in restricted mode |
| Start all Container databases(CDB) primary in normal Read/Write mode |
| Change preference for concurrent statistics gathering |
| Before starting the Database Upgrade Assistant (DBUA) stop and disable all services with PRECONNECT as option for 'TAF Policy specification' |
| Upgrade the Database with Database Upgrade Assistant (DBUA) |
| Running DBUA on Non-CDB, Container database(CDB), and Pluggable database (PDB) : |
| Complete the steps on Non-CDB database, required by the pre-upgrade information tool. Take action on areas identified in the output. |
| Complete the steps on a Container database (CDB), required by the pre-upgrade information tool.Take action on areas identified in the output. |
| Pluggable database(PDB) sequential upgrades using Unplug/Plug (Optional) |
| Review and perform steps in Oracle Upgrade Guide, Chapter 4 'Post-Upgrade Tasks for Oracle Database' |
| Change Custom Scripts and environment variables to Reference the 12.2.0.1 Database Home |
| Initialization Parameters |
| When available: run 12.2.0.1 Bundle Patch Post-Installation Steps |
| Data Guard only - Enable Fast-Start Failover and Data Guard Broker |
| Post-upgrade Steps |
| Remove Guaranteed Restore Point |
| Disable Diagsnap for Exadata |
| DBFS only - Perform DBFS Required Updates |
| Obtain latest mount-dbfs.sh script from Document 1054431.1 |
| Edit mount-dbfs.sh script and Oracle Net files for the new 12.2.0.1 environment |
| If using ACFS apply the fix for the bug 26791882 after the 12.2 Grid Infrastructure upgrade. |
| Run Exachk |
| Optional: Deinstall the 11.2.0.3, 11.2.0.4, 12.1.0.1 or 12.1.0.2 Database and Grid Homes |
| Exadata Bare Metal configurations |
| Exadata Oracle Virtual Machine (OVM) |
| Re-configure RMAN Media Management Library |
| Restore settings for concurrent statistics gathering |
| Advance COMPATIBLE.ASM diskgroup attribute |
| Using earlier Oracle Database Releases with Oracle Grid Infrastructure 12.2 |
| Installing earlier version of Oracle Database |
| Performing Inventory update |
| Troubleshooting |
| Revision History |
| References |