Recovery Manager Command Syntax

cmdLine

Syntax

Purpose

To start RMAN from the O/S command line. Use these arguments to:

Connect to the target, recovery catalog, or auxiliary database.

Note:
On some platforms, you may choose to connect at the command line because the password is visible to other users on the system. The connect command is an alternative method that avoids this problem.

Specify that you are using RMAN without a recovery catalog.
Run a command file, which is a user-defined file containing RMAN commands.
Specify the file in which RMAN records the results of processed commands.
Add to rather than overwrite the contents of the command file.
Generate debugging output and specify its location.
Send a command to the media manager.
Cause RMAN to print message numbers in the list output.

Requirements

Use these arguments at the O/S command line rather than at the RMAN prompt.

Keywords and Parameters

target connectStringSpec

specifies a connect string to the target database, e.g., target sys/change_on_install@inst1. See "connectStringSpec".

catalog connectStringSpec

specifies a connect string to the database containing the recovery catalog, e.g., catalog rman/rman@inst2. See "connectStringSpec".

nocatalog

indicates that you are using RMAN without a recovery catalog.You must use this argument when starting Recovery Manager without a recovery catalog.

auxiliary connectStringSpec

specifies a connect string to an auxiliary database, e.g., auxiliary sys/change_on_install@dupdb. See "connectStringSpec".

log filename

specifies the file where Recovery Manager will record RMAN output, i.e., the commands that were processed and their results. If you do not specify this argument, then Recovery Manager writes its message log file to standard output.

append

causes new output to be appended to the end of the message log file. If you do not specify this parameter and a file with the same name as the message log file already exists, RMAN overwrites it.

cmdfile filename

runs a file containing a user-defined list of RMAN commands. If the first character of the filename is alphabetic, then you can omit the quotes around the filename.
The contents of the command file should be identical to commands entered at the RMAN prompt. For example, the following file contents will cause RMAN to connect to a target database and recovery catalog RCAT:
connect target; connect catalog rman/rman@rcat;
RMAN terminates after running the command file.

@filename

equivalent to cmdfile.

msgno

causes RMAN to print message numbers, i.e., RMAN-xxxx, for the output of the list command. By default, list does not print the RMAN-xxxx prefix.

trace filename

specifies the name of the file in which RMAN logs debugging information. You must also specify the debug option to generate debugging output. If you specify debug without also specifying trace, then RMAN writes the debugging output to standard output or the message log if one is specified.

debug

activates the debugging feature. Use this option only for problem diagnosis under the direction of Oracle World Wide Support.

send 'command'

sends a vendor-specific command string to all allocated channels. See your media management documentation to determine whether this feature is supported.
See Also: To send a string to specific channels, see "send".

Examples

Connecting without a Recovery Catalog

This example connects to the target database PROD1 without a recovery catalog:

% rman target sys/sys_pwd@prod1 nocatalog

Connecting to an Auxiliary Instance

This example connects to the target database PROD1, the recovery catalog database RCAT, and the auxiliary instance AUX1:

% rman target sys/sys_pwd@prod1 catalog rman/rman@rcat auxiliary sys/aux_pwd@aux1

Specifying a Command File

This example connects to the target database PROD1 and the recovery catalog database RCAT, and then runs the command file
b_whole_10.rcv:

% rman target sys/sys_pwd@prod1 catalog rman/rman@rcat @'/oracle/dbs/b_whole_l0.rcv'

Specifying a Message Log in Append Mode

This example connects to the target database PROD1 without a recovery catalog and then specifies that RMAN should append messages to the message log:

% rman target sys/sys_pwd@prod1 nocatalog log = $ORACLE_HOME/dbs/log/msglog.f append

target connectStringSpec	specifies a connect string to the target database, e.g., target sys/change_on_install@inst1. See "connectStringSpec".
catalog connectStringSpec	specifies a connect string to the database containing the recovery catalog, e.g., catalog rman/rman@inst2. See "connectStringSpec".
nocatalog	indicates that you are using RMAN without a recovery catalog.You must use this argument when starting Recovery Manager without a recovery catalog.
auxiliary connectStringSpec	specifies a connect string to an auxiliary database, e.g., auxiliary sys/change_on_install@dupdb. See "connectStringSpec".
log filename	specifies the file where Recovery Manager will record RMAN output, i.e., the commands that were processed and their results. If you do not specify this argument, then Recovery Manager writes its message log file to standard output.
append	causes new output to be appended to the end of the message log file. If you do not specify this parameter and a file with the same name as the message log file already exists, RMAN overwrites it.
cmdfile filename	runs a file containing a user-defined list of RMAN commands. If the first character of the filename is alphabetic, then you can omit the quotes around the filename. The contents of the command file should be identical to commands entered at the RMAN prompt. For example, the following file contents will cause RMAN to connect to a target database and recovery catalog RCAT: connect target; connect catalog rman/rman@rcat; RMAN terminates after running the command file.
@filename	equivalent to cmdfile.
msgno	causes RMAN to print message numbers, i.e., RMAN-xxxx, for the output of the list command. By default, list does not print the RMAN-xxxx prefix.
trace filename	specifies the name of the file in which RMAN logs debugging information. You must also specify the debug option to generate debugging output. If you specify debug without also specifying trace, then RMAN writes the debugging output to standard output or the message log if one is specified.
debug	activates the debugging feature. Use this option only for problem diagnosis under the direction of Oracle World Wide Support.
send 'command'	sends a vendor-specific command string to all allocated channels. See your media management documentation to determine whether this feature is supported. See Also: To send a string to specific channels, see "send".