EVENT:10052 "Stop SMON from cleaning up obj$"
Text: Stop SMON from cleaning up obj$
-------------------------------------------------------------------------------
NOTE:
Events should NEVER be set by customers unless advised to do so by
Oracle Support Services. You must read <Note:75713.1> before setting ANY
event on a system.
Usage:
~~~~~~
To disable cleanup of OBJ$ by SMON set this event in the init.ora file
thus:
EVENT="10052 trace name context forever"
Explanation:
~~~~~~~~~~~~
Setting event 10052 stops SMON trying to clean up OBJ$.
The implication of this is that OBJ$ will grow with entries for
non-existent objects, eg: objects which have been dropped and
object entries created for negative dependency reasons.
The usual reason for setting this event is to prevent SMON from
crashing / spinning in the OBJ$ cleanup code whilst diagnostics
or further investigations are performed. It is also sometimes
used in Parallel Server environments so that OBJ$ cleanup is
only performed on selected nodes.
@ The routine it disables is <Function:kqlclo> (KQL Clean Obj$) which scans
@ obj$ for objects marked as non-existent and then deletes them if
@ they are not child dependencies of anything.
posted on 2013-03-19 00:32 Oracle和MySQL 阅读(145) 评论(0) 编辑 收藏 举报