Skip to main content

Issues and Solutions for Oracle 19c Grid Infrastructure Installation

  
 Common Issues and Solutions for Oracle 19c Grid Infrastructure Installation
      Check Log Files for Details Oracle installation issues often provide valuable clues in the log files. If the installer seems stuck or fails, check the following logs: Install log: /u01/app/oraInventory/logs/installActions<date>.log
      Grid Infrastructure log: $ORACLE_BASE/cfgtoollogs/
       
      These logs can provide error messages and help identify the exact issue.
       
       Check Permissions and Ownership Verify that the Oracle Grid Infrastructure installation directories have the correct ownership and permissions.
       For example:
       Make sure the grid user has permission to write to the directories where the installation is happening.
       Ensure that your server has sufficient swap space and disk space. Oracle can sometimes fail silently if these requirements are not met.
       Check the swap space with:
       Check disk space with:
        
 
bash
chown -R grid:oinstall /u01/app/19.0.0/grid
chmod -R 775 /u01/app/19.0.0/grid
1.      Verify Swap Space and Disk Space
 
bash
free -m
bash
df -h
      Disable Firewall and SELinux Sometimes firewall or SELinux settings can cause issues during installation. Ensure that: Firewall: Disable or open the required ports for Oracle.
      SELinux: Ensure SELinux is set to permissive or disabled:
       
       
 
bash
systemctl stop firewalld
systemctl disable firewalld
bash
setenforce 0
 
      Also check /etc/selinux/config to ensure the line SELINUX=permissive or SELINUX=disabled.
       
      Even though you've checked the packages, run the following command to double-check that all required packages for Oracle 19c are present:
      Additionally, verify that all dependencies listed in the Oracle documentation for your OS version are installed, especially libaio, binutils, gcc, etc.
      Kernel parameters play a crucial role in Oracle installation. Check if all required kernel parameters have been set in /etc/sysctl.conf. You can reapply them with:
      Example of key parameters:
       
 
1.     Ensure Required Packages Are Installed
 
bash
yum install -y oracle-database-preinstall-19c
1.      Set Kernel Parameters Correctly
 
bash
sysctl -p
bash
fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.shmall = 2097152
kernel.shmmax = 4398046511104
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.core.rmem_max = 4194304
net.core.wmem_max = 1048576
net.ipv4.ip_local_port_range = 9000 65500
net.ipv4.tcp_rmem = 4096 87380 4194304
net.ipv4.tcp_wmem = 4096 65536 4194304
         Check for Conflicting Processes Ensure that no other processes or previous Oracle installations are running that could cause conflicts. You can check for running Oracle-related processes with
         If any exist, kill them before attempting the installation again.
         If you continue facing issues, you can try running the installer with debug mode enabled to get more detailed output:
         This might give you more granular information about where the installer is getting stuck.
          
 
ps -ef | grep oracle
1.      Re-run the Installer with Debugging Enabled
 
bash
./runInstaller -debug
 
         Use a Response File in Silent Mode If the GUI is causing issues, use the silent mode with a response file. Make sure that the response file is properly configured, and there are no missing or incorrect parameters.
         For example, you can create a response file (named grid_install.rsp) and run:
          
 
bash
./gridSetup.sh -silent -responseFile /path/to/grid_install.rsp
1                Check X11 Display for GUI
                  If you’re stuck in GUI mode, ensure that the X11 forwarding is set up correctly for remote installations. For local installation:
                  For remote installation, use X11 forwarding:
                  If there are X11 issues, silent mode with a response file is a good fallback.
                   
 
bash
export DISPLAY=:0.0
bash
ssh -X user@host
1                Run the Prerequisite Check Manually
2               Before running the installer again, you can manually run the Oracle prerequisite check to ensure that all requirements are met:
 
bash
./gridSetup.sh -executePrereqs
                This will give you a detailed report of any missing configurations or failed checks.
 

Comments

Popular posts from this blog

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG

ORA-01143: cannot disable media recovery - file 1 needs media recovery

I got a request from the client - To flashback the database to the existing restore point & disable flashback and archive log mode for database UATB. Here I came a cross error - ORA-01143. I followed the below steps. 1. SQL> select name from v$database; NAME ------------ UATB 2. SQL> SELECT NAME FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE='YES' ORDER BY TIME; NAME --------- UATB_COPY Here I'm going to restore the database to the above restore point. NOTE: The flashback database restore has to be done in MOUNT stage of the database. SQL> select name from v$database; NAME --------- UATB SQL> shut immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> startup mount ORACLE instance started. Total System Global Area  612368384 bytes Fixed Size                  1250428 bytes Variable Size             167775108 bytes Database Buffers          436207616 bytes Redo Buffers