ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose]

本文详细记录了在使用Oracle RMAN工具删除归档日志后,数据库在执行shutdown immediate命令时遇到的内部错误ORA-00600,并深入分析了可能的原因和解决方案。通过在执行RMAN命令前先关闭并重新启动实例,避免了该错误的发生。

[oracle@gc44 ora_backup]$ ORACLE_SID=xxxxxxx

[oracle@gc44 ora_backup]$ rman target /

 

Recovery Manager: Release 10.2.0.4.0 - Production on Fri Jul 27 09:21:53 2012

 

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

 

connected to target database: xxxxxxx (DBID=1182361642)

 

RMAN> delete archivelog all;

 

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: sid=136 devtype=DISK

 

List of Archived Log Copies

Key     Thrd Seq     S Low Time  Name

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

633     1    1992    A 23-JUL-12 /app/archivelog/xxxxxxx_1_1992_743799978.arc

634     1    1992    A 23-JUL-12 /app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_23/o1_mf_1_1992_80ttcl4f_.arc

635     1    1993    A 23-JUL-12 /app/archivelog/xxxxxxx_1_1993_743799978.arc

636     1    1993    A 23-JUL-12 /app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_24/o1_mf_1_1993_80w0z92s_.arc

637     1    1994    A 24-JUL-12 /app/archivelog/xxxxxxx_1_1994_743799978.arc

638     1    1994    A 24-JUL-12 /app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_24/o1_mf_1_1994_80xbpdvq_.arc

639     1    1995    A 24-JUL-12 /app/archivelog/xxxxxxx_1_1995_743799978.arc

640     1    1995    A 24-JUL-12 /app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_25/o1_mf_1_1995_80yb7vxv_.arc

641     1    1996    A 25-JUL-12 /app/archivelog/xxxxxxx_1_1996_743799978.arc

642     1    1996    A 25-JUL-12 /app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_25/o1_mf_1_1996_80zz1tgt_.arc

643     1    1997    A 25-JUL-12 /app/archivelog/xxxxxxx_1_1997_743799978.arc

644     1    1997    A 25-JUL-12 /app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_27/o1_mf_1_1997_813tzs2r_.arc

645     1    1998    A 26-JUL-12 /app/archivelog/xxxxxxx_1_1998_743799978.arc

646     1    1998    A 26-JUL-12 /app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_27/o1_mf_1_1998_813tzy9f_.arc

647     1    1999    A 26-JUL-12 /app/archivelog/xxxxxxx_1_1999_743799978.arc

 

Do you really want to delete the above objects (enter YES or NO)? yes 

deleted archive log

archive log filename=/app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_23/o1_mf_1_1992_80ttcl4f_.arc recid=634 stamp=789433851

deleted archive log

archive log filename=/app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_24/o1_mf_1_1993_80w0z92s_.arc recid=636 stamp=789473391

deleted archive log

archive log filename=/app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_24/o1_mf_1_1994_80xbpdvq_.arc recid=638 stamp=789516116

deleted archive log

archive log filename=/app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_25/o1_mf_1_1995_80yb7vxv_.arc recid=640 stamp=789548416

deleted archive log

archive log filename=/app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_25/o1_mf_1_1996_80zz1tgt_.arc recid=642 stamp=789602510

deleted archive log

archive log filename=/app/archivelog/xxxxxxx_1_1997_743799978.arc recid=643 stamp=789729405

deleted archive log

archive log filename=/app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_27/o1_mf_1_1997_813tzs2r_.arc recid=644 stamp=789729405

deleted archive log

archive log filename=/app/archivelog/xxxxxxx_1_1998_743799978.arc recid=645 stamp=789729411

deleted archive log

archive log filename=/app/oracle/base/flash_recovery_area/xxxxxxx/archivelog/2012_07_27/o1_mf_1_1998_813tzy9f_.arc recid=646 stamp=789729411

deleted archive log

archive log filename=/app/archivelog/xxxxxxx_1_1999_743799978.arc recid=647 stamp=789729523

Deleted 10 objects

 

RMAN-06207: WARNING: 5 objects could not be deleted for DISK channel(s) due

RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status

RMAN-06210: List of Mismatched objects

RMAN-06211: ==========================

RMAN-06212:   Object Type   Filename/Handle

RMAN-06213: --------------- ---------------------------------------------------

RMAN-06214: Archivelog      /app/archivelog/xxxxxxx_1_1992_743799978.arc

