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

rmora_createdb
SYNTAX
rmora_createdb -s <oracle_sid> -p <db_server> -t <timestamp>[-n
<clone_sid>] [-h <clone_ora_home>][-o
ascii|binary|for_backup[,recovery|norecovery]] [-d <loc>] [-v]
DESCRIPTION
The rmora_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 control file which was saved in the
Recovery Manager for Oracle repository at the time the virtual copy was created. Using an ascii
control file is more flexible as it allows to change database instance name as well as the structure
of the database.
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. However, because the virtual copy does not contain 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 control files 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 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. Also, because the virtual copy does not contain
redologs and control files, the same directory structure or same ASM diskgroups for redologs and
control files must be pre-created on the backup server.
When you use an offline virtual copy to clone a database, either with a binary control file or an
ascii control file, the cloned database uses the same archive log destination as that of the primary
database. If archive log mode is enabled, you must pre-create the archive log destination. The
offline virtual copy does not contain the archive log destination.
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 -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 –o recovery or -o norecovery option, if recovery is chosen, the clone
database is open with reset log, otherwise, the clone database is in mounted status. The primary
database and the standby database cannot coexist on the same backup server.
Recovery Manager for Oracle does not create virtual copies for virtual volumes used by Oracle
database temporary files, in order to be consistent with Oracle's backup procedure. However,
Recovery Manager for Oracle does create virtual copies for read-only and offline datafiles. (After
the database is cloned on the backup server, be sure to rename the read-only and offline datafiles
as appropriate: use the syntax in the ascii control file that is saved in the timestamp repository to
replace the real file names that are based on the mount points during cloning.)
You must run this command as a super user or Oracle owner user from the backup server. To allow
the Oracle Database Administrator (Oracle Owner) to run this command, an identical Oracle
66 Using the Recovery Manager Command Line Interface