My Oracle Support Banner

Primary Note: Windows Grid Infrastructure Install/Upgrade fails with [INS-20802]: Most Common Causes and Solutions (Doc ID 1542814.1)

Last updated on AUGUST 30, 2023

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Microsoft Windows x64 (64-bit)


The "[INS-20802] Grid Infrastructure Configuration failed" error is a 'catch-all' error that only indicates that the Grid Infrastructure Configuration has failed.  This document lists the most common causes and their solutions for this error in Windows Grid Infrastructure installation and upgrade.


 Windows 11gR2 Grid Infrastructure installation or upgrade fails with: [INS-20802] Grid Infrastructure Configuration failed.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Please check which of the following symptoms are reported, in addition to the INS-20802, in the indicated logs.
 Grid Infrastructure Configuration Failed at 80%
 rootcrs log on local node shows remote install failed; rootcrs on remote node shows success
 Grid Infrastructure Upgrade from to fails
 Upgrade from Standalone ASM to Standalone Grid Infrastructure / Oracle Restart fails
 rootcrs log shows asm configuration failed; asm log shows gpnp profile push failed; mdnsd log shows failure with "invalid mask"
 OUI log shows "Found inconsistent name resolution entries for SCAN name" or "Failed to resolve Single Client Access Name"
 OUI install log shows PRVF-9691, PRVF-9652, "Liveness check failed for "W32Time" "

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.