RE: smon locked sys.fet$ on oracle 816 (unix)

We ended up recovering a database after having dropped a dictionary managed index with over 400,000 extents- smon went out to lunch and the instance ended up becoming unusable. (Yeah - don't know how our monitoring missed the index growing that big...) In any event, the way we got around this problem was to convert the tabelspace to locally managed and then drop the object. As LMTS, the objects go away very quickly - and the conversion from dictionary to locally managed is very fast - so why does it take so long to drop as dictionary managed? That is Oracle for you...

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mayen.Shah_at_lazard.com
Sent: Tuesday, April 17, 2007 9:58 AM
To: Ujang Jaenudin
Cc: oracle-l_at_freelists.org; oracle-l-bounce_at_freelists.org Subject: Re: smon locked sys.fet$ on oracle 816 (unix)

Most probably SMON is coalescing free extents after that truncate. This will be
the case if you are not using LMT (I do not know if you are using LMT or not).
If you are not using LMT and SMON is holding ST lock, you may set event no :
10269 (please confirm with Oracle support) to skip coalescing by SMON. Coalesce
manually when database is not loaded and please convert to LMT.

Good luck.
Mayen Shah      

    "Ujang Jaenudin"
To

    <ujang.jaenudin_at_g Mayen Shah/ITS/Lazard_at_Lazard NYC

    mail.com>
cc

                              oracle-l_at_freelists.org,

    Apr 17 2007 09:53         oracle-l-bounce_at_freelists.org

    AM
Subject

                              Re: smon locked sys.fet$ on oracle 816
(unix)     
 

 

ST

On 4/17/07, Mayen.Shah_at_lazard.com <Mayen.Shah_at_lazard.com> wrote:
>
> Hi Ujang,
>
> What type of lock SMON is holding? Do you use LMT?
>
> Mayen Shah
>

--
http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l