At the end of shutting down a database, got ORA-00600 error in alert log:
Tue Feb 3 12:30:18 2009
Starting background process EMN0
EMN0 started with pid=29, OS id=21581
Tue Feb 3 12:30:18 2009
Shutting down instance: further logons disabled
Tue Feb 3 12:30:18 2009
Stopping background process QMNC
Tue Feb 3 12:30:18 2009
Stopping background process CJQ0
Tue Feb 3 12:30:20 2009
Stopping background process MMNL
Tue Feb 3 12:30:21 2009
Stopping background process MMON
Tue Feb 3 12:30:23 2009
Shutting down instance (immediate)
License high water mark = 46
Tue Feb 3 12:30:23 2009
Stopping Job queue slave processes
Tue Feb 3 12:30:23 2009
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Tue Feb 3 12:32:55 2009
ALTER DATABASE CLOSE NORMAL
Tue Feb 3 12:32:55 2009
SMON: disabling tx recovery
SMON: disabling cache recovery
Tue Feb 3 12:32:56 2009
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 33665
Successful close of redo thread 1
Tue Feb 3 12:32:56 2009
Completed: ALTER DATABASE CLOSE NORMAL
Tue Feb 3 12:32:56 2009
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
System State dumped to trace file /oracle/admin/mydb/udump/mydb_ora_1541.trc
Tue Feb 3 12:32:59 2009
Errors in file /oracle/admin/mydb/udump/mydb_ora_1541.trc:
ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []
|
Note:
1. It is a bug in Oracle 10.2.0.1/2/3/4 identified as Bug 4483084 - OERI[LibraryCacheNotEmptyOnClose] on shutdown. The bug is fixed in 11.1.0.6 base release.
2. The error can be ignored as it just indicates that there are some items in the library cache when closing down the instance. The error itself occurs AFTER the database close and dismount stages so only affects the instance shutdown itself. Datafiles have been closed cleanly.
3. The error is annoying because the RMAN cold backup fails when the error happens.
4. After googling the web, two triggers were suggested to solve the issue if you have not upgraded to 11.1.0.6:
CREATE or replace TRIGGER flush_shared_pool
BEFORE SHUTDOWN ON DATABASE
BEGIN
execute immediate 'ALTER SYSTEM FLUSH SHARED_POOL';
EXCEPTION
WHEN OTHERS THEN
RAISE_APPLICATION_ERROR (num => -20000, msg => 'Error flushing pool');
END;
|
CREATE or replace TRIGGER flush_shared_pool
BEFORE SHUTDOWN ON DATABASE
BEGIN
execute immediate 'alter TRIGGER SYS.OLAPISTARTUPTRIGGER DISABLE';
execute immediate 'ALTER TRIGGER SYS.OLAPISHUTDOWNTRIGGER DISABLE';
execute immediate 'ALTER SYSTEM FLUSH SHARED_POOL';
execute immediate 'alter TRIGGER SYS.OLAPISTARTUPTRIGGER ENABLE';
execute immediate 'ALTER TRIGGER SYS.OLAPISHUTDOWNTRIGGER ENABLE';
EXCEPTION
WHEN OTHERS THEN
RAISE_APPLICATION_ERROR (num => -20000, msg => 'Error flushing pool');
END;
|