19c Grid Infrastructure and Database Upgrade steps for Exadata Database Machine running on Oracle Linux
(Doc ID 2542082.1)
Last updated on MARCH 12, 2021
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.3.1 - Check current status of the services and related instances |
| Step 2.5.3.2 - Relocate or stop services on the node to be maintained |
| 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 4.1 - Backing up the Standby Database and creating a Guaranteed Restore Point (Only Data Guard) |
| Step 4.1.1 - Ensure the Primary SCN is ahead of the standby. |
| Step 4.1.2 - Check the Standby LAG |
| Step 4.1.3 - Verify that the primary is ready to switch to standby |
| Step 4.1.4 - Cancel Managed Recovery on Standby |
| Step 4.1.5 - Ensure Standby database is READ ONLY or MOUNTED mode |
| Step 4.1.6 - Create GRP first on Standby and Validate |
| Step 4.1.7 - Enable Managed Recovery |
| Step 4.1.8 - Check the Standby LAG |
| Step 4.2 - Analyze the Database to Upgrade with the Pre-Upgrade Information Tool |
| Step 4.2.1 - Run Pre-Upgrade Information Tool for Non-CDB or CDB database |
| Step 4.2.2 - Handle obsolete and underscore parameters |
| Step 4.2.3 - Review PreUpgrade information tool output |
| Step 4.2.4 - Requirements for Upgrading Databases That Use Oracle Label Security and Oracle Database Vault |
| Step 4.3 - Move the Standby Database to the 19c RDBMS Home (Only Data Guard) |
| Step 4.3.1 - Disable Fast-Start Failover |
| Step 4.3.2 - Shutdown the standby database and restart it in the 19c database home |
| Step 4.3.3 - Check the Standby LAG |
| Step 4.4 - Database Checks Before Upgrade |
| Step 4.4.1 - All PDBs must be open in Read/Write mode |
| Step 4.4.2 - Change preference for concurrent statistics gathering |
| Step 4.4.3 - Stop and disable all services with PRECONNECT as option for 'TAF Policy specification' |
| Step 4.5 - Oracle Application Express (Apex) manual Upgrade |
| Step 4.5.1 - Install Apex component |
| Step 4.5.2 - Check the old schema for Apex |
| Step 4.5.3 - Remove old APEX schema for Non-CDB |
| Step 4.5.3 - Remove old Apex schema for CDB and all PDB's |
| Step 4.6 - Upgrade the Database with Database Upgrade Assistant (DBUA) |
| Step 4.6.1 - Running DBUA in Silent Mode |
| Step 4.6.2 - Validate component versions and status after upgrade |
| Step 4.6.3 - Check the Standby LAG (Data Guard Only) |
| Step 4.6.4 - Configuring Transparent Data Encryption |
| Step 4.7 - Using Unplug/Plug method Pluggable database(PDB) sequential upgrades (Optional) |
| Step 4.7.1 - Pre-Upgrade Tasks |
| Step 4.7.1.1 - Run Pre-Upgrade Tool |
| Step 4.7.1.2 - Upgrade APEX |
| Step 4.7.1.3 - Check concurrent statistics for the PDB |
| Step 4.7.1.4 - Export Key from PDB |
| Step 4.7.2 - Unplug the PDB |
| Step 4.7.3 - Plug the PDB |
| Step 4.7.4 - Upgrade Pluggable Database |
| Step 4.7.5 - Update the TimeZone for the plugged-in PDB |
| Step 4.7.6 - Validate component versions and status after upgrade |
| Step 4.7.7 - Rename the datafiles to the new CDB (optional) |
| Step 4.8 - Completing remaining tasks for Oracle Database |
| Step 4.8.1 - Review and perform steps in Oracle Upgrade Guide, Chapter 5 'Post-Upgrade Tasks for Oracle Database' |
| Step 4.8.2 - Validate that the database is not in DST upgrade mode |
| Step 4.8.3 - Change Custom Scripts and environment variables to Reference the 19c Database Home |
| Step 4.8.4 - Initialization Parameters |
| Step 4.8.5 - When available, run 19c Bundle Patch Post-Installation Steps |
| Step 4.8.6 - Enable Fast-Start Failover (Only Data Guard) |
| Step 4.8.7 - Open the Standby database to READ ONLY (Only for ADG) |
| Step 4.8.8 - Remove Guaranteed Restore Point |
| Step 4.8.9 - Re-configure RMAN Media Management Library |
| Step 4.8.10 - Restore settings for concurrent statistics gathering |
| Step 4.8.11 - Restore idle-timeout to defaults |
| 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, 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 |