ORA-16038 错误处理

最新推荐文章于 2022-05-23 19:28:41 发布

iteye_13148

最新推荐文章于 2022-05-23 19:28:41 发布

阅读量256

点赞数

CC 4.0 BY-SA版权

分类专栏： ORACLE 文章标签：数据库

本文链接：https://blog.youkuaiyun.com/iteye_13148/article/details/82644020

ORACLE 专栏收录该内容

5 篇文章

订阅专栏

本文记录了一次Oracle数据库启动过程中遇到的归档日志问题。具体表现为启动时提示无法归档log2序列号为391的日志文件，并且达到恢复文件限制。通过查询v$log视图定位到未归档的文件，使用alter database clear unarchived logfile group命令清除未归档日志文件后，成功启动数据库。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

现象：

SQL> shutdown
ORA-01507: database not mounted


ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area 2147483648 bytes
Fixed Size                  2022144 bytes
Variable Size            1560282368 bytes
Database Buffers          570425344 bytes
Redo Buffers               14753792 bytes
Database mounted.
ORA-16038: log 2 sequence# 391 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 2 thread 1: '/data1/oracle/oradata/xxdbse/redo02.log'

解决：

SQL> select group#,sequence#,archived,status from v$log;

    GROUP#  SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
         1        394 NO  CURRENT
         3        393 NO  INACTIVE
         2        391 NO  INACTIVE

SQL> alter database clear unarchived logfile group 3;

Database altered.

SQL> alter database open;

Database altered.

SQL> select group#,sequence#,archived,status from v$log;

    GROUP#  SEQUENCE# ARC STATUS
---------- ---------- --- ----------------
         1        394 NO  INACTIVE
         2        391 NO  INACTIVE
         3        395 NO  CURRENT