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

This page explains how to manually configure Linux kernel parameters when fixup scripts or the Oracle AI Database Preinstallation RPM are unavailable or insufficient. It lists minimum semaphore, shared-memory, file, asynchronous I/O, network port, and socket buffer settings; provides commands to inspect current values; and describes persisting changes in /etc/sysctl.d/97-oracle-database-sysctl.conf before applying and verifying them with sysctl. It also covers configuration guidelines, SUSE-specific hugetlb_shm_group settings, and manual UDP/TCP ephemeral-port configuration, recommending a range beginning at 9000, appropriate even/odd endpoints, sufficient capacity, and persistent application after restart.

Configuring Default Thread Limits Value for SUSE Linux

This page instructs administrators using SUSE Linux Enterprise Server 15 or later to increase the systemd DefaultTasksMax limit from its typical value of 512 to 65535 to prevent service failures caused by thread limits. Administrators should inspect the current setting with systemctl show --property DefaultTasksMax or /etc/systemd/system.conf, uncomment and set the configuration value if necessary, then activate it by rebooting or running systemctl daemon-reload.

Configuring Storage Device Path Persistence Manually

This page describes manually preserving Oracle ASM storage device names, ownership, and permissions across Linux restarts by creating custom udev rules. It explains collecting stable SCSI identifiers with scsi_id, enabling trusted-device handling through /etc/scsi_id.config, and creating rules that assign the installation owner, ASM OSDBA group, and mode 0660 in the required attribute order. On clusters, the rules file must be copied to every node; administrators should run partprobe, test the rules with udevtest, reload or restart udev according to the Linux distribution, and verify the resulting device ownership and permissions.
Read More: Configuring Storage Device Path Persistence Manually