HP StoreServ Application Suite for Oracle Media Pilot# vxdisk list, C0t0d0s2, Error, C2t0d0s2

Recovery Manager for Oracle User’s Guide

Example:

pilot:# vxdisk list		DISK	GROUP	STATUS
DEVICE	TYPE
c0t0d0s2	sliced	-	-	error
c2t0d0s2	sliced	disk01	rootdg	online
c2t0d41s2	sliced	orcl92001	orcl920dg	online
c2t0d42s2	sliced	orcl92002	orcl920dg	online
c2t0d43s2	sliced	orcl92003	orcl920dg	online
c2t0d44s2	sliced	orcl92004	orcl920dg	online
c2t0d45s2	sliced	orcl92005	orcl920dg	online
c2t0d46s2	sliced	orcl92006	orcl920dg	online
c2t0d47s2	sliced	orcl92007	orcl920dg	online
c2t0d48s2	sliced	arch92001	arch920dg	online
c2t0d49s2	sliced	arch92002	arch920dg	online

eRun the fsck command and mount all the file systems. If ASM is being used, mount all involved ASM disk groups.

fRecover the database using the new control file generated from the vcdba_rollback command. The name of the file is ascii_controlfile_for_rollback, and it is located in the virtual copy repository on the backup host. It also shows on the backup host screen when the rollback is done. Copy the ascii control file from the backup host to the primary host.

6(Optional) Recover the cloned database on the backup host as follows:

NOTE: After performing the rollback, if you still want the cloned database on the backup host up and running, the following steps should be performed. Otherwise, this section can be skipped.

aOn the InServ Storage Server, recreate all VLUNs previously removed by issuing the createvlun <vvname> <lun> <host> command.

bOn the backup host, run the vxdctl enable command and import the disk groups using the same name as when you deported them.

Example:

vxdg import orcl920dg_042903142921

vxdg import arch920dg_042903142921

8.6

Database Volumes Under Veritas VxVM Control