HP 3PAR Application Software Suite for Oracle Licenses - Manual (Page 15)

When using an ascii control file:
•
The structure of the clone database is not required to be exactly the same as the structure of
the original database. Therefore the Virtual Copy can be mounted at any mount point.
•
Because the Virtual Copy does not contain online redo logs and control files, their locations
can be specified using the -d option (can be one or more directories or ASM diskgroups,
depending on the desired multiplexing).
•
The number of multiplex redo log locations must be equal to, or less than, the original database
when creating the clone database. Otherwise, the extra redo log multiplex location will be
ignored.
•
If the locations of the redo logs and control files are not specified, they will be created at the
repository location for the Virtual Copy
(/etc/3par/solutions/<host>.ora.<sid>/<vc_name>).
When using a binary control file:
•
The structure of the clone database must be exactly the same as the structure of the original
database. Therefore, the Virtual Copy must be mounted at '/' if the datafiles and archive logs
are on file systems.
•
Because the Virtual Copy does not contain redo logs and control files, the same directory
structure or same ASM diskgroups for the redo logs and control files must be pre-created on
the backup server.
When creating a clone database for backup (RMAN) purposes, the database is started in
MOUNTED mode using the binary control file from the repository without recovering the database.
This can be achieved by using the -o for_backup or -o binary,norecovery option.
A clone database can be created with or without automatic recovery (applying archivelogs from
the Virtual Copy) using the –o recovery or -o norecovery option. If recovery is chosen, the
clone database is open with a resetlogs. If no recovery is chosen, the clone database is mounted
and archive logs from the Virtual Copy are not applied.
The Cloned Database Removal Utility
HP 3PAR Recovery Manager Software for Oracle’s cloned database removal utility
(rmora_removedb command) removes a cloned database, which was created using the
rmora_createdb
command.
The cloned database is shutdown with the shutdown immediate option. The database related
files (Oracle parameter file, control files and redo logs), which were previously created by the
rmora_createdb
command, are removed. The read-write Virtual Copy remains mounted.
The Virtual Copy Removal Utility
HP 3PAR Recovery Manager for Oracle’s Virtual Copy removal utility removes an existing Virtual
Copy from the HP 3PAR StoreServ Storage system. The Virtual Copy must have Available status
in order to be removed using the rmora_remove command. The status of a Virtual Copy is
obtained by using the display utility rmora_display.
This utility only removes the read-only Virtual Copy from the system to free up the snapshot space.
It does not actually remove the repository information if the Virtual Copy has been backed up to
the media. This enables Recovery Manager for Oracle to restore a Virtual Copy, which has been
previously backed-up to the media on the original volumes, as long as the Virtual Copy repository
exists.
Recovery Manager for Oracle Utilities 15