今天在测试环境正常关闭数据库时突然遇到ORA-00600的错误,我的数据库版本为10.2.0.4
11:32:57 MYHSZHLC@SYS> shutdown immediate
Database closed.
Database dismounted.
ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []
在MOS上查了一下,发现这是Oracle的一个Bug,并且在10.2.0.4里面没有相应的补丁,
不过你也可以用“ALTER SYSTEM FLUSH SHARED_POOL”这个sql在每次shutdown前把libray pool清空来解决问题,
ORA-600 [Librarycachenotemptyonclose] Reported At Shutdown [ID 365103.1] 修改时间 14-DEC-2011 类型 PROBLEM 状态 PUBLISHED
In this Document
Symptoms
Cause
Solution
References
Information in this document applies to any platform.
Symptomso ORA-600 [LibraryCacheNotEmptyOnClose] is reported in the alert.log on shutdown.
The trace file shows the following call stack trace and will also include a System State:
kglshu kqlnfy kscnfy ksmshu
opistp_real opistp opiodr ttcpip opitsk opiino opiodr opidrv
sou2o opimai_real main libc_start_main
o Using the mechanism described in Note 301171.1 to pin objects in the Shared Pool
might cause the error. The problem disappears when the pinning of objects is stopped by
deactivating the associated triggers.
CauseThis may be due to unpublished Bug 4483084 'ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE]'
This is a bug in that an ORA-600 error is reported when it is found during shutdown, after database close, that there are still objects in the library cache. It does not indicate any damage or a problem in the system.
There is a separate issue, Bug 7572335: ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE] / ORA-600 [730] DURING SHUTDOWN, which can occur if child cursors are still marked 'KEPT' in the library cache at shutdown. If you are not sure which issue you are encountering, please submit your traces to Global Software Support.
Solution
Due to the nature of the fix, it is not possible to backport to earlier releases.
The error can be safely ignored as it does not indicate a problem with the database.
but there are also one-off fixes available on top of 10.2.0.4 and 11.1.0.7.
ORA-600 [LibraryCacheNotEmptyOnClose] can occur during shutdown. Workaround Ignore the error 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. If the database appears hung on the shutdown, or to avoid the error use the following shutdown commands: shutdown abort startup restrict shutdown immediate Note: It is not possible to get one-off patches for this issue in any 10g release.Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.