RE: Oracle 7.3.4 problem... SLOW Drop user
- From: "Cary Millsap" <cary.millsap@xxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 4 Aug 2004 13:21:31 -0500
The break will probably take a while. The whole reason for the O(n^2)
algorithm is so that you CAN break into it without corrupting anything.
Cary Millsap
Hotsos Enterprises, Ltd.
http://www.hotsos.com
* Nullius in verba *
Upcoming events:
- Performance Diagnosis 101: 8/10 Boston, 9/14 San Francisco, 10/5 =
Charlotte
- SQL Optimization 101: 7/26 Washington DC, 8/16 Minneapolis, 9/20 =
Hartford
- Hotsos Symposium 2005: March 6-10 Dallas
- Visit www.hotsos.com for schedule details...
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx =
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Jared.Still@xxxxxxxxxxx
Sent: Wednesday, August 04, 2004 1:12 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle 7.3.4 problem... SLOW Drop user
> Jared / Everyone
>=20
> Many Thanks for the input.
> One quick question, the situation makes me nervous. Can I kill the =
drop
> session? Will the user still be there?
>=20
Yes, it may take awhile for oracle to recognize the break, as it will
be busy dropping a segment.
The user will still be there, minus some tables and whatnot.
I don't know what the internal procedures are in 7x for dropping a user,
other than what Cary just told us about.
I do know that it was not unusual for a drop user to cause an ORA-36,
which is essentially 'recursion too deep'.
Jared
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
