ORA-19809: limit exceeded for recovery files

Got an error when do the backup.

$ rman target /

Recovery Manager: Release 11.2.0.2.0 - Production on Wed Mar 2 02:12:32 2011

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

connected to target database: LAB10G (DBID=1038266291)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name LAB10G 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 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/orahome/oracle/product/11.2.0/dbhome_01/dbs/snapcf_LAB10G.f'; # default

RMAN> backup database;

Starting backup at 02-MAR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=644 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=00003 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/sysaux01.dbf
input datafile file number=00001 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/system01.dbf
input datafile file number=00010 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/transport01.dbf
input datafile file number=00021 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/migrate_data01.dbf
input datafile file number=00002 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/undotbs01.dbf
input datafile file number=00011 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/svc_mgmt01.dbf
input datafile file number=00004 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/users01.dbf
input datafile file number=00005 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/cmdb01.dbf
input datafile file number=00015 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/nsp01.dbf
input datafile file number=00006 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/mon_mgmt01.dbf
input datafile file number=00012 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/svc_mgmt_idx01.dbf
input datafile file number=00013 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/acct_mgmt01.dbf
input datafile file number=00019 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/knowledge_mgmt01.dbf
input datafile file number=00022 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/am_common_data01.dbf
input datafile file number=00024 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/am_itsp_data01.dbf
input datafile file number=00026 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/am_data01.dbf
input datafile file number=00028 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/attach_svc_data01.dbf
input datafile file number=00007 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/streams_tbs01.dbf
input datafile file number=00008 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/cmdb_idx01.dbf
input datafile file number=00009 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/mon_mgmt_idx01.dbf
input datafile file number=00014 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/acct_mgmt_idx01.dbf
input datafile file number=00016 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/nsp_idx01.dbf
input datafile file number=00020 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/knowledge_mgmt_idx01.dbf
input datafile file number=00023 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/am_common_idx01.dbf
input datafile file number=00025 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/am_itsp_idx01.dbf
input datafile file number=00027 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/am_idx01.dbf
input datafile file number=00029 name=/opt/app/oracle/oracle/product/10.2.0/db_1/oradata/LAB10G/attach_svc_idx01.dbf
channel ORA_DISK_1: starting piece 1 at 02-MAR-11
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/02/2011 02:15:04
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 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 02-MAR-11
channel ORA_DISK_1: finished piece 1 at 02-MAR-11
piece handle=/orahome/oracle/admin/LAB10G/flash_recovery_area/LAB10G/backupset/2011_03_02/o1_mf_ncsnf_TAG20110302T021317_6pw2ol1r_.bkp tag=TAG20110302T021317 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/02/2011 02:15:04
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
$ sqlplus /

SQL*Plus: Release 11.2.0.2.0 Production on Wed Mar 2 02:16:57 2011

Copyright (c) 1982, 2010, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning option

SQL> show parameter recovery

NAME                                 TYPE
------------------------------------ ---------------------------------
VALUE
------------------------------
db_recovery_file_dest                string
/orahome/oracle/admin/LAB10G/f
lash_recovery_area
db_recovery_file_dest_size           big integer
2G
recovery_parallelism                 integer
0
SQL> alter system set db_recovery_file_dest_size=30G
  2  ;

System altered.

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning option
$ rman target /

Recovery Manager: Release 11.2.0.2.0 - Production on Wed Mar 2 02:17:26 2011

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

connected to target database: LAB10G (DBID=1038266291)

Do the backup again.

Just becasue backup files to fast recovery area.

