Close Menu
  • Home
  • Oracle
    • ASM
    • Data Guard
    • OEM
    • RAC
  • MongoDB
  • Performance
  • Python
  • Shell Script
  • Tools
  • Troubleshooting
Search

Oracle RAC 12.2 on VMware Workstation — Post 5: Final Validation and Quick Reference

2026-05-11 Oracle By Henrique

Oracle RAC 12.2 on VMware Workstation – Post 4: Oracle Database Installation and DBCA

2026-05-11 Oracle By Henrique

Oracle RAC 12.2 on VMware Workstation — Post 2: Oracle Linux Configuration and iSCSI

2026-05-11 Oracle By Henrique
YouTube LinkedIn RSS
  • Home
  • About
  • Contact
  • Legal
    • Cookie Policy
    • Disclaimer
    • Privacy Policy
    • Terms of Use
  • RSS
  • English
    • Portuguese (Brazil)
Execute StepExecute Step
YouTube LinkedIn RSS
  • Home
  • Oracle
    • ASM
    • Data Guard
    • OEM
    • RAC
  • MongoDB
  • Performance
  • Python
  • Shell Script
  • Tools
  • Troubleshooting
Execute StepExecute Step
Home » How to Remove an ORACLE_HOME from inventory.xml Using runInstaller
Oracle Tools

How to Remove an ORACLE_HOME from inventory.xml Using runInstaller

HenriqueBy Henrique2026-04-25Updated:2026-05-183 Mins Read
Share
Facebook Twitter LinkedIn Pinterest Email Telegram WhatsApp

This post is also available in: Português (Portuguese (Brazil))

You deleted an Oracle Home directory manually — to free up space or recreate it later — and now inventory.xml still has the entry sitting there. Since the directory is gone, deinstall won’t work. The Oracle-supported fix is runInstaller -detachHome.

💡 If the Oracle Home directory still exists on disk and you want to remove everything (binaries + inventory entry), this is not the right procedure. See: Removing an Old Oracle GRID_HOME After an Upgrade.


Why not edit inventory.xml directly?

Oracle does not support manual edits to inventory.xml. Any inconsistency introduced by hand can corrupt the central inventory and cause failures in future installations or upgrades.


Prerequisites

  • Another valid, working Oracle Home on the server — runInstaller must be called from a different home than the one being removed
  • Read access to inventory.xml to get the exact home name

1. Identify the ORACLE_HOME in inventory.xml

cat /u01/app/oraInventory/ContentsXML/inventory.xml

Example output:

<HOME_LIST>
  <HOME NAME="Orasidb19c_home1_4607" LOC="/u01/app/oracle/product/19.23.0.0/dbhome_1" TYPE="O" IDX="10"/>
  <HOME NAME="Orasidb19c_home1_9789" LOC="/u01/app/oracle/product/19.25.0.0/dbhome_1" TYPE="O" IDX="12"/>
  <HOME NAME="Orasidb19c_home1_2380" LOC="/u01/app/oracle/product/19.26.0.0/dbhome_1" TYPE="O" IDX="14"/>
</HOME_LIST>

You need two values from the entry you want to remove:

  • LOC → the Oracle Home path
  • NAME → the home name in the inventory (case-sensitive)

2. Pick a valid Oracle Home to run runInstaller from

⚠️ runInstaller must be called from a home other than the one being removed. Using the same home you are detaching will cause the command to fail or behave unpredictably.

In the example above, the home to remove is Orasidb19c_home1_2380. We will call runInstaller from Orasidb19c_home1_9789:

export RUNNER_HOME=/u01/app/oracle/product/19.25.0.0/dbhome_1

3. Run detachHome

$RUNNER_HOME/oui/bin/runInstaller \
  -silent \
  -detachHome \
  ORACLE_HOME="/u01/app/oracle/product/19.26.0.0/dbhome_1" \
  ORACLE_HOME_NAME="Orasidb19c_home1_2380"

💡 The values for ORACLE_HOME and ORACLE_HOME_NAME must match exactly what is in inventory.xml. Copy them directly from the file to avoid typos.


4. Validate the result

cat /u01/app/oraInventory/ContentsXML/inventory.xml

Unlike deinstall, runInstaller -detachHome removes the entry completely from inventory.xml — it will not appear at all, not even with REMOVED="T".


Quick Reference

cat /u01/app/oraInventory/ContentsXML/inventory.xml

export RUNNER_HOME=/u01/app/oracle/product/19.25.0.0/dbhome_1

$RUNNER_HOME/oui/bin/runInstaller \
  -silent \
  -detachHome \
  ORACLE_HOME="/u01/app/oracle/product/19.26.0.0/dbhome_1" \
  ORACLE_HOME_NAME="Orasidb19c_home1_2380"

cat /u01/app/oraInventory/ContentsXML/inventory.xml

FAQ

Is it safe to edit inventory.xml by hand? No. Oracle does not support manual changes to this file. Always use runInstaller -detachHome.

Do I need to reboot the server? Generally no. But confirm no processes are using that home before running the command:

fuser -cu /u01/app/oracle/product/19.26.0.0/dbhome_1

What is the difference between deinstall and runInstaller -detachHome?

deinstallrunInstaller -detachHome
Removes binaries from disk✅ Yes❌ No
Updates inventory.xml✅ Yes (marks REMOVED="T")✅ Yes (removes entry completely)
Works without the directory❌ No✅ Yes
Oracle-supported✅ Yes✅ Yes

References

  • Oracle Universal Installer Concepts Guide
  • Oracle Database Installation Guide 19c — Removing Oracle Homes
detachHome lab oracle inventory
Share. Facebook Twitter Pinterest LinkedIn Tumblr Email WhatsApp
Previous ArticleRemoving an Old Oracle GRID_HOME After an Upgrade
Next Article Oracle Database 19c with Vagrant: A Lab in 15 Minutes

Related Posts

Oracle

Oracle RAC 12.2 on VMware Workstation — Post 5: Final Validation and Quick Reference

2026-05-11
Read More
Oracle

Oracle RAC 12.2 on VMware Workstation – Post 4: Oracle Database Installation and DBCA

2026-05-11
Read More
Oracle

Oracle RAC 12.2 on VMware Workstation — Post 2: Oracle Linux Configuration and iSCSI

2026-05-11
Read More
Add A Comment
Leave A Reply Cancel Reply

Demo
Follow Me
  • Email
  • GitHub
  • LinkedIn
  • RSS
  • YouTube

INS-06006 – Passwordless SSH Connectivity Not Set Up

2026-02-2614 Views

ORA-29548 — How to Fix “Java System Class Reported” in Oracle Database

2026-03-0510 Views

PRVG-2002 — How to Fix “Encountered Error in Copying File” in Oracle RAC

2026-03-078 Views
Demo
Blogroll
  • oravirt
Execute Step
YouTube LinkedIn RSS
  • Home
  • About
  • Contact
  • RSS
  • English
    • Português (Portuguese (Brazil))
© 2026 ExecuteStep. Designed by ThemeSphere.

Type above and press Enter to search. Press Esc to cancel.

Ad Blocker Enabled!
Ad Blocker Enabled!
Our website is made possible by displaying online advertisements to our visitors. Please support us by disabling your Ad Blocker.