Configuring Storage for Oracle Grid Infrastructure

Configuring Storage for Oracle Automatic Storage Management

Describes how to plan and configure Oracle ASM storage for Oracle Grid Infrastructure clusters, including database, recovery, OCR, and voting files. It covers redundancy options, failure groups, allocation units, metadata sizing, device-selection guidelines, NFS-based ASM files, existing disk-group validation, disk discovery strings, Clusterware storage requirements, and ASM upgrade behavior. ASMFD is desupported in Oracle AI Database 26ai and unsupported on newer Linux kernels, with ASMlib v3 recommended where applicable.

Configuring Storage Device Path Persistence Using Oracle ASMLIB

Explains how Oracle ASMLIB provides persistent ASM disk labels and permissions, eliminates device rebinding after restarts, and requires the ASM discovery string ORCL:* when used. It outlines installation considerations, including the requirement for ASMLib v3 on Oracle Linux 8 and later kernels, and provides procedures for safely stopping ASM and Clusterware, unloading ASMLIB, disabling its configuration, and removing its packages.

Configuring NVMe Over Fabrics Storage Devices with Oracle ASM

Explains how Oracle ASM can use NVMe over Fabrics storage for database files through Oracle’s native user-space NVMe-oF solution on Linux. It defines supported kernel, networking, and target requirements; recommends dedicated high-speed connections; and provides procedures for configuring Linux TCP NVMe targets, namespaces, ports, and unique NQNs. It also describes building the NVMe ODM library, creating per-node nvmip.ora files, and discovering devices through the ASM disk string n://.

Using Disk Groups with Oracle AI Database Files on Oracle ASM

Provides guidance for using existing or new ASM disk groups for Oracle Clusterware and database files, including custom failure-group design to protect against HBA failures. It recommends uniform device size and performance, separate physical devices, and avoidance of unnecessary logical-volume layers. It also explains how to place database and recovery files on conventional file systems, check available capacity, create directories with appropriate ownership and permissions, and keep the recovery area on separate physical storage when possible.

Deploying Oracle Direct NFS for Oracle AI Database

Describes configuring Oracle Direct NFS for file-system-based database storage, including recommended separation of software and data disks, NFS rsize and wsize settings of at least 32768, TCP buffer tuning, and network restart procedures. It details the oranfstab configuration attributes for servers, local and remote paths, exports, mounts, timeouts, NFS versions, routing, SNMP management, and security modes ranging from UNIX authentication to Kerberos integrity and privacy, with examples for multipath, multiple exports, and authenticated mounts.

Enabling and Disabling Direct NFS Client Control of NFS

Explains how to enable Direct NFS Client control by running the dnfs_on build command from the Grid home on every cluster node, including shared-home environments. It notes that Direct NFS is enabled by default and that restarting a database is required after removing an NFS path in use. The page also lists prerequisites for Hybrid Columnar Compression through Direct NFS, including SNMP on the ZFS server, optional management and community settings in oranfstab, and availability of the Net-SNMP library.

Creating Oracle ASM Client Data File

Describes generating an Oracle ASM client data file on the storage-server cluster with the ASMCMD mkcc command and copying it to a secure location on the client cluster node. ACLs must be enabled beforehand, the grid user must retain access, and credentials should not be exposed to other users. The client cluster version can be specified when it differs from the storage-server version.

Configuring Oracle Advanced Cluster File System

Provides the procedure for creating an Oracle ACFS file system for an Oracle RAC database home using ASMCA after installing Grid Infrastructure. Administrators verify mount-point permissions, select an ASM data disk group, define a unique volume name, mount point, size, database-home owner, and OSDBA group, then either allow ASMCA to run privileged configuration commands or execute its generated script as root. The resulting mount point must be selected as the Oracle RAC home during database installation.

Checking OCFS2 Version Manually

Explains how to verify installed OCFS2 component versions using modinfo and RPM queries. The console and tools packages must be version 1.2.7 or later, associated kernel components must meet the corresponding version pattern, and shared Oracle RAC homes require OCFS2 version 1.4.1 or later.
Read More: Checking OCFS2 Version Manually