Oracle关闭遇到ORA-00600 【LibraryCacheNotEmptyOnClose】的错误
今天在测试环境正常关闭数据库时突然遇到ORA-00600的错误,我的数据库版本为10.2.0.411:32:57 MYHSZHLC@SYSgt; shutdown immedi
今天在测试环境正常关闭数据库时突然遇到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里面没有相应的补丁,不过这个Bug可以忽略!
不过你也可以用“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
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
Bug 4483084 is fixed in 11.1.0.6.
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.
Bug 7572335 is fixed in 11.2 and 10.2.0.5 but there are also one-off fixes available on top of 10.2.0.4 and 11.1.0.7.

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The article discusses using MySQL's ALTER TABLE statement to modify tables, including adding/dropping columns, renaming tables/columns, and changing column data types.

Article discusses configuring SSL/TLS encryption for MySQL, including certificate generation and verification. Main issue is using self-signed certificates' security implications.[Character count: 159]

Article discusses strategies for handling large datasets in MySQL, including partitioning, sharding, indexing, and query optimization.

Article discusses popular MySQL GUI tools like MySQL Workbench and phpMyAdmin, comparing their features and suitability for beginners and advanced users.[159 characters]

The article discusses dropping tables in MySQL using the DROP TABLE statement, emphasizing precautions and risks. It highlights that the action is irreversible without backups, detailing recovery methods and potential production environment hazards.

The article discusses creating indexes on JSON columns in various databases like PostgreSQL, MySQL, and MongoDB to enhance query performance. It explains the syntax and benefits of indexing specific JSON paths, and lists supported database systems.

Article discusses securing MySQL against SQL injection and brute-force attacks using prepared statements, input validation, and strong password policies.(159 characters)

Article discusses using foreign keys to represent relationships in databases, focusing on best practices, data integrity, and common pitfalls to avoid.
