Oracle's OFA architecture

Oracle's Best Flexible architecture (Optimal flexible Architecture, referred to as OFA) refers to the naming conventions and storage location rules for Oracle software and database files and folders. It can be used as a good set of habits, which makes it easy for users to find the file structure associated with an Oracle database.

The use of the best flexible architecture simplifies the management of database systems, makes it easier for database administrators to locate files or add files, and can store the execution files, management files, and data files of Oracle systems on separate hard disks, effectively using all the storage space in the user's system, Overcome some (some) hard disk storage space limitations, reasonable allocation of storage burden, reduce the speed of individual hard disk storage bottlenecks, improve the overall system storage efficiency.

Optimal flexible architecture (Optimal flexible Architecture, abbreviated OFA)

OFA is actually a kind of Oracle specification, its meaning is to use a uniform to file and folder rules, and file directory rules to make a convention. In this way, we do not install multiple versions of Oracle database, because the directory specification, naming specifications, so that the software does not conflict, easy to manage, files are also easy to find. By following the guidance of OFA, the whole system can be more flexible.

OFA naming mechanism on the Linux/unix platform
The mount point is named with/PM, where p is a string constant and M is a fixed-length number. For example:/u01,/u02,/ORA01,/ora02 are good choices.

The base directory is usually/pm/h/u, where H is a character constant, usually an app. U is the directory owner, typically Oracle.
The Oracle_home directory is usually/pm/h/u/product/v. where V is the version number, for example 9.2.0, 10.2.0. Some of the new components, such as ASM and Agent, are under this directory, such as/u01/app/oracle/product/10.2.0/agent,/u01/app/oracle/product/10.2.0/asm
Database-specific management files, such as startup parameter files, dump file directories, are usually/pm/h/u/admin/d/a. Where admin is a fixed character, D is the name of the database, a indicates the name of the subdirectory, for example, the alarm log is Alert_ora10g.log, the user directory is bdump, the database instance name is ora10g, the alert log is in the directory, $ORACLE _base/ Admin/orcl/bdump/alert_ora10g.log.

The key file is usually/pm/h/u/q/d, where Q is a string, usually oradata,d represents the data name. The control file is usually a number that is controln.ctl,n to two bits long, such as Control01.ctl, Control02.ctl. Redon.log,n is a two-bit length number, such as Redo01.log, Redo02.log, data file tn.dbf,t represents the name of the Tablespace, N is a two-bit length number, such as USERS01.DBF, USERS02.DBF, etc.
Directory structure under normal circumstances

Sub-directory Name
Use
Example
Adhoc Storage database-specific SQL and $oracle_base/admin/sid/adhoc PL scripts
Arch stores archived redo log Files $oracle_base/admin/sid/arch
Adump the directory where the audit files are stored (you need to set the audit_file_dest first) parameter $oracle_base/admin/sid/adump
Bdump stores background process trace files with warning log files. Set with the Background_dump_dest parameter $oracle_base/admin/sid/bdump
Cdump stores core heap files. Set with the Core_dump_dest parameter $oracle_base/admin/sid/cdump
Udump stores user process trace files. Set with the User_dump_dest parameter $oracle_base/admin/sid/udump
Scripts stores the script used to create the database. When you create a new database, DBCA sets the script for creating the database in this directory $oracle_base/admin/sid/scripts
EXP recommends storing a directory of database export files created using the Export utility or ORACLE Data pump $oracle_base/admin/sid/exp
Logbook store database history and status log files $oracle_base/admin/sid/logbook
Pfile The parameter file used to start the database is placed in this directory $oracle_base/admin/sid/pfile
Orainventory
Oracle uses a manifest directory named Oracle on the server, also known as a special directory for orainventory, to hold all Oracle software inventory. Multiple Oracle installations can share the same inventory directory. Only the first time you install Oracle you need to specify in the environment variable

Oracle's OFA architecture