B.5 Optimal Flexible Architecture File Path Examples

This topic shows examples of hierarchical file mappings of an Optimal Flexible Architecture-compliant installation.

This example shows an Optimal Flexible Architecture-compliant installation with three Oracle home directories and three databases, as well as examples of the deployment path differences between a cluster install and a standalone server install of Oracle Grid Infrastructure. The databasefiles are distributed across three mount points: D:\, E:\, and F:\.

Note:

  • The Grid homes are examples of Grid homes used for an Oracle Grid Infrastructure for a standalone server deployment (Oracle Restart), or a Grid home used for an Oracle Grid Infrastructure for a cluster deployment (Oracle Clusterware). You can have either an Oracle Restart deployment, or an Oracle Clusterware deployment. You cannot have both options deployed at the same time.

  • Oracle Automatic Storage Management (Oracle ASM) is included as part of an Oracle Grid Infrastructure installation. Oracle recommends that you use Oracle ASM to provide greater redundancy and throughput.

Table B-2 Optimal Flexible Architecture Hierarchical File Path Examples

Directory Description
C:\

System directory

C:\app\

Subtree for application software

C:\app\oraInventory

Central OraInventory directory, which maintains information about Oracle installations on a server. Members of the group designated as the OINSTALL group have permissions to write to the central inventory. All Oracle software installation owners must have the OINSTALL group as their primary group, and be able to write to this group.

C:\app\oracle\

Oracle base directory for user oracle. There can be many Oracle Database installations on a server, and many Oracle Database software installation owners.

Oracle software homes that an Oracle installation owner owns should be located in the Oracle base directory for the Oracle software installation owner, unless that Oracle software is Oracle Grid Infrastructure deployed for a cluster.

C:\app\grid\username

Oracle base directory for the Oracle Grid Infrastructure software, where username is the name of the user that performed the software installation. The Oracle home (Grid home) for Oracle Grid Infrastructure for a cluster installation is located outside of the Grid user. There can be only one Grid home on a server, and only one Grid software installation owner.

The Grid home contains log files and other administrative files.

C:\app\oracle\admin\

Subtree for database administration files

C:\app\oracle\admin\TAR

Subtree for support log files

C:\app\oracle\admin\db_sales\

admin subtree for database named “sales”

C:\app\oracle\admin\db_dwh\

admin subtree for database named “dwh”

C:\app\oracle\fast_recovery_area\

Subtree for recovery files

C:\app\oracle\fast_recovery_area\db_sales

Recovery files for database named “sales”

C:\app\oracle\fast_recovery_area\db_dwh

Recovery files for database named “dwh”

D:\app\oracle\oradata
E:\app\oracle\oradata
F:\app\oracle\oradata

Oracle data file directories

C:\app\oracle\product\

Common path for Oracle software products other than Oracle Grid Infrastructure for a cluster.

C:\app\oracle\product\19.0.0\dbhome_1

Oracle home directory for Oracle Database 1, owned by Oracle Database installation owner account oracle.

C:\app\oracle\product\19.0.0\dbhome_2

Oracle home directory for Oracle Database 2, owned by Oracle Database installation owner account oracle

C:\app\oradbowner\product\19.0.0\dbhome_2

Oracle home directory for Oracle Database 2, owned by Oracle Database installation owner account oradbowner.

C:\app\oracle\product\19.0.0\grid

Oracle home directory for Oracle Grid Infrastructure for a standalone server, owned by Oracle Database and Oracle Grid Infrastructure installation owner oracle.

C:\app\19.0.0\grid
Oracle home directory for Oracle Grid Infrastructure for a cluster (Grid home), owned by user grid before installation, and owned by root after installation.
C:\app\grid\username\diag\crs\hostname\crs\trace

Oracle Clusterware log files