4 Mar

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

This error may appear during instance shutdown. You may safely ignore this error, as it is raised only after the database has been closed. No action or corrective steps on the part of the DBA are required. Although the occasional appearance of this error on instance shutdown is messy and annoying, it is not harmful in any significant way.

Oracle provides patches for this bug (7572335) for a limited set of platforms and versions:

  • Solaris Sparc 64-bit ( – and
  • IBM AIX POWER 64-bit (

The limited availability of a patch is due to the harmless nature of the error.

4 Responses to “ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose]”

  1. Pradip Patel 25. Mar, 2009 at 11:50 am #

    I got this error today (25-Mar-2009). I ignore this error. Again I started and shutdown my instance. Surprisingly error gone for now.


  2. siva 07. Jun, 2010 at 9:57 pm #

    We have the same issue, restarted the database( and error is gone, but we have weekly cold back after two weeks it showup. ITS Haunting…

  3. Willis Brits 12. Dec, 2010 at 8:33 pm #

    Hi Guys,

    There is a patch for this error, but only on certain OS’s – so check metalink.
    The error doesn’t cause issues, just a worry, but if you’re shutting down for backup (or maintenance/db profile changes), it is good practice to restart the DB and shut down clean before backup.


  4. jwilton 13. Dec, 2010 at 2:15 pm #

    Thanks Willis. I have updated the main blog entry with the available patches. It is a good lesson for those who dread the sight of any ORA-600. Most are not harmful, and have low impact.

    I was a little curious about your advice regarding starting back up and shutting down again “clean.” My understanding is that the error does not result in any process crashing, and that ‘shutdown immediate’ completes successfully, despite the appearance of this ORA-600. Can you explain your rationale for the restart and re-shut-down?

Leave a Reply