Configuring Storage for Oracle Grid Infrastructure for a Standalone Server

About Configuring Storage for Oracle Grid Infrastructure for a Standalone Server Page

Oracle Grid Infrastructure for a standalone server, also known as Oracle Restart, provides high availability support for single-instance databases and includes Oracle ASM for volume management and file storage. Oracle recommends installing Grid Infrastructure before creating databases when using Oracle ASM or Oracle Restart; Oracle Restart cannot be installed on, or added to, a cluster member node managed by Grid Infrastructure for a Cluster.

Read More: About Configuring Storage for Oracle Grid Infrastructure for a Standalone Server Page

Configuring Storage for Oracle Automatic Storage Management

Plan Oracle ASM storage by selecting whether database files, recovery files, or both will use ASM; choosing disk-group redundancy; calculating capacity; and defining failure groups where needed. External redundancy relies on storage-level protection, normal redundancy generally provides two-way mirroring, high redundancy provides three-way mirroring, and flex or extended redundancy support more flexible or site-aware protection. Use similarly sized and performing devices owned by the grid installation user, avoid multiple partitions from one physical disk, and prefer direct LUNs over complex logical volumes. ASMFD is deprecated on Linux and Solaris, and ASMlib v3 is recommended for supported Linux kernels. Existing ASM disk groups can be inspected with ASMCMD, while NAS files, DAS, and SAN partitions may also provide ASM devices when configured correctly.

Read More: Configuring Storage for Oracle Automatic Storage Management

Configuring Storage Device Path Persistence Using Oracle ASMLIB

Oracle ASMLIB provides persistent ASM disk labels, permissions, and device discovery across system restarts and operating-system upgrades. Configure the disk discovery string as ORCL:*, and use an interactive ASMCA installation method when creating a database with the ASM library driver. Install ASMLIB v3 on Oracle Linux 8 and later kernels and ASMLIB v2 on Oracle Linux 7 and earlier, verifying the system kernel and architecture first; ASMLIB is not supported on IBM Linux on System z or Linux for Arm.

Read More: Configuring Storage Device Path Persistence Using Oracle ASMLIB

Deinstalling Oracle ASMLIB On Oracle 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 packages, and delete any remaining Oracle ASM RPMs or configuration files. After cleanup, restart the Oracle Restart stack.

Read More: Deinstalling Oracle ASMLIB On Oracle Database

Creating Directories for Oracle Database Files

To place database and recovery files on separate file systems, check available capacity with df -h, select mount points meeting the database and recovery space requirements, and create directories manually when the installer lacks permission. Assign the Oracle software owner and inventory group, apply suitable permissions, and preferably place the fast recovery area on a separate physical disk from the database files so it remains available for recovery if the database storage fails.

Read More: Creating Directories for Oracle Database Files

Migrating from Oracle ASM Filter Driver to Oracle ASMLib for Oracle Restart

On Linux kernels 5.14 and later, migrate Oracle ASMFD to ASMLIB 3.1 in rolling mode because ASMFD filtering is disabled. Confirm ASMFD disks, apply required patches and compatibility changes, stop Oracle Restart and ACFS, deconfigure ASMFD, install and configure ASMLIB, initialize and enable its service, scan and verify that the disk list matches the original configuration, restart ACFS and Oracle Restart, and confirm that ASM disks are exposed with the ORCL: prefix and owned by the asmdba group.

Read More: Migrating from Oracle ASM Filter Driver to Oracle ASMLib for Oracle Restart

Deconfiguring Oracle ASM Filter Driver

To deconfigure unused ASMFD, set a temporary ORACLE_BASE, stop Oracle Restart and ACFS, run asmcmd afd_deconfigure, restart ACFS even when it is not otherwise used, and then start Oracle Restart. For future upgrades where ASMFD is desupported, ensure ASM devices have the required asmdba ownership and group configuration.
Read More: Deconfiguring Oracle ASM Filter Driver