RMAN Show Command
The SHOW command returns the values of various parameters.
SHOW ALL
The SHOW ALL command shows the value of all configuration parameters.
The default values are as follows:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_TEST.f'; # default
The default value for SNAPSHOT CONTROLFILE NAME is $ORACLE_HOME/snapcf_.f
Following statement can be used to see non-default configurations
SELECT NAME, VALUE FROM V$RMAN_CONFIGURATION ;
1) CONFIGURE RETENTION POLICY TO REDUNDANCY 1; (default)
RMAN considers backups and copies of datafiles and control files as obsolete,
i.e. no longer needed for media recovery, according to criteria that you specify
in the CONFIGURE command.
There are two options to set this,
a) RECOVERY WINDOW
A recovery window is a period of time that begins with the current time and
extends backward in time to the point of recoverability. The point of recoverability
is the earliest time for a hypothetical point-in-time recovery, that is, the earliest
point to which you can recover following a media failure.
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
You can then periodically or regularly issue the REPORT OBSOLETE command to view
obsolete files and DELETE OBSOLETE to delete them. Note that RMAN does not automatically delete these files if a flash recovery area is not defined and used correctly. (10g feature). The files will be deleted when the DELETE OBSOLETE command is executed.
Delete obsolete is different than delete expired. Backups reported in DELETE OBSOLETE means this particular backup is not needed for recovery where as DELETE EXPIRED means that a particular backup is not found physically on disk / media during a CROSSCHECK.
b) REDUNDANCY
REDUNDANCY parameter specifies that any number of backups or copies beyond a
specified number need not be retained.
For example, you can specify:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RECOVERY WINDOW option is mutually exclusive with the REDUNDANCY option.
By default, the retention policy is configured to REDUNDANCY = 1 to maintain
Compatibility with the behavior of REPORT OBSOLETE in earlier RMAN releases.
If you run the following command, then RMAN returns the retention policy to the
default value:
CONFIGURE RETENTION POLICY CLEAR;
You can also run the following command to disable the retention policy altogether:
CONFIGURE RETENTION POLICY TO NONE;
If the retention policy is configured to NONE, then REPORT OBSOLETE and DELETE
OBSOLETE do not consider any backups to be obsolete.
You can use KEEP clause to exclude that particular backup from retention policy.
2) CONFIGURE BACKUP OPTIMIZATION OFF; # default
If you enable backup optimization, then the BACKUP command skips the backup of a file when the identical file has already been backed up to the allocated device type.
Criteria to Determine an Identical File:
Datafile : Same DBID, checkpoint SCN, and RESETLOGS SCN and time.
The datafile must be offline-normal, read-only, or closed normally.
Archived redo log : Same thread, sequence number, and RESETLOGS SCN and time.
Backupset : Same backup set recid and stamp.
Retention policy and duplexing policy affect this optimization algorithm.
To override backup optimization and back up all files whether or not they have changed, specify the FORCE option on the BACKUP command. To disable backup optimization, specify OFF on the CONFIGURE BACKUP OPTIMIZATION command. The CLEAR option returns backup optimization to its default value of OFF.
3) CONFIGURE DEFAULT DEVICE TYPE TO DISK;
Run the CONFIGURE DEFAULT DEVICE TYPE command to specify a default device
type for automatic channels.
For example, you may make backups to tape most of the time and only occasionally make a backup to disk. In this case, configure channels for disk and tape devices, but make the device of sbt the default device:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # configure device disk
CONFIGURE DEVICE TYPE sbt PARALLELISM 2; # configure device sbt
CONFIGURE DEFAULT DEVICE TYPE TO sbt;
RMAN will now only allocate sbt channels when you run backup commands.
RMAN knows the command that is running. For backups, only a single type of channel is allocated. For restores, RMAN knows which device types are required, allocating all necessary channels. Because RMAN has a pre-configured automatic DISK channel, you do not have to manually allocate a maintenance channel when running CHANGE ... AVAILABLE, CROSSCHECK,or DELETE against a file that is only on disk.
When a channel is automatically allocated by RMAN, its name
is in the format ORA_devicetype_n. For example, ORA_SBT_TAPE_1 or
ORA_DISK_1. Automatic channel allocation also applies to
maintenance commands: ORA_MAINT_DISK_1, ORA_SBT_TAPE_1.
When parallelizing channels, it may be necessary for each channel to be uniquely identified. A typical example of this is in a Real Application Clusters (RAC) architecture. In the RAC environment, online redo logs are archived to different nodes in a cluster and it is necessary for RMAN to connect to each node to backup the archived logs.
CONFIGURE CHANNEL 1 DEVICE TYPE sbt CONNECT 'node1' PARMS='ENV=(NSR_SERVER=bksvr1)';
Additional properties of a channel maybe specified such as NAME, PARMS,
CONNECT STRING, DEBUG, FORMAT, TRACE, MAXPIECESIZE, RATE, MAXOPENFILES,
and SEND:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE = 2M;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK MAXPIECESIZE = 900K;
To clear the any parameters configured for a particular device type:
RMAN> CONFIGURE CHANNEL DEVICE TYPE SBT CLEAR;
4) CONFIGURE CONTROLFILE AUTOBACKUP OFF;
If CONFIGURE CONTROLFILE AUTOBACKUP is ON (by default it is OFF), then RMAN automatically backs up the control file and the current server parameter file
a) After every BACKUP or COPY command issued at the RMAN prompt.
b) Whenever a BACKUP or COPY command within a RUN block is followed by a command that is neither BACKUP nor COPY.
c) At the end of every RUN block if the last command in the block was either BACKUP or COPY.
d) After database structural changes such as adding a new tablespace, altering the state of a tablespace or datafile (for example, bringing it online), adding a new online redo log, renaming a file, adding a new redo thread, and so forth.
CONFIGURE CONTROLFILE AUTOBACKUP ON;
If you are not using catalog database, it is recommended that this parameter is configured ON.
5) CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
By default, the format of the autobackup file for all configured devices is the
substitution variable %F.
This variable format translates into c-IIIIIIIIII-YYYYMMDD-QQ, where:
IIIIIIIIII stands for the DBID.
YYYYMMDD is a time stamp
QQ is the sequence in hexadecimal number that starts with 00 and has a maximum of FF (256)
You can change the default format by using the following command, where
Device Specifier is any valid device such as DISK or sbt, and 'string' contains the variable %F and is a valid handle for the specified device:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE deviceSpecifier TO 'string';
For example, you can run the following command:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '?/oradata/cf_%F';
You can return the default autobackup format to %F by running this command,
where deviceSpecifier is any valid device such as DISK or sbt:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE deviceSpecifier CLEAR;
RMAN can create control file autobackups in the flash recovery area. Use the RMAN command:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;
to clear any configured format option for the control file autobackup location on disk. Control file autobackups will be placed in the flash recovery area when no other destination is configured.
To configure the autobackup of the controlfile to the flash recovery area, you must first clear the format as documented in the 10g Backup and Recovery Advanced User's Guide:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;
Note 302153.1 Auto Control File Backup Not going to Flash Recovery Area
6) CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
The CONFIGURE DEVICE TYPE ... PARALLELISM command specifies the number of channels that RMAN uses when allocating automatic channels for a specified device type. For example, if you configure parallelism to 2, then RMAN allocates two channels of the default device type whenever it uses automatic channels.
RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
new RMAN configuration parameters are successfully stored
The following RMAN output shows that two channels are getting allocated while using backup command
RMAN> backup datafile 3;
Starting backup at 19-APR-05
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=16 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/opt/prod92/users01.dbf
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=/opt/oracle/product/ora92/dbs/0jgi8ka9_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-APR-05
7) CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
This configuration specifies the number of copies of each backup set for DATAFILE
(both datafiles and control files) or ARCHIVELOG files on the specified device type
For example, run the following to make 2 copies:
RMAN> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters:
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters are successfully stored
This is an illustration of two backup copies with the above configuration set:
RMAN> backup datafile 3;
Starting backup at 19-APR-05
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/opt/prod92/users01.dbf
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05 with 2 copies
piece handle=/opt/oracle/product/ora92/dbs/0kgi8kkf_1_1 comment=NONE
piece handle=/opt/oracle/product/ora92/dbs/0kgi8kkf_1_2 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-APR-05
8) CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
This configuration specifies the number of copies of each backup set for ARCHIVELOG
backups:
RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters are successfully stored
The following RMAN output reports the 2 backup pieces generated as a result of the configuration.
RMAN> backup archivelog all ;
Starting backup at 19-APR-05
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=167 recid=36 stamp=556028199
input archive log thread=1 sequence=168 recid=38 stamp=556031296
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05 with 2 copies
piece handle=/opt/oracle/product/ora92/dbs/0lgi8na0_1_1 comment=NONE
piece handle=/opt/oracle/product/ora92/dbs/0lgi8na0_1_2 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-APR-05
9) CONFIGURE MAXSETSIZE TO UNLIMITED;
This configuration is used to set the maximum size of a backupset created during any backup. The maximum size of a backupset must be greater than the size of the biggest file it is to backup.
If we set the maxsetsize to a small value and attempt a backup a datafile of a greater size, an error will be generated. A backup of a datafile cannot span multiple backupsets.
Example:
Set the maxsetsize to 10M and attempt a backup of a datafile size 450M.
RMAN> CONFIGURE MAXSETSIZE TO 10M;
new RMAN configuration parameters:
CONFIGURE MAXSETSIZE TO 10 M;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 1;
Starting backup at 19-APR-05
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/19/2005 19:11:15
RMAN-06183: datafile or datafilecopy larger than MAXSETSIZE: file# 1 D:\ORACLE\O
RADATA\ORCL10G\SYSTEM01.DBF
RMAN>
In the backup example below, maxsetsize is configured to 500M:
RMAN> CONFIGURE MAXSETSIZE to 500M;
old RMAN configuration parameters:
CONFIGURE MAXSETSIZE TO 100 M;
new RMAN configuration parameters:
CONFIGURE MAXSETSIZE TO 500 M;
new RMAN configuration parameters are successfully stored
RMAN> backup database;
Starting backup at 19-APR-05
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=D:\ORACLE\ORADATA\ORCL10G\SYSTEM01.DBF
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=D:\ORACLE\FLASH_RECOVERY_AREA\ORCL10G\BACKUPSET\2005_04_19\O1_MF_NN
NDF_TAG20050419T191617_16B2XC6S_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:05
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=D:\ORACLE\ORADATA\ORCL10G\SYSAUX01.DBF
input datafile fno=00005 name=D:\ORACLE\ORADATA\ORCL10G\EXAMPLE01.DBF
input datafile fno=00004 name=D:\ORACLE\ORADATA\ORCL10G\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=D:\ORACLE\FLASH_RECOVERY_AREA\ORCL10G\BACKUPSET\2005_04_19\O1_MF_NN
NDF_TAG20050419T191617_16B2ZF1Y_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:00
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00002 name=D:\ORACLE\ORADATA\ORCL10G\UNDOTBS01.DBF
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=D:\ORACLE\FLASH_RECOVERY_AREA\ORCL10G\BACKUPSET\2005_04_19\O1_MF_NN
NDF_TAG20050419T191617_16B3197R_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=D:\ORACLE\FLASH_RECOVERY_AREA\ORCL10G\BACKUPSET\2005_04_19\O1_MF_NC
SNF_TAG20050419T191617_16B31VDY_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:10
Finished backup at 19-APR-05
RMAN>
10) CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; (10g only)
Governs archived redo log deletion policy for the flash recovery area.
Possible options :
APPLIED ON STANDBY - enables flash recovery area to delete archivelogs that are applied on mandatory standby.
NONE - enables flash recovery area to delete archivelogs that are backed up to tertiary device and that are obsolete based on the configured backup retention policy. This is the default configuration.
CLEAR - clears the deletion policy and returns the specified configuration to default value. The default value is NONE.
By default, archived redo log files in a flash recovery area that were backed up to a
tertiary device or made obsolete (as defined by the RMAN retention policy) are eligible for deletion.
However, you can change this default deletion policy using the following RMAN command:
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
Examples of the CONFIGURE ARCHIVELOG DELETION POLICY Command
When backups of archived redo log files are taken on the standby database:
1. Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
2. Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
When backups of archived redo log files are taken on the primary database:
1. Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
2. Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
Reconfiguring the Deletion Policy After a Role Transition :
After a switchover or failover, you may need to reissue the RMAN CONFIGURE
ARCHIVELOG DELETION POLICY command on each database.
If the backup site for archived redo log files remains the same, then do nothing.
Otherwise, you must switch the archivelog deletion policy by issuing the
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY statement on the database where backups are not taken, and issuing the CONFIGURE ARCHIVELOG DELETION POLICY TO NONE statement on the database where backups are taken.
Viewing the Current Deletion Policy
To view the current setting (APPLIED ON STANDBY, CLEAR, NONE) for a database,
issue the following query:
SELECT NAME, VALUE FROM V$RMAN_CONFIGURATION WHERE
NAME LIKE '%ARCHIVELOG DELETION POLICY%';
NAME VALUE
----------------------------- --------------
ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
You can also find the existing configuration using the RMAN SHOW ARCHIVELOG
DELETION POLICY command:
RMAN> SHOW ARCHIVELOG DELETION POLICY
RMAN configuration parameters are:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
11) CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/ora10g/dbs/snapcf_db10g.f';
When RMAN needs to resynchronize from a read-consistent version of the control file, it creates a temporary snapshot control file. RMAN needs a snapshot control file only when resynchronizing with the recovery catalog or when making a backup of the current control file.
This configuration specifies where the snapshot controlfile is created.
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\SNAPORA.CTL';
snapshot controlfile name set to: D:\ORACLE\SNAPORA.CTL
new RMAN configuration parameters are successfully stored
12) You can backup a 10g target using a 9i RMAN client, but there are some restrictions
when changing controlfile persistent configuration parameters.
If you change parameters as
CONFIGURE DEVICE TYPE DISK PARALLELISM 2; using a 10g RMAN client and then
connect using a 9i RMAN client:
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: DB10G (DBID=4244657420)
RMAN> show all;
using target database controlfile instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 06/03/2005 20:22:25
RMAN-12010: automatic channel allocation initialization failed
RMAN-06466: error parsing configuration string (CONFIGURE DEVICE TYPE DISK PARAL
LELISM 2 BACKUP TYPE TO BACKUPSET;)
RMAN-01005: syntax error: found "backup": expecting one of: ";"
RMAN-01007: at line 1 column 42 file: Configuration Row
Note 307022.1 RMAN Compatibility Oracle8i 8.1.7.4 - Oracle10g 10.1.0.4
provides the explanation and solution to use the 10g RMAN client and clear:
CONFIGURE DEVICE TYPE disk clear;
13) EXCLUDE FOR TABLESPACE excludes the specified tablespace from BACKUP DATABASE commands. Note that you cannot exclude the SYSTEM tablespace. By default, each tablespace is not excluded, that is, the exclude functionality is disabled. The exclusion is stored as an attribute of the tablespace, not the individual datafiles, so the exclusion applies to any files that are added to this tablespace in the future. If you run CONFIGURE ... CLEAR on a tablespace after excluding it, then it returns to the default configuration of "not excluded."
CONFIGURE EXCLUDE FOR TABLESPACE USERS;
RMAN> REPORT SCHEMA;
Report of database schema
File K-bytes Tablespace RB segs Datafile Name
---- ---------- -------------------- ------- -------------------
1 204800 SYSTEM *** /opt/oracle/oradata/stby92/system01.dbf
2 20480 UNDOTBS1 *** /opt/oracle/oradata/stby92/undo01.dbf
3 10240 USERS *** /opt/oracle/oradata/stby92/users01.
RMAN> SHOW EXCLUDE;
RMAN configuration parameters are:
CONFIGURE EXCLUDE FOR TABLESPACE 'USERS';
RMAN> backup database;
Starting backup at 07-JUN-05
using channel ORA_DISK_1
file 3 is excluded from whole database backup <=========> Excluded.
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00001 name=/opt/oracle/oradata/stby92/system01.dbf
input datafile fno=00002 name=/opt/oracle/oradata/stby92/undo01.dbf
channel ORA_DISK_1: starting piece 1 at 07-JUN-05
channel ORA_DISK_1: finished piece 1 at 07-JUN-05
piece handle=/opt/oracle/product/920/dbs/02gmdami_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
Finished backup at 07-JUN-05
Query V$TABLESPACE via SQL*Plus:
SQL> select name,INCLUDED_IN_DATABASE_BACKUP from v$tablespace;
NAME INC
------------------------------ ---
SYSTEM YES
UNDOTBS1 YES
USERS NO
TEMP YES
The SHOW command returns the values of various parameters.
SHOW ALL
The SHOW ALL command shows the value of all configuration parameters.
The default values are as follows:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_TEST.f'; # default
The default value for SNAPSHOT CONTROLFILE NAME is $ORACLE_HOME/snapcf_.f
Following statement can be used to see non-default configurations
SELECT NAME, VALUE FROM V$RMAN_CONFIGURATION ;
1) CONFIGURE RETENTION POLICY TO REDUNDANCY 1; (default)
RMAN considers backups and copies of datafiles and control files as obsolete,
i.e. no longer needed for media recovery, according to criteria that you specify
in the CONFIGURE command.
There are two options to set this,
a) RECOVERY WINDOW
A recovery window is a period of time that begins with the current time and
extends backward in time to the point of recoverability. The point of recoverability
is the earliest time for a hypothetical point-in-time recovery, that is, the earliest
point to which you can recover following a media failure.
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
You can then periodically or regularly issue the REPORT OBSOLETE command to view
obsolete files and DELETE OBSOLETE to delete them. Note that RMAN does not automatically delete these files if a flash recovery area is not defined and used correctly. (10g feature). The files will be deleted when the DELETE OBSOLETE command is executed.
Delete obsolete is different than delete expired. Backups reported in DELETE OBSOLETE means this particular backup is not needed for recovery where as DELETE EXPIRED means that a particular backup is not found physically on disk / media during a CROSSCHECK.
b) REDUNDANCY
REDUNDANCY parameter specifies that any number of backups or copies beyond a
specified number need not be retained.
For example, you can specify:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
RECOVERY WINDOW option is mutually exclusive with the REDUNDANCY option.
By default, the retention policy is configured to REDUNDANCY = 1 to maintain
Compatibility with the behavior of REPORT OBSOLETE in earlier RMAN releases.
If you run the following command, then RMAN returns the retention policy to the
default value:
CONFIGURE RETENTION POLICY CLEAR;
You can also run the following command to disable the retention policy altogether:
CONFIGURE RETENTION POLICY TO NONE;
If the retention policy is configured to NONE, then REPORT OBSOLETE and DELETE
OBSOLETE do not consider any backups to be obsolete.
You can use KEEP clause to exclude that particular backup from retention policy.
2) CONFIGURE BACKUP OPTIMIZATION OFF; # default
If you enable backup optimization, then the BACKUP command skips the backup of a file when the identical file has already been backed up to the allocated device type.
Criteria to Determine an Identical File:
Datafile : Same DBID, checkpoint SCN, and RESETLOGS SCN and time.
The datafile must be offline-normal, read-only, or closed normally.
Archived redo log : Same thread, sequence number, and RESETLOGS SCN and time.
Backupset : Same backup set recid and stamp.
Retention policy and duplexing policy affect this optimization algorithm.
To override backup optimization and back up all files whether or not they have changed, specify the FORCE option on the BACKUP command. To disable backup optimization, specify OFF on the CONFIGURE BACKUP OPTIMIZATION command. The CLEAR option returns backup optimization to its default value of OFF.
3) CONFIGURE DEFAULT DEVICE TYPE TO DISK;
Run the CONFIGURE DEFAULT DEVICE TYPE command to specify a default device
type for automatic channels.
For example, you may make backups to tape most of the time and only occasionally make a backup to disk. In this case, configure channels for disk and tape devices, but make the device of sbt the default device:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # configure device disk
CONFIGURE DEVICE TYPE sbt PARALLELISM 2; # configure device sbt
CONFIGURE DEFAULT DEVICE TYPE TO sbt;
RMAN will now only allocate sbt channels when you run backup commands.
RMAN knows the command that is running. For backups, only a single type of channel is allocated. For restores, RMAN knows which device types are required, allocating all necessary channels. Because RMAN has a pre-configured automatic DISK channel, you do not have to manually allocate a maintenance channel when running CHANGE ... AVAILABLE, CROSSCHECK,or DELETE against a file that is only on disk.
When a channel is automatically allocated by RMAN, its name
is in the format ORA_devicetype_n. For example, ORA_SBT_TAPE_1 or
ORA_DISK_1. Automatic channel allocation also applies to
maintenance commands: ORA_MAINT_DISK_1, ORA_SBT_TAPE_1.
When parallelizing channels, it may be necessary for each channel to be uniquely identified. A typical example of this is in a Real Application Clusters (RAC) architecture. In the RAC environment, online redo logs are archived to different nodes in a cluster and it is necessary for RMAN to connect to each node to backup the archived logs.
CONFIGURE CHANNEL 1 DEVICE TYPE sbt CONNECT 'node1' PARMS='ENV=(NSR_SERVER=bksvr1)';
Additional properties of a channel maybe specified such as NAME, PARMS,
CONNECT STRING, DEBUG, FORMAT, TRACE, MAXPIECESIZE, RATE, MAXOPENFILES,
and SEND:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE = 2M;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK MAXPIECESIZE = 900K;
To clear the any parameters configured for a particular device type:
RMAN> CONFIGURE CHANNEL DEVICE TYPE SBT CLEAR;
4) CONFIGURE CONTROLFILE AUTOBACKUP OFF;
If CONFIGURE CONTROLFILE AUTOBACKUP is ON (by default it is OFF), then RMAN automatically backs up the control file and the current server parameter file
a) After every BACKUP or COPY command issued at the RMAN prompt.
b) Whenever a BACKUP or COPY command within a RUN block is followed by a command that is neither BACKUP nor COPY.
c) At the end of every RUN block if the last command in the block was either BACKUP or COPY.
d) After database structural changes such as adding a new tablespace, altering the state of a tablespace or datafile (for example, bringing it online), adding a new online redo log, renaming a file, adding a new redo thread, and so forth.
CONFIGURE CONTROLFILE AUTOBACKUP ON;
If you are not using catalog database, it is recommended that this parameter is configured ON.
5) CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
By default, the format of the autobackup file for all configured devices is the
substitution variable %F.
This variable format translates into c-IIIIIIIIII-YYYYMMDD-QQ, where:
IIIIIIIIII stands for the DBID.
YYYYMMDD is a time stamp
QQ is the sequence in hexadecimal number that starts with 00 and has a maximum of FF (256)
You can change the default format by using the following command, where
Device Specifier is any valid device such as DISK or sbt, and 'string' contains the variable %F and is a valid handle for the specified device:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE deviceSpecifier TO 'string';
For example, you can run the following command:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '?/oradata/cf_%F';
You can return the default autobackup format to %F by running this command,
where deviceSpecifier is any valid device such as DISK or sbt:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE deviceSpecifier CLEAR;
RMAN can create control file autobackups in the flash recovery area. Use the RMAN command:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;
to clear any configured format option for the control file autobackup location on disk. Control file autobackups will be placed in the flash recovery area when no other destination is configured.
To configure the autobackup of the controlfile to the flash recovery area, you must first clear the format as documented in the 10g Backup and Recovery Advanced User's Guide:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;
Note 302153.1 Auto Control File Backup Not going to Flash Recovery Area
6) CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
The CONFIGURE DEVICE TYPE ... PARALLELISM command specifies the number of channels that RMAN uses when allocating automatic channels for a specified device type. For example, if you configure parallelism to 2, then RMAN allocates two channels of the default device type whenever it uses automatic channels.
RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
new RMAN configuration parameters:
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
new RMAN configuration parameters are successfully stored
The following RMAN output shows that two channels are getting allocated while using backup command
RMAN> backup datafile 3;
Starting backup at 19-APR-05
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=16 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/opt/prod92/users01.dbf
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=/opt/oracle/product/ora92/dbs/0jgi8ka9_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-APR-05
7) CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
This configuration specifies the number of copies of each backup set for DATAFILE
(both datafiles and control files) or ARCHIVELOG files on the specified device type
For example, run the following to make 2 copies:
RMAN> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters:
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters are successfully stored
This is an illustration of two backup copies with the above configuration set:
RMAN> backup datafile 3;
Starting backup at 19-APR-05
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=/opt/prod92/users01.dbf
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05 with 2 copies
piece handle=/opt/oracle/product/ora92/dbs/0kgi8kkf_1_1 comment=NONE
piece handle=/opt/oracle/product/ora92/dbs/0kgi8kkf_1_2 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-APR-05
8) CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
This configuration specifies the number of copies of each backup set for ARCHIVELOG
backups:
RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
new RMAN configuration parameters are successfully stored
The following RMAN output reports the 2 backup pieces generated as a result of the configuration.
RMAN> backup archivelog all ;
Starting backup at 19-APR-05
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=167 recid=36 stamp=556028199
input archive log thread=1 sequence=168 recid=38 stamp=556031296
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05 with 2 copies
piece handle=/opt/oracle/product/ora92/dbs/0lgi8na0_1_1 comment=NONE
piece handle=/opt/oracle/product/ora92/dbs/0lgi8na0_1_2 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 19-APR-05
9) CONFIGURE MAXSETSIZE TO UNLIMITED;
This configuration is used to set the maximum size of a backupset created during any backup. The maximum size of a backupset must be greater than the size of the biggest file it is to backup.
If we set the maxsetsize to a small value and attempt a backup a datafile of a greater size, an error will be generated. A backup of a datafile cannot span multiple backupsets.
Example:
Set the maxsetsize to 10M and attempt a backup of a datafile size 450M.
RMAN> CONFIGURE MAXSETSIZE TO 10M;
new RMAN configuration parameters:
CONFIGURE MAXSETSIZE TO 10 M;
new RMAN configuration parameters are successfully stored
RMAN> backup datafile 1;
Starting backup at 19-APR-05
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/19/2005 19:11:15
RMAN-06183: datafile or datafilecopy larger than MAXSETSIZE: file# 1 D:\ORACLE\O
RADATA\ORCL10G\SYSTEM01.DBF
RMAN>
In the backup example below, maxsetsize is configured to 500M:
RMAN> CONFIGURE MAXSETSIZE to 500M;
old RMAN configuration parameters:
CONFIGURE MAXSETSIZE TO 100 M;
new RMAN configuration parameters:
CONFIGURE MAXSETSIZE TO 500 M;
new RMAN configuration parameters are successfully stored
RMAN> backup database;
Starting backup at 19-APR-05
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=D:\ORACLE\ORADATA\ORCL10G\SYSTEM01.DBF
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=D:\ORACLE\FLASH_RECOVERY_AREA\ORCL10G\BACKUPSET\2005_04_19\O1_MF_NN
NDF_TAG20050419T191617_16B2XC6S_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:05
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00003 name=D:\ORACLE\ORADATA\ORCL10G\SYSAUX01.DBF
input datafile fno=00005 name=D:\ORACLE\ORADATA\ORCL10G\EXAMPLE01.DBF
input datafile fno=00004 name=D:\ORACLE\ORADATA\ORCL10G\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=D:\ORACLE\FLASH_RECOVERY_AREA\ORCL10G\BACKUPSET\2005_04_19\O1_MF_NN
NDF_TAG20050419T191617_16B2ZF1Y_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:00
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00002 name=D:\ORACLE\ORADATA\ORCL10G\UNDOTBS01.DBF
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=D:\ORACLE\FLASH_RECOVERY_AREA\ORCL10G\BACKUPSET\2005_04_19\O1_MF_NN
NDF_TAG20050419T191617_16B3197R_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 19-APR-05
channel ORA_DISK_1: finished piece 1 at 19-APR-05
piece handle=D:\ORACLE\FLASH_RECOVERY_AREA\ORCL10G\BACKUPSET\2005_04_19\O1_MF_NC
SNF_TAG20050419T191617_16B31VDY_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:10
Finished backup at 19-APR-05
RMAN>
10) CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; (10g only)
Governs archived redo log deletion policy for the flash recovery area.
Possible options :
APPLIED ON STANDBY - enables flash recovery area to delete archivelogs that are applied on mandatory standby.
NONE - enables flash recovery area to delete archivelogs that are backed up to tertiary device and that are obsolete based on the configured backup retention policy. This is the default configuration.
CLEAR - clears the deletion policy and returns the specified configuration to default value. The default value is NONE.
By default, archived redo log files in a flash recovery area that were backed up to a
tertiary device or made obsolete (as defined by the RMAN retention policy) are eligible for deletion.
However, you can change this default deletion policy using the following RMAN command:
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
Examples of the CONFIGURE ARCHIVELOG DELETION POLICY Command
When backups of archived redo log files are taken on the standby database:
1. Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
2. Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
When backups of archived redo log files are taken on the primary database:
1. Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
2. Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
Reconfiguring the Deletion Policy After a Role Transition :
After a switchover or failover, you may need to reissue the RMAN CONFIGURE
ARCHIVELOG DELETION POLICY command on each database.
If the backup site for archived redo log files remains the same, then do nothing.
Otherwise, you must switch the archivelog deletion policy by issuing the
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY statement on the database where backups are not taken, and issuing the CONFIGURE ARCHIVELOG DELETION POLICY TO NONE statement on the database where backups are taken.
Viewing the Current Deletion Policy
To view the current setting (APPLIED ON STANDBY, CLEAR, NONE) for a database,
issue the following query:
SELECT NAME, VALUE FROM V$RMAN_CONFIGURATION WHERE
NAME LIKE '%ARCHIVELOG DELETION POLICY%';
NAME VALUE
----------------------------- --------------
ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
You can also find the existing configuration using the RMAN SHOW ARCHIVELOG
DELETION POLICY command:
RMAN> SHOW ARCHIVELOG DELETION POLICY
RMAN configuration parameters are:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
11) CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/ora10g/dbs/snapcf_db10g.f';
When RMAN needs to resynchronize from a read-consistent version of the control file, it creates a temporary snapshot control file. RMAN needs a snapshot control file only when resynchronizing with the recovery catalog or when making a backup of the current control file.
This configuration specifies where the snapshot controlfile is created.
RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\SNAPORA.CTL';
snapshot controlfile name set to: D:\ORACLE\SNAPORA.CTL
new RMAN configuration parameters are successfully stored
12) You can backup a 10g target using a 9i RMAN client, but there are some restrictions
when changing controlfile persistent configuration parameters.
If you change parameters as
CONFIGURE DEVICE TYPE DISK PARALLELISM 2; using a 10g RMAN client and then
connect using a 9i RMAN client:
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: DB10G (DBID=4244657420)
RMAN> show all;
using target database controlfile instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 06/03/2005 20:22:25
RMAN-12010: automatic channel allocation initialization failed
RMAN-06466: error parsing configuration string (CONFIGURE DEVICE TYPE DISK PARAL
LELISM 2 BACKUP TYPE TO BACKUPSET;)
RMAN-01005: syntax error: found "backup": expecting one of: ";"
RMAN-01007: at line 1 column 42 file: Configuration Row
Note 307022.1 RMAN Compatibility Oracle8i 8.1.7.4 - Oracle10g 10.1.0.4
provides the explanation and solution to use the 10g RMAN client and clear:
CONFIGURE DEVICE TYPE disk clear;
13) EXCLUDE FOR TABLESPACE excludes the specified tablespace from BACKUP DATABASE commands. Note that you cannot exclude the SYSTEM tablespace. By default, each tablespace is not excluded, that is, the exclude functionality is disabled. The exclusion is stored as an attribute of the tablespace, not the individual datafiles, so the exclusion applies to any files that are added to this tablespace in the future. If you run CONFIGURE ... CLEAR on a tablespace after excluding it, then it returns to the default configuration of "not excluded."
CONFIGURE EXCLUDE FOR TABLESPACE USERS;
RMAN> REPORT SCHEMA;
Report of database schema
File K-bytes Tablespace RB segs Datafile Name
---- ---------- -------------------- ------- -------------------
1 204800 SYSTEM *** /opt/oracle/oradata/stby92/system01.dbf
2 20480 UNDOTBS1 *** /opt/oracle/oradata/stby92/undo01.dbf
3 10240 USERS *** /opt/oracle/oradata/stby92/users01.
RMAN> SHOW EXCLUDE;
RMAN configuration parameters are:
CONFIGURE EXCLUDE FOR TABLESPACE 'USERS';
RMAN> backup database;
Starting backup at 07-JUN-05
using channel ORA_DISK_1
file 3 is excluded from whole database backup <=========> Excluded.
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
input datafile fno=00001 name=/opt/oracle/oradata/stby92/system01.dbf
input datafile fno=00002 name=/opt/oracle/oradata/stby92/undo01.dbf
channel ORA_DISK_1: starting piece 1 at 07-JUN-05
channel ORA_DISK_1: finished piece 1 at 07-JUN-05
piece handle=/opt/oracle/product/920/dbs/02gmdami_1_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
Finished backup at 07-JUN-05
Query V$TABLESPACE via SQL*Plus:
SQL> select name,INCLUDED_IN_DATABASE_BACKUP from v$tablespace;
NAME INC
------------------------------ ---
SYSTEM YES
UNDOTBS1 YES
USERS NO
TEMP YES
No comments:
Post a Comment