Common Issues and Solutions for Oracle 19c Grid
Infrastructure Installation
1. Check Log Files for Details
o 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/
o These logs can provide error messages and help identify the exact issue.
2. Check Permissions and Ownership
o Verify that the Oracle Grid Infrastructure installation directories have the correct
ownership and permissions.
o For example:
bash
chown -R grid:oinstall /u01/app/19.0.0/grid
chmod -R 775 /u01/app/19.0.0/grid
o Make sure the grid user has permission to write to the directories where the installation
is happening.
3. Verify Swap Space and Disk Space
o Ensure that your server has sufficient swap space and disk space. Oracle can
sometimes fail silently if these requirements are not met.
o Check the swap space with:
bash
free -m
o Check disk space with:
bash
df -h
4. Disable Firewall and SELinux
o Sometimes firewall or SELinux settings can cause issues during installation. Ensure
that:
▪ Firewall: Disable or open the required ports for Oracle.
bash
systemctl stop firewalld
systemctl disable firewalld
▪ SELinux: Ensure SELinux is set to permissive or disabled:
bash
setenforce 0
▪ Also check /etc/selinux/config to ensure the line SELINUX=permissive or
SELINUX=disabled.
5. Ensure Required Packages Are Installed
o Even though you've checked the packages, run the following command to double-check
that all required packages for Oracle 19c are present:
bash
yum install -y oracle-database-preinstall-19c
o Additionally, verify that all dependencies listed in the Oracle documentation for your
OS version are installed, especially libaio, binutils, gcc, etc.
6. Set Kernel Parameters Correctly
o 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:
bash
sysctl -p
o Example of key parameters:
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
7. Check for Conflicting Processes
o Ensure that no other processes or previous Oracle installations are running that could
cause conflicts. You can check for running Oracle-related processes with
ps -ef | grep oracle
o If any exist, kill them before attempting the installation again.
8. Re-run the Installer with Debugging Enabled
o If you continue facing issues, you can try running the installer with debug mode
enabled to get more detailed output:
bash
./runInstaller -debug
o This might give you more granular information about where the installer is getting
stuck.
9. Use a Response File in Silent Mode
o 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.
o For example, you can create a response file (named grid_install.rsp) and run:
bash
./gridSetup.sh -silent -responseFile /path/to/grid_install.rsp
10. Check X11 Display for GUI
• If you’re stuck in GUI mode, ensure that the X11 forwarding is set up correctly for remote
installations.
o For local installation:
bash
export DISPLAY=:0.0
o For remote installation, use X11 forwarding:
bash
ssh -X user@host
o If there are X11 issues, silent mode with a response file is a good fallback.
11. Run the Prerequisite Check Manually
• 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.
