偶遇问题之ORA-600 [Librarycachenotemptyonclose]

23112312

一个库报ORA-600 [Librarycachenotemptyonclose] ，查了下mos，问题不大，记录一下：

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54

ORA-600 [Librarycachenotemptyonclose] Reported At Shutdown (文档 ID 365103.1)       In this Document Symptoms Cause Solution References APPLIES TO: Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.5 [Release 10.2] Information in this document applies to any platform. ***Checked for relevance on 26-May-2014*** SYMPTOMS Next error is reported in the alert.log on shutdown: ORA-600 [LibraryCacheNotEmptyOnClose] The trace file shows a call stack trace like below 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 CAUSE This may be due to unpublished Bug 4483084 - ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE] This is a bug in that an ORA-600 error is reported during shutdown, after database close because 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. Bug 4483084 is fixed in 11.1.0.6. Please refer to Note 4483084.8 - Bug 4483084 - ORA-600 [LibraryCacheNotEmptyOnClose] on shutdown Due to the nature of the fix, it is not possible to backport to earlier releases. Bug 7572335 is fixed in 11.2 and 10.2.0.5 but there are also interim patches available on top of 10.2.0.4 and 11.1.0.7. Please refer to Note 7572335.8 - Bug 7572335 - ORA-600 [LibraryCacheNotEmptyOnClose] during shutdown SOLUTION The error can be safely ignored as it does not indicate a problem with the database. If the database appears hung on the shutdown, or to avoid the error, use the following shutdown commands: shutdown abort startup restrict shutdown immediate