Professional Documents
Culture Documents
The Setup: an Oracle database supporting an application called ABC, and given th
e following:
Assuming that we need to create filesystems intended for Oracle and:
we are using a SID of 'ABC'
we have nine disks, c0t0d1 through c0t0d9
we will be creating six volumes: /u01/oradata/ABC ( 4gb ), /u02/oradata/ABC (4gb
), /u03/oradata/ABC (8gb ), /u04/oradata/ABC ( 4gb ), /u01/app/oracle/product/8
.0.5_ABC ( 4gb ), and /u01/admin/ABC ( 4gb ).
We added these disks to Volume Manager Control during installation with vxinstal
l, or later with vxdiskadd(1m). Both vxinstall and vxdiskadd can add either init
ialize a previously unused disk, or 'encapsulate' a disk already containing data
, but not under Volume Manager control.
we could take the following steps to set up our filesystems.
Adding an EMC disk to Veritas
Use the inq utility to see if you have SCSI visibility to the disk
Use vxdisk -o alldgs list to see if Veritas has seen the disk
if not, try the following, and then repeat the previous step:
devfsadm
vxdctl initdmp
vxdctl enable
Creating a Disk Group in Volume Manager:
Create a vxvm disk group for the Oracle SID using vxdg(1m). It's important that
all of the disks/filesystems necessary for the ABC database to run are included
in the disk group, otherwise the database could not be moved to another system.
The easiest way to do this is to use vxdiskadd
vxdiskadd c0t0d0 c0t0d1 c0t0d2 . . .
Doing it the hard way:
vxdg init ABCdg ABCdg01=c0t0d1
This would create a disk group called ABCdg containing one physical disk, c0t0d1
, which will be referred to by it's name within vxvm, ABCdg01. You cannot initia
te a disk group without specifying at least one disk as a member of the group. Y
ou should not include any disks destined to be part of an Oracle Database in the
default vxvm group, rootdg. This allows you to use the vxdg 'deport' and 'impor
t' commands to migrate an entire vxvm disk group to another host.
Now that we've create the disk group for our database, we can add the rest of ou
r disks to it:
vxdg -g ABCdg adddisk ABCdg02=c0t0d2
#
#
#
#
#
#
#
umount
umount
umount
umount
umount
umount
umount
/u01/app/oracle/admin/REPORTS
/u01/app/oracle/product/8.0.5REPORTS
/u01/oradata/REPORTS
/u02/oradata/REPORTS
/u03/oradata/REPORTS
/u04/oradata/REPORTS
/u11/oraarch/REPORTS
than one sd
-g dwproddg
-g dwproddg
-g dwproddg
-g dwproddg
# now for the scary part. dis-associating the plexes and sd's
vxplex -o rm dis dw01-01
# zap the dm from the dg
vxdg -g dwproddg rmdisk dwprodd01
# nuke the da
vxdisk rm c2t2d13s2
NAME
nclproddg
STATE
ID
enabled 949356971.2501.dfwns19