Oracle Restart: Grid Infrastructure 19c + ASM (single server)

Installs Oracle Restart (Grid Infrastructure 19c standalone, HA_CONFIG) and ASM on a single server: grid user and ASM groups, persistent disk names (udev, ASMLib or ASM Filter Driver; single-path or multipath disks), gridSetup.sh -silent with the RU applied, DATA and FRA disk groups, verification with srvctl/asmcmd. For single-server environments that want the database on ASM; apply it before the database installation. It does not build a cluster (RAC); for that use the Oracle RAC 19c guide. At the end ASM, the listener and the database installed later are managed by Oracle Restart and start automatically at boot.

Topology: 1 server + non-shared ASM disks

Before you start

• Oracle Linux / RHEL … is supported and up to date.… On OL9/RHEL9 Oracle's Release Notes recommend GI RU 19.32 or later plus the listed one-offs for Grid 19c (this guide applies both during installation with -applyRU/-applyOneOffs).… OL/RHEL 7.9: 19c (including Grid) is supported; minimum kernel on OL7 is UEK4 4.1.12-124.19.2, UEK5 4.14.35-1818.1.6, UEK6 5.4.17-2011.4.4 or RHCK 3.10.0-862.11.6 (RHEL 7.5+). The 19.3 base installer recognizes OL7; the RU is still applied during installation.… On OL 8.8 with the UEK7 kernel, Grid 19c requires at least GI RU 19.23.…… For AFD the running kernel must be older than 5.14 (RHCK 4.18 or UEK6) and listed as supported in MOS 1369107.1; on the UEK7 (5.15) kernel AFD filtering is disabled.…… ASMLib v2 (OL7): on UEK the oracleasm driver ships with the kernel, on RHCK kmod-oracleasm is required.…… ASMLib v3: on OL9 UEK7/UEK8/RHCK (io_uring), on OL8 UEK7 (io_uring), UEK6 or RHCK (kmod-redhat-oracleasm driver).…
• The disks set aside for ASM are empty (no partition, file system or LVM) and attached only to this server…; the multipath aliases (/dev/mapper/...) are configured and every LUN has at least 2 healthy paths…: DATA … disk(s) (…), FRA … disk(s) (…). …NORMAL needs at least 2, ……HIGH needs at least 3, …and the disks must be the same size. All data on these disks is erased.
• DM-Multipath is installed and every ASM LUN appears as /dev/mapper/<alias> with an alias bound to its WWID (multipath phase of the Storage preparation: multipath guide). The devices in the form are these aliases.
• The files are under …: LINUX.X64_193000_grid_home.zip (oracle.com / edelivery: 'Oracle Database 19c Grid Infrastructure for Linux x86-64'), GI RU …, OPatch …… and the one-offs (…; p<number>_.zip)… (My Oracle Support). Verify the patch numbers on MOS.… ASMLib library oracleasmlib-.rpm (from the Oracle ASMLib download page, for OL…; …2.0.x on OL7…3.1.x recommended…).…
• At least 12 GB free for the Grid home, at least 10 GB for … and at least 1 GB in /tmp. Swap: equal to RAM if RAM ≤16 GB, otherwise 16 GB.
• Hostname … is set and resolves to its own IP.
• There is no previous Grid/Oracle Restart installation on the server.
• A maintenance window is booked and a snapshot of the server has been taken; disk assignments have been confirmed with the storage team (wrong disk = data loss).

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 …
• Directories and environment — Create the Grid directories · Write the grid user's environment file · Load the environment file at login
• Preparing the ASM disks — Verify the multipath devices · Partition the disks · Write the udev rules (persistent name and ownership) · Install ASMLib · Enable io_uring (ASMLib v3) · Configure ASMLib …
• Grid Infrastructure installation — Check the installation files · Extract the Grid software into the Grid home · Update OPatch · Extract the GI Release Update and the one-offs · Install the cvuqdisk RPM · Check AFD kernel support …
• Verification — Check the Oracle Restart resources · Check ASM, the listener and the disks · Check the AFD state · Change the listener port
• Creating the FRA disk group — Label the FRA disks with AFD · Create the FRA disk group · Verify the Oracle Restart state of the disk groups
• Database and post-installation — Verify readiness for the database installation · Verify that Oracle Restart starts at boot · Back up the OLR