Oracle With Examples : Oracle

Oracle Applications EBS 11i, R12      Oracle Database      Data Warehouse & BI      Oracle Middleware      PL/SQL      Linux ...

Oracle DBA

Real Application Cluster (RAC) Maintenance tasks Backup and Recovery Database Architecture Replication Oracle Performance Tuning Oracle DBA - Other articles Oracle scripts/ Selects for DBA Oracle Errors (ORA-nnnnn)

The last articles in the site (HOT)

The most visited articles in the site  -> Oracle DBA

-> Oracle OFA : Oracle Optimal Flexible Architecture


 Oracle OFA : Oracle Optimal Flexible Architecture



Oracle OFA (Optimal Flexible Architecture) is a set of rules guidelines that help you to manage the database easier and assure that all the tasks are done quicker and better. This is the reason why we need to read the Oracle OFA rules. These rules are not mandatory, but are good to follow them. Sometimes there are rules related to an Oracle version, but the most of all are generic and are created most for the production environments. The rules may changes function of the hardware / the architecture we use (if we use RAID or not for instance).


1. OFA naming convention for directories

   - all the oracle binaries (Oracle homes) stay in a directory path to differentiate the Oracle product (database, middleware, etc)  and the version. Also we have to know that this is an Oracle product.

      For this reason, ORACLE_HOME directory path must be like this:


     "database" => there we have the database binaries

     "11.2.0"    => for the 11.2.0 version      (generally we use the 3 digit version)


   - the datafiles (including the control files, and the log files) are not stored in the same directory with the Oracle binaries (we cannot have the data files in Oracle homes !!!).

     For this reason the data files are situated in a directory like this:


    "oradata"  => we have data files here

    "PDD"     =>  for the ORACLE_SID = PDD

2. Mount points naming

If we have 2 disks (physical disks generally) we can create 2 mount points for them like :  /oradata/PDD  and  /data2/PDD but if you read this it is not evident that we deal with 2 disks (this thing is very important for an Oracle DBA).


In order to fix this "issue" Oracle OFA recommends using this notation:  /u01  and /u02


When you read ... /u01/oradata/PDD/users01.dbf  and /u02/oradata/PDD/users02.dbf it's clear that we have 2 data files located on different disks.


3. Tuning I/O loads across all disks

This guideline is useful generally when we are not using a RAID as storage.


4. Name the file extensions function of their content


.ctl       --->  for control files
.log      --->  for log files
.dbf     --->  for data files

.arc     --->  for achieve log files


5. Database administration files are located in the same location (have a common directory their directory are stored in )

Oracle With Examples 11g this is done by setting the DIAGNOSTIC_DEST initialization parameter.


Oracle With Examples 11g, ADR location: <diagnostic_dest>/diag/rdbms/<dbname>/<instname>

The following files are located under the ADR home directory:

Trace files - located in subdirectory <adr-home>/trace
Alert logs - located in subdirectory <adr-home>/alert
Core files - located in the subdirectory <adr-home>/cdumd


6. The data files have names which can identify quickly their associated tablespace.

For the TEMP tablespace "temp01.dbf" could be a good name for instance.  -> Oracle DBA

-> Oracle OFA : Oracle Optimal Flexible Architecture

Oracle Applications EBS 11i, R12      Oracle Database      Data Warehouse & BI      Oracle Middleware      PL/SQL      Linux ...


     Copyright (c) 2018  |  Disclaimer: The views expressed on this web site are my own and do not reflect the views of Oracle Corporation. You may use the information from this site only at your risk.