|
|
|
|
|
Run a command file
in the same directory as another command file that is currently running.
The @@ command
differs from the @ command only when run from within a command file.
|
|
|
Establish a
channel, which is a connection between RMAN and a database instance.
|
|
|
Allocate a channel
in preparation for issuing maintenance commands such as DELETE.
|
|
|
A subclause that
specifies channel control options such as PARMS, FORMAT, and MAXOPENFILES.
|
|
|
Mount or open a
database.
|
|
|
Specify a range of
archived redo logs files.
|
|
|
Back up a database,
tablespace, datafile, archived log, or backup set.
|
|
|
Recover an
individual data block or set of data blocks within one or more datafiles.
|
|
|
Add information
about a datafile copy, archived redo log, or control file copy to the
repository.
|
|
|
Mark a backup
piece, image copy, or archived redo log as having the status UNAVAILABLE or AVAILABLE; remove the
repository record for a backup or copy; override the retention policy for a
backup or copy.
|
|
|
Specify a time
range during which the backup or copy completed.
|
|
|
Configure
persistent RMAN settings. These settings apply to all RMAN sessions until
explicitly changed or disabled.
|
|
|
Establish a
connection between RMAN and a target, auxiliary, or recovery catalog
database.
|
|
|
Specify the
username, password, and net service name for connecting to a target, recovery
catalog, or auxiliary database. The connection is necessary to authenticate
the user and identify the database.
|
|
|
Create an image
copy of a datafile, control file, or archived redo log.
|
|
|
Create the schema
for the recovery catalog.
|
|
|
Create a stored
script and store it in the recovery catalog.
|
|
|
Determine whether
files managed by RMAN, such as archived logs, datafile copies, and backup
pieces, still exist on disk or tape.
|
|
|
Specify a datafile
by filename or absolute file number.
|
|
|
Delete backups and
copies, remove references to them from the recovery catalog, and update their
control file records to status DELETED.
|
|
|
Delete a stored
script from the recovery catalog.
|
|
|
Specify the type of
storage device for a backup or copy.
|
|
|
Remove the schema
from the recovery catalog.
|
|
|
Use backups of the
target database to create a duplicate database that you can use for testing
purposes or to create a standby database.
|
|
|
Run an RMAN stored
script.
|
|
|
Quit the RMAN
executable.
|
|
|
Invoke an operating
system command-line subshell from within RMAN or run a specific operating
system command.
|
|
|
Specify that a
backup or copy should or should not be exempt from the current retention
policy.
|
|
|
Produce a detailed
listing of backup sets or copies.
|
|
|
A subclause used to
specify which items will be displayed by the LIST command.
|
|
|
A subclause used to
specify additional options for maintenance commands such as DELETE and CHANGE.
|
|
|
A subclause used to
determine which backups and copies are obsolete.
|
|
|
|
|
|
Exit the RMAN
executable.
|
|
|
A subclause used to
specify which objects the maintenance commands should operate on.
|
|
|
Apply redo logs or
incremental backups to a restored backup set or copy in order to update it to
a specified time.
|
|
|
Register the target
database in the recovery catalog.
|
|
|
|
|
|
|
|
|
Replace an existing
script stored in the recovery catalog. If the script does not exist,
then REPLACE SCRIPT creates it.
|
|
|
Perform detailed
analyses of the content of the recovery catalog.
|
|
|
Inform RMAN that
the SQL statement ALTER DATABASE OPEN RESETLOGS has been executed and that a new incarnation of the
target database has been created, or reset the target database to a prior
incarnation.
|
|
|
Restore files from
backup sets or from disk copies to the default or a new location.
|
|
|
Perform a full
resynchronization, which creates a snapshot control file and then copies any
new or changed information from that snapshot control file to the recovery
catalog.
|
|
|
Execute a sequence
of one or more RMAN commands, which are one or more statements executed
within the braces of RUN.
|
|
|
Send a
vendor-specific quoted string to one or more specific channels.
|
|
|
Make the following
session-level settings:
·
Control whether
RMAN commands are displayed in the message log
·
Set the DBID when
restoring a control file or server parameter file
·
Specify new
filenames for restored datafiles
·
Specify a limit for
the number of permissible block corruptions
·
Override default
archived redo log destinations
·
Specify the number
of copies of each backup piece
·
Determine which
server session corresponds to which channel
·
Control where RMAN
searches for backups when using an Oracle Real Application Clusters
configuration
·
Override the
default format of the control file autobackup
|
|
|
Displays the
current CONFIGURE settings.
|
|
|
Shut down the
target database. This command is equivalent to the SQL*Plus SHUTDOWN command.
|
|
|
Write RMAN output
to a log file.
|
|
|
Execute a SQL
statement from within Recovery Manager.
|
|
|
Start up the target
database. This command is equivalent to the SQL*Plus STARTUP command.
|
|
|
Specify that a
datafile copy is now the current
datafile, that is, the datafile pointed to by the control file. This
command is equivalent to the SQL statement ALTERDATABASE RENAME FILE as it applies
to datafiles.
|
|
|
A subclause
specifying an upper limit by time, SCN, or log sequence number. This clause
is usually used to specify the desired point in time for an incomplete
recovery.
|
|
|
Upgrade the
recovery catalog schema from an older version to the version required by the
RMAN executable.
|
|
|
Examine a backup
set and report whether its data is intact. RMAN scans all of the backup
pieces in the specified backup sets and looks at the checksums to verify that
the contents can be successfully restored.
|
No comments :
Post a Comment
Note: only a member of this blog may post a comment.