凌晨时分,帮一客户关闭数据库。在关闭实例阶段,alert显示
错误很明确了, LibraryCacheNotEmptyOnClose内存在实例关闭时,没有释放。估计是bug引起的,并不会引起数据库的不一致。经查metalink,偶然验证了我的判断。以下是matalink的说明:
引用
Fri May 14 01:08:49 2010
System State dumped to trace file /u01/app/oracle/oracle/product/10.2.0/db_2/admin/HIS3/udump/his3_ora_634882.trc
Fri May 14 01:08:49 2010
Errors in file /u01/app/oracle/oracle/product/10.2.0 _2/admin/HIS3/udump/his3_ora_634882.trc:
ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []
System State dumped to trace file /u01/app/oracle/oracle/product/10.2.0/db_2/admin/HIS3/udump/his3_ora_634882.trc
Fri May 14 01:08:49 2010
Errors in file /u01/app/oracle/oracle/product/10.2.0 _2/admin/HIS3/udump/his3_ora_634882.trc:
ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []
错误很明确了, LibraryCacheNotEmptyOnClose内存在实例关闭时,没有释放。估计是bug引起的,并不会引起数据库的不一致。经查metalink,偶然验证了我的判断。以下是matalink的说明:
引用
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 - Release: 10.2 to 10.2
Information in this document applies to any platform.
Symptoms
o ORA-600 [LibraryCacheNotEmptyOnClose] is reported in the alert.log on shutdown.
The trace file shows 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.
Cause
This is due to unpublished Bug 4483084 'ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE]'
This is a bug in that an ORA-600 error is reported when it is found that something is still going on during shutdown. It does not indicate any damage or a problem in the system.
Solution
This problem 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.
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 - Release: 10.2 to 10.2
Information in this document applies to any platform.
Symptoms
o ORA-600 [LibraryCacheNotEmptyOnClose] is reported in the alert.log on shutdown.
The trace file shows 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.
Cause
This is due to unpublished Bug 4483084 'ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE]'
This is a bug in that an ORA-600 error is reported when it is found that something is still going on during shutdown. It does not indicate any damage or a problem in the system.
Solution
This problem 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.