Search This Blog

Total Pageviews

Wednesday, 18 November 2026

Oracle Grid Infrastructure – Deinstallation

 

Oracle Grid Infrastructure – Deinstallation of Old Grid Home

Server: ora26
Operating System: CentOS Stream 9
Activity: Deinstallation of old Oracle Grid Infrastructure home
Old Grid Home: /u01/app/26.0.0/grid
New Grid Home: /u01/app/26.4.0/grid
Software Owner: grid


1. Objective

The objective of this activity is to safely deinstall the old Oracle Grid Infrastructure home (26.0.0) after successfully switching to the new Grid Infrastructure home (26.4.0).

The new Grid home must remain operational throughout this activity. ASM and its associated disk groups must not be affected.

2. Important Considerations

  • The new Grid home /u01/app/26.4.0/grid is the active Grid Infrastructure home.

  • The old Grid home /u01/app/26.0.0/grid is no longer configured as an active Grid Infrastructure home.

  • The previous deinstall -checkonly operation reported that the old home was not a configured Grid Infrastructure home.

  • ASM was not detected in the old Grid home.

  • Do not deinstall or modify the new Grid home.

  • Ensure the active ASM instance and disk groups remain operational.

3. Pre-Deinstallation Checks

3.1 Verify Grid Infrastructure status

Run as the grid user:

/u01/app/26.4.0/grid/bin/crsctl check crs

Check the active version:

/u01/app/26.4.0/grid/bin/crsctl query crs activeversion

Check the installed software version:

/u01/app/26.4.0/grid/bin/crsctl query crs softwareversion

All required Grid Infrastructure services should be operational.

3.2 Verify Oracle Local Registry location

cat /etc/oracle/olr.loc

Confirm that the active Grid home points to:

/u01/app/26.4.0/grid

Do not proceed if the OLR still references the old Grid home.

3.3 Verify ASM status

ps -ef | grep [a]sm_pmon

Connect to ASM:

export ORACLE_HOME=/u01/app/26.4.0/grid
export ORACLE_SID=+ASM
export PATH=$ORACLE_HOME/bin:$PATH

sqlplus / as sysasm

Check ASM instance status:

SELECT instance_name, status
FROM v$instance;

Check disk group status:

SELECT name, state, type
FROM v$asm_diskgroup;

Exit SQL*Plus:

EXIT;

3.4 Verify Oracle Inventory

cat /etc/oraInst.loc

Check registered Oracle homes:

grep -i '26.0.0\|26.4.0' \
/u01/app/oraInventory/ContentsXML/inventory.xml

3.5 Check /etc/oratab

cat /etc/oratab

Current entries may include:

+ASM:/u01/app/26.0.0/grid:N
+ASM:/u01/app/26.4.0/grid:N

The active ASM entry must ultimately reference the new Grid home.

3.6 Check whether any processes are using the old home

ps -ef | grep '/u01/app/26.0.0/grid' | grep -v grep

Also check open files:

lsof +D /u01/app/26.0.0/grid

If lsof is unavailable, install or use an alternative process inspection method.

Investigate any remaining processes before proceeding.

4. Deinstallation Check

The following command was previously executed:

/u01/app/26.0.0/grid/deinstall/deinstall -checkonly

The check reported:

  • Active GI home: /u01/app/26.4.0/grid

  • Selected old home: /u01/app/26.0.0/grid

  • Old home is NOT a configured Grid Infrastructure home.

  • ASM was not detected in the old home.

This confirms that the old home is not identified as the active Grid Infrastructure configuration.

5. Deinstall Old Grid Home

Log in as the grid user.

Set the old Grid home:

export ORACLE_HOME=/u01/app/26.0.0/grid
export PATH=$ORACLE_HOME/bin:$PATH

Run the deinstallation utility:

/u01/app/26.0.0/grid/deinstall/deinstall

Review all prompts and proposed changes carefully.

Important: If the deinstallation utility proposes removing the active Grid Infrastructure configuration, ASM configuration, OCR/OLR, disk groups, or resources associated with /u01/app/26.4.0/grid, cancel the operation.

Only proceed when the utility is targeting the old home.

Review the deinstallation logs under:

/u01/app/oraInventory/logs/

6. Post-Deinstallation Verification

6.1 Verify new Grid home

ls -ld /u01/app/26.4.0/grid

6.2 Verify Clusterware services

/u01/app/26.4.0/grid/bin/crsctl check crs

6.3 Verify ASM

ps -ef | grep [a]sm_pmon

Connect to ASM and check disk groups:

SELECT name, state
FROM v$asm_diskgroup;

6.4 Verify old Grid home

ls -ld /u01/app/26.0.0/grid

Confirm the deinstallation completed successfully and that the old home is no longer registered in Oracle Inventory.

Do not manually delete the old directory if the deinstallation utility has reported errors or left registered components behind.

6.5 Clean up /etc/oratab

After confirming successful deinstallation, remove the obsolete entry:

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

Retain the active entry:

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

7. Success Criteria

The activity will be considered successful when:

  1. Old Grid home 26.0.0 has been successfully deinstalled.

  2. New Grid home 26.4.0 remains operational.

  3. Clusterware services are running successfully.

  4. ASM instance is running.

  5. All ASM disk groups are mounted and accessible.

  6. Oracle Inventory no longer contains the old Grid home.

  7. /etc/oratab contains the correct active ASM entry.

  8. No database or ASM availability issues are observed.

8. Rollback / Recovery Considerations

This is a deinstallation activity, not a Grid home switch.

If deinstallation fails:

  • Stop further cleanup activities.

  • Do not remove the new Grid home.

  • Do not manually modify OLR or OCR.

  • Preserve the deinstallation logs.

  • Investigate Oracle Inventory and the deinstall error messages.

  • If necessary, reinstall or restore the old software home using the appropriate Oracle installation media and configuration procedures.

Note: Reinstalling the old software home does not automatically restore its previous configuration.


Expected Final State

ComponentExpected state
Old Grid home – 26.0.0Deinstalled
New Grid home – 26.4.0Active
ASM instanceRunning
ASM disk groupsMounted
ClusterwareOperational
Oracle InventoryOld home removed
/etc/oratabNew home retained

Oracle DBA

anuj blog Archive