ORA-19809: limit exceeded for recovery files

简介:

常常会遇到下面的报错信息

 

 

欢迎大家加入ORACLE超级群:17115662 免费解决各种ORACLE问题,以后BLOG将迁移到http://www.htz.pw

 

ARCH: Error 19809 Creating archive log file to '/oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_113_%u_.arc'

ARC1: Error 19809 Creating archive log file to '/oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_114_%u_.arc'

Errors in file /oracle/app/oracle/diag/rdbms/orcl1124/orcl1124/trace/orcl1124_ora_22611.trc:

ORA-16038: log 2 sequence# 113 cannot be archived

ORA-19809: limit exceeded for recovery files

ORA-00312: online log 2 thread 1: '/oracle/app/oracle/oradata/orcl1124/redo02.log'

ARCH: Archival stopped, error occurred. Will continue retrying

ORACLE Instance orcl1124 - Archival Error

ORA-16038: log 3 sequence# 114 cannot be archived

ORA-19809: limit exceeded for recovery files

ORA-00312: online log 3 thread 1: '/oracle/app/oracle/oradata/orcl1124/redo03.log'

System state dump requested by (instance=1, osid=22611), summary=[abnormal instance termination].

System State dumped to trace file /oracle/app/oracle/diag/rdbms/orcl1124/orcl1124/trace/orcl1124_diag_22544_20140605180150.trc

Dumping diagnostic data in directory=[cdmp_20140605180150], requested by (instance=1, osid=22611), summary=[abnormal instance termination].

USER (ospid: 22611): terminating the instance due to error 16038

Instance terminated by USER, pid = 22611

原因很简单:归档目录满了,解决的方法也很多的

1,如果归档存放在FRA区,修改一个FRA区的大小就可以了,前提是FRA目录上还有剩余的空间。

2,使用单独的归档目录,扩一下文件系统或者将归档路径修改到其它的地方就可以了。

3,下面我们测试另一种方法

 

1,启动数据库报错

[oracle@www.htz.pw oradata]$sqlplus / as sysdba

 

SQL*Plus: Release 11.2.0.4.0 Production on Thu Jun 5 18:01:30 2014

 

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

 

Connected to an idle instance.

 

www.htz.pw > startup

ORACLE instance started.

 

Total System Global Area  379965440 bytes

Fixed Size                  2253464 bytes

Variable Size             171969896 bytes

Database Buffers          201326592 bytes

Redo Buffers                4415488 bytes

Database mounted.

ORA-03113: end-of-file on communication channel

Process ID: 22611

Session ID: 1 Serial number: 5

2alert中报下面的错误

ORA-19815: WARNING: db_recovery_file_dest_size of 4385144832 bytes is 100.00% used, and has 0 remaining bytes available.

************************************************************************

You have following choices to free up space from 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.

************************************************************************

ARCH: Error 19809 Creating archive log file to '/oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_113_%u_.arc'

ARC1: Error 19809 Creating archive log file to '/oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_114_%u_.arc'

Errors in file /oracle/app/oracle/diag/rdbms/orcl1124/orcl1124/trace/orcl1124_ora_22611.trc:

ORA-16038: log 2 sequence# 113 cannot be archived

ORA-19809: limit exceeded for recovery files

ORA-00312: online log 2 thread 1: '/oracle/app/oracle/oradata/orcl1124/redo02.log'

ARCH: Archival stopped, error occurred. Will continue retrying

ORACLE Instance orcl1124 - Archival Error

ORA-16038: log 3 sequence# 114 cannot be archived

ORA-19809: limit exceeded for recovery files

ORA-00312: online log 3 thread 1: '/oracle/app/oracle/oradata/orcl1124/redo03.log'

System state dump requested by (instance=1, osid=22611), summary=[abnormal instance termination].

System State dumped to trace file /oracle/app/oracle/diag/rdbms/orcl1124/orcl1124/trace/orcl1124_diag_22544_20140605180150.trc

Dumping diagnostic data in directory=[cdmp_20140605180150], requested by (instance=1, osid=22611), summary=[abnormal instance termination].

USER (ospid: 22611): terminating the instance due to error 16038

Instance terminated by USER, pid = 22611

3,下面将归档库更改为非归档就可以正常启动了

我做的事情增加了resetlog的方式,在生产环境这里可以使用noresetlogs的方式就可以了,因为我们只是更改一下归档模式的。

CREATE CONTROLFILE REUSE DATABASE "ORCL1124" RESETLOGS  NOARCHIVELOG

    MAXLOGFILES 16

    MAXLOGMEMBERS 3

    MAXDATAFILES 100

    MAXINSTANCES 8

    MAXLOGHISTORY 292

LOGFILE

  GROUP 1 '/oracle/app/oracle/oradata/orcl1124/redo01.log'  SIZE 50M BLOCKSIZE 512,

  GROUP 2 '/oracle/app/oracle/oradata/orcl1124/redo02.log'  SIZE 50M BLOCKSIZE 512,

  GROUP 3 '/oracle/app/oracle/oradata/orcl1124/redo03.log'  SIZE 50M BLOCKSIZE 512

-- STANDBY LOGFILE

DATAFILE

  '/oracle/app/oracle/oradata/orcl1124/system01.dbf',

  '/oracle/app/oracle/oradata/orcl1124/sysaux01.dbf',

  '/oracle/app/oracle/oradata/orcl1124/undotbs01.dbf',

  '/oracle/app/oracle/oradata/orcl1124/users01.dbf',

  '/oracle/app/oracle/oradata/orcl1124/htz01.dbf',

  '/oracle/app/oracle/oradata/orcl1124/undotbs02.dbf'

CHARACTER SET ZHS16GBK

;

 

 

 

