记一次ADG备库归档目录满导致的延时处理

报错如下，原因是存放传过来的归档的目录+HWAREDODG满了，MRP进程无法应用归档，我在手动传了几个归档之后发现不是GAP，select * from V$ARCHIVE_GAP 显示没有GAP。于是就把HWAREDODG下已经应用的归档删掉，

rman target /

rman>select ‘run{‘ from dual

union all

select ‘delete noprompt archivelog until sequence ‘||max(sequence#)||‘ thread ‘||thread#||‘;‘ from v$archived_log where applied=‘YES‘ and name is not null GROUP BY thread#

union all

select ‘}‘ from dual;

删除后归档顺利生成，MRP进程正常应用

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

FAL[client]: Failed to request gap sequence

GAP - thread 1 sequence 19387-19387

DBID 3365933973 branch 982424855

FAL[client]: All defined FAL servers have been attempted.

------------------------------------------------------------

Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization

parameter is defined to a value that‘s sufficiently large

enough to maintain adequate log switch information to resolve

archivelog gaps.

------------------------------------------------------------

Mon Feb 18 22:22:06 2019

Archived Log entry 10638 added for thread 2 sequence 16410 ID 0xc935a096 dest 1:

Mon Feb 18 22:22:06 2019

Unable to create archive log file ‘+HWAREDODG‘

Mon Feb 18 22:22:06 2019

Errors in file /oracle/app/oracle/diag/rdbms/wlwzz/wlwcdb/trace/wlwcdb_arc3_10142.trc:

ORA-19504: failed to create file "+HWAREDODG"

ORA-17502: ksfdcre:4 Failed to create file +HWAREDODG

ORA-15041: diskgroup "HWAREDODG" space exhausted

ARC3: Error 19504 Creating archive log file to ‘+HWAREDODG‘

Mon Feb 18 22:29:06 2019

Unable to create archive log file ‘+HWAREDODG‘

Mon Feb 18 22:29:06 2019

Errors in file /oracle/app/oracle/diag/rdbms/wlwzz/wlwcdb/trace/wlwcdb_arc1_10138.trc:

ORA-19504: failed to create file "+HWAREDODG"

ORA-17502: ksfdcre:4 Failed to create file +HWAREDODG

ORA-15041: diskgroup "HWAREDODG" space exhausted

ARC1: Error 19504 Creating archive log file to ‘+HWAREDODG‘

Mon Feb 18 22:36:06 2019

Unable to create archive log file ‘+HWAREDODG‘

Mon Feb 18 22:36:06 2019

Errors in file /oracle/app/oracle/diag/rdbms/wlwzz/wlwcdb/trace/wlwcdb_arc0_10136.trc:

ORA-19504: failed to create file "+HWAREDODG"

ORA-17502: ksfdcre:4 Failed to create file +HWAREDODG

ORA-15041: diskgroup "HWAREDODG" space exhausted

ARC0: Error 19504 Creating archive log file to ‘+HWAREDODG‘

Mon Feb 18 22:44:07 2019

Unable to create archive log file ‘+HWAREDODG‘

Mon Feb 18 22:44:07 2019

Errors in file /oracle/app/oracle/diag/rdbms/wlwzz/wlwcdb/trace/wlwcdb_arc3_10142.trc:

ORA-19504: failed to create file "+HWAREDODG"

ORA-17502: ksfdcre:4 Failed to create file +HWAREDODG

ORA-15041: diskgroup "HWAREDODG" space exhausted

ARC3: Error 19504 Creating archive log file to ‘+HWAREDODG‘

Mon Feb 18 22:51:07 2019

Unable to create archive log file ‘+HWAREDODG‘

Mon Feb 18 22:51:07 2019

Errors in file /oracle/app/oracle/diag/rdbms/wlwzz/wlwcdb/trace/wlwcdb_arc1_10138.trc:

ORA-19504: failed to create file "+HWAREDODG"

ORA-17502: ksfdcre:4 Failed to create file +HWAREDODG

ORA-15041: diskgroup "HWAREDODG" space exhausted

ARC1: Error 19504 Creating archive log file to ‘+HWAREDODG‘

原文地址：https://www.cnblogs.com/kawashibara/p/10403085.html

时间： 2024-10-06 11:45:39

记一次ADG备库归档目录满导致的延时处理的相关文章

DG备库磁盘空间满导致无法创建归档

上周五去某客户那里做数据库巡检,是window 2008系统上10g的一套NC系统的库,已经配置了DG,但是巡检时发现数据库报错: Tue Nov 11 10:13:57 2014 LNS: Standby redo logfile selected for thread 1 sequence 3945 for destination LOG_ARCHIVE_DEST_2 Tue Nov 11 10:14:29 2014 Errors in file d:\oracle\product\10.2

12c ADG无法删除备库归档RMAN-08137

一.环境描述12c 变化很大,目前上线的系统越来越多,大家需要不断更新自己的知识库. On : 12.1.0.2 version, RAC? can't delete archivelog? ERROR? -----------------------? RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process? archived log file name=+ARC

oracle--DG模式备库归档缺失问题（1）

01.问题描述 备库的归档日志没有增加,一直等待一个 查询问题: SQL> SELECT * FROM V$ARCHIVE_GAP; THREAD# LOW_SEQUENCE# HIGH_SEQUENCE# ---------- ------------- -------------- 1 6434 6435 select name ,sequence# from v$archived_log; NAME SEQUENCE# -----------------------------------

ADG 备库数据文件损坏处理

一.描述单实例ADG数据库,备库system01.dbf文件损坏,需要重新恢复数据文件,保证主库库数据一致. 二.处理过程 1.数据库启动到mount状态Recovery Manager: Release 11.2.0.4.0 - Production on Thu Dec 12 20:42:35 2019 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to targe

ADG 备库不允许切换日志

备库数据文件是不允许写数据,切换日志是需要写数据到数据文件中的.为什么rman备份可以,是因为rman备份写的是控制文件~ 1.备库演示,会报错,数据库为打开. SQL> archive log list; Database log mode Archive Mode Automatic archival Enabled Archive destination /arch Oldest online log sequence 4132 Next log sequence to archive 0

ORA-21561、ORA-15055、ORA-25253 导致DG备库无法应用归档

昨天去某客户那里做巡检,顺便看一下上次搭建的RAC-DG环境是否正常,不看不知道,一看吓一跳,上次的DG是8月20日运行的,而DG备库从8月31日之后实例就没有开启过,后来询问后才得知,原来那天断过一次电,后来重启了机器.直到今天我过去了,才把实例启动起来.也就是说,从8月31日到今天快1个月的时间,备库一致处于未使用状态. 接着查看备库归档,显然已经缺失了很多了,tnread1 最后一个日志为1661,tnread2 最后一个日志为1324,而此时主库中还保留的最早的日志是9月8日的,thre

dataguard 归档丢失(主库中无此丢失归档处理),备库基于SCN恢复

dataguard 归档丢失(主库中无此丢失归档处理),备库基于SCN恢复 环境: OS: CentOS 6.5 DB: Oracle 10.2.0.5 1.主备库环境 主库: SQL> select dbid,name,LOG_MODE,open_mode,db_unique_name,DATABASE_ROLE,PROTECTION_MODE from v$database; DBID NAME LOG_MODE OPEN_MODE DB_UNIQUE_NAME DATABASE_ROLE

备库简介

备库类型:1.物理备库:2.逻辑备库:3.快照备库. 可以同时配置1个或多个类型的备库 1.物理备库 是主库的块对块的拷贝,应用重做日志,通过从主库接受重做数据应用到物理备库上的机制 可以以read only模式打开,11g之后可以配置active DG以只读模式打开应用重做数据 物理备库的好处: 1. 灾难恢复和高可用 2. 数据保护 支持多有的DDL和DML操作 3. 减小主库负载 以只读模式打开,用于报表和查询 4. 性能 底层拷贝,绕过SQL级别代码层 2. 逻辑备库 通过SQL应用更新

Oracle 11g Dataguard 暂停物理备库的日志传输

Oracle 11g Dataguard 暂停物理备库的日志传输分类: Oracle2017-07-18 10:03:17这两天生产端的日志产生过多导致灾备端的归档日志目录满的现象,在清除灾备端的日志后发现log_archive_dest_2处于error状态,需要将其enable.在实际生产系统中,通常有这样的场景,例如在系统维护日,对主库进行大量的业务更新,会有大量的DML操作:为了避免主库中的业务更新对备库造成影响,可以暂停主库对备库的日志传输,这样的话,如果主库的更新出现问题,备库还保留