Refer to this example when configuring the disk layout
in a Oracle environment.
The following figure shows file systems involved in a
sample disk layout. Figure 1. Example overall
disk layout for a Oracle environment
The respective disk categories contain the following
disk types that are used for the various file systems:
Local disks on the production system (p_disk category) for the
file systems
/oracle/A01 part of VG ora_main
/oracle/A01/acs (ACS_DIR)
The Oracle database binary
files are located in the directory that is defined by the ORACLE_HOME
environment variable.
Source volume disks on the production system (db_disk category)
for the file systems
/oracle/A01/oradata/system part of VG ora_d1
/oracle/A01/oradata/temp part of VG ora_d2
/oracle/A01/oradata/custom part of VG ora_d3
/oracle/A01/origlogA part of VG ora_l1
/oracle/A01/origlogB part of VG ora_l1
/oracle/A01/mirrlogA part of VG ora_l2
/oracle/A01/mirrlogB part of VG ora_l2
The
file systems for the control files must not reside on volume groups
that are part of the FlashCopy® backup.
For FlashCopy cloning
at least one of the three Oracle control files must reside on a volume
group that is part of the FlashCopy cloning
operation.
/oracle/A01/cntrl/cntrlA01.dbf part of VG ora_main
/oracle/A01/misc/cntrlA01.dbf part of VG ora_misc
/oracle/A01/arch/cntrlA01.dbf part of VG ora_arch
The p_db_disk category is not used for this setup.
Local disks on the backup system (b_disk category) for the file
system
/oracle/A01
/oracle/A01/acs (ACS_DIR)
There is no need to create separate volume groups for logs and
control files.