www.htz.pw > recover database using backup controlfile until cancel;

ORA-00279: change 2795841 generated at 06/05/2014 17:52:39 needed for thread 1

ORA-00289: suggestion :

/oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_115

_%u_.arc

ORA-00280: change 2795841 for thread 1 is in sequence #115

 

 

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

/oracle/app/oracle/oradata/orcl1124/redo03.log

ORA-00310: archived log contains sequence 114; sequence 115 required

ORA-00334: archived log: '/oracle/app/oracle/oradata/orcl1124/redo03.log'

 

 

www.htz.pw > recover database using backup controlfile until cancel;

ORA-00279: change 2795841 generated at 06/05/2014 17:52:39 needed for thread 1

ORA-00289: suggestion :

/oracle/app/oracle/fast_recovery_area/ORCL1124/archivelog/2014_06_05/o1_mf_1_115

_%u_.arc

ORA-00280: change 2795841 for thread 1 is in sequence #115

 

 

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

/oracle/app/oracle/oradata/orcl1124/redo01.log

Log applied.

Media recovery complete.

这里一定要手动输入日志路径,不然可以会丢失数据,或者遇到其它的报错的。

 

 

www.htz.pw > alter database open resetlogs;

 

Database altered.

 

 

www.htz.pw > archive log list;

Database log mode              No Archive Mode

Automatic archival             Disabled

Archive destination            USE_DB_RECOVERY_FILE_DEST

Oldest online log sequence     1

Current log sequence           1


     本文转自7343696 51CTO博客,原文链接:http://blog.51cto.com/luoping/1424425,如需转载请自行联系原作者


相关文章
146Echarts - 矩形树图(Basic Treemap)
146Echarts - 矩形树图(Basic Treemap)
442 0
|
XML JSON API
淘宝天猫API接入说明(淘宝天猫商品详情+关键词搜索商品列表)商品详情数据,商品sku数据,商品优惠券数据
业务场景:作为全球最大的 B2C 电子商务平台之一,淘宝天猫平台提供了丰富的商品资源,吸引了大量的全球买家和卖家。为了方便开发者接入淘宝天猫平台,淘宝天猫平台提供了丰富的 API 接口,其中历史价格接口是非常重要的一部分。大家有探讨稳定采集淘宝(天猫)京东阿里拼多多等平台整站实时商品详情历史价格数据接口,通过该接口开发者可以更好地了解商品的情况,商品详情数据详细信息查询,数据参数包括:商品链接,商品列表主图、价格、标题,sku,库存,销量,店铺昵称,店铺等级,商品详情SKU属性,商品视频,商品优惠券,促销信息,详情属性描述,宝贝ID,区域ID,发货地,发货至,快递费用,物流费用等页面上有的数据
|
7月前
|
机器学习/深度学习 人工智能 自然语言处理
DeepSeek估值1500亿美元:AI领域的新星崛起
据外媒Bloomberg报道,DeepSeek的估值已达到1500亿美元,相当于OpenAI估值的一半。在巴黎AI峰会上,DeepSeek成为焦点话题,其影响力甚至延伸至普通民众。据报道,巴黎地铁上的70岁老人也在讨论这一新兴科技公司,显示出DeepSeek不仅在专业领域备受关注,在公众中也引起了广泛兴趣。
627 7
|
9月前
|
API Windows
恶意代码分析入门--PE结构能告诉我们很多信息(chapter1_Lab01-04)
本实验分析了Lab01-04.exe文件,通过VirusTotal检测其是否匹配反病毒特征,检查是否存在加壳或混淆,并使用PEiD、Strings、Resource Hacker等工具进行静态分析,提取资源文件,分析其编译时间、导入函数及潜在恶意行为。实验在Windows XP SP3环境下进行。
161 5
恶意代码分析入门--PE结构能告诉我们很多信息(chapter1_Lab01-04)
|
Linux 网络安全
在Linux中,如何设置防火墙规则?
在Linux中,如何设置防火墙规则?
|
弹性计算 运维 自然语言处理
启迪操作系统智慧的神:操作系统智能助手OS Copilot
OS Copilot 是阿里云针对Linux推出的一款智能助手,基于大模型构建,简化了Linux操作和运维工作。它支持自然语言问答,辅助命令执行,阿里云CLI调用以及系统运维和调优。这款工具特别适合初学者和运维人员,减少了对命令记忆的需求,通过对话式交互即可完成任务。
405 15
|
关系型数据库 MySQL 分布式数据库
PolarDB产品使用问题之从MySQL迁移数据到PolarDB-X时,自定义函数不会自动迁移,该怎么办
PolarDB产品使用合集涵盖了从创建与管理、数据管理、性能优化与诊断、安全与合规到生态与集成、运维与支持等全方位的功能和服务,旨在帮助企业轻松构建高可用、高性能且易于管理的数据库环境,满足不同业务场景的需求。用户可以通过阿里云控制台、API、SDK等方式便捷地使用这些功能,实现数据库的高效运维与持续优化。
235 1
|
域名解析 缓存 安全
cdn服务器连接异常怎么办
当遇到CDN服务器连接异常时,可采取以下步骤排查:检查CDN配置,包括域名解析和防火墙设置;清空CDN缓存;测试网络连接;确认源服务器状态;更换CDN服务器;等待恢复;联系服务商;检查本地电脑安全;检查程序代码;保持更新和维护。具体解决步骤需根据实际情况调整。
1988 0
|
SQL Oracle 关系型数据库
PL/SQL生成表的数据结构关系图
PL/SQL生成表的数据结构关系图
235 0
ArcGIS中ArcMap为不含坐标系的图层添加地理坐标系或投影坐标系
ArcGIS中ArcMap为不含坐标系的图层添加地理坐标系或投影坐标系
388 1