Skip to main content

Cleaning Up Inactive Patches in Oracle RAC

🧼 Cleaning Up Inactive Patches in Oracle RAC

In Oracle RAC environments, patches accumulate over time, many of which become inactive due to rollback, superseding, or failed attempts. These inactive patches can clutter the patch inventory, slow down operations, and introduce inconsistencies across nodes. This post explains how to clean them up safely using opatch util deleteinactivepatches, and why it's essential to run this under both Grid Infrastructure and Oracle RDBMS users. 


$ORACLE_HOME/OPatch/opatch util deleteinactivepatches -silent

🔍 What Does This Command Do?

This command removes all inactive patches from the Oracle inventory. These include:

  • Rolled-back patches
  • Superseded interim or PSU patches
  • Obsolete metadata left from earlier patch attempts
It frees up space, reduces conflict risk, and improves future patching performance. The -silent flag allows it to run without user input.

⚙️ Importance in RAC Setup

Oracle RAC requires consistent patch levels across all cluster nodes. An unclean patch inventory can:

  • Cause mismatched metadata errors
  • Slow down opatchauto validations
  • Increase cluster-wide patching time
To avoid these, patch cleanup must be performed under both:
  • grid user — for Grid Infrastructure Home
  • oracle user — for RDBMS Oracle Home

🛠 Mandatory Cleanup Steps (Grid + Oracle Users)

Follow these steps in both Grid and Oracle environments: 


sudo su -
su - grid

# 🔍 Check inactive patches
$ORACLE_HOME/OPatch/opatch util listorderedinactivepatches

# 📁 Check OPatch config
cat $ORACLE_HOME/OPatch/config/opatch.properties
# ➤ Ensure this line exists:
# RETAIN_INACTIVE_PATCHES=1
# This setting keeps the latest patch and one one-off for rollback safety.

# 🧹 Delete inactive patches
$ORACLE_HOME/OPatch/opatch util deleteinactivepatches -silent

exit

# Repeat the same steps for Oracle RDBMS home
su - oracle

# 🔍 Check inactive patches
$ORACLE_HOME/OPatch/opatch util listorderedinactivepatches

# 📁 Check OPatch config
cat $ORACLE_HOME/OPatch/config/opatch.properties
# ➤ Ensure this line exists:
# RETAIN_INACTIVE_PATCHES=1

# 🧹 Delete inactive patches
$ORACLE_HOME/OPatch/opatch util deleteinactivepatches -silent

🔁 Note: Both users must perform the cleanup on their respective Oracle Homes to maintain RAC consistency.

🔐 Best Practices

  • ✅ Set RETAIN_INACTIVE_PATCHES=1 in opatch.properties
  • ✅ Always validate patch success before cleanup
  • ✅ Backup Oracle Home and Central Inventory as a precaution
  • ✅ Automate cleanup via post-patch scripts or Ansible

📌 Conclusion

Using opatch util deleteinactivepatches as both grid and oracle users ensures a clean and consistent environment for future patching. It's a must-have step in your Oracle RAC patch lifecycle, and doing it right helps avoid inventory bloat, improves performance, and simplifies maintenance. Add it to your post-patch checklist today! ✅

Labels:

Comments

Post a Comment

Popular posts from this blog

🚀 Automating Oracle Database Patching with Ansible: A Complete Guide

Oracle database patching has long been the bane of DBAs everywhere. It's a critical task that requires precision, expertise, and often results in extended maintenance windows. What if I told you that you could automate this entire process, reducing both risk and downtime while ensuring consistency across your Oracle estate? 💡 In this comprehensive guide, I'll walk you through a production-ready Ansible playbook that completely automates Oracle patch application using OPatch. Whether you're managing a single Oracle instance or hundreds of databases across your enterprise, this solution will transform your patch management strategy! 🎯 🔥 The Challenge: Why Oracle Patching is Complex Before diving into the solution, let's understand why Oracle patching is so challenging: 🔗 Multiple dependencies : OPatch versions, Oracle Home configurations, running processes ⚠️ Risk of corruption : Incorrect patch application can render databases unusable ⏰ Downtime requirements : Da...
Post a Comment
Read more

Complete Guide to PostgreSQL 18 Source Installation with Performance Optimization

PostgreSQL 18 brings powerful new features and performance improvements that make it an excellent choice for modern database workloads. In this comprehensive guide, I'll walk you through installing PostgreSQL 18 from source code while implementing a strategic disk layout that maximizes performance. Why Install from Source? While package managers offer convenience, building PostgreSQL from source gives you complete control over configuration and optimization options. This flexibility allows you to tailor the database precisely to your hardware and workload requirements. Prerequisites Before we begin, ensure you're working with a RHEL, CentOS, or Fedora-based system. We'll be installing several development tools and libraries needed for compilation. Installation Process 1. Download PostgreSQL 18 Source Code First, grab the latest PostgreSQL 18 source tarball: wget https://ftp.postgresql.org/pub/source/v18.0/postgresql-18.0.tar.gz 2. Install Required Dependencies Install all n...
Post a Comment
Read more

⚡ Automating Oracle 19c Database Patching on Windows Server with PowerShell

Applying Oracle patches on Windows often feels repetitive and error-prone — stopping services, updating OPatch, applying patches, running datapatch , and restarting services. To save time ⏱ and reduce mistakes ⚠, I created a PowerShell automation script that performs the patching process end-to-end 🚀. 🔹 Why Automate Oracle Patching? ⏱ Save time by automating repetitive steps ⚙ Avoid manual errors during patching 📜 Maintain logs for auditing and troubleshooting 🛡 Ensure consistent, reliable patching 🔹 Full PowerShell Script # --- CONFIGURATION --- $oracleHome = "c:\users\administrator\downloads\v982656-01" # Change if this is not your actual Oracle Home! $patchDir = "C:\Users\Administrator\Downloads\p37962957_190000_MSWIN-x86-64\37962957" #update the Patchfile directory $opatchDir = "$oracleHome\OPatch" $opatchZip = "C:\Users\Administrator\Downloads\p6880880_190000_MSWIN-x86-64.zip" #Based on your setup update Opatch di...
Post a Comment
Read more