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

rmora_removedb
SYNTAX
rmora_removedb -s <oracle_sid> -p <db_server> -t <timestamp>
[-n <clone_sid>] [-h <clone_ora_home>] [-f] [-v]
DESCRIPTION
The rmora_removedb command removes a clone database that was created using the
rmora_createdb
command.
The clone database is shutdown with the shutdown immediate option. All files (Oracle
parameter file, control files, and redo logs), previously created with the rmora_createdb
command are removed. The Virtual Copy remains mounted.
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
Database Administrator user must exist on backup server. In addition, permission on the Recovery
Manager for Oracle Installation and Repository directories must be changed appropriately.
OPTIONS
The following options are supported:
-s <oracle_sid>
The Oracle SID of the database instance. For Real Application Cluster (RAC) database, an Oracle
SID of any RAC instance can be specified.
-p <db_server>
The corresponding host name of the database server where the specified Oracle database instance
is running. The value of the database server name must match the output of the hostname
command.
-t <timestamp>
The timestamp of a Virtual Copy that was previously used to create the clone database.
-n <clone_sid>
The instance ID of the clone database to be removed. If the clone database uses the same oracle_sid
as the primary oracle_sid, this option can be omitted.
-h <clone_ora_home>
The Oracle home directory of the cloned database on the backup server. If specified, this value is
used instead of the value of the ORACLE_HOME_BACKUP parameter in the configuration file.
-f
Forces the removal of the clone database. Recovery Manager for Oracle uses Oracle’s shutdown
abort
command to shut down the clone database.
-v
Runs the command in verbose mode.
Recovery Manager Commands 89