RMAN-06214: Archivelog      /app/archivelog/xxxxxxx_1_1993_743799978.arc

RMAN-06214: Archivelog      /app/archivelog/xxxxxxx_1_1994_743799978.arc

RMAN-06214: Archivelog      /app/archivelog/xxxxxxx_1_1995_743799978.arc

RMAN-06214: Archivelog      /app/archivelog/xxxxxxx_1_1996_743799978.arc

 

 

RMAN>

 

RMAN>

 

RMAN>

 

RMAN>

 

RMAN> exit  

 

 

Recovery Manager complete.

[oracle@gc44 ora_backup]$ sqlplus / as sysdba

 

SQL*Plus: Release 10.2.0.4.0 - Production on Fri Jul 27 09:25:23 2012

 

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.

 

 

Connected to:

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

 

SQL> shutdown immediate

Database closed.

Database dismounted.

ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []

SQL>

 

References Metlink:

 

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.2 and later [Release: 10.2 and later ]
Information in this document applies to any platform.
***Checked for relevance on 15-Dec-2011***

Symptoms

RMAN script. fails after executing 'shutdown immediate':

RMAN-03002: failure of shutdown command at 06/17/2006 18:01:23
ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []

Cause

Bug 4483084 'ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE]' - This is an unpublished bug.

This ORA-600 is in itself harmless and indicates that some other activity was taking place in the database at the time of shutdown; it can be safely ignored as there is no problem with the database.

However if the shutdown is issued from within an rman script. the error is detected by RMAN which
subsequently fails upon receipt of an error from Oracle - this is expected behaviour on the part
of RMAN but avoidance action needs to be taken to prevent RMAN from failing unnecessarily.

Solution

Shutdown and mount the instance before invoking RMAN - you can do this by invoking SQLPlus prior
to invoking RMAN in your backup shell script.

 

-----end---------

 

 

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/13750068/viewspace-737526/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/13750068/viewspace-737526/

### ORA-00600错误代码参数为-4019的解决方案 ORA-00600Oracle数据库中的一种内部错误,通常表示数据库遇到了一个不可预期的情况。当参数为`-4019`时,该错误可能与索引块损坏或索引结构不一致相关[^1]。以下是关于ORA-00600 internal error code arguments -4019的具体分析和解决方案: #### 1. 错误原因 ORA-00600 [-4019]通常发生在对索引进行操作时,例如插入、更新或删除数据。这种错误可能是由于以下原因之一引起的: - 索引块损坏。 - 索引结构不一致。 - 数据库文件(如数据文件或重做日志文件)存在物理损坏。 - 使用了隐藏参数或不当的数据库恢复方法。 #### 2. 解决方案 以下是针对ORA-00600 [-4019]的常见解决步骤: ##### 2.1 检查告警日志和跟踪文件 首先需要检查数据库的告警日志和相关的跟踪文件,以获取更多关于错误的详细信息。这些文件通常位于`$ORACLE_BASE/diag/rdbms/<dbname>/<instance>/trace/`目录下。通过分析这些文件,可以确定具体的索引对象及其相关问题[^3]。 ##### 2.2 验证索引完整性 使用`ANALYZE INDEX`命令验证受影响的索引是否存在逻辑损坏: ```sql ANALYZE INDEX <index_name> VALIDATE STRUCTURE; ``` 如果发现索引损坏,可以通过重建索引来修复问题: ```sql ALTER INDEX <index_name> REBUILD; ``` ##### 2.3 检查数据文件一致性 如果索引重建无法解决问题,可能需要进一步检查数据文件的一致性。可以使用`DBVERIFY`工具验证数据文件的物理和逻辑结构: ```bash dbv file=<datafile_path> blocksize=<block_size> ``` ##### 2.4 恢复受影响的对象 如果上述方法无效,可以尝试从备份中恢复受影响的表空间或数据文件。在恢复之前,请确保已启用归档模式并备份了所有必要的归档日志。 ##### 2.5 联系Oracle支持 如果以上方法均无法解决问题,建议收集相关诊断信息(如告警日志、跟踪文件等),并联系Oracle官方支持以获取进一步帮助。 #### 3. 示例代码 以下是一个示例脚本,用于验证和重建索引: ```sql -- 验证索引结构 ANALYZE INDEX my_index VALIDATE STRUCTURE; -- 如果发现损坏,重建索引 ALTER INDEX my_index REBUILD; ``` --- ###
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值