DG环境RMAN删除归档报错RMAN-08137: archived log not deleted

Oracle 12C DG环境,备库归档目录告警,查看crontab脚本,发现有删除操作,保持两天的,后手动执行,查看具体报错原因;

RMAN> delete noprompt expired archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=5408 device type=DISK
specification does not match any archived log in the repository

RMAN> delete noprompt archivelog until time ‘sysdate-2‘;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=5408 device type=DISK
RMAN-08137: warning: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/arch/fcdstdydb1_948_973216253.dbf thread=1 sequence=948
RMAN-08137: warning: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/arch/fcdstdydb1_949_973216253.dbf thread=1 sequence=949
RMAN-08137: warning: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/arch/fcdstdydb1_950_973216253.dbf thread=1 sequence=950
RMAN-08137: warning: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/arch/fcdstdydb1_951_973216253.dbf thread=1 sequence=951
RMAN-08137: warning: archived log not deleted, needed for standby or upstream capture process
archived log file name=/u01/arch/fcdstdydb1_952_973216253.dbf thread=1 sequence=952
RMAN-08137: warning: archived log not deleted, needed for standby or upstream capture process

---解决---

RMAN> delete noprompt force archivelog all completed before ‘sysdate-2‘;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=5408 device type=DISK
List of Archived Log Copies for database with db_unique_name FCDSTDYDB

Key Thrd Seq S Low Time



935 1 948 A 2018:06:05 02:23:34
Name: /u01/arch/fcdstdydb1_948_973216253.dbf

936 1 949 A 2018:06:05 02:28:52
Name: /u01/arch/fcdstdydb1_949_973216253.dbf

937 1 950 A 2018:06:05 02:32:32

---说明---

此为11g的bug,需要在delete后加上force关键字,metalink上有记载
RMAN-08137 When deleting archivelogs even when Streams CAPTURE does not require them [ID 1079953.1]

In this Document
??Symptoms
??Changes
??Cause
??Solution
??References

Symptoms
Applies To:?11gR1-11gR2

RMAN is unable to delete archive logs from database even though they are not needed by CAPTURE process anymore.

Changes
?

Cause
In 11g, RMAN looks at MIN_REQUIRED_CAPTURE_CHANGE# in v$database and not at DBA_CAPTURE. By default this value is updated every 6 hours. So by default the value in v$database will be six hours behind the current value.

Solution
Since changing frequency of update to MIN_REQUIRED_CAPTURE_CHANGE# in v$database can not be controlled, following workaround can be used:

Archive log which are not needed by capture process can be deleted using:

delete noprompt force archivelog all completed before ‘sysdate-10/1440‘;

PS:我们的环境是12C DG,该BUG在11g中有明确标识,12C就此MARK一下;

原文地址:http://blog.51cto.com/yangjunfeng/2132820

时间: 2024-08-28 19:24:11

DG环境RMAN删除归档报错RMAN-08137: archived log not deleted的相关文章

12.2备库rman使用delete删除归档日志报错RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

问题: 客户环境12.2 dg备库环境,定时清理归档脚本并未正常清理归档日志文件. 观察日志可以发现存在如下信息 RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process . 一般情况下,如果在备库环境或者主库环境,配置归档清理测量后,DG环境未应用归档将不允许删除. 本次排查RMAN清理归档策略默认,且无法删除的归档日志在DG视图v$archived_log 中ap

通过RMAN删除归档日志不释放问题

我的生产环境中归档日志满了,通过如下脚本删除后,空间并没有释放,看有网友有相关的解决思路,可以跟大家一起分享一下: RMAN> crosscheck archivelog all; RMAN> delete expried archivelog all; 关于rm删除文件空间不释放的问题可以写成一个FAQ了 一般说来不会出现rm掉不释放空间的情况出现这样的情况一般是由于有进程在向文件中写数据或有进程正在访问文件而此时rm文件则会出现不释放空间的情况 理解这样的问题需要理解rm的操作内含一个文件

dojo处理删除操作报错

1.错误描述    java.lang.IllegalArgumentException:attempt to create delete event with null entity. 2.错误原因    dojo.xhrPost({         url:"", content:{     "userId":userId         },         success:function(data)         {         }    });  

winserver2003环境发布ASP程序报错(HTTP 错误 403.1 - 禁止访问:执行访问被拒绝)

问题: 在Windows Server 2003 + IIS6.0上布署.Net 2.0网站时发生如下错误: 该页无法显示 您试图从目录中执行 CGI.ISAPI 或其他可执行程序,但该目录不允许执行程序. -------------------------------------------------------------------------------- 请尝试以下操作: 如果您认为该目录应该允许执行访问权限,请与网站管理员联系. HTTP 错误 403.1 - 禁止访问:执行访问被

reactNative环境搭建+打包+部分报错总结

个人搭建记录+个人收集: 多些真诚,少些坑. 排版书写过程可能不够详细,还望见谅. 详细见:http://files.cnblogs.com/files/chunlei36/reactNative%E7%8E%AF%E5%A2%83%E6%90%AD%E5%BB%BA%26%E6%89%93%E5%8C%85%26%E6%8A%A5%E9%94%99%E6%80%BB%E7%BB%93.pdf reactNative环境搭建+打包+部分报错总结

11gR2RAC环境DBCA创建数据库报错ORA-15055 ORA-15001

11gR2RAC环境DBCA创建数据库报错ORA-15055 ORA-15001 问题现象: 在11gR2 GridInfrastructure和Database软件安装完成之后,执行DBCA创建数据库到30%的时候报如下错误,点击OK后提示忽略并停止安装. 问题分析:      从上面的问题我们不难看出是因为无法访问ASM磁盘组导致,但是要解决该问题就得进入到ASM中去探个究竟,为什么刚装好的集群,建库就出现问题. 随即我们先通过grid用户登录到asm实例执行如下查询操作,我们发现磁盘组均为

RMAN删除归档日志不释放问题

今天同事问到一个问题,他那边的一套Oracle 11g数据库使用RMAN没办法删除旧的归档,导致磁盘使用率很高. [email protected]:[/opt/oracle/archive/db] ls -ltr |moretotal 3059881082 -rw-r-----   1 oracle     oinstall   725320704 May 20  2016 1_1_91233774.dbf -rw-rw----   1 oracle     oinstall   175693

rman备份密码报错-转义

同事备份遇到了一个报错,提示用户密码拒绝.经过确认用户和密码都没有问题,那可能是什么问题呢! 1.现象 <roidb01:orcl:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin>$ <roidb01:orcl:/u01/app/oracle/product/11.2.0/dbhome_1/network/admin>$sh rman.sh Recovery Manager: Release 11.2.0.4.0 - Pr

转: 第二步CentOS上安装LAMP之PHP环境及安装过程报错解决方案(纯净系统环境)

最近有空就配置CentOS系统上的AMP环境,现在配置到PHP环境了 多话不说上传送门:http://blog.csdn.net/zhangatle/article/details/77447653 其中有些改动,毕竟博主的centOS的系统没有安装必须的开发环境包,他是纯净CentOS安装的!佩服 注:本文站在菜鸟的角度看待并解决问题,中间不可避免会遇到许多坑,而本文的目的就在于帮大家解决这些坑 工欲善其事,必先利其器,为了后续工作,需要先进行以下准备工作 将所需要的软件安装包上传到服务器,本