Using Serviceguard Extension for RAC, 9th Edition, September 2010

Table 3-2 Required Oracle File Names for Demo Database
Oracle File
Size (MB)*
Raw Logical Volume Path NameLV Size
(MB)
Logical Volume Name
100
/dev/vg_ops/ropsctl1.ctl
108
opsctl1.ctl
100
/dev/vg_ops/ropsctl2.ctl
108
opsctl2.ctl
100
/dev/vg_ops/ropsctl3.ctl
108
opsctl3.ctl
20
/dev/vg_ops/rops1log1.log
28
ops1log1.log
20
/dev/vg_ops/rops1log2.log
28
ops1log2.log
20
/dev/vg_ops/rops1log3.log
28
ops1log3.log
20
/dev/vg_ops/rops2log1.log
28
ops2log1.log
20
/dev/vg_ops/rops2log2.log
28
ops2log2.log
20
/dev/vg_ops/rops2log3.log
28
ops2log3.log
400
/dev/vg_ops/ropssystem.dbf
408
opssystem.dbf
100
/dev/vg_ops/ropstemp.dbf
108
opstemp.dbf
120
/dev/vg_ops/ropsusers.dbf
128
opsusers.dbf
15
/dev/vg_ops/ropstools.dbf
24
opstools.dbf
200
/dev/vg_ops/ropsdata1.dbf
208
opsdata1.dbf
200
/dev/vg_ops/ropsdata2.dbf
208
opsdata2.dbf
200
/dev/vg_ops/ropsdata3.dbf
208
opsdata3.dbf
300
/dev/vg_ops/ropsroolback.dbf
308
opsrollback.dbf
5
/dev/vg_ops/ropsspfile1.ora
5
opsspfile1.ora
312
/dev/vg_ops/ropsundotbs1.dbf
320
opsundotbs1.dbf
312
/dev/vg_ops/ropsundotbs2.dbf
320
opsundotbs2.dbf
160
/dev/vg_ops/ropsexample1.dbf
168
opsexample1.dbf
100
/dev/vg_ops/ropscwmlite1.dbf
108
opscwmlite1.dbf
70
/dev/vg_ops/ropsindx1.dbf
78
opsindx1.dbf
90
/dev/vg_ops/ropsdrsys1.dbf
98
opsdrsys1.dbf
*
The size of the logical volume is larger than the Oracle file size because Oracle needs extra space
to allocate a header in addition to the file's actual data capacity.
Create these files if you wish to build the demo database. The three logical volumes at the bottom
of the table are included as additional data files, that you can create as needed, supplying the
appropriate sizes. If your naming conventions require, you can include the Oracle SID and/or
the database name to distinguish files for different instances and different databases. If you are
using the ORACLE_BASE directory structure, create symbolic links to the ORACLE_BASE files
from the appropriate directory. Example:
# ln -s /dev/vg_ops/ropsctl1.ctl /u01/ORACLE/db001/ctrl01_1.ctl
After creating these files, set the owner to oracle and the group to dba with a file mode of 660.
The logical volumes are now available on the primary node, and the raw logical volume names
can now be used by the Oracle DBA.
Creating a Storage Infrastructure with LVM 81