zoukankan      html  css  js  c++  java
  • ORA19815: WARNING: db_recovery_file_dest_size of 5218762752 bytes is 100.00% used, and has 0 remain

    今天一个同学问的一个有关数据库的问题,我看了一下alert日志,发现有以下报错信息。现记录下来,以备后用

    ORA-19815: WARNING: db_recovery_file_dest_size of 5218762752 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.
    ************************************************************************
    Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_3488.trc:
    ORA-19809: limit exceeded for recovery files
    ORA-19804: cannot reclaim 41370112 bytes disk space from 5218762752 limit
    ARCH: Error 19809 Creating archive log file to 'E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2010_10_22\O1_MF_1_192_%U_.ARC'
    Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_3488.trc:
    ORA-16038: log 3 sequence# 192 cannot be archived
    ORA-19809: limit exceeded for recovery files
    ORA-00312: online log 3 thread 1: 'E:\DATA\ORCL\REDO03.LOG'
    USER (ospid: 3488): terminating the instance due to error 16038
    Instance terminated by USER, pid = 3488

    SQL > startup mount

    SQL > alter system set db_recovery_file_dest_size=10G scope=both;

    总结一下:

    LOG_ARCHIVE_DEST is applicable only if you are running the database in ARCHIVELOG mode or are recovering a database from archived redo logs. LOG_ARCHIVE_DEST is incompatible with the LOG_ARCHIVE_DEST_n parameters, and must be defined as the null string ("") or (' ') when any LOG_ARCHIVE_DEST_n parameter has a value other than a null string. Use a text string to specify the default location and root of the disk file or tape device when archiving redo log files. (Archiving to tape is not supported on all operating systems.) The value cannot be a raw partition.

    DB_RECOVERY_FILE_DEST specifies the default location for the flash recovery area. The flash recovery area contains multiplexed copies of current control files and online redo logs, as well as archived redo logs, flashback logs, and RMAN backups.

    log_archive_dest是归档日志
    db_recovery_file_dest是闪回
    不一样的,如果归档和闪回打开的话分别使用各自的目录,

    这次报错就是因为闪回使用的5G全部用完了,所以增加到20G ,问题解决

    解决方案:

    1、扩容

    2、删除文件

    参考文章

  • 相关阅读:
    oracle数据库创建后要做的事情
    (转)ORA-12519: TNS:no appropriate service handler found 的问题处理。
    oracle数据库出现“批处理中出现错误: ORA-00001: 违反唯一约束条件”解决方法
    oracle一点记录
    ora-01400 无法将NULL插入 ID 解决方法
    execl一个工作薄中有几个个工作表,将这几个个工作表分别保存到不同execl文件中
    cutpFTP设置步骤
    Oracle数据库备份与还原操作具体步骤
    redis的安装和pip连接
    微信授权登录
  • 原文地址:https://www.cnblogs.com/arcer/p/3116247.html
Copyright © 2011-2022 走看看