Configuring Storage for Oracle Grid Infrastructure for a Standalone Server

About Configuring Storage for Oracle Grid Infrastructure for a Standalone Server

Oracle Grid Infrastructure for a standalone server, also known as Oracle Restart, supports single-instance Oracle AI Database deployments and includes Oracle ASM for volume management, database files, recovery files, binaries, and general-purpose file systems. Oracle Grid Infrastructure must be installed before creating the database when using Oracle ASM or Oracle Restart; Oracle Restart cannot be installed on or added to a cluster member node.

Configuring Storage for Oracle Automatic Storage Management

Configuring Oracle ASM requires determining storage usage, disk capacity, redundancy, allocation unit size, and failure-group design. External redundancy relies on storage-level protection, normal redundancy generally provides two-way mirroring, high redundancy provides three-way mirroring, flex redundancy supports file-specific protection and quotas, and extended redundancy protects across sites. Disk groups should use appropriately sized, similarly performing devices owned by the installation user, with separate groups recommended for database and recovery files. Existing groups can be inspected with ASM tools, NAS files can serve as ASM devices when correctly created and permissioned, and DAS or SAN disks should generally have one partition per physical disk.

Configuring Storage Device Path Persistence Using Oracle ASMLIB

Oracle ASMLIB simplifies ASM device management by providing persistent disk labels and permissions across system restarts and operating-system upgrades. Configure the disk discovery string as ORCL:*, and use an interactive installation method that runs ASMCA when creating a database with the ASM library driver. Install the appropriate ASMLIB packages for the operating system and kernel, using ASMLIB v3 on Oracle Linux 8 and later kernels; ASMLIB is not supported on IBM Linux on System z.

Deinstalling Oracle ASMLIB On Oracle AI Database

To remove unused Oracle ASMLIB, log in as root, stop the database, ASM, and Oracle Restart stack, unload and disable ASMLIB, remove the oracleasm-support and oracleasmlib RPMs, and verify and remove any remaining related packages or configuration files. After removal, restart the Oracle Restart stack.

Creating Directories for Oracle AI Database Files

Database and recovery files can reside on file systems separate from the Oracle base directory. Use df -h to identify suitable mount points, allowing at least 1.5 GB for database files on one file system or 3.5 GB across multiple file systems and at least 2 GB for recovery files, adding requirements when sharing storage. If the installer lacks write access, manually create the directories, assign the Oracle installation owner and inventory group, set appropriate permissions, and preferably place the fast recovery area on a separate physical disk from database files.

Configuring NVMe Over Fabrics Storage Devices with Oracle ASM

Oracle AI Database 26ai supports Oracle-native user-space NVMe over Fabrics over TCP for ASM disk groups on Linux, using Linux kernel 5.4 or later, nvmet_tcp targets, and dedicated 25 GbE-or-faster networking. Configure target subsystems, namespaces, ports, and unique NQNs with nvmetcli; build the NVMe ODM library; create /etc/oracle/nvm/nvmip.ora on each Grid Infrastructure node with initiator and target addresses; and discover devices through asm_diskstring='n:/*/*'. All standard ASM storage and failure-domain guidelines apply, and every initiator must communicate with all configured targets.
Read More: Configuring NVMe Over Fabrics Storage Devices with Oracle ASM