ARC3: Error 19809 Creating archive log file to '+FRADG'

最新推荐文章于 2021-04-08 03:16:22 发布

原创最新推荐文章于 2021-04-08 03:16:22 发布 · 3.6k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#oracle

RAC 专栏收录该内容

4 篇文章

订阅专栏

本文探讨了数据库空间管理的问题，包括错误提示、日志文件占用情况及解决方案，重点介绍了通过调整归档目的地来优化空间使用，并解决了日志文件迅速写满导致的系统故障。最终通过设置归档目的地并验证，成功地将大量归档日志文件从闪回区移出，确保系统稳定运行。

Tail -1000f alert_sid.log

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

Errors in file /u01/app/oracle/diag/rdbms/oms/OMS2/trace/OMS2_arc3_10861.trc:

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

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

ARC1: Error 19809 Creating archive log file to '+FRADG'

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.

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

ARC3: Error 19809 Creating archive log file to '+FRADG'

ARCH: Archival error occurred on a closed thread. Archiver continuing

ORACLE Instance OMS2 - Archival Error. Archiver continuing.

Errors in file /u01/app/oracle/diag/rdbms/oms/OMS2/trace/OMS2_arc1_10857.trc:

ORA-19815: WARNING: db_recovery_file_dest_size of 6005194752 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 /u01/app/oracle/diag/rdbms/oms/OMS2/trace/OMS2_arc0_10850.trc:

ORA-19815: WARNING: db_recovery_file_dest_size of 6005194752 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.

ARC1: Error 19809 Creating archive log file to '+FRADG'

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.

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

ARC0: Error 19809 Creating archive log file to '+FRADG'

ARCH: Archival error occurred on a closed thread. Archi

（2）登录失败

[oracle@fps-ordb02 ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 4 16:34:28 2014

ERROR:

ORA-09817: Write to audit file failed.

Linux-x86_64 Error: 28: No space left on device

Additional information: 12

ORA-01075: you are currently logged on

（3）报警日志迅速写满根目录，业务优先把报警日志给删除了

[oracle@fps-ordb02 alert]$ pwd

/u01/app/oracle/diag/rdbms/oms/OMS2/alert

（4）然后正常登陆

sqlplus / as sysdba

(5) 检查闪回参数

SQL> show parameter recovery

NAME TYPE VALUE

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

db_recovery_file_dest string +FRADG

db_recovery_file_dest_size big integer 5727M

recovery_parallelism integer 0

（6）业务优先，先把数据扩大

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

System altered.

（7）到 db_recovery_file_dest（+FRADG）中检查

发现大量的归档日志

（8）检查归档信息，如果不设置 LOG_ARCHIVE_DEST_1，数据默认USE_DB_RECOVERY_FILE_DEST，会把ARCHIVELOG写到FRA内，造成以上问题！

SQL> archive log list

Database log mode Archive Mode

Automatic archival Enabled

Archive destination USE_DB_RECOVERY_FILE_DEST

Oldest online log sequence 72

Next log sequence to archive 75

Current log sequence 75

（6）验证确实是

SQL> show parameter DB_RECOVERY_FILE_DEST

NAME TYPE VALUE

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

db_recovery_file_dest string +FRADG

db_recovery_file_dest_size big integer 20G

（7）归档占用大量的DB_RECOVERY_FILE_DEST空间，造成FRA满了，所以要更改归档地址

ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=+DATADG/OMS/ARCHIVELOG/ARCHIVE1/ARC1' SCOPE=both SID='OMS1' ;

ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='LOCATION=+DATADG/OMS/ARCHIVELOG/ARCHIVE1/ARC2' SCOPE=both SID='OMS1' ;

ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=+DATADG/OMS/ARCHIVELOG/ARCHIVE2/ARC1' SCOPE=both SID='OMS2' ;

ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='LOCATION=+DATADG/OMS/ARCHIVELOG/ARCHIVE2/ARC2' SCOPE=both SID='OMS2' ;

（8）现在原来在闪回区的日志文件删除！

完成！