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

6.18
Recovery Manager 3.0.3/3.0.4 for Oracle User’s Guide
COMMAND
vcdba_createdb
SYNTAX
vcdba_createdb -s <oracle_sid> -p <db_host> -t <timestamp>
[-n <clone_sid>] [-h <clone_ora_home>]
[-o ascii|binary|for_backup[,recovery|norecovery]] [-d <loc>] [-v]
DESCRIPTION
Creates a new database instance from a virtual copy.
The vcdba_createdb command creates a fully functional single-instance database or starts
up a clone database in MOUNTED mode for RMAN backup purposes. The fully functional
single-instance database can be used for any off-host processing purpose. The clone database
that is started in MOUNTED mode can only be used for RMAN backup.
The virtual copy used for cloning a database must be either an online or offline virtual copy
(created using the online or offline option), respectively. The virtual copy must have been
mounted prior to running this command.
You can create a clone database using an ascii or binary controlfile which was saved in the
Recovery Manager repository at the time the virtual copy was created. Using an ascii
controlfile is more flexible as it allows to change database instance name as well as the
structure of the database.
When using an ascii controlfile, 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. However, since the virtual copy does not contains online redo
logs and control files, their locations can be specified using -d option (can be one or more
directories or ASM diskgroups, depends on desired multiplexing). If the locations of the
redologs and controlfiles are not specified, they are created at the repository location for the
virtual copy (/etc/3par/solutions/<host>.ora.<sid>/<vc_name>).
When using a binary controlfile. 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. Also, since the virtual copy does not contain
redologs and archivelogs, the same directory structure or same ASM diskgroups for redologs
and controlfiles must be pre-created on the backup host.