Upgrading Oracle RAC Database from 12c to 19c: Step-by-Step Guide
Upgrading an Oracle RAC database from 12c to 19c is a critical task to enhance performance, ensure extended support, and unlock new features. Here’s a simplified guide to streamline your upgrade process.
π§ Pre-Upgrade Preparations
1οΈβ£ Analyze Current Environment:
Verify the current database version (12c Release 2) and ensure it meets the upgrade prerequisites.
Use the opatch lsinventory command to confirm the latest patches are applied.
2οΈβ£ Download Upgrade Tools:
Download Oracle 19c binaries and the latest Pre-Upgrade Information Tool from Oracle Support.
3οΈβ£ Run the Pre-Upgrade Tool:
Execute preupgrade.jar to identify warnings and recommendations.
Fix any flagged issues (e.g., invalid objects, incompatible parameters).
4οΈβ£ Backup Everything:
Take a full backup of the database, OCR, voting disk, and Oracle Home.
5οΈβ£ Validate the Cluster:
Ensure the RAC nodes and shared storage are fully operational.
π Upgrade Steps
Step 1: Install Oracle 19c Software
Install the Oracle 19c binaries on all RAC nodes without affecting the existing 12c installation.
Step 2: Prepare the 12c RAC Database
Disable any unsupported features or components.
Stop listener services for the database youβre upgrading.
Step 3: Run Pre-Upgrade Fixups
Execute fix-up scripts generated by the preupgrade.jar tool to address pre-check warnings.
Step 4: Perform the Upgrade
Switch to the Oracle 19c environment:
export ORACLE_HOME=<19c_Oracle_Home>
export PATH=$ORACLE_HOME/bin:$PATH
Use the DBUA (Database Upgrade Assistant) or the command-line upgrade:
dbupgrade
Step 5: Post-Upgrade Fixups
Execute post-upgrade scripts such as utlrp.sql to recompile invalid objects.
Step 6: Test Your Database
Run functional and performance tests to ensure all components work as expected.
π Post-Upgrade Activities
β Update Configuration:
Update listener, tnsnames, and cluster configuration to point to the new Oracle Home.
β
Enable Deprecated Features (if required):
Address any deprecated or obsolete features that need configuration changes.
β
Backup Upgraded Database:
Take a fresh full backup of the upgraded RAC database.
β
Monitor Performance:
Use AWR and ADDM reports to monitor the database and optimize settings.
π‘ Pro Tip: Always perform the upgrade in a staging environment first to address any compatibility or application-specific issues before upgrading production.