https://docs.oracle.com/en/database/oracle/oracle-database/19/ladbi/checking-resource-limits-for-oracle-software-installation-users.htmlTable 5-1 Oracle Software Installation Owner and Oracle Grid Infrastructure Software Installation Owner Resource Limit Recommended RangesResource Shell LimitResourceSoft LimitHard LimitOpen file descriptorsnofileat least 1024at least 65536Number of processes available to a single usernprocat least 2047at least 16384Size of the stack segment of the processstackat least 10240 KBat least 10240 KB, and at most 32768 KBMaximum locked memory limitmemlockat least 90 percent of the current RAM when HugePages memory is enabled and at least 3145728 KB (3 GB) when HugePages memory is disabled.Note: unlimited on Exadata systems.at least 90 percent of the current RAM when HugePages memory is enabled and at least 3145728 KB (3 GB) when HugePages memory is disabledNote: unlimited on Exadata systems.Configuring NFS Buffer Size Parameters for Oracle DatabaseSet the values for the NFS buffer size parameters rsize and wsize to at least 32768.For example, to use rsize and wsize buffer settings with the value 32768 for an Oracle Database data files mount point, set mount point parameters to values similar to the following:COPYnfs_server:/vol/DATA/oradata /home/oracle/netapp nfs\rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600Direct NFS Client issues writes at wtmax granularity to the NFS server.Checking TCP Network Protocol Buffer for Direct NFS ClientCheck your TCP network buffer size to ensure that it is adequate for the speed of your servers.By default, the network buffer size is set to 1 MB for TCP, and 2 MB for UDP. The TCP buffer size can set a limit on file transfers, which can negatively affect performance for Direct NFS Client users.To check the current TCP buffer size, enter the following command:# sysctl -a |grep -e net.ipv4.tcp_[rw]memThe output of this command is similar to the following:COPYnet.ipv4.tcp_rmem = 4096 87380 1056768net.ipv4.tcp_wmem = 4096 16384 1056768Oracle recommends that you set the value based on the link speed of your servers. For example, perform the following steps:1.As root, use a text editor to open /etc/sysctl.conf, and add or change the following:net.ipv4.tcp_rmem = 4096 87380 4194304net.ipv4.tcp_wmem = 4096 16384 41943042.Apply your changes by running the following command:COPY# sysctl -p3.Restart the network:COPY# /etc/rc.d/init.d/network restartVerifying HugePages AvailabilityEnsure that the underlying Linux kernel supports HugePages.HugePages not only reduces TLB misses but also substantially reduces the memory footprint for virtual to physical address translation.To determine the HugePages size on your system, run:COPY$grep Hugepagesize /proc/meminfoHugepagesize: 2048 kBIn this example, the HugePages size is 2 MiB (mebibyte).NoteAn MiB (mebibyte) is a unit of measure that represents 1024 * 1024 bytes.Oracle ASM Disk Space RequirementsDetermine the total amount of Oracle Automatic Storage Management (Oracle ASM) disk space that you require for the database files and recovery files.Table 9-1 Oracle ASM Disk Number and Minimum Space Requirements for an Oracle database (non-CDB)Redundancy LevelMinimum Number of DisksData FilesRecovery FilesBoth File TypesExternal12.5 GB7.5 GB10 GBNormal or Flex with two-way mirroring25.2 GB15.6 GB20.8 GBHigh or Flex with three-way mirroring37.6 GB22.8 GB30.4 GBTable 9-2 Oracle ASM Disk Number and Minimum Space Requirements for a multitenant container database (CDB) with one pluggable database (PDB)Redundancy LevelMinimum Number of DisksData FilesRecovery FilesBoth File TypesExternal14 GB12 GB16 GBNormal or Flex with two-way mirroring28 GB24 GB32 GBHigh or Flex with three-way mirroring312 GB36 GB48 GBNote- If an Oracle ASM instance is running on the system, then you can use an existing disk group to meet these storage requirements. If necessary, you can add disks to an existing disk group during the database installation.- The disk devices must be owned by the user performing the grid installation.Check with your system administrator to determine if the disks used by Oracle ASM are mirrored at the storage level. If so, select External for the redundancy. If the disks are not mirrored at the storage level, then select Normal for the redundancy.- Every Oracle ASM disk is divided into allocation units (AU). An allocation unit is the fundamental unit of allocation within a disk group. You can select the AU Size value from 1, 2, 4, 8, 16, 32 or 64 MB, depending on the specific disk group compatibility level. The default value is 4 MB for flex disk group and 1 MB for all other disk group types. On engineered systems, the default value is 4 MB.Creating Directories for Oracle Database FilesIdentify the file systems to use, from the display:OptionDescriptionDatabase FilesSelect one of the following:A single file system with at least 1.5 GB of free disk spaceTwo or more file systems with at least 3.5 GB of free disk space in totalRecovery FilesChoose a file system with at least 2 GB of free disk space