1. Full backup database, and the Backup Type is specified as backupset
RMAN> backup as backupset database;
Starting backup at 13-FEB-14
Using channel ORA_DISK_1
.....
2. Back up the users tablespace again and specify the Backup Type as backupset.
RMAN> backup as backupset device type disk tablespace users;
Starting backup at 13-FEB-14
Using channel ORA_DISK_1
Channel ORA_DISK_1: starting full datafile backup set
Channel ORA_DISK_1: specifying datafile (s) in backup set
Input datafile file number = 00004 name =/home/Oracle/app/oradata/ora11g/users01.dbf
Channel ORA_DISK_1: starting piece 1 at 13-FEB-14
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/13/2014 14:01:16
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
3. Analyze the above error, exceeding the file recovery limit
SQL> show parameter db_recovery
NAME TYPE VALUE
-----------------------------------------------------------------------------
Db_recovery_file_dest string/home/oracle/app/flash_recover
Y_area
Db_recovery_file_dest_size big integer 2G
Check the upper limit of recovery files. The current value is 2 GB.
4. Check how much space is currently used for restoration.
Oracle @ linux :~ /App/flash_recovery_area> du-sm *
2010 ORA11G
The maximum size of the backup file is 2 GB. Therefore, the failure may be due to the fact that the size of the target backup file exceeds 2048-MB.
5. Re-specify the retention policy to prevent the archivelog from increasing
RMAN> configure retention policy to recovery window of 7 days;
Old RMAN configuration parameters:
Configure retention policy to recovery window of 7 DAYS;
New RMAN configuration parameters:
Configure retention policy to recovery window of 7 DAYS;
New RMAN configuration parameters are successfully stored
RMAN> configure retention policy to redundancy 3;
Old RMAN configuration parameters:
Configure retention policy to recovery window of 7 DAYS;
New RMAN configuration parameters:
Configure retention policy to redundancy 3;
New RMAN configuration parameters are successfully stored
6. Modify the size of db_recovery_file_dest_size.
SQL> alter system set db_recovery_file_dest_size = 4g scope = both;
System altered.
7. Back up the users tablespace again
RMAN> backup as backupset device type disk tablespace users;
Starting backup at 13-FEB-14
Using channel ORA_DISK_1
Channel ORA_DISK_1: starting full datafile backup set
Channel ORA_DISK_1: specifying datafile (s) in backup set
Input datafile file number = 00004 name =/home/oracle/app/oradata/ora11g/users01.dbf
Channel ORA_DISK_1: starting piece 1 at 13-FEB-14
......
Recommended reading:
RMAN: Configure an archive log deletion policy
Basic Oracle tutorial-copying a database through RMAN
Reference for RMAN backup policy formulation
RMAN backup learning notes
Oracle Database Backup encryption RMAN Encryption