Oracle Database 19c single instance installation (EE / SE2)

Installs Oracle Database 19c from scratch on a single server running Oracle Linux / RHEL 7.9, 8 or 9: operating system preparation (preinstall RPM or manual), OFA directories, silent software installation together with the Release Update, listener, CDB + PDB (AL32UTF8, SGA/PGA sized from RAM, redo, FRA, ARCHIVELOG), HugePages, automatic startup, security hardening and the first RMAN backup. Data can be kept on a file system or in the ASM disk groups of a previously installed Oracle Restart. The result is a database that is backed up, starts by itself at server boot and has a verified patch level; for RAC open the 19c RAC installation guide, for 26ai the 26ai installation guide.

Topology: 1 server

Before you start

• The operating system is supported and up to date: Oracle Linux / RHEL …. …19c became supported on OL9/RHEL9 with the 19.19 RU; Oracle's current Release Notes recommend RU 19.32 or later and the listed one-offs (this guide applies both during installation). Minimum kernel: UEK7 5.15.0-1.43.4.2 or RHCK 5.14.0-70.22.1; for UEK8 (6.12) at least the 19.32 RU and OL 9.6.…OL/RHEL 7.9 is recommended. Minimum kernel: OL 7.4 + UEK4 4.1.12-124.19.2, OL 7.4 + UEK5 4.14.35-1818.1.6, OL 7.7 + UEK6 5.4.17-2011.4.4, RHCK (OL/RHEL 7.5) 3.10.0-862.11.6. The base 19.3 installer recognizes OL7; the RU is still applied during installation.…Minimum kernel: UEK6 5.4.17-2011.0.7 or RHCK 4.18.0-80; for OL 8.8 + UEK7 (5.15.0-202.135.2) at least the 19.21 RU.…
• RAM matches the value in the form (… GB). Swap is at least … GB (equal to RAM if RAM ≤16 GB, otherwise 16 GB). At least 1 GB free in /tmp.
• At least 20 GB free under … for the software (19c home + RU backups) and at least 10 GB for ….… … (data) and … (FRA, at least … GB) are mounted as separate disks/LVs and persistent in /etc/fstab (XFS recommended).…
• The installation files are under …: LINUX.X64_193000_db_home.zip (oracle.com or edelivery.oracle.com, 'Oracle Database 19c for Linux x86-64'), …GI …RU …, OPatch …… and the one-offs (…; p<number>_.zip)… (My Oracle Support → Patches & Updates). Check the patch numbers on MOS (Doc ID 2118136.2; for recommended one-offs Doc ID 555.1). The directory you upload the files to needs at least 10 GB of free space; the zips can be deleted after installation.
• A valid Oracle license and a My Oracle Support account linked to a support contract (CSI) for downloading patches.
• The hostname … is set (hostname -f returns the same name) and resolves to the server's own IP (DNS or /etc/hosts). The listener and client connections use this name.
• Port … is not used by another process.
• The time zone is correct and the clock is synchronized with NTP (chrony). The SELinux state is known (Oracle Database can run with SELinux in enforcing mode; leave it according to your organization's policy).
• Oracle Restart (Grid Infrastructure 19c) is installed, ASM is running, the … and … disk groups are MOUNTED; the oracle user is in the asmdba group. The disks were prepared …with a udev rule…with ASM Filter Driver…with ASMLib……, through multipath aliases… (Storage preparation, Oracle Restart + ASM).
• A maintenance window is scheduled; a snapshot of the server (if it is a VM) has been taken.

Phases of the guide

• Operating system preparation — Hostname, /etc/hosts and system update · Install the Oracle preinstall RPM · Install the required RPMs · Create the Oracle groups and the oracle user · Write the kernel parameters (sysctl) · Apply the kernel parameters …
• Directory layout and environment — Create the directories and set ownership · Write the environment variables file · Hook the environment file into the session
• ASM and Oracle Restart pre-check — Verify the disk layer, ASM and the disk groups
• Software installation (together with the RU) — Check the installation files · Extract the base software into ORACLE_HOME · Update OPatch · Extract the Release Update and the one-offs · Prepare the installation response file · Install the software together with the RU (runInstaller) …
• Listener — Create the listener (netca)
• Database creation (dbca) — Create the CDB and the PDB · Keep the PDB open after startup · Fix the SGA/PGA values and restart · Add additional redo log groups · Set local_listener (port other than 1521) · Verify ARCHIVELOG and the FRA …
• Automatic startup — Enable automatic startup in oratab · Write the systemd service file · Enable the service and start through it
• Oracle Restart registration — Verify the database registration in Oracle Restart
• Verification — Check the version, components, patches and settings · Check the listener services · Check the alert log
• Security hardening — Lock Oracle accounts that are still open (ACCOUNT LOCK) · Set the password profiles · Review the unified audit policies
• Post-installation: backup and monitoring — RMAN settings and the first full backup · Back up while ARCHIVELOG is disabled · Plan scheduled backups · Monitoring: FRA and tablespace usage