Ins-10201 Execution Of 39-gi Install 39- Script Failed [updated] -

The INS-10201: Execution of 'GI Install' script failed error typically occurs during the final phase of an Oracle Grid Infrastructure (GI) installation. It indicates that the automated execution of the configuration scripts—such as root.sh or gridconfig.bat —encountered a critical failure on one or more cluster nodes. Common Root Causes Ins-10201 Execution Of 39-gi Install 39- Script Failed ins-10201 execution of 39-gi install 39- script failed. Keyword. Go. 13.222.175.18 [INS-32148] - Execution of 'GI Install' script failed on nodes - RAC 12c on Windows 2012 Server

Troubleshooting INS-10201: Execution of 'GI Install' Script Failed in Oracle Grid Infrastructure Introduction Oracle Grid Infrastructure (GI) installation is a critical step for setting up Oracle Real Application Clusters (RAC), Automatic Storage Management (ASM), or a standalone Oracle Restart environment. However, even seasoned DBAs can find themselves staring at a frustrating, generic error message that halts the installation process. Error Code: INS-10201 Message: Execution of 'gi install' script failed This error occurs during the "Execute Configuration Scripts" phase of the Oracle Universal Installer (OUI). The installer has copied the necessary binaries and just triggered the root scripts ( root.sh , orainstRoot.sh , etc.) to perform system-level configurations. When the installer does not receive a successful exit code from these scripts, it aborts with INS-10201. This article provides a deep dive into the causes, diagnostic procedures, and step-by-step solutions for resolving the INS-10201 error.

Understanding the Root Cause Before attempting fixes, it is vital to understand what is happening behind the scenes. INS-10201 is not a specific error but rather a wrapper error —a bucket into which dozens of underlying Linux/UNIX system issues fall. When you click "Install" and then "Execute Configuration Scripts," the OUI performs the following sequence:

It copies root.sh , orainstRoot.sh , and rootupgrade.sh to the Oracle Inventory ( /u01/app/oraInventory ) and Grid home. It prompts the installer user (usually oracle ) to run these scripts as root . The root.sh script modifies system files ( /etc/oratab , /etc/inittab ), sets permissions on devices (ASM disks), configures network resources (VIPs, SCAN listeners), and starts Clusterware services (CRS/OHASD). The OUI waits for the root.sh script to complete and return an exit code of 0 (success). ins-10201 execution of 39-gi install 39- script failed

INS-10201 fires when the exit code is non-zero or the process hangs. Common triggers include:

Insufficient OS prerequisites (missing kernel parameters, packages, or user/group configurations). SSH equivalency issues (for multi-node RAC installations). Permission errors on ASM disks or voting disks. Network misconfigurations (incorrect hostname resolution, missing VIP host entries, firewall). Inconsistent Inventory ( oraInventory ownership or permissions). Resource limits (insufficient shared memory, file descriptors). Incompatible patches or kernel versions .

Phase 1: Immediate Diagnosis When you see INS-10201, do not immediately click "Retry" or "Ignore." First, perform forensic analysis. Step 1: Check the Installation Logs The OUI logs are located in $ORACLE_BASE/cfgtoollogs/ (typically /u01/app/oracle/cfgtoollogs ). Look for: Keyword

installActions<timestamp>.log – The main installer log. cloneActions<timestamp>.log – If it’s a software-only or RAC clone install. Post-install logs: $ORACLE_BASE/cfgtoollogs/crsconfig/rootcrs_<hostname>.log

Use grep to search for errors: grep -i "ins-10201" installActions*.log grep -i "error" installActions*.log | tail -100 grep -i "failed" $ORACLE_BASE/cfgtoollogs/crsconfig/rootcrs_*.log

Step 2: Check the root.sh Output The root.sh script is run in the terminal where you answered "yes" to the OUI prompt. If you closed that terminal, check: cat $GI_HOME/root.sh.out cat $GI_HOME/install/root_<hostname>_<timestamp>.err However, even seasoned DBAs can find themselves staring

Step 3: Validate Silent Response Files (Silent Install Only) If you are using a silent response file (e.g., grid_install.rsp ), a missing or incorrect parameter (like INVENTORY_LOCATION without write permissions) can cause INS-10201. Validate the response file syntax.

Phase 2: Common Scenarios and Fixes Below are the most frequent specific failures that manifest as INS-10201, along with their solutions. Scenario A: ASM Disk Group Permission Issues Symptoms in log: CRS-4124: Oracle High Availability Services startup failed. PROT-1: Failed to obtain handle to ASM instance. CSSD could not open voting file. Permission denied. Cause: The root.sh script cannot access the disks assigned to the ASM disk group because the disk ownership/permissions are incorrect. Solution: