Re: temp tablespace questions....

This is too funny, I'd been working out the syntax in the back of my mind for years now.

DROP USER FOOFOO; DROP USER FOOFOO CASCADE; DROP USER FOOFOO CASCADE
    WITH EXTREME PREJUDICE; DROP USER FOOFOO CASCADE

     WITH EXTREME PREJUDICE CASCADE TO BOSS
      AND WITH DETACH THE HORSE HE RODE INTO TOWN ON NOWAIT;

DROP USER FOOFOO CASCADE
    WITH EXTREME PREJUDICE
    WITH KILL THE HORSE OPTION

     WITH NOTIFY ALL DBA PEOPLE EVERYWHERE TO PROHIBIT NEW ID
     NOWAIT;

It is quite aggravating. I'd fry anyone that had TEMP all tied up in knots. Normal, if you are merciless in killing -9 anything to do with the miscreant the TEMP resources should be released.

RSH. "Billy Verreynne" <vslabs_at_onwe.co.za> wrote in message news:3c846633.319999515_at_news.saix.net...
> cmercer_at_vibrant-1.com (Carl Mercer) wrote:
>
> >I have a 9.0.1.2.0 instance that has a temporary tablespace (duh...).
> >The tablespace was created as follows:
> >
> >CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE
> >'/dev_tools/oracle/product/oradata/PRODDB/sys3/temp01.dbf'
> >SIZE 50M REUSE AUTOEXTEND ON NEXT 100M MAXSIZE UNLIMITED
> >EXTENT MANAGEMENT LOCAL;
>
> I would not recommend using auto and unlimited extents on temp. This
> is just an invite to some silly developer or user to pull one of them
> infinite running disk crashing queries-from-hell on the database,
> doing cartesians joins and using perverted S&M SQL (like doing the
> TO_CHAR on the date colum in the WHERE clause and not using the
> TO_DATE on the literal instead).
>
> Don't you also at times wish that there is an optional WITH ASSASINATE
> parameter for the DROP USER statement? :-)
>
> --
> Billy
>
Received on Tue Mar 05 2002 - 01:46:30 CST