19c Grid Infrastructure and Database Upgrade steps for Exadata Database Machine running on Oracle Linux
(Doc ID 2542082.1)
Last updated on AUGUST 10, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]Oracle Exadata Storage Server Software - Version 19.1.2.0.0 and later
Linux x86-64
Purpose
This document provides step-by-step instructions for upgrading Oracle Database and Oracle Grid Infrastructure, from Oracle Database 11.2.0.4 and higher, and Grid Infrastructure (GI) Version 12.1.0.2 and higher to DB and GI version Release 19c 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 19c.
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 |
| Grid Infrastructure or Database 11.2.0.4, 12.1.0.2, 12.2.0.1 or 18c upgrade to 19c |
| Overview |
| Conventions |
| Assumptions |
| References |
| Oracle Documentation |
| My Oracle Support Documents |
| Phase 1 - Prepare the Existing Environment |
| Step 1.1 - Planning |
| Step 1.1.1 - Evaluate checklist for continuous application service during maintenance window |
| 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 19c Upgrade Prerequisites |
| Step 1.2.1 - Required Exadata Storage Server Software version |
| Step 1.2.2 - Grid Infrastructure and Database Software |
| Step 1.2.3 - Required Grid Infrastructure and Database Patches |
| Step 1.2.3.1 - Grid Infrastructure Upgrade to 19c |
| Step 1.2.3.2 - Database Upgrade to 19c |
| Step 1.2.3.3 - Managing older database with 19c Grid Infrastructure: |
| Step 1.2.4 - Generic Requirements |
| Step 1.2.5 - ASM password location |
| Step 1.2.6 - ACFS Supported Transport |
| Step 1.2.7 - Oracle Application Express(APEX) Supported Versions |
| Step 1.2.8 - Data Guard considerations |
| Step 1.3 - Preparations for upgrades on Oracle Exadata Database Machine deployed as non-virtual configuration |
| Step 1.3.1 - Download and staging Required Files |
| Step 1.3.2 - Update OPatch in the source Grid Home and Database Homes on all Database Servers |
| Step 1.3.3 - Prepare installation software |
| Step 1.3.3.1 - Create the new 19c Grid Infrastructure (GI_HOME) |
| Step 1.3.3.2 - Unzip Grid Installation software |
| Step 1.3.3.3 - Unzip latest OPatch into the new Grid Installation Software |
| Step 1.3.3.4 - Unzip latest RU patches into the staging area if available |
| Step 1.3.3.5 - Unzip latest One-off Patches into the staging area |
| Step 1.3.4 - Generate a Response File for Grid Infrastructure Upgrade (Only for Silent Mode) |
| Step 1.3.5 - Apply a Grid Infrastructure Patch Before Grid Infrastructure Configuration is Executed |
| Step 1.3.6 - Validate Readiness for Oracle Clusterware Upgrade using CVU |
| Step 1.3.7 - Using Dry-Run Upgrade Mode to Check System Upgrade Readiness |
| Step 1.3.7.1 - Execute Dry-Run Mode in Interactive Mode |
| Step 1.3.7.1.1 - Select configuration options from the installer screens |
| Step 1.3.7.1.2 - Execute rootupgrade.sh only on the local database server |
| Step 1.3.7.1.3 - Continue with 19c GI installation in wizard |
| Step 1.3.7.2 - Execute Dry-Run Mode in Silent Mode |
| Step 1.3.8 - Validate oracle binary is relinked with RDS |
| Step 1.4 - Preparations for upgrade on Oracle Exadata Database Machine deployed as virtual (KVM or Xen) configuration |
| Step 1.4.1 - Download and unzip Exadata Deployment Assistant (OEDA) |
| Step 1.4.2 - Download and stage gold images |
| Step 1.5 - Validate Environment |
| Step 1.5.1 - Update and run Exachk |
| Step 1.5.2 - Download and Run Pre-Upgrade Information Tool to analyze databases to be upgraded |
| Step 1.5.3 - Verify and remove HAIP |
| Scenario 1: HAIP is not enabled: |
| Scenario 2: HAIP is in use and Grid Infrastructure is 12.2 and higher |
| Scenario 3: HAIP is in use, Grid Infrastructure is 12.1 and ACFS is not in use |
| Scenario 4: HAIP is in use, Grid Infrastructure is 12.1 and ACFS is in use |
| Step 1.5.4 - Idle timeout setting management |
| Phase 2 - Upgrade Grid Infrastructure to 19c |
| Step 2.1 - Understand how MGMTDB is handled during upgrade |
| Step 2.2 - Validate HugePages Memory Allocation |
| 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 - Investigate Log for Errors (TFA) |
| Step 2.4.2 - Verify no active rebalance is running |
| Step 2.4.3 - Verify stack size setting |
| Step 2.4.4 - Verify ACFS Supported Replication |
| Step 2.5 - Oracle Exadata Database Machine deployed as a non-virtual configuration |
| Step 2.5.1 - Recommended Graceful Application Switchover Workflow |
| Step 2.5.2 - Execute gridSetup.sh on the first database node |
| Step 2.5.3 - Gracefully drain connections |
| Step 2.5.4 - Execute rootupgrade.sh |
| Step 2.5.5 - Complete the configuration |
| Step 2.5.6 - Verify cluster status |
| Step 2.6 - Oracle Exadata Database Machine deployed as a virtual (KVM or Xen) configuration |
| Step 2.6.1 - Update OEDA configuration with non-default passwords |
| Step 2.6.2 - Discover current Exadata configuration |
| Step 2.6.3 - Upgrade Cluster to 19c |
| Step 2.6.4 - Verify cluster status |
| Step 2.7 - Post-Upgrade |
| Step 2.7.1 - ASM Password Location |
| Step 2.7.2 - Verify Flex ASM Cardinality is set to "ALL" |
| Step 2.7.3 - Change Custom Scripts and environment variables to Reference the 19c Grid Home |
| Step 2.7.4 - Perform DBFS Required Updates (DBFS only) |
| Step 2.7.4.1 - Obtain latest mount-dbfs.sh script |
| Step 2.7.4.2 - Edit mount-dbfs.conf script and Oracle Net files for the new 19c environment |
| Step 2.7.5 - Perform Inventory update |
| Step 2.7.6 - Disable Diagsnap for Exadata |
| Step 2.7.7 - Advance ASM Compatible Diskgroup Attribute |
| Phase 3 - Install Database 19c Software |
| Step 3.1 - Oracle Exadata Database Machine deployed as a non-virtual 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 - Unzip latest OPatch into the new Oracle Installation Software |
| Step 3.1.4 - Register 19c Database Software Installation with the Oracle Universal Installer (OUI) |
| Step 3.1.4.1 - Using the Oracle Universal Installer in Interactive Mode |
| Step 3.1.4.2 - Using the Oracle Universal Installer in Silent Mode |
| Step 3.1.5 - When available: Install the latest 19c GI RU (which includes the DB RU) to the Database Home when available |
| Step 3.1.5.1 - Stage the patch |
| Step 3.1.5.2 - Patch 19c database home |
| Step 3.1.6 - Apply Customer-specific 19c One-Off Patches |
| Step 3.1.7 - Verify relink of Oracle Executable in Database Home with RDS |
| Step 3.2 - Oracle Exadata Database Machine deployed as a virtual (KVM or Xen) configuration |
| 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 19c |
| Step 4a - Using AutoUpgrade for Oracle Database Upgrades |
| Step 4a.1 - Review Considerations for Database Upgrade to 19c |
| Step 4a.2 - Obtain the Latest AutoUpgrade Version |
| Step 4a.3 - Set ORACLE_BASE environment variable |
| Step 4a.4 - Create AutoUpgrade Configuration File |
| Step 4a.5 - (TDE Only) Configure AutoUpgrade Configuration File for Wallet Root Conversion |
| Step 4a.6 - Run Latest EXAchk and Address Critical Alerts |
| Step 4a.7 - Analyze the Database to Upgrade with AutoUpgrade Analyze |
| Step 4a.8 - (Data Guard Only) Creating a Guaranteed Restore Point |
| Step 4a.8.1 - Check the Standby LAG |
| Step 4a.8.2 - Verify that the Primary is Ready to Switch to Standby |
| Step 4a.8.3 - Cancel Redo Apply on the Standby |
| Step 4a.8.4 - Ensure Standby Database is in READ ONLY or MOUNTED Mode |
| Step 4a.8.5 - Create GRP on Standby and Validate |
| Step 4a.8.6 - Enable Redo Apply on the Standby |
| Step 4a.8.7 - Check the Standby LAG |
| Step 4a.9 - Prepare the Database to Upgrade with AutoUpgrade Fixup Processing Mode |
| Step 4a.9.1 - Run AutoUpgrade Fixup Processing Mode |
| Step 4a.9.2 - Handle Obsolete and Underscore Parameters (Data Guard Only) |
| Step 4a.9.3 - Requirements for Upgrading Databases that use Oracle Label Security and Oracle Database Vault |
| Step 4a.10 - (Data Guard Only) Move the Standby Database to the 19c RDBMS Home |
| Step 4a.10.1 - Disable Fast-Start Failover |
| Step 4a.10.2 - Shutdown the Standby Database and Restart it in the 19c Database Home |
| Step 4a.10.3 - Check the Standby LAG |
| Step 4a.11 - Upgrade the Primary Database with AutoUpgrade Deploy Processing Mode |
| Step 4a.11.1 - Running AutoUpgrade in Deploy Processing Mode |
| Step 4a.11.2 - Validate component versions and status after upgrade |
| Step 4a.11.3 - (Data Guard Only) Check the Standby LAG |
| Step 4a.12 - Perform Post Upgrade Steps |
| Step 4a.12.1 - Validate that the database is not in DST upgrade mode |
| Step 4a.12.2 - Change Custom Scripts and environment variables to Reference the 19c Database Home |
| Step 4a.12.3 - (Data Guard Only) Enable Fast-Start Failover |
| Step 4a.12.4 - (ADG Only) Open the Standby database to READ ONLY |
| Step 4a.12.5 - Drop Guaranteed Restore Point on Standby and Primary |
| Step 4a.12.6 - Re-configure RMAN Media Management Library |
| Step 4a.12.7 - Restore idle-timeout to defaults |
| Step 4a.12.8 - Run EXAchk |
| Step 4a.12.9 - Optionally set the COMPATIBLE Parameter |
| Step 4b - Unplugging, Plugging, and Upgrading a PDBto a New CDB |
| Step 4b.1 - Pre-Upgrade Tasks |
| Step 4b.1.1 - Run Pre-Upgrade Tool |
| Step 4b.1.2 - Upgrade APEX |
| Step 4b.1.3 - Check concurrent statistics for the PDB |
| Step 4b.1.4 - Export Key from PDB |
| Step 4b.2 - Unplug the PDB |
| Step 4b.3 - Plug the PDB |
| Step 4b.4 - Upgrade Pluggable Database |
| Step 4b.5 - Update the TimeZone for the plugged-in PDB |
| Step 4b.6 - Validate component versions and status after upgrade |
| Step 4b.7 - Rename the datafiles to the new CDB (optional) |
| Phase 5 - Post-upgrade Steps |
| Step 5.1 - Run Exachk |
| Step 5.2 - Deinstall the 11.2.0.4, 12.1.0.2, 12.2.0.1 or 18c Database and Grid Homes (optional) |
| Step 5.2.1 - Oracle Exadata Database Machine deployed as a non-virtual configuration |
| Step 5.2.2 - Oracle Exadata Database Machine deployed as a virtual (KVM or Xen) configuration |
| Troubleshooting |
| Revision History |
| References |