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

yyp2009發表於2012-07-27

[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/,如需轉載,請註明出處,否則將追究法律責任。

相關文章