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

🚀 DB BOT: Real-Time Oracle & GoldenGate Monitoring in Slack

In today's fast-paced DevOps environment, quick access to database metrics is essential. This blog will walk you through creating a Slack bot that provides real-time monitoring of Oracle databases and Golden Gate replication. With simple slash commands, your team can check tablespace usage, Flash Recovery Area status, and Golden Gate replication health directly in Slack. Project Overview Our "DB Bot" offers these key capabilities: Monitor tablespace usage across multiple Oracle databases Check Flash Recovery Area (FRA) status on multiple databases View GoldenGate process status across different servers List GoldenGate credential stores Monitor replication lag in GoldenGate Prerequisites Node.js v14+ Python 3.6+ Oracle client libraries (instantclient_21_19) Access to Oracle databases and GoldenGate servers A Slack workspace with permissions to add apps   Project Structure oracle-slack-bot...
1 comment
Read more

Oracle Golden Gate Bi-directional Replication Implementation Guide

Oracle GoldenGate (OGG) is a comprehensive software package for real-time data integration and replication in heterogeneous IT environments. Bi-directional replication enables organizations to maintain synchronized data across multiple data centers, providing high availability, disaster recovery, and load distribution capabilities. This detailed guide provides step-by-step instructions for implementing Oracle GoldenGate bi-directional replication between two Oracle databases. Architecture Overview In this setup, we'll configure: TestDC1 : Primary data center with TestDB1 TestDC2 : Secondary data center with TestDB2 Bi-directional sync : Changes flow in both directions with conflict resolution Step 1: Software Installation ⚠️ SERVER EXECUTION: Perform these steps on BOTH TestDC1 and TestDC2 servers Step 1.1: Download and Prepare Software First, create the necessary directory structure and prepare for installation: # Create directory for the software mkdir /data01/ogg_setup cd /d...
Post a Comment
Read more