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

Oracle RAC Switchover & Switchback: Step-by-Step Guide

 Ensuring business continuity requires regular Disaster Recovery (DR) drills. This guide covers the Switchover and Switchback process between Primary (DC) and Standby (DR) databases . Pre-checks Before Performing Switchover Before starting the activity, ensure there are no active sessions in the database. If any are found, share the session details with the application team, get their confirmation, and terminate the sessions. Primary Database Name: PRIMARY Standby Database Name: STANDBY  Identify Active Sessions set lines 999 pages 999 col machine for a30 col username for a30 col program for a30 compute sum of count on report break on report select inst_id,username,osuser,machine,program,status,count(1) "count" from gv$session where inst_id=1 and program like 'JDBC%' group by inst_id,username,osuser,machine,program,status order by 1,2; select inst_id,username,osuser,machine,program,status,count(1) "count" from gv$session where inst_id=2 and program lik...
Post a Comment
Read more

Mastering Oracle RAC with SRVCTL Commands

Oracle Real Application Clusters (RAC) provide high availability, scalability, and manageability for databases. One of the most powerful tools for managing RAC databases is srvctl , a command-line utility that allows administrators to control various database services. This blog explores essential srvctl commands to help you efficiently manage Oracle RAC environments. 1. Checking Database Configuration and Status  List all available databases on the host:                  srvctl config database   Check the status of a specific database and its instances:                    srvctl status database -d <database_name>   Retrieve detailed status information about a database, including its instances and states:                    srvctl status database -d <database_name> -v 2. Stopping and Starting Databases   ...
Post a Comment
Read more