Scribd
Upload
12 views2 pages

Oracle Flexible Architecture

Oracle Optimal Flexible Architecture (OFA) provides configuration guidelines for organizing Oracle installations, enhancing administration and maintenance. It ensures optimal performance by minimizing fragmentation and contention while allowing multiple databases to coexist. Following OFA rules is particularly beneficial for large databases or those with multiple installations, as it simplifies management and supports consistent configurations.

Uploaded by

pheist40
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views2 pages

Oracle Flexible Architecture

Oracle Optimal Flexible Architecture (OFA) provides configuration guidelines for organizing Oracle installations, enhancing administration and maintenance. It ensures optimal performance by minimizing fragmentation and contention while allowing multiple databases to coexist. Following OFA rules is particularly beneficial for large databases or those with multiple installations, as it simplifies management and supports consistent configurations.

Uploaded by

pheist40
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Optimal Flexible Architecture

Oracle Optimal Flexible Architecture (OFA) rules are a set of configuration guidelines created
to ensure well-organized Oracle installations, which simplifies administration, support and
maintenance. Oracle Optimal Flexible Architecture (OFA) rules help you to organize database software
and configure databases to allow multiple databases, of different versions, owned by different users to
coexist.

In earlier Oracle Database releases, the OFA rules provided optimal system performance by
isolating fragmentation and minimizing contention. In current releases, OFA rules provide
consistency in database management and support, and simplifies expanding or adding databases,
or adding additional hardware.

By default, Oracle Universal Installer places Oracle Database components in directory locations
and with permissions in compliance with OFA rules. Oracle recommends that you configure all
Oracle components in accordance with OFA guidelines. Oracle recommends that you accept the
OFA default. Following OFA rules is especially of value if the database is large, or if you plan to
have multiple databases.

Note:
OFA assists in identification of an ORACLE_BASE with its Automatic Diagnostic Repository
(ADR) diagnostic data to properly collect incidents.

For example:

If you are performing an Oracle Database installation, and you set ORACLE_BASE for user
oracle to the path /u01/app/oracle before installation, and grant 755 permissions to oracle for that
path, then Oracle Universal Installer creates the Oracle Inventory directory one level above the
ORACLE_BASE in the path ORACLE_BASE/../oraInventory, so the Oracle Inventory path is
/u01/app/oraInventory. Oracle Universal Installer installs the software in the ORACLE_BASE path.
If you are performing an Oracle Grid Infrastructure for a Cluster installation, then the Grid
installation path is changed to root ownership after installation, and the Grid home software
location should be in a different path from the Grid user Oracle base.

If you create the OFA path /u01, and grant oracle 755 permissions to write to that path, then the
Oracle Inventory directory is created in the path /u01/app/oraInventory, and Oracle Universal
Installer creates the path /u01/app/oracle, and configures the ORACLE_BASE environment
variable for the Oracle user to that path. If you are performing an Oracle Database installation,
then the Oracle home is installed under the Oracle base. However, if you are installing Oracle
Grid Infrastructure for a cluster, then be aware that ownership of the path for the Grid home is
changed to root after installation and the Grid base and Grid home should be in different
locations, such as /u01/app/19.0.0/grid for the Grid home path, and /u01/app/grid for the Grid base.
/u01/app/oraInventory, owned by grid:oinstall
/u01/app/oracle, owned by oracle:oinstall
/u01/app/oracle/product/19.0.0/dbhome_1/, owned by oracle:oinistall
/u01/app/grid, owned by grid:oinstall
/u01/app/19.0.0/grid, owned by root

If you have neither set ORACLE_BASE, nor created an OFA-compliant path, then the Oracle
Inventory directory is placed in the home directory of the user that is performing the installation,
and the Oracle software is installed in the path /app/owner, where owner is the Oracle software
installation owner. For example:

You might also like