EVENT:10052 "Stop SMON from cleaning up obj$"

作者: Maclean Liu , post on April 19th, 2008 , English Version
【本站文章除注明转载外,均为本站原创编译】
转载请注明:文章转载自: Oracle Clinic – Maclean Liu的个人技术博客 [http://www.oracledatabase12g.com/]
本文标题: EVENT:10052 “Stop SMON from cleaning up obj$”
本文永久地址: http://www.oracledatabase12g.com/archives/event-10052-stop-smon-from-cleaning-up-obj.html

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.

© 2008 – 2011, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.

相关文章 | Related posts:

  1. EVENT:10061 disable SMON from cleaning temp segment
  2. EVENT: 10500 “turn on traces for SMON”
  3. Database Hangs Because SMON is taking 100% CPU doing transaction recovery
  4. Setting an Oracle event:The structure of the trace syntax
  5. EVENT:10210 check data block integrity
  6. EVENT:10211 check index block integrity
  7. EVENT:10228 trace application of redo by kcocbk
  8. EVENT:10226 trace CR applications of undo for data
  9. EVENT:10212 check cluster integrity
  10. EVENT:10218 dump uba of applied undo

1 comment to EVENT:10052 “Stop SMON from cleaning up obj$”

  • $cat _smon_32440.trc|grep -B2 namespace=TABL
    name=SYS.SMON_SCN_TIME
    hash=64364cd39e83bca37e6006b5672109bb timestamp=03-12-2008 00:40:22
    namespace=TABL flags=KGHP/TIM/SML/[02000000]

    name=SYS.MON_MODS$
    hash=df1bb295b5059c6267f1ab1c62b948c4 timestamp=03-12-2008 00:40:00
    namespace=TABL flags=KGHP/TIM/SML/[02000000]

    name=SYS.COL_USAGE$
    hash=424f2fc316c1e986ebd61129d2da1b83 timestamp=03-12-2008 00:40:21
    namespace=TABL flags=KGHP/TIM/SML/[02000000]

    name=SYS.FET$
    hash=ebbd04e5693db8814ccf17a96c13497e timestamp=03-12-2008 00:39:48
    namespace=TABL flags=PKP/KGHP/TIM/KEP/SML/BSO/[02900002]

    name=SYS.TS$
    hash=470fcbc62b4c96ac89843f456219060e timestamp=03-12-2008 00:39:48
    namespace=TABL flags=PKP/KGHP/TIM/KEP/SML/BSO/[02900002]

    name=SYS.TAB$
    hash=dba1f47a6c1943c58ece900e1400a489 timestamp=03-12-2008 00:39:48
    namespace=TABL flags=PKP/KGHP/TIM/KEP/SML/BSO/[02900002]

    name=SYS.USER$
    hash=bcbc05875d5d31ba1d668ecc7b18ab07 timestamp=03-12-2008 00:39:48
    namespace=TABL flags=PKP/KGHP/TIM/KEP/SML/BSO/[02900002]

Leave a Reply

  

  

  

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>