• 07 Sep, 2026
• 0 Comments
• 5 Mins Read

INS-41803 Oracle Grid Infrastructure Error: How to Fix Stale ASM Entries

INS-41803 During Oracle Grid Infrastructure Installation: How to Fix Stale ASM Entries

When reinstalling Oracle Grid Infrastructure / Oracle RAC, you may encounter the following error during the installation:

INS-41803: An entry for Oracle ASM is found in the system registry or oratab,
but it is not associated with a software home location.

This error usually indicates that a previous Oracle Grid Infrastructure installation was not completely removed.

The old Grid Infrastructure software may have already been deleted, but Oracle Installer can still detect references to the previous Oracle ASM (+ASM) configuration in files such as /etc/oratab, Oracle Inventory, or Oracle Local Registry.

As a result, the installer assumes that an existing ASM installation is present but cannot find its associated Grid Home.

What Causes INS-41803?

The most common scenario looks like this:

Previous Grid Installation
        ↓
Grid Home removed
        ↓
Old ASM / Grid entries remain
        ↓
Oracle Universal Installer scans the system
        ↓
Finds +ASM registration
        ↓
Associated Grid Home does not exist
        ↓
INS-41803

For example, /etc/oratab may still contain:

+ASM:/u01/app/grid/product/19.3.0/grid_home:N

while the actual Grid Home has already been deleted:

/u01/app/grid/product/19.3.0/grid_home

This mismatch can trigger INS-41803.

Step 1: Check /etc/oratab

First, check whether an old ASM entry is present.

Run as root:

cat /etc/oratab

Look for entries such as:

+ASM:/u01/app/grid/product/19.3.0/grid_home:N

or:

+ASM:/u01/app/19.3.0/grid:N

If you find an obsolete +ASM entry, edit the file:

vi /etc/oratab

Remove the stale line beginning with:

+ASM:

Save and exit.

Important: Do not blindly remove every Oracle-related entry from /etc/oratab. Remove only the stale ASM entry that belongs to the previous Grid Infrastructure installation.

Step 2: Check Oracle Inventory

Oracle Universal Installer maintains an inventory of installed Oracle homes.

First, check the inventory location:

cat /etc/oraInst.loc

You may see:

inventory_loc=/u01/app/oraInventory
inst_group=oinstall

Now check the inventory:

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

Look for an old Grid Infrastructure home, for example:

<HOME NAME="OraGI19Home1"
      LOC="/u01/app/grid/product/19.3.0/grid_home">

If this location is registered in the inventory but the directory no longer exists, the inventory contains a stale Oracle Home reference.

Step 3: Verify Whether the Old Grid Home Exists

Check the old Grid Home:

ls -ld /u01/app/grid/product/19.3.0/grid_home

If the output is:

ls: cannot access '/u01/app/grid/product/19.3.0/grid_home': No such file or directory

then the Grid Home has been removed from the filesystem.

However, Oracle Inventory may still contain a reference to it.

This is a common reason for INS-41803 during a fresh Grid Infrastructure installation.

Step 4: Check /etc/oracle

Next, check whether Oracle Clusterware configuration files remain on the server:

ls -l /etc/oracle

Pay particular attention to:

olr.loc

Check whether it exists:

ls -l /etc/oracle/olr.loc

If it exists, display its contents:

cat /etc/oracle/olr.loc

You may see a reference similar to:

olrconfig_loc=/u01/app/grid/product/19.3.0/grid_home/cdata/...

If the referenced Grid Home has already been deleted, this can indicate that remnants of the previous Grid Infrastructure configuration are still present.

Step 5: Search for Oracle .loc Files

You can also search /etc for Oracle location files:

find /etc -name "*.loc"

This helps identify files that may still contain references to an old Oracle installation.

For example:

/etc/oraInst.loc
/etc/oracle/olr.loc

Review any Oracle-related .loc files carefully before making changes.

Step 6: Check Registered Oracle Homes

Finally, check which Oracle Homes are registered in the Oracle Inventory:

grep HOME /u01/app/oraInventory/ContentsXML/inventory.xml

For example:

<HOME NAME="OraGI19Home1"
LOC="/u01/app/grid/product/19.3.0/grid_home"
...

Compare the registered home with the actual filesystem:

ls -ld /u01/app/grid/product/19.3.0/grid_home

If the inventory shows the Grid Home but the directory does not exist, you have identified a stale Oracle Inventory entry.

Commands to Collect for Troubleshooting

Before making any cleanup changes, collect the output of these commands:

cat /etc/oratab

cat /etc/oraInst.loc

grep HOME /u01/app/oraInventory/ContentsXML/inventory.xml

ls -ld /u01/app/grid/product/19.3.0/grid_home

ls -l /etc/oracle

cat /etc/oracle/olr.loc

These outputs will help determine exactly where the stale ASM/Grid registration exists.

How to Understand the Problem

The important thing is to identify the difference between the registered Grid Home and the actual Grid Home.

For example:

In simple terms:

Oracle Installer
      │
      ├── Checks /etc/oratab
      │        └── Finds +ASM
      │
      ├── Checks Oracle Inventory
      │        └── Finds old Grid Home
      │
      └── Checks Oracle configuration
               └── Old references exist
                       ↓
                 INS-41803

Important: Don’t Delete Files Blindly

Although stale configuration is often the cause, do not immediately delete Oracle Inventory, OLR, or other Oracle configuration files without verifying what they belong to.

For example, the server may contain:

• Another Oracle Database Home
• Another Grid Infrastructure installation
• An active RAC configuration
• ASM disks or disk groups
• A valid Oracle Inventory used by other Oracle software

Therefore, first collect and compare the outputs.

Only remove entries that are confirmed to belong to the old/failed Grid Infrastructure installation.

Conclusion

The INS-41803 error generally indicates a mismatch between Oracle’s recorded ASM/Grid configuration and the actual software installed on the server.

A typical situation is:

Old Grid Home
     ↓
Deleted from filesystem
     ↓
But +ASM / Inventory / OLR references remain
     ↓
Oracle Installer detects stale ASM configuration
     ↓
INS-41803

Start troubleshooting by checking:

/etc/oratab
/etc/oraInst.loc
/u01/app/oraInventory/ContentsXML/inventory.xml
/etc/oracle/olr.loc

and verify whether the previously registered Grid Home actually exists.

Once the stale references are correctly identified and cleaned up, the Oracle Grid Infrastructure installation can be attempted again without the old ASM registration interfering.

Quick Troubleshooting Checklist

☑ Check /etc/oratab
☑ Check /etc/oraInst.loc
☑ Check Oracle Inventory
☑ Verify old Grid Home
☑ Check /etc/oracle
☑ Check olr.loc
☑ Search for .loc files
☑ Compare registered homes with actual directories
☑ Remove only confirmed stale configuration
☑ Retry Grid Infrastructure installation