主页 / dba / 问题 / 133890
Accepted
SQL Hammer
Asked: 2016-03-31 16:40:58 +0800 CST

帮助解释 Oracle RMAN 结果

  • 772

我对 Oracle 非常陌生，不得不在 NOARCHIVELOG 模式下的 11g 数据库上进行备份。下面是输出。它声称备份失败，但我有一个适当大小的文件，我希望在其中创建备份。

有人可以帮我解释这个日志吗？

Recovery Manager: Release 11.2.0.3.0 - Production on Wed Mar 30 20:30:27 2016

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

 connected to target database: HS (DBID=3540555849)


RMAN> RUN {

2> 

3> CONFIGURE COMPRESSION ALGORITHM 'HIGH';

4> 

5> show all;

6> 

7> shutdown immediate;

8> 

9> startup mount;

10> 

11> backup database;

12> 

13> alter database open;

14> 

15> }

16> 

17> LIST BACKUP SUMMARY ;

18> 

19> EXIT 

using target database control file instead of recovery catalog

new RMAN configuration parameters:

CONFIGURE COMPRESSION ALGORITHM 'HIGH' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;

new RMAN configuration parameters are successfully stored


RMAN configuration parameters for database with db_unique_name HS are:

CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'HIGH' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\APP\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFHS.ORA'; # default
database closed
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area    4275781632 bytes
Fixed Size                     2262048 bytes
Variable Size               2818575328 bytes
Database Buffers            1442840576 bytes
Redo Buffers                  12103680 bytes
Starting backup at 30-MAR-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=395 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00005 name=D:\APP\ORACLE\ORADATA\HS\HS_F0_SVMC.CID
input datafile file number=00003 name=D:\APP\ORACLE\ORADATA\HS\UNDOTBS01.DBF
input datafile file number=00006 name=D:\APP\ORACLE\ORADATA\HS\AUDIT_DATA.DBF
input datafile file number=00002 name=D:\APP\ORACLE\ORADATA\HS\SYSAUX01.DBF
input datafile file number=00001 name=D:\APP\ORACLE\ORADATA\HS\SYSTEM01.DBF
input datafile file number=00007 name=D:\APP\ORACLE\ORADATA\HS\AUDIT_IDX.DBF
input datafile file number=00004 name=D:\APP\ORACLE\ORADATA\HS\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 30-MAR-16
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/30/2016 20:32:43
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 67108864 bytes disk space from 4322230272 limit
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
including current SPFILE in backup set
channel ORA_DISK_1: starting piece 1 at 30-MAR-16
channel ORA_DISK_1: finished piece 1 at 30-MAR-16
piece handle=D:\APP\ORACLE\FAST_RECOVERY_AREA\HS\BACKUPSET\2016_03_30\O1_MF_NCSNF_TAG20160330T203107_CHRW1F69_.BKP tag=TAG20160330T203107 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================



RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/30/2016 20:32:43

ORA-19809: limit exceeded for recovery files

ORA-19804: cannot reclaim 67108864 bytes disk space from 4322230272 limit



Recovery Manager complete.
oracle backup

1 个回答

  1. Best Answer

    让我们看看 Oracle 提供的oerr实用程序是如何描述您的错误的。

    [oracle@testsrv Desktop]$ oerr ora 19804

    ORA-19804 无法从 %s 限制回收 %s 字节磁盘空间

    原因： Oracle 无法从 DB_RECOVERY_FILE_DEST_SIZE 限制中回收指定字节的磁盘空间。

    操作：有五种可能的解决方案：
    1) 使用 RMAN 经常备份恢复区。
    2) 考虑更改 RMAN 保留策略。
    3) 考虑更改 RMAN 归档日志删除策略。
    4) 增加磁盘空间，增加DB_RECOVERY_FILE_DEST_SIZE。
    5) 使用 RMAN 从恢复区中删除文件。

    ORA-19809 超过恢复文件的限制

    原因：超出了 DB_RECOVERY_FILE_DEST_SIZE 指定的恢复文件限制。

    操作：有五种可能的解决方案：
    1) 使用 RMAN 经常备份恢复区。
    2) 考虑更改 RMAN 保留策略。
    3) 考虑更改 RMAN 归档日志删除策略。
    4) 增加磁盘空间，增加DB_RECOVERY_FILE_DEST_SIZE。
    5) 使用 RMAN 从恢复区中删除文件。

    将 RMAN 通道的大小增加db_recovery_file_dest_size或指定格式到不同的位置。

    例子

    SQL> conn / 作为 sysdba
SQL> alter system set db_recovery_file_dest_size=30G;

    您应该注意定义为快速恢复区的磁盘的实际磁盘空间大小。如果您想将您的备份存储在闪回恢复区以外的其他位置，那么您可以如下所示分配频道。

    跑
{
  分配通道磁盘 1 设备类型磁盘格式 'E:\%U';
  备份数据库加上归档日志；
}
    • 2

相关问题