Completing Preinstallation Tasks Manually

You can complete the preinstallation configuration tasks manually.

Oracle recommends that you use Oracle Universal Installer and Configuration Verification Utility (CVU) fixup scripts to complete minimal configuration settings. If you cannot use fixup scripts, then complete minimum system settings manually.

Configuring Kernel Parameters for Linux

Manually configure Linux kernel parameters when fixup scripts or the Oracle Database Preinstallation RPM are unavailable, using the documented minimum values for semaphore limits, shared memory, file handles, asynchronous I/O, network ports, and socket buffers while retaining any higher existing settings. Inspect values with sysctl, persist required changes in /etc/sysctl.d/97-oracle-database-sysctl.conf, apply them with sysctl --system, and verify the results; increase fs.file-max and fs.aio-max-nr for demanding RAC workloads. SUSE Linux Enterprise Server additionally requires enabling boot.sysctl and setting vm.hugetlb_shm_group to the oinstall GID. Configure ephemeral UDP/TCP ports with an even/odd-compatible range beginning at 9000 or higher, sized for workload requirements, and make the setting persistent.

Configuring Default Thread Limits Value for SUSE Linux

On SUSE Linux Enterprise Server 12 SP2 or later and version 15 or later, increase systemd’s DefaultTasksMax from its typical value of 512 to 65535 to prevent service failures caused by thread limits. Check the current value with systemctl show --property DefaultTasksMax or by reviewing /etc/systemd/system.conf, uncomment and set the parameter to 65535 if necessary, then reboot or run systemctl daemon-reload to activate the change.

Configuring Storage Device Path Persistence Manually

To preserve Oracle ASM device names, ownership, and permissions across reboots, identify each disk’s stable SCSI identifier with scsi_id, enable trusted-device scanning through /etc/scsi_id.config, and create a UDEV rules file under /etc/udev/rules.d/ that assigns the appropriate installation owner, ASM OSDBA group, and mode 0660. Ensure OWNER, GROUP, and MODE precede other rule attributes, copy the rules to every cluster node, run partprobe, test the rules with udevtest, and reload or restart UDEV using the distribution-specific command. Verify that all ASM devices have the intended persistent paths, ownership, and permissions.
Read More: Configuring Storage Device Path Persistence Manually