11.2.0.2, 11.2.0.3 or 11.2.0.4 to 12.1.0.1 Grid Infrastructure and Database Upgrade on Exadata Database Machine
(Doc ID 1555059.1)
Last updated on APRIL 28, 2022
Applies to:
Exadata Database Machine X2-2 Hardware - Version All Versions and laterExadata X4-2 Hardware - Version All Versions and later
Exadata X3-8 Hardware - Version All Versions and later
Oracle Exadata Storage Server Software - Version 11.2.1.2.0 and later
Exadata Database Machine V2 - Version All Versions and later
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 release 11.2.0.2, 11.2.0.3 or 11.2.0.4 to 12.1.0.1 on Oracle Exadata Database Machine running Oracle Linux and Oracle Solaris on x86-64 database servers. This document does not cover upgrading Oracle Database and Oracle Grid Infrastructure to 12.1.0.1 on SPARC SuperCluster (SSC).
Scope
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 |
| Scope |
| 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 |
| Review 12.1.0.1 Upgrade Prerequisites |
| Sun Datacenter InfiniBand Switch 36 is running software release 1.3.3-2 or later. |
| Grid Infrastructure Software |
| Database Software |
| Generic requirements |
| Exadata Storage Server software release 11.2.3.2.1 for Exadata database servers and Exadata storage servers with patch 16547261 applied on Exadata Storage Servers |
| Exadata database servers running 11.2.3.2.1 on Linux using must be running one of the following kernels prior to 12c Grid Infrastructure installation: |
| 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 Required Files |
| Patch matrix for 12539000 - Required Patches when upgrading from 11.2.0.2 Linux and Solaris x86-64 |
| Patch matrix for 14639430 - patch requirements for rolling-back upgrades from 12.1.0.1 to 11.2.0.2 Linux |
| Patch matrix for 14639430 - patch requirements for rolling-back upgrades from 12.1.0.1 to 11.2.0.3 Linux |
| Patch matrix for 13460353 - Optional patch for those who will be creating 11.2.0.2 databases while running a 12.1.0.1 Grid infrastructure |
| Patch matrix for 13460353 - Optional patch for those who will be creating 11.2.0.3 databases while running a 12.1.0.1 Grid infrastructure |
| Apply patches / updates where required before upgrading proceeds |
| Update OPatch in existing 11.2 Grid Home and existing 11.2 Database Homes on All Database Servers |
| For Exadata Storage Servers and Database Servers on releases earlier than Exadata 11.2.3.2.1: |
| For database servers running Exadata release 11.2.3.2.1 using Unbreakable Enterprise Kernel (UEK) - when on kernel 2.6.32-400.11.1.el5uek or 2.6.32-400.21.1.el5uek install kernel and packages: |
| For 11.2.0.2 Grid Infrastructure and Database: |
| For 11.2.0.3 Grid Infrastructure and Database: |
| Run Exachk or HealthCheck |
| Validate Readiness for Oracle Clusterware upgrade using CVU and Exachck |
| Early stage pre-upgrade check: analyze your databases to be upgraded with the Pre-Upgrade Information Tool |
| Install and Upgrade Grid Infrastructure to 12.1.0.1 |
| Validate hugepage configuration for new ASM sga requirements |
| Create a snapshot based backup of the database server partitions |
| Create the new Grid Infrastructure (GI_HOME) directory where 12.1.0.1 will be installed |
| Prepare installation software |
| Change css misscount setting back to default before upgrading |
| Perform the 12.1.0.1 Grid Infrastructure software installation and upgrade using OUI |
| Install OPatch 12.1 |
| Apply recommended patches to the Grid Infrastructure before running rootupgrade.sh |
| Patch 17065496 |
| Relink oracle binary with RDS before running the rootupgrade script |
| If available apply 12.1.0.1 Bundle Patch Overlay Patches to the Grid Infrastructure Home as Specified in Document 888828.1 |
| Apply Customer-specific 12.1.0.1 One-Off Patches to the Grid Infrastructure Home |
| Change SGA memory settings for ASM |
| Verify values for memory_target, memory_max_target and use_large_pages |
| Stop and disable OC4J in the 11.2 Grid Infrastructure home before running rootupgrade.sh |
| Stop non-default VIPs (for example vips on backup lan) |
| Checks to do before executing rootupgrade.sh on each database server |
| Change Custom Scripts and Environment Variables to Reference the 12.1.0.1 Grid Home |
| Modify the dbfs_mount cluster resource |
| Install Database 12.1.0.1 Software |
| Prepare Installation Software |
| Create the new Oracle DB Home directory on all database server nodes |
| Perform 12.1.0.1 Database Software Installation with the Oracle Universal Installer (OUI) |
| Relink Oracle Executable in Database Home with RDS |
| Update/Install OPatch in New Database Home on All Database Servers |
| Install the latest 12.1.0.1 GI PSU (which includes the DB PSU) to the Database Home when available - Do Not Perform Post-Installation Steps |
| Stage the patch |
| Create OCM response file if required |
| Patch 12.1.0.1 database home |
| Skip patch post-installation steps |
| When available: Apply 12.1.0.1 Patch Overlay Patches to the Database Home as Specified in Document 888828.1 |
| Apply Customer-specific 12.1.0.1 One-Off Patches |
| Upgrade Database to 12.1.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 |
| Handle obsolete and underscore parameters |
| Review pre-upgrade information tool output |
| Data Guard only - Synchronize Standby and Change the Standby Database to use the new 12.1.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 an 12.1.0.1 database home |
| Start all primary instances in restricted mode |
| Upgrade the Database with Database Upgrade Assistant (DBUA) |
| 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.1.0.1 Database Home |
| Underscore Initialization Parameters |
| When required: run PSU Post-Installation Steps |
| Data Guard only - Enable Fast-Start Failover and Data Guard Broker |
| Post-upgrade Steps |
| Remove Guaranteed Restore Point |
| 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.1.0.1 environment |
| Run Exachk or HealthCheck |
| Optional: Deinstall the 11.2.0.2, 11.2.0.3 or 11.2.0.4 Database and Grid Homes |
| Re-configure RMAN Media Management Library |
| Restore settings for concurrent statistics gathering |
| Troubleshooting |
| Revision History |
| Community Discussions |
| References |