<think>嗯,用户遇到了Oracle数据库的权限问题,具体是ORA-01031权限不足,还有涉及DBMS_SNAPSHOT和SYS包的调用错误。首先,我需要回想一下ORA-01031错误的常见原因。这个错误通常是因为用户没有执行特定操作所需的权限。比如,如果用户尝试访问某个表或执行某个存储过程,但没有相应的权限,就会报这个错误。所以,解决这个问题的第一步应该是检查用户的权限是否足够。 接下来,用户提到DBMS_SNAPSHOT_UTL包的问题,可能是在创建或管理物化视图日志时遇到的。这个包属于SYS用户,普通用户可能需要显式授权才能使用。我记得SYS的包默认只有DBA权限的用户才能访问,所以需要确认用户是否有EXECUTE权限。另外,引用1和2中提到的问题可能与Oracle版本有关,特别是11g的bug可能导致某些存储过程出错。这时候可能需要应用补丁或者升级数据库。 然后,用户还提到ORA-01555和ORA-12034错误。ORA-01555通常与UNDO表空间不足或查询时间过长有关,需要调整UNDO表空间的大小或优化查询。ORA-12034则涉及物化视图日志的问题,可能需要重新创建日志或调整刷新策略。 接下来,我需要考虑如何逐步指导用户解决这些问题。首先检查权限,授予必要的系统权限和对象权限。比如,如果用户需要创建物化视图,可能需要GRANT CREATE MATERIALIZED VIEW。然后检查SYS包的权限,比如DBMS_SNAPSHOT_UTL,可能需要用SYSDBA用户授予EXECUTE权限。 如果权限没有问题,可能需要考虑数据库版本的问题。引用2提到Oracle 11g的bug,如果在10g上没问题,可能需要查看是否触发了已知的bug,并检查是否有可用的补丁。此外,ORA-01555的问题需要调整UNDO表空间,增加大小或保留时间,避免长事务导致的错误。 最后,关于物化视图日志的问题,如ORA-12034,可能需要检查日志是否损坏,必要时重建,并确保刷新操作在合理的时间窗口内完成,避免数据不一致。 用户可能需要具体的步骤示例,比如如何授予权限,如何检查UNDO配置,如何重建物化视图日志等。同时,需要提醒用户谨慎操作SYS对象,最好在测试环境验证后再应用到生产环境。如果有必要,联系Oracle支持处理潜在的bug。</think>### 分步解决方案 #### **1. 解决 ORA-01031 权限不足问题** **步骤 1:确认操作所需的权限** - 若涉及创建/修改对象(如表、物化视图),需检查用户是否具备以下权限: ```sql GRANT CREATE TABLE, CREATE MATERIALIZED VIEW, CREATE ANY SNAPSHOT TO [用户名]; ``` - 若涉及系统包(如`DBMS_SNAPSHOT_UTL`),需授予`EXECUTE`权限: ```sql GRANT EXECUTE ON SYS.DBMS_SNAPSHOT_UTL TO [用户名]; ``` **步骤 2:检查角色继承** - 确保用户未被限制通过角色继承权限。Oracle 中某些权限需直接授予用户而非角色: ```sql SELECT * FROM DBA_ROLE_PRIVS WHERE GRANTEE = '[用户名]'; ``` **步骤 3:验证 SYS 对象权限** - 若报错涉及`SYS.DBMS_SNAPSHOT_UTL`,需以`SYSDBA`身份检查包状态和权限: ```sql SELECT OBJECT_NAME, STATUS FROM DBA_OBJECTS WHERE OWNER = 'SYS' AND OBJECT_NAME = 'DBMS_SNAPSHOT_UTL'; GRANT EXECUTE ON SYS.DBMS_SNAPSHOT_UTL TO [用户名]; ``` **示例场景** 若用户执行物化视图刷新时出现权限不足: ```sql -- 直接授予物化视图相关权限 GRANT CREATE MATERIALIZED VIEW TO scott; GRANT EXECUTE ON DBMS_SNAPSHOT TO scott; ``` --- #### **2. 处理 DBMS_SNAPSHOT 和 SYS 包调用问题** **步骤 1:验证包状态** - 检查`DBMS_SNAPSHOT_UTL`是否有效: ```sql SELECT OBJECT_NAME, STATUS FROM DBA_OBJECTS WHERE OBJECT_NAME IN ('DBMS_SNAPSHOT_UTL', 'DBMS_SNAPSHOT'); ``` 若状态为`INVALID`,需重新编译: ```sql ALTER PACKAGE SYS.DBMS_SNAPSHOT_UTL COMPILE; ``` **步骤 2:处理 Oracle 版本兼容性问题** - 若问题在 Oracle 11g 中出现(如引用[^2]所述),检查是否触发已知 Bug: - 查询 Oracle 支持文档(如 MOS),确认 Bug 编号(如 Bug 12345678)。 - 应用官方补丁或升级到修复版本。 **步骤 3:重建物化视图日志(ORA-12034)** 若报错`ORA-12034: 实体化视图日志比上次刷新后的内容新`[^5]: ```sql -- 删除原有日志 DROP MATERIALIZED VIEW LOG ON scott.user_table; -- 重新创建日志 CREATE MATERIALIZED VIEW LOG ON scott.user_table WITH PRIMARY KEY, ROWID; ``` --- #### **3. 相关错误 ORA-01555 的预防** - **调整 UNDO 表空间**: ```sql ALTER DATABASE DATAFILE '/path/undo.dbf' RESIZE 10G; ALTER SYSTEM SET UNDO_RETENTION = 3600; -- 单位:秒 ``` - **避免长事务**:优化查询逻辑,减少全表扫描和锁竞争[^4]。 --- ### 总结操作顺序 1. 授予显式权限(对象权限 + SYS 包权限)。 2. 检查并修复无效的 SYS 包。 3. 处理版本兼容性问题(补丁/升级)。 4. 重建物化视图日志(针对 ORA-12034)。 5. 调整 UNDO 配置(针对 ORA-01555)。 ### 注意事项 - **谨慎操作 SYS 对象**:直接修改 SYS 拥有的包可能导致系统不稳定,建议先在测试环境验证。 - **监控 UNDO 使用**:通过`V$UNDOSTAT`视图分析 UNDO 空间使用趋势[^4]。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值