RMAN进行备份恢复


RMAN进行备份恢复
 
--RMAN备份是完全联机热备份
RMAN> connect target sys/lubinsu@orcl
 
connected to target database: ORCL (DBID=1326384392)
 
RMAN> backup database;
 
Starting backup at 12-JUN-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=148 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00004 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/users01.dbf
input datafile fno=00001 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/system01.dbf
input datafile fno=00007 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/tbs_data.dbf
input datafile fno=00002 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/undotbs01.dbf
input datafile fno=00003 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/sysaux01.dbf
input datafile fno=00005 name=/home/oracle/oracle/product/10.2.0/db_1/dbs/TBS_ORCL_DATA01.DBF
input datafile fno=00006 name=/home/oracle/oracle/product/10.2.0/db_1/dbs/TBS_ORCL_IDX01.DBF
channel ORA_DISK_1: starting piece 1 at 12-JUN-13
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/12/2013 12:11:36
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 12-JUN-13
channel ORA_DISK_1: finished piece 1 at 12-JUN-13
piece handle=/home/oracle/oracle/product/10.2.0/flash_recovery_area/ORCL/backupset/2013_06_12/o1_mf_ncsnf_TAG20130612T120900_8vhx7tnw_.bkp tag=TAG20130612T120900 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
 
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/12/2013 12:11:36
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 LIMIT
 
--这里提示空间不足了，我们来查看下详细的跟踪日志：
 
[lubinsu@localhost ~]$ cat /home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orclsid_ora_5086.trc
/home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orclsid_ora_5086.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /home/oracle/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      localhost.localdomain
Release:        2.6.18-8.el5
Version:        #1 SMP Fri Jan 26 14:15:21 EST 2007
Machine:        i686
Instance name: orclsid
Redo thread mounted by this instance: 0 <none>
Oracle process number: 15
Unix process pid: 5086, image: oracle@localhost.localdomain (TNS V1-V3)
 
*** SERVICE NAME:() 2013-05-25 09:58:17.633
*** SESSION ID:(159.1) 2013-05-25 09:58:17.633
kccsga_update_ckpt: num_1 = 8, num_2 = 0, num_3 = 0, lbn_2 = 0, lbn_3 = 0
/home/oracle/oracle/product/10.2.0/db_1/admin/orcl/udump/orclsid_ora_5086.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /home/oracle/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      localhost.localdomain
Release:        2.6.18-8.el5
Version:        #1 SMP Fri Jan 26 14:15:21 EST 2007
Machine:        i686
Instance name: orclsid
Redo thread mounted by this instance: 1
Oracle process number: 23
Unix process pid: 5086, image: oracleorclsid@localhost.localdomain
 
*** 2013-06-12 12:10:18.861
*** ACTION NAME:(0000022 STARTED16) 2013-06-12 12:10:18.826
*** MODULE NAME:(backup full datafile) 2013-06-12 12:10:18.826
*** SERVICE NAME:(orcl) 2013-06-12 12:10:18.826
*** SESSION ID:(148.13) 2013-06-12 12:10:18.826
ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 86.98% used, and has 279703040 remaining bytes available.
*** 2013-06-12 12:10:18.862
************************************************************************
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************
*** 2013-06-12 12:11:15.771
ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 99.18% used, and has 17559040 remaining bytes available.
*** 2013-06-12 12:11:15.771
************************************************************************
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************
*** 2013-06-12 12:11:27.166
ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 100.00% used, and has 0 remaining bytes available.
*** 2013-06-12 12:11:27.166
************************************************************************
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
&