RE: Drop user fails with ORA-01418

  • From: "William B Ferguson" <wbfergus@xxxxxxxx>
  • To: chadi@xxxxxxxxxxxxxxxxxx, thomas.mercadante@xxxxxxxxxxxxxxxxx
  • Date: Tue, 16 Nov 2004 09:05:57 -0700


The BIN$... Object is a dropped trigger (it appears to be anyway), that =
in the recycle bin, and apparently the drop user statement seems to be
having trouble deleting the user with an associated object in the =

To try and get around it, try going the web-enable enterprise manager, =
administration page, then Tables (or actaully any object), filter for =
owner of the object, the the recycle bin button appears. Or, from the =
prompt, you can do a "purge dba_recyclebin;" (to empty the recycle bin =
all users, or connect as the user and issue a "purge recyclebin;".

I think this will get around the problem you are experiencing.

Bill Ferguson
U.S. Geological Survey - Minerals Information Team
PO Box 25046, MS-750
Denver, Colorado 80225
Voice (303)236-8747 ext. 321 Fax (303)236-4208

~ Think on a grand scale, start to implement on a small scale ~

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx =
On Behalf Of chadi@xxxxxxxxxxxxxxxxxx
Sent: Tuesday, November 16, 2004 8:32 AM
To: 'Mercadante, Thomas F'
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: Drop user fails with ORA-01418

Actually, this is my problem. I couldn't drop some objects in the user, =
i decided to rebuild the user and still stuck with this:

the trace is shwoning that some trigger is causing the ora600:

ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [15239], [], [], [], [], [],
[], [] Current SQL statement for this session: drop trigger


-----Original Message-----
From: Mercadante, Thomas F [mailto:thomas.mercadante@xxxxxxxxxxxxxxxxx]
Sent: Tuesday, November 16, 2004 10:24 AM
To: 'chadi@xxxxxxxxxxxxxxxxxx'; oracle-l@xxxxxxxxxxxxx
Subject: RE: Drop user fails with ORA-01418


Did the user get dropped?

If not, can you go through and drop the users objects manually?  And =
drop the user?  It is obviously an Oracle problem.  But if you can find =
workaround, then you can chalk it up to experience.

Personally, I do not drop a user that has a bunch of objects.  I prefer =
drop all the objects first and then the user just for this reason.

Hope this helps.

Tom Mercadante
Oracle Certified Professional

-----Original Message-----
From: Chadi Kassan [mailto:chadi@xxxxxxxxxxxxxxxxxx]=20
Sent: Tuesday, November 16, 2004 10:01 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Drop user fails with ORA-01418

Hi everyone,

I'm pretty sure, many had run into this problem before and can provide
some help. When I try to drop one of my user, I get the following:

SQL> drop user theuser cascade;

ORA-00604: error occurred at recursive SQL level 1
ORA-01418: specified index does not exist

What index it's talking about, metalink says this is related to some =
corruption in data dictionnary, but doesn't provide a solution.

We run Oracle Database 10g Release on Linux.

Thank you.

Other related posts: